What Happens If We Keep Running a Xamarin App?

If your Xamarin app still works, it is reasonable to wonder why you need to migrate it at all.

The short answer: a Xamarin app will not suddenly stop working because Xamarin reached end of support. Existing installations may continue running. What gets harder is maintaining, updating, securing, and distributing the app as Apple, Google, and the rest of the mobile ecosystem move forward without Xamarin.

Microsoft ended support for Xamarin on May 1, 2024. Xamarin's final supported platforms include Android API 34 and Xcode 15, covering the iOS 17 generation. Microsoft no longer provides Xamarin fixes, updates, security updates, or support for newer platform SDKs.

That distinction, between running software and maintainable software, is the real issue.

Will an existing Xamarin app keep working?

Possibly, and in many cases it already has.

End of support did not introduce an expiration date into Xamarin applications. If an app is installed on a compatible device and its operating-system APIs, backend services, authentication systems, and third-party integrations continue behaving as expected, it can keep running.

That can make staying on Xamarin seem relatively low-risk.

The problem is that Xamarin is now effectively frozen while the systems surrounding it continue changing.

A new iOS version can alter platform behavior. Google can raise its Android API requirements. A payment or authentication SDK can discontinue Xamarin support. A NuGet package can move to a newer version of .NET. Your build environment can become harder to reproduce.

Each change narrows the number of safe options available to the development team.

What happens when you stay on Xamarin?

Usually, there is no single catastrophic event. Risk accumulates across several areas.

For many businesses, app-store distribution becomes a problem before the application itself stops launching.

Can we still update a Xamarin iOS app?

This has become particularly difficult.

Xamarin.iOS officially ended with support for Xcode 15. Apple now requires apps uploaded to App Store Connect to be built with Xcode 26 or later using the iOS 26 SDK or a later SDK. That requirement has been in effect since April 28, 2026.

An existing Xamarin app may remain installed and available to current users. But when you need to ship a bug fix, security update, compatibility change, or new feature, the old supported Xamarin toolchain can no longer satisfy Apple's current submission requirements.

That converts Xamarin's end of support from abstract technical debt into a release-management problem.

What about Xamarin Android apps on Google Play?

Android has reached a similar point.

Xamarin.Android's final official release can target Android API level 34. Starting August 31, 2026, Google Play requires ordinary new mobile apps and app updates to target Android 16/API level 36. Existing apps generally need to target at least Android 15/API level 35 to remain available to new users on devices running newer Android versions. Google offers eligible developers an extension until November 1, 2026.

In practical terms, an old Xamarin Android app may continue working for people who already have it, while becoming harder to update and less discoverable to new users.

Google's policy specifically ties current target API levels to security, privacy, performance, and compatibility expectations.

Is running Xamarin a security risk?

Unsupported does not automatically mean insecure.

It means you can no longer count on Microsoft to fix Xamarin if a new framework-level problem appears.

There is also a larger dependency chain to consider. Production mobile apps typically rely on authentication providers, analytics tools, notification services, mapping libraries, payment integrations, device APIs, NuGet packages, and backend services.

Those systems are not frozen.

As their maintainers move to current .NET, Android, and Apple SDKs, an older Xamarin application can become trapped between keeping an outdated dependency and attempting an upgrade that its underlying framework was never designed to support.

That is where technical debt starts becoming operational risk.

What if our Xamarin app is stable and rarely changes?

There are situations where retaining it temporarily can be reasonable.

A narrowly used internal application running on controlled devices is different from a public consumer app that must remain compatible with the latest phones and app-store policies. If the app has limited exposure, does not need frequent releases, and has a known retirement or modernization date, continued operation may be an acceptable short-term decision.

But “keep it for now” should be an explicit strategy, not the absence of one.

At minimum, know:

• Which devices and OS versions must remain supported.
• Whether future App Store or Google Play releases will be necessary.
• Which external libraries and services the application depends on.
• Whether the current Xamarin build environment can be reproduced.
• What events would trigger migration.
• How long the business is willing to accept the increasing maintenance risk.

The more important the application is to customers, revenue, regulated workflows, or daily operations, the more consequential those questions become.

Do we have to rewrite the Xamarin app?

No.

Microsoft's migration guidance is explicit that Xamarin projects can be upgraded to modern .NET and do not necessarily need to be rewritten. Xamarin.Android and Xamarin.iOS projects can move to modern .NET SDK-style projects, while Xamarin.Forms applications can migrate to .NET MAUI. Microsoft also notes that an existing multi-project solution does not have to become a single multi-targeted project simply because it is being modernized.

That does not make migration automatic.

Third-party dependencies may need replacements. Xamarin.Forms custom renderers may need to become .NET MAUI handlers. Platform-specific code may need updating. Build pipelines and app-store deployment processes may need modernization.

But substantial portions of an application's C# business logic, models, services, and workflows can often remain useful.

The goal should be to preserve what still creates business value while replacing the unsupported foundation.

The best time to migrate is before the app fails

A functioning Xamarin application gives you something valuable: options.

You can inventory dependencies, identify high-risk platform code, determine what can be reused, migrate in phases, compare the new application against a working reference, and schedule the project around business priorities.

Once an OS change, app-store requirement, or critical dependency forces the issue, much of that flexibility disappears.

Art+Logic encountered exactly this kind of challenge while modernizing a long-standing Xamarin mobile platform. Rather than treating the project as a wholesale automated conversion, the team migrated it incrementally to .NET MAUI, using AI-assisted development for appropriate repetitive work while keeping architecture, validation, and quality under experienced engineering oversight.

That is a useful model for thinking about Xamarin modernization generally.

The app still working is not a reason to ignore migration. It is an opportunity to plan the migration before you are forced to do it.

FAQs

Will Xamarin apps stop working after the end of support?

No, not automatically. Existing Xamarin applications can continue running on compatible devices. Problems are more likely to emerge over time through operating-system changes, dependencies, app-store requirements, and an increasingly outdated development environment.

Is Xamarin still supported?

No. Microsoft ended support for all Xamarin SDKs, including Xamarin.Forms, on May 1, 2024.

Can you still publish Xamarin apps?

Existing applications may remain available, but current store requirements have moved beyond Xamarin's final supported tooling. Apple requires Xcode 26 and the iOS 26 SDK for current App Store uploads, while Google Play now requires Android 16/API 36 for ordinary new apps and app updates.

What replaced Xamarin?

Xamarin.Forms evolved into .NET MAUI. Xamarin.Android and Xamarin.iOS functionality has been integrated into modern .NET for Android and .NET for iOS.

Should we migrate a Xamarin app if it still works?

If the application still needs ongoing releases, security maintenance, new-device compatibility, or app-store distribution, migration should be actively planned. A controlled internal application may sometimes remain on Xamarin temporarily, but retaining it should be a deliberate risk decision with a defined modernization or retirement path.