I'm working on a basic MVP for a local fashion catalog. The features are simple: no online payments or prices, just browsing and filters, with the option to contact via Facebook or WhatsApp. The application will handle user authentication and authorization, allowing users to save their favorite items and merchants to manage their listings. Everything will be hosted on a single VPS that will include the database, images, and web server. As a solo developer with limited time, I'm trying to decide which stack is more practical, both now and for future maintenance. Should I go with Razor Pages + HTMX + Hydro or ASP.NET API + Svelte 5 + SMUI? My main priorities are to create the MVP quickly, ensure low maintenance, and allow for easy feature additions or interactivity later on. Which option would you recommend and why?
4 Answers
If you've got some experience with Svelte, I'd recommend going for SvelteKit combined with BetterAuth, Drizzle, and Shadcn-Svelte. It'll streamline your work and let you add features easily down the line.
Honestly, it really comes down to what you're most comfortable working with. If speed is your main goal, stick with what you know best; it’ll save you a lot of time.
Have you considered React? The nature of your project plays a huge role in this decision. I'm a big fan of Next.js and Nest.js—if you're just starting, a React/Node.js stack is generally a safe bet.
I’d suggest Blazor. It could speed up your development process significantly since it integrates well with .NET. If you're already familiar with it, it might be the fastest route to get your MVP up and running.
I tried Blazor recently but found it a bit risky. Its reliance on SignalR for server-side state management feels like it could create performance issues, especially with traffic spikes on a single VPS.
I’d argue that SvelteKit is way better! It comes with fewer complications and is very developer-friendly.