Inspiration
We built Swimly to help people avoid wasting time driving to the beach only to find bad swimming conditions. We've heard stories of people taking the time to visit these beaches only to turn back because the water was too cold or the tide was unsafe. We wanted to make it easier for people to check real-time conditions before they make their trip to the beach.
What it does
Swimly analyzes real-time water level, tide prediction, and water temperature data from the NOAA APIs. The user can enter a station number and based on the values it spits out, it will recommend whether it's a good day to swim.
How we built it
We built the frontend using HTML, CSS, and JavaScript and built the backend using Python and Flask.
Challenges we ran into
A challenge we faced was finding the right APIs that provided enough useful data and whether they allowed us to use it. Another was setting them up remotely for easier use for our users.
Accomplishments that we're proud of
We're proud that we've completed a functioning live website that helps users make helpful decisions based on real-world data. We're also happy with the design of the website and that we didn't have to do another idea because of API issues.
What we learned
We learned how to structure API calls, parse and filter the real-time environmental data and be able to present it clearly. We also got a better understanding of backend-to-frontend data calls.
What's next for Swimly
We like to have our search station set up on our website rather than sending our users elsewhere to find those outside of California. In addition, we would like to add more features that could help the user decide if today's a safe day to swim. Whether that be the marine life that lives there or any construction or events taking place there.
Log in or sign up for Devpost to join the conversation.