How I work.

I am Nadir Ben Salah. I build mobile apps from Amiens, in northern France, and I have been doing this kind of work for about ten years.

What a year of publishing taught me

In September 2025 I put my first app on the App Store. It was a party game, and honestly there is nothing remarkable about it. What it taught me does not exist in any tutorial: the developer account, signing, certificates, the listing, the screenshots, the privacy questionnaire, and above all what App Review actually looks at.

The other seven came out roughly a year later, between 7 August and 2 September 2026, after eleven months of building them in parallel. Each one was chosen to force a constraint the previous ones had not. A flight computer that must make no network call at all, because there is no signal in a cockpit. A parking timer that has to live in the Dynamic Island, so Swift, and fit in 3.3 MB. A pet health record you can verify in airplane mode, because claiming a server does not exist is easy and proving it is not.

That has become how I work: decide the constraint before the first line of code, then hold it all the way to release. A constraint you abandon halfway has taught nobody anything.

The technical part

React Native and TypeScript for the shared trunk, Swift for everything the framework cannot reach: widgets, Live Activities, App Intents, Apple Watch, NFC. On the server side, Node.js, Firebase, Supabase or PostgreSQL depending on what the product needs, never on what is fashionable.

But the technology is not the point. The point is that a product ends up in somebody else's hands. Between a working repository and an app installed on a stranger's phone there is an entire job that most projects underestimate, and it is where most of them stop.

Working with me

I say what I do not know how to do. I would rather scope something smaller and ship it than promise widely and disappoint. When a project does not justify a mobile app at all, I say so, even when that is against my own interest.

I like explicit constraints, written decisions, and installable builds early. A mockup does not tell the truth about a product; a phone in your hand tells it immediately.

Practicalities

I am in France, so cet: same hours as london plus one, four hours of overlap with new york. I invoice as a registered sole trader, which for a UK or US company is an ordinary international supplier invoice, with no employer of record and no umbrella company involved.

My written English is solid, including for code review, specs and documentation. Calls are fine. I am not going to pretend to be a native speaker, and if a role needs client-facing presentations in English every day, somebody else is a better fit. I would rather say that now than three weeks in.