Why Xams?

In our quest for a solution to supercharge our development process, we explored renowned platforms like Firebase, Supabase, and Pocketbase. These platforms stand out for their simplicity, efficiency, and ability to provide a significant boost to application development. However, each has its set of limitations:

• None are natively integrated with the .NET ecosystem.
• Firebase lacks a relational database, complicating certain data modeling and queries.
• Pocketbase, while visually appealing, employs SQLite, presenting scalability challenges.
• With Supabase, business logic is often penned in SQL Triggers.

On the other side, there are ASP.NET frameworks such as ABP, Serenity, and ASP.NET Zero. Perfect for expansive projects, these frameworks promote an opinionated architecture that ensures project organization. While they expedite certain processes because of their predefined implementations, they also confine developers, often leading to cumbersome boilerplate code and scenarios where developers feel they're wrestling with the framework. Not to mention, none of these frameworks are inherently tailored for React, despite its expansive ecosystem which reigns supreme among web frameworks.

So, how do you harness the agility of platforms like Firebase while leveraging the .NET ecosystem, all without being shackled by a rigid framework?

Enter Xams

Xams brilliantly bridges this gap. Think of it as having the best of both worlds: it offers the advantages you'd get from Firebase, Supabase, or Pocketbase, but tailored for C# and the .NET framework. Designed akin to frameworks like ABP, Serenity, and ASP.NET Zero, Xams remains substantially more lightweight and flexible. It upholds an architecture that fosters code structure and purity without becoming overbearing.

In essence, Xams glows with the nimbleness of Firebase and carries many benefits akin to ABP. If you’re keen on jump-starting your ASP.NET project without being bogged down by an excessively opinionated structure, Xams is your answer.