React Native maintenance · 5 slots open

Your app stays in the stores. $500 a month.

Google and Apple move the goalposts every year. When the developer who built your app is gone, or busy, the app quietly stops being installable for new users. I take that job off you for a flat monthly price, and the deadline emails come to me.

  • 1 Store deadlines handled before they hit
  • 2 Crashes and breakages fixed
  • 3 Month to month, cancel any month

Two client apps live in the stores, kept there by me. One of them has been through every Google Play requirement from 2025 to now and is still listed. My name is on neither. That is the arrangement.

Send the store link. You get a written check-up in two business days. Free, no call.

  • 2client apps kept live in the stores
  • 5AI features I built, running in them
  • 5maintenance slots open right now
What breaks, and when

Three letters every app owner gets, whether they read them or not

None of this is my opinion. Each one is on the platform’s own page, linked, with the date. Next year the same three arrive again with new numbers. That is the job.

Google PlayPassed

Target Android 16 or updates are refused

New uploads must target Android 16. Existing apps must target at least Android 15 or they stop being available to new users on newer phones. An extension to 1 November 2026 can be requested, once.

Source: Play Console Help, opens in a new tab
App StoreIn force

Built with Xcode 26 or the upload is rejected

Every upload to App Store Connect must be built with Xcode 26 and the iOS 26 SDK. An app on an older toolchain cannot ship a fix, even a one line one, until the build setup is brought forward.

Source: Apple Developer, opens in a new tab
React NativeSince 0.82

The old architecture is gone

React Native 0.82 removed the legacy architecture. Any library that never made the move stops working on upgrade, and the further behind an app is, the more of them it has.

Source: reactnative.dev, opens in a new tab

An app that misses one of these does not crash. It just stops appearing for new users on new phones, and nobody tells you. The first sign is usually a flat install graph.

Prices

Four numbers. No call to find out the real one.

Most apps want the first one. The second is for apps with a backlog. The third is for an app that has been left alone too long. The fourth is for when you want something new in it.

Keep-alive

$500per month

For an app that works today and has nobody watching the store deadlines.

  • Google Play and App Store requirement changes handled before they hit
  • React Native and library upgrades needed to keep building
  • Crash fixes after OS updates
  • Store policy paperwork: data safety, privacy manifest, review replies
  • Resubmissions on both stores
  • Replies within one business day

Month to month. Cancel any month. Billed at the start of the month.

Start with a check-up

Rescue

$1,500fixed

For an app nobody has touched in a year and that no longer builds or uploads.

  • React Native upgraded to a current version
  • Android target level and Xcode 26 build sorted
  • Dead or abandoned libraries replaced
  • Resubmitted and live again on both stores
  • Written handover of what changed and why

You pay when it is live. If the check-up shows it is worse than this, I say so before you commit.

Start with a check-up

Feature

$2,000fixed

For one thing your users should be able to do that they cannot do today. AI or otherwise.

  • Scope written down in one paragraph we both agree on
  • Built into your existing app, through your review process
  • About two weeks
  • You watch it run on your own data before you pay
  • Thirty days of fixes on it after it ships

Not what you wanted? I take the code back and you pay nothing.

Send the feature

Keep-alive is the floor, not a teaser. If a month needs more than what is listed, I say so before doing it, and you decide. Nothing gets invoiced that was not agreed in writing first.

Rescue and Feature are paid on results. Rescue when the app is live again. Feature when you have watched it run. The monthly plans are the only things paid in advance, and those you can cancel any month.

How it starts

One link, then a written answer

Every developer you email sounds equally confident, so I take that part out. You do not have to trust the pitch. You send a link and get a diagnosis you can check against the sources above, before any money is mentioned.

  1. 01

    Send the store link

    That is the whole first step. App Store, Google Play, or both. No form to fill, no call to book, no deck to read.

  2. 02

    You get a written check-up in two business days

    What is about to break and when, what fixing it costs, and what keeping it from happening again costs. Free, in writing, and if the app is fine it says so.

  3. 03

    Say yes, and the deadline emails become mine

    You add me as a user on your store accounts and give me the repository. From that month on, the letters from Google and Apple land on my desk, not yours.

The check-up is not a sales call in disguise. It is what I can see from the outside and what I would need access to see the rest. If your app is fine and your current developer is doing the job, it says that, and we are done.

Almighty chat screen with message bubbles and a voice note button
EzeeNotes home screen with subject cards for physics, chemistry and maths
Almighty voice call screen showing a connected caller
EzeeNotes screen showing a chapter list inside a subject
Almighty group call screen with participant controls
EzeeNotes screen showing practice questions
Almighty community screen with a post composer and threaded replies
EzeeNotes notes page with a QR code that opens a video explanation
Almighty news feed screen with categorised story cards
Almighty photo sharing screen with a multi image post
Almighty comment thread with one tap translation across languages
Already in the stores

Two client apps, built and kept live by me

Both are live, both were built end to end by me, and my name is on neither listing. That is the arrangement you would be buying. The code is under NDA, the apps are not, so every claim below is checkable from the store page. Where you would have to install the app to see something, it says so.

AlmightyIn the stores

A social and messaging app with chat, voice and video calls, communities and a feed. React Native, iOS and Android.

Kept in the store

  • Built end to end and shipped to both stores.
  • Updated continuously on iOS and Android since launch.

AI I built for it

  • Inside the appTone check before a message sendsA message that is going to land harsh gets caught on the way out, and the sender is asked whether they want to soften it.
  • Inside the appTone rewriteThe softer version, generated, with the meaning kept. The sender picks which one goes.
  • Inside the appSensitive information detectionFlags things like a phone number or an address before they leave in a message the sender did not think twice about.
  • Inside the appCrisis language detectionSelf harm signals in a message are detected and surfaced. It is a safety net inside the product, not a clinical tool, and it is built and described as one.

Wired in, not built by me

  • On the store listingTranslation on every screen, 50+ languagesAny post, comment or message rendered in the reader's own language. The translation model is Google's, through their API. What is mine is the integration: wiring it into every surface in the app and making it hold up under real traffic. It is on the store listing and has its own screenshot.
Almighty chat screen with message bubbles and a voice note button
Almighty voice call screen showing a connected caller
Almighty group call screen with participant controls
Almighty community screen with a post composer and threaded replies
Almighty news feed screen with categorised story cards
Almighty photo sharing screen with a multi image post
Almighty comment thread with one tap translation across languages

These are the screenshots on the App Store and Google Play listings. Open one and check.

EzeeNotesIn the stores

A study app for Class 11 and 12 students. Notes, concept videos behind QR codes, and practice questions. React Native, Android.

Kept in the store

  • Built end to end and shipped to Google Play.
  • Taken through every Google Play requirement that landed on it from 2025 to now. Still in the store.

AI I built for it

  • Inside the appPersonal study analyticsEach student's own activity turned into a read on what they actually know and what they keep avoiding, generated per student rather than pulled off a fixed dashboard.
EzeeNotes home screen with subject cards for physics, chemistry and maths
EzeeNotes screen showing a chapter list inside a subject
EzeeNotes screen showing practice questions
EzeeNotes notes page with a QR code that opens a video explanation

These are the screenshots on the Google Play listing. Open it and check.

When you want something new in it

Features I have already shipped, and where

Maintenance is the job. This is the range. Each of these is running in one of the two apps above, tagged with which one. A feature is $2,000 fixed, about two weeks, and you watch it run on your data before you pay.

Tone check and rewrite before a message sends

In Almighty

A message about to land harsh is caught on the way out, and a softer version with the meaning kept is offered. The sender picks.

Sensitive information caught before it leaves

In Almighty

A phone number or an address typed into a message without thinking is flagged before it goes.

Crisis language detection

In Almighty

Self harm signals in a message are detected and surfaced. A safety net inside the product, built and described as one.

Translation on every screen

In Almighty

Posts, comments and messages rendered in the reader's own language. Google's model through their API. The wiring across every surface is mine.

Per user insights from their own activity

In EzeeNotes

Each student's activity turned into a read on what they know and what they keep avoiding, generated per student.

Something else

Ask

Ask. If I have built it before I will say where. If I have not, I will say that instead, and you decide.

Fit

When this goes well

A flat price only works when both sides know what it covers. These are the conditions that make that possible.

  • Your app is React Native and it is in at least one store.
  • The person who built it is gone, or is busy building, and nobody is watching the store.
  • You can give one developer access to the repository and the store accounts.
  • You want a fixed monthly number, not an hourly surprise.
No spin

What I am, plainly

Who you get
Mohammed Zaiban, working on it directly. LinkedIn. Not a company and not a team. Where this page says we, it means you and me.
How many apps
Two now, both above. Room for 5 more. When those are taken this page will say so, because the alternative is taking your money and doing a worse job.
What I need from you
A user seat on App Store Connect and Google Play Console, and access to the repository. You never hand over a password, and you can remove me in a minute.
Not React Native
Then I am not the right person, and the check-up will say that instead of pretending otherwise.
Can you see the code
No. Both apps belong to clients and the code is under NDA, and so is yours. The same thing that stops me showing you theirs is what stops the next person seeing yours.
Where I am
Outside the US. My hours overlap US afternoons, and you get a reply within one business day.
Whose name is on it
Yours. My name is on neither store listing above, and it will not be on yours.
What it costs
Keep-alive $500 per month. Maintain $1,000 per month. Rescue $1,500 fixed. Feature $2,000 fixed. Every number is on this page. There is no call where the real price comes out.

Send the store link.

That is the whole first step. Two business days later you have a written check-up: what is about to break, what it costs, and whether I am taking it. If the app is fine, it says that. The only thing you risk is the ten seconds it takes to paste a link.

zaiban@greeencode.com

Prefer a form? Use the contact page. It lands in the same inbox.