My team is looking to build a platform using .NET 5 for most of the components. For the mobile apps, we are pretty set on using Xamarin.Forms (as we have built our current platform using this framework) and it is clear that Microsoft intends to update the framework to .NET 5 eventually.
The platform will have a primary SQL database hosted in Azure and a RESTful API exposed to the mobile applications. Our requirements for the mobile apps state that the app shall be offline first with a sync capability with the primary database when an internet connection is available. We feel comfortable using SQLite for the local db on mobile device. While researching synchronization techniques and libraries, it became evident that Azure App Service supports an "offline sync" feature that by all indications in the documentation does exactly what we want it to do (this feature was formerly available in Azure Mobile Apps). One of our interns built a demonstration project (hosting the mobile API in Azure App Services and building an App for Android using Xamarin.Forms), and verified the feature.
When looking at bootstrapping some projects myself, I noticed that the quickstarts for the .NET backend had languished for over a year, and I also verified that the NuGet packages for both the Client and Server which enable access to the offline sync feature weren't being actively updated. Also, the .NET backend quickstart targets .NET Framework 4.6 (this would be forgivable considering Xamarin.Forms is still using older framework versions also).
We are looking for a solution that is a little more manageable than the "roll your own db sync," as this has caused great pain in previous projects. We are looking at 3rd-party db sync solutions as well but we heavily use Microsoft tools and frameworks and like to use 1st-party integrations when possible.
Is offline sync migrating to .NET 5, or should my team look for another database synchronization solution?