Create an application to buy food from a restaurant, check how long it will take to be ready and a map of how to get your feed.
- The user must have a login view.
- After logged in it should see a list of restaurants.
- When accessing a restaurant it should see the menu with pictures, names, descriptions and prices of each product.
- The user should be able to add a product to its cart.
- A product could be multiple times in the cart.
- When leaving the restaurant to another restaurant or the list it should previously confirm with the user.
- If the user confirms it should clear the cart.
- If the user doesn't confirm it shouldn't leave the restaurant.
- After the user finish picking its food the should be able to request it.
- When the user create an order it should see a map with the location of the restaurant.
- In the map it should also see the user location and keep listening for movements.
- It must use semantic HTML
- It must use React
- It must be Responsive
- It must use CSS in JS
- It must have tests
- Snapshot tests
- Behavior tests
- It must use Reach Router
- It could use Reach UI components
- It must use Redux
- It must be a Progressive Web App
- It must pass with green the Performance tests of the Chrome Audits
- It must pass with green the Accessibility tests of the Chrome Audits
- It must pass with green the Best Practices tests of the Chrome Audits
- It must pass with green the SEO tests of the Chrome Audits
- It must pass with green the PWA tests of the Chrome Audits
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify