0

I have a Xamarin.Forms application and I would like to continue using Xamarin.Forms for at least the next 2 years.

I understand that Xamarin.Forms has reached its end of support (official support ended on May 1, 2024), but migrating to .NET MAUI is currently not feasible for our team due to time constraints.

I’m looking for advice on the following:

Is it technically safe to continue using Xamarin.Forms on Android 14/15/16 and iOS 17/18, assuming I can handle breaking changes via renderers or custom code?

Are there any third-party vendors or community groups that still provide paid or open-source support for Xamarin.Forms?

Are there known limitations or critical issues for newer Android/iOS versions that cannot be bypassed without MAUI?

Any leads or suggestions would be greatly appreciated.

I have reviewed Microsoft’s official Xamarin.Forms lifecycle documentation and confirmed that it reached end of support on May 1, 2024.

I tested my existing Xamarin.Forms app on Android 14 and Android 15 preview devices and it still works for the most part, except for some UI inconsistencies and warnings related to deprecated APIs.

I also searched for ongoing community support options, like open GitHub forks or third-party service providers, but didn’t find any concrete leads.

I’m expecting to find out:

Whether anyone else is successfully running Xamarin.Forms on Android 15/16

If there are specific issues that would block me from continuing for the next 2 years.

Whether there are any support vendors (commercial or freelance) still helping maintain Xamarin.Forms apps.

Improve this question
6
  • 2
    The problem is that bindings for the new APIs won't be available, which means you won't be able to build against the latest Android and iOS SDKs and if you don't target the minimally required target APIs, the stores will reject your XF app. I'm afraid you don't have much of a choice unless you hack together something for the bindings yourself - work that the MAUI team chose not to do in favor of going full MAUI. However, what's the problem with migrating to MAUI? You don't have to use all the new features, you can still keep the separate projects approach and even use old renderers. Commented Jul 14 at 13:46
  • Can you clarify which specific platform SDK versions (e.g., Android API 34, iOS 17) you intend to target for store submission? Commented Jul 14 at 13:50
  • Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Commented Jul 14 at 14:29
  • @JuLian Thanks for your response. In my case, most screens in the app use grouping with expand/collapse behavior. However, when I try the same in MAUI, some group headers are missing, and items from one group merge into others. This issue makes the migration challenging. I've attached a sample in MAUI that shows the problem. github.com/dotnet/maui/issues/19334 Commented Jul 16 at 8:11
  • 1
    @VIJAY ListView is deprecated anyway, you should try to switch to CollectionView instead or use a third party control. Commented Jul 16 at 9:24

1 Answer 1

Reset to default
0

The short answer to this is not possible now, Please migrate the application to .NET Maui, and Microsoft provides tools to migrate the applications easily, Please refer the Microsoft Document.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.