HouseFlow Planner App Update #29042025: Sometimes, you underestimate the time it takes to complete a task, but implementing logging and a custom transporter has taken too long. It is taking longer than I was expecting to launch to early adopters. Join the wait list [HouseFlow

It turns out that my approach to building the HouseFlow Planner App was not ideal because I followed the waterfall methodology. From now on, I am building small parts simultaneously instead of a big chunk as I was doing. Join the journey. #buildinpublic #saas #indiehacker

Time to dust off my UNI notes to design the database for [Houseflow Planner]( https://t.co/yTApsRIlIx). I am starting with conceptual design, then I'll create logical and physical design. By then, I will also have a normalised database schema. Here are my notes so far. Join

Houseflow Planner App Update #020425: In my first post about https://t.co/yTApsRIlIx, I said I would share the challenges I face during development. Well, those last two days were spent fighting #GitHub Actions. It turns out I did not give the docker runner account a shell to

Houseflow Planner App Update #290325: The landing page for the https://t.co/yTApsRIlIx app is live. Today, I polished a few things and added a custom 404 page for unknown paths. Next, I will design the API and database schema. Join the waitlist. #buildinpublic

My landing page, https://t.co/yTApsRIlIx, went live yesterday, and here is how they have tried to catch me lacking. Thankfully, I have known for the longest time not to put sensitive info at my project's root.

Houseflow Planner App Update #260325: Just deployed the first version of the landing page for https://t.co/yTApsRIlIx. However, it seems like some Tailwind CSS classes are not rendered correctly, but that is a job for another day. Follow for updates! #buildinpublic

Houseflow Planner App Update #250325: I just added the GDPR-friendly analytics #goatcounter to my landing page. Also, I have added #recaptcha and wired the email marketing platform for early users. Going live in a few days. Follow for updates! #buildinpublic

Houseflow Planner App Update #170325: I have finished the UI for the landing page and it should go live soon. Next, I will wire the email marketing platform or provision my own db to save the early subs' emails. Follow for updates! #buildinpublic #IndieDev

Houseflow Planner App Update: I have implemented a couple of sections of the beta landing page. See how it is coming along. Follow me for updates! #buildinpublic

I just got into my first battle with Angular. What does this even mean if I already have the attributes required?

For JavaScript developers. What is printed and why? #javascript #WebDevelopment #programming

Houseflow Planner Update: To move faster I will settle for the current landing page I've designed and adapted to mobile. Any feedback on the current design is welcome. #Penpot is great and has come a long way. Follow the journey! #buildinpublic

HouseFlow Planner Progress update: I just finished the first draft of the landing page. Tomorrow, I’ll start implementing it. This app will you to share calendars, medication reminders and shopping lists with family members. follow along as #BuildInPublic!

I have selected the colour I will use on my app [HouseFlow Planner]( https://t.co/k1q0fPQSrr). I am still working on my design skills. I will work on the landing page design (using #Penpot) today and share it when it's done. #UIDesign #buildinpublic #penpot #Webdesign

This app solves real problems that I face often. If you’re interested in this sort of thing or just want to see a product come to life, follow along. You can also be the first one to try the app for FREE by joining the waiting list https://t.co/k1q0fPQSrr #buildinpublic #SaaS

I’m taking an API-first approach, defining everything with OpenAPI v3. So that I can auto-generate API docs just in case. Also, if anyone knows which #golang framework is better at generating OpenAPI documentation from the endpoints would be nice.

Before launching the app, I’m designing a custom landing page to get early adopters and let it be known to anyone who might find it useful. Regardless if others want it or not I will use it.