A react framework for indie hackers
As someone who is constantly building new products and testing out new ideas, it's often more important to me how efficient the tech i'm using is as opposed to how good it is. Obviously good tech still matters, but the last thing I want to be doing is getting lost in infrastructure or documentation. I want to be delivering value. Going from zero to one... quickly!
Over the past two months I've been seeing more and more people express how complex it is to build with React these days and I tended to agree. The problem is, React has barely changed over the years and still provides just a handful of elegant primitives that can be used to build absolutely anything you can imagine. It was the meta-frameworks that we all use that had gotten complicated.
At this point, I was convinced that it would be possible for me to build a framework on top of React that was both minimal and powerful, and this is when Firebolt was born.
Firebolt is an ultra lightweight framework for building full-stack web apps using React. Most importantly, Firebolt introduces two shiny new things to the React framework eco-system that I personally love because it is both simple and powerful:
-
Unified Routes: A single directory for all pages, layouts, assets and endpoints. This is super intuitive and keeps all things accessible by a URL in a single place instead of spread out across different directories.
-
Composability: Any component in your app can fetch or interact with data on the server (ie a database). This paired with CSS-in-JS means you build entire platforms using JUST components. This is absolutely mind boggling once you try it.
If you'd like to check it out, you find it here: https://firebolt.dev
If you have any questions or suggestions, feel free to comment below or find me on X 🫡
From $0 to $1K MRR in 8 Months: Bootstrapping Habit Pixel as a Solo Dev
How to acquire your first users for $0?
Share your project, and I’ll tell you how to get your first dedicated users
Revenue-Share SaaS MVP - Stripe + Automation
It would be helpful to know what are the exact pain points, perhaps list them in bullet points, and give examples. Also simplicity might also make me think that it's limited in features.
Also, with AI, perhaps your issue is less of an issue. For example, if you don't know how to do something with react or next.js, you can just ask chatGPT to show you how instead of getting lost in docs.
Looks promising, I'll try it. Thank you Ashxn
The project is useful. I will try it immediately. Thank you Ashxn.
This is such a nice project. I immediately forked it, i want to have a look at the source code in my free time.
I think it's a nice idea, if it works for you, it can definitely work for someone else.
I also have something like this but as a suite of function and components for Remix.
What are its advantages compared to Next.js? I mean, it would be better if you could write more about its advantages compared to other frameworks on your webpage.
That’s fair. It’s actually quite similar to both Next and Remix but it achieves this with a much more minimal and intuitive api.
This is done by focusing on the core of what people actually need to be productive, instead of over complicating it just to say “yeah it works with all 29 ways you might want to use CSS” or “it runs on node, bun, edge, workers, everywhere”.
You end up spending less time wrangling the docs when the framework is so simple that you barely need any docs after reading them once.
Thanks for your feedback, I’m going to try make this a bit clearer!
This comment was deleted 2 years ago.