Inspiration
When I first arrived in New York City as an international student, I quickly realized that navigating an unfamiliar city is not only about getting somewhere quickly, but also about feeling safe along the way. One night, I followed Google Maps to a theater using the fastest route it suggested. During a transfer, I suddenly felt very uncomfortable. People on the street were staring at me, and a stranger approached me in a way that felt threatening. I was extremely scared. Later that night, I searched online and found that the area I passed through had a high rate of gun violence. That experience made me realize that most navigation tools today focus almost entirely on speed. They rarely consider how safe a route might feel, especially for newcomers, students, or anyone traveling alone at night. After talking with friends and local residents, I learned that this need is widely shared. Many people want more safety context when navigating places they do not know well.
This experience inspired us to build WaySafe.
What We Built
WaySafe is a navigation tool that helps users choose routes based on how safe they feel, not just how fast they arrive. Instead of showing only the fastest option, WaySafe analyzes historical crime data and combines it with the user’s personal preference between safety and speed. Based on these factors, WaySafe evaluates multiple route options and ranks the top three routes using a composite score that reflects overall suitability. For each route, WaySafe also provides a safety score to help users understand the relative safety level of that option, along with estimated travel time and a short explanation of why the route was selected.
How We Built It
To use WaySafe, users enter their starting point and destination. They then adjust a comfort slider to indicate how much they want to prioritize safety versus speed. After clicking the Find Routes button, the system evaluates possible routes using weighted factors based on the user’s preference and historical crime data along each path. WaySafe presents the top three recommended routes ranked by a composite score. Each route also includes an estimated travel time and a safety score for reference. When users select a route, the map highlights that route while an expanded panel appears nearby. This expanded view provides more detailed information, including a brief safety summary, key risk factors inferred from historical data, and practical safety tips. The map and the detail panel update together so users can clearly connect the information with the route’s spatial context.
Challenges we ran into
One challenge was working with historical crime data alone. Translating aggregated data into route level insights that are easy to understand, while still being meaningful, required several design and modeling iterations. Time constraints were also a challenge. As with many hackathon projects, we had to prioritize core functionality and focus on delivering a clear and coherent user experience.
Accomplishments that we're proud of
We are proud that we were able to turn a personal and emotional experience into a concrete, working product idea within a short time frame. WaySafe goes beyond traditional navigation by introducing safety as a first class factor in route selection. Instead of treating safety as an afterthought, we designed a system where users can actively express their comfort level and see how that preference changes route recommendations. We are also proud of the clarity of the user experience. The combination of a simple input flow, clear route ranking, safety scores, and an expandable detail view allows users to understand both the recommendation and the reasoning behind it. This transparency was an important design goal for our team.
What we learned
Through building WaySafe, we learned that safety is not a binary concept. People rarely need a route to be labeled simply as safe or unsafe. What they really want is context, comparison, and control. We also learned the importance of honest design. When working with historical crime data, it is critical to communicate uncertainty and tradeoffs clearly, without overstating conclusions or creating unnecessary fear.
What's next for WaySafe
If we continue developing WaySafe, we would like to expand the scope of safety signals while remaining responsible and transparent about data sources. Future directions include incorporating time of day effects more deeply, improving the granularity of safety scoring, and adapting the system to different cities with varying data availability. We also see potential in refining the interface based on user feedback, especially around how safety information is explained and personalized. Ultimately, our goal is to make WaySafe a tool that helps people feel more confident and in control when navigating unfamiliar environments.
Built With
- api
- css.react
- javascript
- python
- react.js
- typescript
Log in or sign up for Devpost to join the conversation.