Why a generic utility map loses to an athlete-first lifeline.
| Dimension | Generic Utilities (e.g. Aquafinder) | Athlete-First Model (Your App) |
|---|---|---|
| Primary Use Case | Tourists refilling Hydroflasks in cities. | Marathoners avoiding dehydration at Mile 16 on a greenway. |
| Data Source | ✖ Static API scrapes (OpenStreetMap). Highly inaccurate. | ✔ Crowdsourced / Community-verified by local run clubs. |
| Real-Time Status | ✖ None. Assumes a pin = water. | ✔ Live toggles: "Flowing," "Broken," "Winterized (Off)." |
| User Interface (UX) | Pan and zoom map interface. Requires two hands and stopping. | High-contrast, large-touch targets. One-tap "Nearest Working Water" compass view. |
| Trust Model | Anonymous internet data. | "Verified working 3 hrs ago by East Nasty Runner." |
| Greenway Density | ✖ Poor. Relies on municipal data which ignores hidden park taps. | ✔ High. Mapped manually by the exact people who run the routes. |
Aquafinder is a directory. You are building a survival tool. If an athlete runs a mile off-route for an Aquafinder pin and the fountain is shut off for winter, they will delete the app immediately. Real-time verification is your entire moat.