In about 17 days (I hope I m counting correctly), I ll be re-launching the mobile app, and now I m wondering how much the Product Hunt community will try it out.
I spend 100% of my time on a desktop on this platform.
But the majority of the population is mobile-only.
Yep, we aren't smoking our socks either; there's a difference between vibe (vulnerabilities in beta environment) coding and what we're doing. We pre-architect the schema of the entire project, develop detailed PRDs, QA the tasks that come out of that, select testing criteria and frameworks and only then hand over to Cascade.
We build in a lot of qa in the agentic process and we also run codeQL and dependabot on the repo. This way, we're doing the heavy thinking while Cascade does the heavy typing. It's worked so far.......
So, because we decided quite late on, to do the #buildinpublic, I'm going to review our historic notes, emails, and chats, then provide a week-by-week post dealing with the interesting elements for that week. I'm not sure if that's the right way to do it but here's hoping.
I'm not sure whether it's ok to admit Myaigi started as a muse........ I feel it should've been something bigger and a better story, but well, that's what it is.
So the way this all started was around a Friday night beer.
We've been working on Myaigi for a few months now and had planned to launch in mid jan. We're obviously late with that because........founders and product but we're close. Part of our launch plan involved a consult with Chris and initially we assumed it'd be pretty standard but it was actually a very free flowing session where we got huge value out of his critiques (very brutal critiques; he called our landing page thirsty :) and figured that we needed to do a mini pivot. Part of his other advice was to #buildinpublic so here goes.
