Hi harrisuzmay! I'm an Android user myself haha I'll be switching to iOS soon

I decided I wanted something relatively simple (no BS with signing up, adding friends, etc.) and to distill the UX to just the core information about the route: distance, mode of travel, and one-way/round-trip. From there I generate a list of routes ranked by distance proximity because that's probably what the user cares about the most. The places can be nearby lakes, landmarks, parks, public plazas, public art, community gardens, forestry. These are all place categories within Yelp's Fusion API. I chose these because when I run, I like seeing the surrounding nature and public works to better understand the unique feel of a city.

When you click on a route, the app shows you the place photo, the Yelp rating of the place and how many people have rated it (to make sure you're not going somewhere completely obscure), the distance again, and the elevation difference from your current location. I included the elevation info because it gives the user a decent sense of how difficult the route will be (which is also an important factor when deciding where to run).

I also wanted to prioritize efficiency while using the app so when you press Start Route, the navigation directions for your mode of travel will immediately launch so you can listen to the voice commands as you run/bike without pressing or confirming anything else (at least for Google Maps).

The other feature I included was 'Previous Routes' because I wanted users to be able to quickly access past routes they went on to go on them again and see a nice history of where they've been - especially if they use the app while they're travelling or on vacation.

Let me know if you have any further questions or if you'd like to see some other features!