D2S Running Race Event Organizer · Engineering Case Study
D2S Running Race Event Organizer — Engineering Case Study
How a client and partner running-race event organizer was engineered across Android, PHP backend/API, database, Strava integration, and race-result web, with deployment and hosting.
D2S Running Race Event Organizer is a client and partner project for organizing running races. Herry’s contributions span the full system: product and workflow design, architecture, the Android application, the PHP backend and API, the database, Strava integration, race-result website functionality, and deployment and hosting. Testing was collaborative with other testers; Herry did not perform all testing alone. The system is currently in internal beta testing, and the source code remains private.
Project context
D2S is a sports and running domain product built as a client and partner engagement. The system spans Android, backend, and web surfaces, and Herry contributed across all of them, which made the engagement end-to-end rather than scoped to one layer.
Because the source code is private, this case study focuses on engineering surfaces, contributions, and decisions rather than implementation details that cannot be disclosed.
Problem and product context
Organizing a running race event through D2S involves several system surfaces: an Android application, a PHP backend and API, a database, Strava integration, and a race-result website. These components needed to form one coherent product rather than remain disconnected pieces.
The engineering scope Herry contributed to was building that coherence: the Android app, the PHP backend and API, the database, the Strava integration, and the race-result web all formed parts of the same D2S product.
Product and workflow design
Herry contributed to product and workflow design for D2S, helping shape how the product supports the workflow of organizing a running race event across its Android, backend, and web surfaces.
System architecture
Herry contributed to the system architecture. The architecture spans three platforms — Android, backend, and web — with the Android application, the PHP backend and API, the database, Strava integration, and the race-result website forming parts of the same D2S product.
Android application
Herry contributed to the Android application, one of the platform surfaces of D2S alongside the backend and web.
Backend API and database
Herry contributed to the PHP backend and API, along with the database. PHP is the established technology for the backend, and the database underpins the system’s data.
Strava integration
Herry contributed to the Strava integration, built on the Strava API. Strava is an external running platform, and the integration introduced a third-party integration boundary into the D2S system.
Race-result web
Herry contributed to race-result website functionality, the web portion of the D2S system that presents race results.
Deployment and hosting
Herry contributed to deployment and hosting for the system, covering the backend, the API, and the race-result website.
Testing and collaboration
Testing was collaborative. Herry worked alongside other testers to validate the system. He did not perform all testing alone, and the testing effort was shared across the team rather than owned by a single person.
Current state and engineering takeaways
D2S remains in internal beta testing. It is not presented as a publicly released product.
Herry’s contribution spanned engineering surfaces across mobile, backend, and web: product and workflow design, architecture, Android, PHP backend and API, database, Strava integration, race-result web, deployment and hosting, and collaborative testing. The case study complements the Product Overview, which describes what the product is, while this narrative describes how Herry contributed to engineering the system across its surfaces.