2
3 Comments

Why FastReact?

For the last 2 years, I’ve shipped multiple AI SaaS projects with SvelteKit + FastAPI and backend + SPA pattern has worked really well. I decided to make this a SaaS starter kit and become my first customer for my future projects and built FastSvelte (https://fastsvelte.dev/).

I wasn't expecting any sales but sold 3 licenses and got positive feedback from customers. That motivated me to build FastReact due to React's popularity.

I poured my 15+ years of development experience into this. Both FastSvelte and FastReact share the same FastAPI backend.

Recenty, I've added AI-SaaS related features like token metering and billing. Also a fully working, sample AI-pilot feature.

I am really proud of both projects. I've spend around 8 months so far on building these.

Some technical details: Backend does the heavy-lifting. Frontend is designed as a presentation layer with minimal business logic. Backend uses a 3-layered (data, service, api) architecture and dependency injection, similar to Spring Boot but. I really gave a lot of thought on how to organize the backend. As a result, Claude Code can understand the codebase really well and and easily add a new feature by applying the existing pattern. Docs contain much more details that are free to access: https://docs.fastreact.dev

posted toAvatar for product FastReact
FastReact
  1. 2

    One thing I'd keep testing is whether developers are buying a React starter kit or buying a development philosophy.

    The architecture you've described seems designed to make future changes predictable—for both humans and AI. If that's the real advantage, I'd lean into that outcome rather than the framework itself. React may attract attention, but maintainability is what people keep paying for.

    1. 1

      I will figure that out over time as I have more customers. But maintainability is very important for as the backend is and will be the base for my own projects.

      1. 1

        That makes sense.

        Your reply gave me one thought about building a framework for yourself first and for customers second. I'd rather explain it with your product as the context than try to condense it into a thread.

        If you're interested, what's the best email to reach you on?