AMA! I'm Brandon Bayer, the creator of Blitz.js which is a Rails-like framework for monolithic, fullstack React Apps
Hey IH! I'm the creator of Blitz.js, and we just launched our official beta release last week on the 1 year launch anniversary!
I've been a long time indie hacker. My first successful product was Storeo for Instagram which yielded a total of $61,000 profit for my biz partner and me.
I then launched an affiliate site called The Gluten Project, but it failed because it was too small a nich and I couldn't convince industry partners to work with me.
So next I started working on Acorn Bookmark Manager off and on until February 2020. In February 2020, I had the idea for Blitz.js and quickly abandoned the bookmark manager to work on Blitz because I knew it had WAY more potential for impact.
Now here we are 1 year later and Blitz has almost 7,000 Github stars and 5,000 weekly npm downloads.
I currently bring in $1,500/month from Github sponsorships. Next I'm going to be releasing video screencasts for the $15/month sponsorship tier which should increase my sponsorship income. And I also have some other business ideas to start on top of Blitz (similar to the Laravel approach).
Got any questions about me or Blitz? Ask away!
Hi thanks for doing the AMA. I am really excited for Blitz and Redwood. The FS jamstack is an exciting new frontier. I have a few questions. Do you have a way to do many to many relationships with Blitz? Do you have an example of a Blitz app using auth with a forgot password implementation? When do you plan to release 1.0 and do you expect to have many breaking changes before then? Thanks.
Yes, you can do easily do many-to-many with Prisma (see the prisma docs on this)
And yes, all new blitz apps come with forgot password flow already set up for you (run
npx blitz new myAppto test it out)We expect a 1.0 release around April. We don't expect many breaking changes, but likely there will be a few minimal ones.
Hey there! Blitz looks exactly what I'm looking for when building nextjs apps. At some point the frontend work is done, and the back-end experience is suboptimal. Too many stuff to configure. I really don't have a question, I'm very glad to watch the project mature and hopefully I can rock it in production.
Cool, let me know how it goes!