Olly
A native iOS fertility-care companion, taken to its first App Store launch in about three months.
I moved from Android into native iOS and owned Olly's first App Store launch in about three months, working in a five-person international team. Over roughly five months overall, I delivered connected fertility-care workflows through 10+ builds including TestFlight and owned production releases.
Project evidence
- ~3 months
- to first App Store launchWithin an overall delivery period of roughly five months.
- 5 people
- international product teamTwo frontend engineers, two backend engineers, and a technical lead.
- 3
- product languagesEnglish, French, and Spanish.
- 10+ builds
- delivery including TestFlightDevelopment and release builds, with ongoing production delivery after launch.
01 / Adaptability and ownership
Move into native iOS and own the first launch.
I moved from production Android engineering into native iOS before adopting AI-assisted development, and owned Olly's client from architecture through its first App Store release. I reached that first launch in about three months, within roughly five months of overall delivery and 10+ builds including TestFlight.
Olly supports people navigating assisted reproduction and IVF. I worked in a five-person international team with another frontend engineer, two backend engineers, and a technical lead, taking responsibility for the native workflows and their release behavior.
02 / The product surface
Make connected care workflows feel like one journey.
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.
I structured the SwiftUI/UIKit client around reusable state and concurrency boundaries because medication schedules, appointments, records, documents, and alerts could change independently. That architecture kept partial loading, updates, and navigation coherent across the connected care journey.
System model
A connected fertility-care journey
The client coordinates multiple sensitive workflows against API-driven state from onboarding through ongoing care.
Shared state with connected care flows
- 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
Connections
- OnboardingFertility journey
- Fertility journeyCare schedule
- Care scheduleHealth records
- Apple HealthFertility journey
- Shared API stateOnboarding
- Shared API stateCare schedule
- Shared API stateHealth records
03 / Sustained delivery
Connect native platform integration with production delivery.
I used Swift Concurrency, reusable SwiftUI/UIKit architecture, and REST integrations to build the native client. My delivery included Apple Health-connected fertility tracking and care workflows localized in English, French, and Spanish.
I owned App Store launch and ongoing production releases as the client evolved. The production product was promoted at CES 2024, with my contribution focused on the native iOS experience and its delivery.
Discuss the work
Bring me the next product problem.
I bring product judgment, hands-on leadership, and the engineering depth to take an important problem from the first decision through release. Let’s talk about what you want to build or improve.
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.