We hit #1 on Product Hunt, then our infra nearly gave out, here's what we learnt and upgraded.

A couple of weeks ago, I remember stressing over the launch with my cofounder because one random fine day I told him, "btw... I scheduled a launch for 23rd next week" and we were not at all prepared for what was about to come <insert hysterical laughter>

We had the month watching other launches and trying to figure out they did different to get a top launch, visiting product hunt every day and studying the launches, who the makers were, what their product did, their positioning, creatives and more.

There is a huge difference between observing launches and actually prepping for your launch.

Construct hit #1 rank when the leaderboard points were revealed, and consistently held the position of #1 Product of the Day throughout the remaining 20 hours, received 4000+ visitors, tripled the number of signups and usage for platform, and it nearly broke our production!!

This launch caused a substantial amount of usage and gave us a great deal of information about how people use our platform, what UIUX issues they have, user behaviour, and things they dont like.

Surprisingly 22% of the users were on mobile, which we did not expect (a web OS is meant to be used from a desktop browser anyway), although we did make the web OS responsive and optimised for mobile it still wasnt enough, the huge variety of mobile devices handle networking, live sockets, background sessions very differently from each other, which we didnot expect, and it broke things we didn't even imaging could break.

Since then we have shipped 60+ commits to fix all of those issues and still continue to ship at speed.

• Made chats recover after a mobile browser freezes or suspends the tab.

• Made unfinished agent turns continue reliably instead of silently stopping.

• Added account-wide live activity, so you can see work running anywhere.

• Fixed new-chat drafts, slash commands, conversation switching, and scroll behavior.

• Improved overload handling so a busy agent reports an understandable limit instead of throwing a mysterious error.

• Reduced noisy production alerts and added more useful health checks.

• Overhauled onboarding based on where new users were getting stuck.

• Shipped a status page for better monitoring and reporting

We also made one deliberately unglamorous decision to make the complete Construct OS desktop-only while we work toward proper native mobile experiences. Making the desktop fit inside a phone-shaped rectangle was not the same as building something we were proud to call mobile.

The launch reminded us that production traffic does more than test infrastructure. It tests every assumption you made about who your users are, what they will try, and which parts of the product they will or will not tolerate.

Launch day is not our finish line. It is the first time your product meets people who do not know how it is supposed to be used.

Huge thanks to everyone who supported us, tried Construct, reported something confusing, or accidentally discovered a new way to break it.

We’re shipping quickly with far better information than we had before August 23.
If you want to follow the journey, keep up with us on X (@use_construct) or Discord as we share what we’re building and learning.

We’re also opening our pre-seed round and looking for our first checks. If you invest in ambitious AI infrastructure, products and the future of work or know someone who does, we’d love an introduction.

Following, sharing, feedback, intros, and support of any kind all go a long way. Feel free to reach out to us directly at hello@construct.computer, we read all mails

Best,

Ankush

Cofounder @ ConstructComputer