Help for owners
My app is built in old technology that hardly anyone works with
Short answer
When a technology reaches end of support, its maker no longer provides fixes or updates, and finding developers gets harder over time. The app usually keeps running until a store or phone update breaks it. Do not publish new updates without a developer who can build it. First secure the code, then plan a move.
Does this sound like your situation?
- Developers say they do not work with this technology.
- The app is built with Xamarin, an old Ionic or Cordova setup, or another retired framework.
- It cannot be built any more after an Apple or Google update.
- Store warnings mention a newer required version.
- Fixing one thing takes far longer than it should.
Why does this happen?
The maker ended support
Microsoft states that Xamarin reached end of support and that it no longer provides fixes, updates or online technical assistance. Its final target versions are Android API 34 and the iOS 17 SDKs, and no new APIs are planned.
Confirmed by dotnet.microsoft.com
A successor exists, but it is a migration
Microsoft says Xamarin.Forms evolved into .NET MAUI and that existing Xamarin.Forms projects should be migrated to it. The native Xamarin parts moved into .NET itself and need upgrading to the new project format.
Confirmed by dotnet.microsoft.com
Stores raise their requirements
Google Play requires apps to target a recent Android level, so an app on a frozen toolkit eventually cannot be updated.
Technical detail: Play Console will not accept the release because of its target API level
Fewer developers know it
As a technology fades, fewer people learn it and each takes longer to find. That raises the effort and the risk of every change.
Tools and plugins stop matching
Build tools, signing and libraries move on. An old project fails to build on a new machine, and the fix gets harder each year.
Technical detail: Flutter build fails because the Android project uses the v1 embedding
What can I do about it today?
- Get the complete source codeMake sure you hold a copy of the code, the signing files and the store accounts. Without these, no plan is possible.
- Find out exactly what it is built withAsk your developer for the framework and its version, and write it down.
- Do not rush a new releaseReleasing an update from a machine that nobody has built on can fail halfway. Hold until someone can build it reliably.
- Check the store messagesLook in the Apple and Google developer accounts for warnings or required deadlines, and copy them down.
- List what the app must keep doingKey screens, logins, payments and the data behind them. This is what any migration is tested against.
When should I bring someone in?
- A store warning has a deadline.
- The app can no longer be built or released.
- Developers have told you it must be rewritten and you cannot judge that.
How do I handle it?
- Prove it can still be builtFirst I rebuild the app from the code on a clean machine, which tells us how fragile it is.
- Choose the targetUpgrade within the same family, move to Flutter, or keep part of it. I explain what each costs in effort and risk in plain words.
- Migrate screen by screenThe key flows are moved and checked against the old app, so users keep the behaviour they know.
- Release with a way backThe first new version goes out after a backup of the current build and a tested path to return to it.
- Hand over the documentsYou receive the code, the build steps and a short guide so that the next developer is not lost.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Will the app stop working tomorrow?
Not by itself. End of support means no more fixes from the maker. Problems usually appear when a phone or store change breaks something that cannot be repaired.
Do my users have to reinstall?
A migrated app can be released as an update to the same listing, as long as it is published under the same account and signing identity.
Which technology should it move to?
It depends on the app and your team. I compare options for your case, and I will tell you if staying is acceptable for now.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Play Console blocks submitting a release whose app bundle targets an API level below 36Play Console will not accept the release because of its target API levelBuild failed due to use of deprecated Android v1 embeddingFlutter build fails because the Android project uses the v1 embeddingDeprecated Gradle features were used in this build, making it incompatible with Gradle 10.Gradle says deprecated features were used and the build will break on the next major versionApplying Flutter's app_plugin_loader Gradle plugin imperatively using the apply script method is deprecatedFlutter warns that the Gradle plugin is applied the old imperative way