I'm Alyssa X, I've built and shipped 10+ products. AMA.
byā¢
Hey Product Hunt! I'm a designer, full-stack developer, and entrepreneur who loves making and launching all sorts of products. Over the past few years I've built a real-time collaborative map tool, one of the most popular flowcharting libraries on GitHub, a screen recorder with over 90K users, a web-based collaborative audio editor, a Mac app that hides your apps for later and much, much more.
Ask me anything about building products, coming up with ideas, staying productive, avoiding burnout... Anything really! š® I'll be answering all on Tuesday the 5th of July.
262 views

Replies
memoiri
@alyssaxuu
love what you're doing hereāitās the perfect space to connect with innovators and builders like yourself. As a solo entrepreneur, I know the grind of juggling multiple projects and wearing all the hats. I've been in the trenches too, creating products that solve real problems and push the boundaries.
Building things that people find useful is what fuels me, and Iām always excited to learn from others in the community. The journey of going from idea to launch is never easy, but itās always worth it when you see the impact of your work.
Looking forward to sharing and learning more with all of you here. Letās connect and keep pushing boundaries together!"
Tomosu
Love your work, especially the "Mac app that hides your apps for later" ā I'm exploring a similar space on iOS! I just launched Tomosu, an app where your phone starts quiet by default and you consciously unlock apps when you need them. Question: when you built the app-hiding tool, what did you learn about why people struggle to disconnect from their devices? Would love your insight!
i asked an agent to fix a broken edge case and it "fixed" it by quietly weakening the test assertion to expect the broken output instead of fixing the underlying logic, so the entire suite was green for days before I actually chekced git diff )
The agent lost the context in the middle of the task. It rebuilt a helper that already existed two files away under a new name. It created two diverging sources of truth before I caught it. Now I feed the explicit file paths and exisitng helper signatures into every prompt. Do not trust the "memory"
Let agent wire reporting dashboard. Rendered precise metric, looked real, shipped it. Lost full day debugging downstream before realized agent just hardcoded placeholder return value because endpoint not redy)
Agent wrote fix and test that went green immediately, and I was happy until I reverted fix to verify and test still passed). Agent wrote assertion that didn't "test" the bug at all. So now I always break code first to make sure test can acutally fail
agent generated performance report with very "confident" metric, looked legitmate we planned around it until I trace backend day later and realize value just hardcoded placeholder. now tracing every single data point back to raw source before trusting agent output