
Ticket
Navigation · live since 2 September 2026
You park, you tap a duration. That is all.
Eight apps on the App Store, four with native Swift modules
Live Activities, the Dynamic Island, App Intents, widgets, a Watch companion. None of them have a JavaScript equivalent, and that is usually where a project stalls. I write the Swift, bridge it properly, and ship it through App Review. AI agents speed up the work; I scope them, and I sign off on every change.
Remote from France · CET: same hours as London plus one, four hours of overlap with New York
The short version
Most React Native work stops where iOS begins. Live Activities, the Dynamic Island, App Intents, widgets, a Watch companion: none of them have a JavaScript equivalent, and that is usually where a project stalls. I write the Swift, wire it to the React Native side, and ship it through App Review. Twice I decided the bridge was not worth paying for, and wrote the whole app in Swift.
Why me
Plenty of developers write code. The work really starts when it has to reach somebody's phone.
Six of my published apps contain Swift I wrote, and two are written in Swift from top to bottom: ActivityKit for Live Activities, App Intents for Siri and the Control Center, WidgetKit, SwiftData, a SwiftUI Watch app. That is the part most React Native teams outsource or abandon.
Signing, privacy questionnaire, screenshots, rejections and the replies that get them overturned. The gap between a working build and a live app is a job of its own, and it is where most projects stop.
A flight computer that makes no network calls, ever. A parking timer in 3.3 MB driving the Dynamic Island. A pet health record you can verify in airplane mode. The constraint is decided before the first line of code.
Invoicing from France, one hour ahead of London, four hours of overlap with New York. No visa question, no agency in between, no intermediary reading your brief before I do.
The proof
A parking timer living in the Dynamic Island. A prayer app with a SwiftUI Watch companion and a Live Activity. A flight computer that makes no network call, ever.
What I take on
Live Activities and the Dynamic Island, App Intents for Siri and the Control Center, home screen widgets, a Watch companion, NFC. Written in Swift, bridged properly, shipped.
An independent read of your React Native codebase: architecture, performance, technical debt and App Store risk. A written report ordered by priority, with an effort estimate per item.
An app someone else started and left. I find out what is really there, what it costs to finish, and whether finishing is the right call. Sometimes it is not, and I say so.
Repeated rejections, a privacy questionnaire that contradicts the binary, a build that will not sign. These are known problems with known fixes.
Working with someone in France
A stalled project, a native feature you can't get working, a codebase somebody left behind. I reply within a day, and I say so when it isn't for me.