There are so many web frameworks!īut, I made a simple decision.

But that consistency evaporates when platform issues are addressed. Lovely! Consistency everywhere (well, mostly). This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. I was also worried how Xamarin Forms, if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. Xamarin Forms is mobile only the Windows incarnation is different. NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Test framework: Infrastructure: moreįinding the most effective dev stack for a solo developer.Build and Release Pipelines: Azure DevOps.Libraries: jQuery, Database: Source Control: Git.IDEs: Visual Studio Code, Visual Studio.Language: C#, Microsoft SQL Server, JavaScript.Trusted Authentication Provider: Frameworks.For this service I opted to keep it as a classic WebAPI project and deployed to AppService. Net developers and an Azure infrastructure environment using server-less functions, logic apps and SaaS where ever possible. This API provides a way to add and manage more complex permission structures than can easily be maintained in Azure AD. The front-end using the Azure AD B2C to allow 3rd party trusted identity providers to authenticate. This is the backing API to store additional profile and complex membership metadata outside of an Azure AD B2C provider. Secure Membership Web API backed by SQL Server.

Android studio