-
Final product with CSS
-
while (inside the geofence) {return Alive;}
-
An example of a geofence we tested.
We started off with many ideas of how to use Radar.io's geofences. But the more we became familiar with the control panel dashboard, the more we realized our ideas were not possible. First, we thought of a biking path enclosed by a perimeter, and wanted to obtain time elapsed based on how long the user stays inside. However, the minimum radius we could have for a circular geofence was 50 meters, which is much larger than the building our hackathon used for hacking rooms. We ended up spending more than 5 hours brainstorming applications of geofences, and even looked into other sponsored challenges. We decided to stick with our original idea, but instead have users generate geofences if they choose to 'fight' each other for whatever reason. If the user steps out of the ring, they forfeit the match and lose. Mini-Arena was born as an idea for a new type of minigame such as laser tag.
Our vision was to have a website with google maps showcasing geofences working in real-time (people walking in and out). However, after purchasing the free domain, we did not know how to host it. We also struggled with coding because we're quite new to using React.
Note: You'd need to download the phone app 'Radar Toolkit' and enter an API key to use this React web app.
This project was bootstrapped with Create React App.
Available Scripts
In the project directory, you can run:
npm start
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.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
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.
npm run eject
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.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
Code Splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
Analyzing the Bundle Size
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
Making a Progressive Web App
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
Advanced Configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
Deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
npm run build fails to minify
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify
Log in or sign up for Devpost to join the conversation.