Your app stays maintained, month after month
Ongoing maintenance for React Native and Expo apps: fixing bugs, keeping dependencies and SDK versions current, shipping releases to Google Play and the App Store. From 1,200 euro per month, 30 hours included, 55 euro per hour beyond that.
- React Native
- Expo
- Next.js
- 30 hours a month
- Cancel monthly
For teams with an app that has to keep running
The app is built and live in the stores. The developer who built it has moved on, answers once a month, or is gone for good. That is the gap this page fills. If you need something new built instead, start on the React Native development page.
What happens to an app nobody looks after
An app ages even when nobody touches it. Google and Apple move their requirements, dependencies pick up security advisories, and one day the project stops building. For the Expo side of that, EAS Build, over-the-air updates and SDK upgrades, see the Expo development page.
Bugs just sit there
A crash on login hits everyone who opens the app. With nobody to reproduce and fix it, it stays in your store reviews for weeks.
Dependencies fall behind
The longer an upgrade waits, the more it costs. One skipped SDK version turns into several weeks of migration after two years.
Store requirements change
Google and Apple keep raising the required target API level and asking for new privacy declarations. Miss one and you cannot ship an update at all.
Nobody answers
When a payment fails or a push never arrives, someone has to respond. A developer who has time again in three months does not help in that moment.
The knowledge sits elsewhere
Signing keys, store access, environment variables: often that lives in one person's head or on one old laptop. A handover brings it back.
Every small change is a new quote
Commissioning single changes costs more coordination than work. A fixed monthly scope turns it into one planned line in the budget.
What the retainer covers and what it does not
From 1,200 euro per month, 30 hours included, 55 euro per hour beyond that. You decide what those hours go into. If a web app or a customer portal belongs to the same product, the Next.js development page covers that side.
Fixing bugs
Reproducing crashes and broken behavior, fixing them and shipping the update. Reported by email or in your issue tracker, whichever you already use.
Keeping versions current
Raising React Native, the Expo SDK and the dependencies on a regular rhythm. In small steps, instead of one large jump every two years.
Shipping releases
Producing builds, keeping version numbers and changelogs, submitting to Google Play and the App Store and following the review through.
Small features
An extra field, a new filter, a reworked screen. Anything that fits the monthly scope goes in without writing a quote for it first.
Handover from another developer
I read into the existing code, collect access, keys and environment variables, and write down how a release is produced from the repository.
Reachable on working days
You write, I answer on working days. Whatever is broken in production comes before whatever is only meant to look better.
Not included: full-time development
30 hours a month is roughly one working day a week. A new app, a rewrite or a feature spanning several months belongs in its own project.
Not included: on-call cover
No round-the-clock promise, no nights, no weekends, no pager rotation. I study alongside this work, so I only promise what I can keep.
Not included: your accounts and contracts
Store fees, hosting, push services and licences stay on your accounts and your invoices. I work inside them, I do not own them.
From handover to a repeating month
The first month looks different from the ones after it. For everything else I build, see the home page.
Look at the code
I go through the repository, the dependencies and the current build, then tell you what state the app is in. Including when that answer is uncomfortable.
Handover
Access to Play Console and App Store Connect, signing keys, environment variables and anything else a build needs, all in one place.
First month
The painful things first: open bugs, overdue upgrades, a release that goes through again. After that the app is in a state you can work from.
Every month after
You send what is due, I work through it inside the monthly scope and tell you before the 30 hours are used up. Cancel at the end of any month.
Should I take over your app?
Tell me which app it is, what it is built on and what is piling up right now. You get an honest read on whether 30 hours a month is enough for your case. If it is not, I will say so.
Questions about the retainer
From 1,200 euro per month, 30 hours included, 55 euro per hour beyond that. No tiers, no setup fee. At the end of each month you get a short summary of where the hours went.
The price stays the same, because you are paying for available time, not per reported bug. In quiet months the hours go into what otherwise never happens: raising dependencies, cleaning up the build pipeline, fixing edge cases. If a month is genuinely empty, we talk about it instead of burning the time.
Beyond the 30 hours I bill 55 euro per hour. Before that happens I tell you, and you decide whether it has to be this month or can move into the next one. Nothing goes over the scope without your go-ahead.
On working days. I study alongside this work, so I promise neither round-the-clock availability nor a response time measured in hours. What I do promise: an answer on working days, and anything broken in production comes before everything else in the running month.
Yes. The retainer runs month to month and ends at the end of a month, with no minimum term. On the way out you get everything you need to carry on: access, keys and a written description of how a release is produced from the repository.
That is the normal case. I look at the code first and tell you what I find. If the state needs more than maintenance, a large upgrade or a rebuild for example, I say so up front and we treat it as its own project.
React Native, Expo, Next.js, Kotlin and Jetpack Compose, daily. I will look at an app in a different stack, but I will say plainly when I am not the right person for it.
Let's build something great together.
Have a project in mind? I'd love to hear about it. Send me a message and I'll get back to you as soon as possible.
