Wayk | Devpost

Inspiration

When walking in a metropolitan environment, getting lost is common. Popular map apps do not have the pedestrian in mind. Road obstruction are common and often go unreported.

What it does

Wayk uses crowdsourced information about obstructions to inform the user about bad sidewalks, construction, car accidents and more. It also uses a gemini endpoint to validate the crowdsourced information so that we are resistant to faulty information.

How we built it

We used React-native with the expo framework to display to the user, We used the Open Street Maps API to display the map and create paths. We also used a Gemini Endpoint for obstacle validation.

Challenges we ran into

Accuracy of Data: Ensuring the reliability of crowdsourced data was challenging, especially in densely populated areas where false or outdated information could clutter the map. Building the Gemini endpoint to validate data in near real-time was a solution, but configuring it to handle such rapid updates was a hurdle. Battery Optimization: Managing battery usage while running real-time location and obstacle updates was another challenge, as frequent GPS polling can quickly drain a device’s battery. We had to fine-tune our app to balance location accuracy with battery efficiency. Integrating OpenStreetMap API: Integrating OpenStreetMap with React Native through the Expo framework presented some compatibility issues. OpenStreetMap is highly customizable but required careful setup to render accurately on mobile.

Accomplishments that we're proud of

Successful Crowdsourcing Validation System: Developing a validation system for crowdsourced data is something we’re proud of, as it gives users more reliable information and limits false reporting. Cross-platform App with Real-time Updates: Building a React Native app that can operate smoothly on both iOS and Android while handling live updates was a technical win. The app remains responsive, even with data-intensive updates. Community Engagement: Wayk’s potential for community engagement is exciting. Users have the opportunity to contribute to safer, more accessible pedestrian navigation in their city.

What we learned

What we learned Working with Map Data: Using OpenStreetMap exposed us to the complexities and benefits of open-source map data. We learned to customize map layers and use map data more creatively for the needs of pedestrians. Data Validation Techniques: Implementing data validation through a Gemini endpoint was a learning experience in ensuring data reliability while managing the app’s performance. This has given us new insights into managing crowdsourced data in a scalable way. React Native and Battery Management: React Native was useful for development speed, but we also learned techniques for managing battery-intensive features, which will be valuable for future mobile projects.

What's next for Wayk

Improved Obstacle Reporting: Adding features to allow users to upload images or give detailed descriptions of obstructions would make the data even more valuable. Enhanced Validation with Machine Learning: Introducing a machine learning model to analyze crowdsourced data, along with location history and user activity, could help detect anomalies and further improve validation. Accessibility Features: Adding features for those with mobility challenges, like wheelchair-accessible routes and auditory guidance, would expand Wayk’s value. Local Government Partnerships: Collaborating with city agencies could help report and resolve obstructions more effectively, making Wayk not only a navigation tool but also a community resource for pedestrian safety.