Existing product to iOS and Android
You already have a web product, SaaS product or API and need to bring it properly to iOS and Android.
Senior mobile engineer · UK
Hands-on mobile engineering for existing products.
I help product teams ship difficult iOS and Android work across native apps, Kotlin Multiplatform and the APIs behind them, from technical discovery through delivery and release.
Native iOS depth Production Android and KMP experience App Store delivery
When I’m useful
The product exists. The hard part needs an owner.
Cross-platform feature
A difficult feature crosses iOS, Android, shared code or backend boundaries and needs one experienced owner.
KMP and iOS friction
Kotlin Multiplatform is working technically, but awkward APIs or workflows are slowing down the iOS team.
Delivery or release problem
An inherited codebase, integration or store milestone needs a clear route from the current state to release.
Work
Selected work
Public work shown with its real constraints, ownership and outcome. Technology sits in the supporting detail.
Dee
Muay Thai training planner and workout companion for iPhone and iPad
- Problem
- Make personalised training useful in the gym, where connectivity, attention, and time are limited, without requiring another account or making a remote service the centre of the experience.
- Ownership
- Product direction and interaction design, iPhone and iPad implementation, Training-plan generation and workout guidance.
- Outcome
- A released App Store product for iPhone and iPad that combines generated plans, offline workouts, private sync, and accessible in-session feedback in one coherent experience.
Ways to work together
A bounded route from unclear to shipped.
Start with a technical discovery when the risks are unclear, or a delivery sprint when the outcome is already defined.
Mobile Technical Discovery
Turn an unclear mobile milestone into a concrete technical and delivery plan.
See the engagementMobile Delivery Sprint
Own a defined feature, integration or release milestone through to a shipped outcome.
See the engagementiOS / Kotlin Multiplatform Support
Improve the iOS side of an existing or actively adopting Kotlin Multiplatform codebase.
Explore iOS and KMP supportSpecialist support
Make Kotlin Multiplatform work properly for your iOS team.
Improve Swift-facing APIs, shared and native boundaries, SwiftUI integration, testing, the Xcode and Gradle workflow, and the release path. The goal is not to force more code into the shared layer. It is to make the whole product easier for the team to build and ship.
Explore iOS and KMP supportAbout
A mobile engineer who stays close to delivery.
I’m Noam, a UK-based senior mobile engineer. My background is deepest in iOS, with production work across Android and Kotlin Multiplatform, plus the API, testing and release systems around the apps.
I write practical technical guides because explaining a system clearly is part of building it well. The same approach carries into consulting: understand the constraints, make the useful decision, then do the work.
More about how I workWriting
Engineering notes from the work.
Mobile engineering
Swift Devs: Should You Use Skip or Kotlin Multiplatform?
Which one is better for you?
GitHub Actions to TestFlight - from zero to hero
Auto-Deploy to TestFlight via GitHub Actions Tag
The holy grail - automatic TestFlight deployment when you tag with "testflight"
iOS tooling
Delete Dead Swift Code Safely Using Periphery
Safely delete dead Swift code with one script (and a verification pass)
Start with the current state
What exists today, and what needs to ship?
Send a short note about the product, the blocked milestone and the timeframe. I’ll reply with a few focused questions and, if it’s a good fit, suggest the most useful next step.