Mobile app upgrade
Store-compliance upgrade for Flutter apps on a Laravel backend
Google and Apple publish the deadlines, and an app that misses one cannot ship an update. We bring Flutter apps that talk to a Laravel API back to a shippable state on both stores at a fixed price, then keep them there under the same care plan as the backend.
The review is $750, credited in full against any sprint or upgrade. A human writes the verdict back within two working days.
The store calendar is enforced
Unlike a PHP end-of-life date, these are not advisory. Miss one and the app cannot ship an update, is hidden from new users, or is removed.
28 April 2026
Apple Xcode 26 floor (already in force)
Uploads must be built with Xcode 26 and the iOS 26 SDK. An app not rebuilt since April 2026 cannot ship an update until it is.
“Apps uploaded to App Store Connect must be built with Xcode 26 or later using an SDK for iOS 26, iPadOS 26, tvOS 26, visionOS 26, or watchOS 26.”
9 September 2026
Apple iOS 13 minimum deployment target
Older minimum targets are refused on upload. Flutter 3.47 already raised its own minimum to iOS 15.
1 November 2026
Google Play API 36 extension ends
Updates must target Android 16 (API 36). Apps targeting API 34 or lower have been hidden from new users on newer phones since 31 August 2026.
“… it will stop being available in Google Play store to new users on devices running Android OS newer than what your app targets.”
30 November 2026
Flutter Material and Cupertino deprecation
The in-SDK design libraries are formally deprecated in the November 2026 stable; apps migrate to the standalone packages.
“The original design libraries inside the core SDK are scheduled for formal deprecation in the upcoming Fall stable release in November.”
1 February 2027
Google 16 KB page-size requirement
Updates to any app with native libraries — every Flutter and React Native app — are blocked unless built for 16 KB pages.
“Starting February 1, 2027, if your app updates don't support 16 KB memory page sizes, you won't be able to release these updates.”
1 April 2027
Apple iOS 27 SDK floor
Apple has announced that uploads will require the iOS 27 SDK and Xcode 27 from April 2027. The exact day is published nearer the time; the pattern is now annual.
“Starting April 2027, apps and games uploaded to App Store Connect need to meet the following minimum requirements: iOS and iPadOS apps must be built with the iOS 27 & iPadOS 27 SDK or later”
Not sure where your app sits? Send the manifest and we will tell you.
Three fixed prices
The review decides which one fits. Fixed means fixed: if we underestimated, that is our cost.
Second-opinion review
$750
£570 · €690
5 working days
A written architecture and store-compliance report for any Flutter or React Native app.
- Framework and dependency currency against the supported windows
- Store compliance: target API, Xcode floor, minimum targets, privacy manifests, 16 KB readiness
- Which package below fits, with the fixed price attached
- Credited in full against any sprint or upgrade
- Code changes
Store-Compliance Sprint
$2,500–$3,500
£1,900–£2,650 · €2,300–€3,200
7–10 working days
A Flutter app no more than two stables behind, brought back to a shippable state on both stores.
- Android target API raised to the current requirement; 16 KB page-size readiness
- Rebuilt with the current Xcode and iOS SDK floor
- Privacy manifests, age rating and store metadata brought current
- Flutter and dependencies bumped; tests green
- Both stores resubmitted and approved; hand-over notes
- Null-safety or design-library migrations (Catch-up)
- New features
Catch-up Upgrade
$6,000–$12,000
£4,550–£9,100 · €5,500–€11,000
3–5 weeks
An app two or more years behind: migrations done, discontinued packages replaced, tests backfilled.
- Everything in the Store-Compliance Sprint
- Dart null-safety and Material/Cupertino package migrations where pending
- Discontinued and unmaintained packages replaced with maintained equivalents
- React Native New Architecture migration, after the review
- Work on a flag-gated branch; test coverage backfilled around the flows the business depends on
- Redesigns
- New features
Then keep it in the store: the Mobile module
An add-on to any care plan for the Flutter app that talks to the Laravel application under care. From +$300/month on top of the plan.
| Added to | Extra hours / month | Covers | Module price |
|---|---|---|---|
| Essentials | 3 | One Flutter app pair kept shippable. | +$300 per month +£230 · +€275 |
| Standard | 6 | Current, and moving: monthly releases from your backlog. | +$450 per month +£340 · +€415 |
| Partner | 8 | Release pipeline owned, a second app covered. | +$600 per month +£455 · +€555 |
On Essentials
- Both annual store deadlines handled: Google Play target API and the Apple Xcode floor
- Quarterly Flutter and dependency bump with the release rebuilt and resubmitted
- Store metadata compliance: privacy manifests, age rating, trader status
- Crash monitoring and one maintenance release a quarter
On Standard
- Everything in the Essentials module
- Monthly releases carrying small features and fixes from the backlog
- A Flutter web admin, kiosk or dashboard kept building alongside the app
- Device testing on both platforms before every release
On Partner
- Everything in the Standard module
- A second app pair, or a React Native app after a paid review
- Release pipeline owned end to end: signing via your accounts, CI builds, store tracks
- Store-rule changes assessed in writing within the SLA when Google or Apple announce them
Precondition. The app must be current — it has passed a Store-Compliance Sprint or Catch-up Upgrade — and its backend must be a Laravel application under care or maintained by your own team.
React Native
We also work in React Native and Expo. We have not yet published a React Native case study, so we quote React Native work only after a paid review.
Flutter web
Flutter web is right for the internal tool, kiosk or dashboard that mirrors your app, and we keep those building. It is the wrong tool for a public marketing site, and we will say so.
Send us the manifest
Paste the pubspec.yaml or package.json and the store links. No code, no credentials. A human reads it and writes the verdict back within two working days.
Request the review
The manifest is optional, but it turns a conversation into a verdict.
What you get within two working days
Where the app sits on the store calendar
Target API, Xcode and SDK floor, minimum deployment target, privacy manifests and 16 KB readiness, each marked current, due or overdue.
Framework and dependency currency
The Flutter or React Native version against the supported window, and the packages that are discontinued or more than a major behind.
The package that fits, with the price
Store-Compliance Sprint, Catch-up Upgrade or nothing at all. If the app only needs the Mobile module, we say so.
A store-account and signing checklist
What we would need access to, at which role, and what stays in your custody before any work starts.
Why a human, not a tool
The manifest tells us the framework and the packages; the store listings tell us the rest. Reading both together is what turns "probably fine" into a list of what is overdue, and a fixed price for fixing it.
How we work inside your store accounts
Store work carries liability a Laravel plan never had, so the rules are written down before anyone is given access.
The same ten clauses appear in our terms of service.
Mobile upgrade questions
Who owns the store accounts?
You do. You enrol as an organisation and remain Account Holder on Apple and Owner on Google Play, and you pay Apple and Google directly. We work inside your accounts at the lowest role that lets us do the job, and the access is revoked when the work ends.
Who actually submits the app?
We prepare the build, the metadata and the release notes, and submit from inside your App Store Connect and Play Console accounts. We never submit your app under our own developer account, so nothing about the listing, the reviews or the revenue ever sits with us.
How long does store review take?
Apple typically clears nine in ten submissions in under 48 hours; Google can take up to seven days, longer for new or recently changed accounts. Our response times cover our work; store review time is outside the clock, and we say so in the terms.
Our Android app has disappeared for new users. Why?
Because its target API level is behind the store. Google states the effect in its own words: "Only apps that are not compliant with the policy will receive a policy warnings and notification in Play Console." So the only owners who hear about it are the ones already affected, and the warning in Play Console is where the extension form lives. Google's extension wording: "If you plan to update your app to a higher target API and need more time beyond August 31 2026, you may request an extension to continue distributing to all Google Play users until November 1 2026." A Store-Compliance Sprint raises the target to API 36, rebuilds for 16 KB pages and resubmits from your account.
Our backend is not Laravel. Can you still help?
Not yet. The upgrade and the Mobile module are built around a Laravel API we care for or your own team maintains, because that is where we can stand behind the whole release. If the backend is something else, we will say so on the first reply and point you to someone who fits.
Do you work in React Native?
We also work in React Native and Expo. We have not yet published a React Native case study, so we quote React Native work only after a paid review.
Building a new app instead? Flutter apps on a Laravel API, at a fixed price.
What you are actually buying
The answer to "why an agency in India?", in writing.
Who you contract with
Jigomit LLP, Ahmedabad, India. The company name on the contract and on every invoice.
UK/EU working hours
Working hours overlap the UK and EU day in full; the US East Coast morning in part.
NDA before requirements
We sign your NDA, or send ours, before you share a repository or a brief.
You own every line
You own every line. Code lives in your repository from day one. All IP in the work transfers to you on payment.
Named engineer
The same engineer stays on your account. No junior substitution.
Fixed means fixed
Fixed means fixed: if we underestimated, that is our cost, not yours.
Data-processing terms published
UK GDPR Article 28 processing terms are published and signed as a schedule to the engagement letter. Read the data-processing terms
Written SLAs
Response times in the contract, not on a slide.
Find out before the store does
Send the manifest and the store links. Within two working days you know what is overdue and what it costs to fix, whether or not you hire us.