SAFETYBIT was born out of the need to create a safer environment for joggers at night.
What it does
SAFETYBIT extracts latitude and longitude coordinates from the GPS in Fitbit Ionic. We then use reverse-Geocoding to convert those coordinates into a physical address that is sent out as an alert on an app when the 'Emergency' button on the Fitbit is pressed.
How we built it
Challenges we ran into
The Fitbit's GPS does not work well indoors, which is why we had to resolve to the Fitbit OS Simulator to test our program, although we did connect our phone to it. We had trouble transfering the GPS data from the Fitbit app to the Android Studio app because Fitbit needs to authenticate third-party apps before giving them permission to access data from the Fitbit, which we did not have time for.
Accomplishments that we're proud of
We have never worked with Fitbit and their SDK. Two of us had no experience with Android Studio before, so we learned a lot. We navigated challenges and many trials well as a team.
What we learned
We learned that it is probably best to fully learn about a new technology before starting a project based on it. Also, we learned that some companies are very restrictive with their data privacy, even though we were given access to a Fitbit to develop on.
What's next for SAFETYBIT
We will wait for Fitbit's approval of our app, and if approved, pass data from the device to our app to get it running. We also need a more specific address to match the coordinates collected. And then we can use Google's Nearby API broadcasts alerts to all nearby devices.
Log in or sign up for Devpost to join the conversation.