First iteration of this project (March 2019): I made a search app where the user can enter a term and the NASA API will present a list of results on cards.
I was learning about components, state and props before this project and the hardest parts of building this as my first React app were: the container component and how the components all relate to each other through it, and creating the cards through mapping the images in the search state.
This was challenging because to handle the errors where a field in the json was empty, I needed to gracefully still show something. I decided to have a default image shown in case of no image results. I also needed to let the user know when their search term didn't return anything.
I will make a game where a user is presented with two images from the NASA API and they pick the correct one matching the name they see.
I will make a game where a description of the object is given and the image of some items and the user has to match the image and description.
Another idea: a game where four objects are given, and they are two matching sets. The user has to match the items with each other.
The challenge here is going to be position randomization.
This project was bootstrapped with Create React App.
In the project directory first install all dependencies:
Then 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