Olly
0→1 native iOS delivery for a sensitive fertility-care journey.
A production ART/IVF companion promoted at CES 2024. As one of two frontend engineers in a five-person international product team, I owned the native iOS client from 0→1 through App Store launch and ongoing delivery, working with two backend engineers and a technical lead.
Project evidence
- 0→1
- native iOS delivery
- 5 people
- international product teamTwo frontend engineers, two backend engineers, and a technical lead.
- 3
- product languagesEnglish, French, and Spanish.
- CES 2024
- product promotion
Ownership in context
A broad client role inside a deliberately small team.
I was one of two frontend engineers in a five-person international product team, alongside two backend engineers and a technical lead. I owned 0→1 delivery of the native iOS client through App Store launch and continued production releases.
That meant making product and client-architecture decisions while coordinating API-driven state and release behavior with the rest of the team. It was end-to-end iOS ownership, not sole ownership of the overall product.
The product surface
Healthcare journeys are long, stateful, and unforgiving of ambiguity.
I built multi-step workflows for medication and appointment tracking, fertility journeys, medical histories, blood tests, questionnaires, document upload, preview and sharing, onboarding, and alerts.
Each flow had to translate API-driven state into a clear native experience across a sensitive domain where partial progress and recovery mattered.
System map
A connected fertility-care journey
The client coordinates multiple sensitive workflows against API-driven state while keeping the user oriented from onboarding through ongoing care.
- 01Onboarding
Initial state and care context
- 02Fertility journey
Treatment and progress flows
- 03Care schedule
Medication · appointments · alerts
- 04Health records
History · tests · questionnaires · documents
- 05Apple Health
Connected fertility tracking
- 06Shared API state
REST-backed product state and recovery
- Onboarding connects to Fertility journey.
- Fertility journey connects to Care schedule.
- Care schedule connects to Health records.
- Apple Health connects to Fertility journey.
- Shared API state connects to Onboarding.
- Shared API state connects to Care schedule.
- Shared API state connects to Health records.
Sustained delivery
Launch was the beginning of the engineering work.
The SwiftUI/UIKit client evolved through sustained releases using Swift Concurrency, reusable UI architecture, and REST integrations. I added Apple Health-connected fertility tracking as the product expanded.
Localization across English, French, and Spanish extended those workflows without separating them into divergent product implementations.
Proprietary production code
About the source code.
The source code is proprietary to Shuru Technologies. I can discuss my responsibilities, architecture, testing strategy, technical decisions, trade-offs, and outcomes without disclosing confidential material.