Building Scrabl in public — month 1.
Waitlist is live. Backend deployed. Emails are going out. Here's everything that went wrong (and right) in my first month building this alone.
Month one of building Scrabl in public taught me one simple thing: transparency builds trust faster than polish. People wanted to see the process, not just the final product.
I launched the waitlist, wrote the first emails, and set up the backend so the product could scale when creators signed up. There were server errors, missed deploys, and a lot of late-night debugging, but the feedback made it worth the effort.
The biggest win: the tiny details matter. A faster waitlist flow, clearer feature language, and a more honest story helped the right people sign up first. Those are the creators who will shape Scrabl's voice with me.
I also learned that building in public is not the same as building on a public timeline. It means sharing what matters, what changes, and why — not just every little update. So I'm focusing on the lessons that will make the product better for creators, not the noise.
Next month, I'm shipping the first voice DNA improvements, stronger hashtag support, and a smarter screenshot workflow. For now: thanks for being here, and for helping me build something that actually feels different.