Navigating the mess
The app was reliant on multiple third-part APIs for different datasets
With a firm deadline tied to upcoming race seasons, we had to prioritize flows that could reliably ship within the technical limitations of this phase
NYRR 2.0 focused on unifying all race content into one consistent mobile experience. We established the core information architecture, redesigned tracking and results, and built the initial design system. Because of API limitations and a tight race-season timeline, this phase prioritized stability, clarity, and flows that could reliably ship without personalized dataship without personalized data
With the 2.0 foundation in place, 2.5 expands the platform into a more personalized, community-driven experience. This phase introduces login, saved races, deeper results history, donations, and new engagement modules—features that weren’t feasible earlier due to API and legal constraints. 2.5 builds on the structure of 2.0 to support year-round use, not just race-week interactions.
We partnered closely with the development team, maintaining constant communication and collaboration. By understanding development limitations early, we planned phased design releases that aligned with their sprint cycles, ensuring design updates stayed in sync with development and keeping the project on track for a successful launch.