Did I Break My “No Build in Public” Rule? What Actually Happened

Last October, I declared that I wouldn’t be building my SaaS app in public. Since then, I’ve been posting videos of me building low-level SaaS code with the Drogon C++ framework.

So… what gives? Did I lie? Did I change my mind?

I say no. Here’s my case — you can decide for yourself.

What Am I Working On?

Let me ask you this: what SaaS app am I working on? I didn’t mention it once in any of those videos. Go back and check if you want…

That’s intentional. Right now, I’m not writing a SaaS app at all. I’m writing a framework or platform, on top of which I’ll launch not one, but multiple SaaS apps. Every SaaS app needs the same basics: authentication, sending emails, billing, a UI, etc. Writing that code is a lot of work, so I plan to write it once, and use it many times.

I’m sharing the process with you, knowing full well that it’ll do NOTHING to market my first planned app. Why? Because the target market isn’t interested in how SaaS products are built. So, everything I said in that original “not building in public” video still stands.

I’ve decided to document the SaaS framework building process for fun, and to keep this blog (and associated YouTube channel) active.

Make sure you subscribe, because there will be more coming.

Right now I have basic login, and even translations working (see below). Normally I’d tell you not to waste time with multi-language support this early. But, my app needs it sooner rather than later. And, in my experience adding locale support after the fact is a real pain – especially for apps that serve multiple users in different languages, simultaneously. I’ve taken care of it now, so that it doesn’t turn into a high-maintenance bitch later…

Did I Break My No Build In Public Rule Time 0 01 4320

That’s it for now. See you next time, when I’ve implemented the next core feature.

Leave a Comment

Your email address will not be published. Required fields are marked *

 


Shopping Cart
Scroll to Top