Loading page content
Services
You do not need to choose a technology first. Start with the problem, and I will tell you which engagement gives it the best chance of shipping well.
You need an iOS and Android app that feels native, and you do not want to fund two separate teams to get it.
Production iOS and Android applications built on React Native CLI, including the native work most cross-platform projects avoid.
You need one engineer who can take a product from database schema to shipped interface without handoffs going missing.
Frontend, backend, database and API built as one system by one person accountable for all of it.
The app works, mostly — but it crashes, it is slow, and every change takes three times longer than it should.
Debugging, modernisation, performance work and technical debt reduction on codebases that have drifted.
Also covered inside these engagements: APIs, real-time systems, subscriptions, third-party integrations, performance work and technical architecture. They are capabilities, not nine separate things you need to buy.
If something here is not answered, ask me directly — a short question by email is always fine.
Mostly React Native apps that are already in production and are now slow, crashing, or hard to release — plus full-stack product work where the mobile app and the backend need to be designed together. If your app has real users and a real problem, that is the shape of thing I am best at.
Both. But an existing app with a specific problem is where I add the most, because nine years of production experience is worth more when something is already broken than when nothing has been built yet.
A call, then a short written scope. For anything sizeable I would rather start with a fixed-price audit — a week, ending in a document that says what is wrong, what it would take to fix, and in what order. It is low risk for you, and you own the document whether or not you continue with me.
It depends on the scope, so I quote the project rather than an hourly rate — hourly billing turns speed and experience into an argument against me and makes the conversation about timesheets instead of results. Tell me what you are trying to fix and I will tell you honestly whether it is a week or a quarter, before either of us commits.
I work remotely with teams across European and US time zones and keep several hours of overlap with whichever one you are in. Reviews, releases and anything that needs a conversation are scheduled inside that overlap rather than left to asynchronous guessing.
You do. Everything I write for you is yours, delivered in your repository as I go rather than in one drop at the end. You should never be in a position where the work exists only on my machine.
Because the agreements that work was delivered under do not allow me to name the clients or use their screenshots, and I am not going to break them to make a portfolio look better. The role, the decisions and the stack are all real, every image on this site is my own artwork, and I am happy to walk through any of it on a call.
I will say so in the first reply, and tell you what I would look for instead. That costs me a project occasionally and it is still the right trade — I would rather turn something down than take it on badly.
Engagement
Not sure which of these you need?
That is a normal place to start. Describe the situation and I will tell you what I think the actual problem is — including if it is not one I should be solving.