othmanosx

Well... I guess squiggly lines are more useful now than ever with agents shipping tons of code every day

Just run the /insights command on your Claude and see what it gives you, you'd be shocked what it knows about you just talking to it.

Looks cool, goes into flames when I tick a few more things

Virtualization missing, that's commonly a difficult task to nail on a messages list. another thing is mounting and unmounting complex elements efficiently, that was part of why switching threads or sessions felt heavy.

btw, native apps can feel heavy and janky too if not properly optimized for large lists. it's just a matter of shipping a good app that's battle tested with large data sets

That's why they have an "auto" mode that you should be using over the "bypass permissions". no matter how many guardrails you put on it. AI is not deterministic, so sometimes it likes to do whatever it wants.

I can’t say this with certainty, but ever since I started building it, I’ve noticed updates and fixes that quietly addressed some of the workarounds I relied on for certain features. It almost felt like they were aware of the gaps I was tapping into. Considering they review the extension, you could read that as a subtle signal… but that might just be me connecting dots that aren’t really there.

For years, the Meet chat barely changed. It stayed minimal and uninspiring. So seeing Google suddenly invest attention in it caught me off guard. Maybe I’m overthinking it. Or maybe they did notice that some users were frustrated enough to start building their own tools just to make the experience better.

Thanks! I appreciate the perspective. You're absolutely right; failure isn’t always black and white, and I probably framed it too harshly.

To clarify, I don’t think the problem itself failed, there’s definitely demand for better workflow aggregation. Like you said, companies have succeeded in that space. But in my case, the way I approached it, the execution, timing, and maybe even the target audience, didn't gain traction. I took the lack of interest as a signal that my specific take on the solution wasn’t compelling enough, at least in the way I was presenting it.

Maybe a different approach could have worked, and in hindsight, I could’ve explored other ways to validate it instead of relying on a newsletter signup as my primary gauge. That’s a great point.

And yeah, the original problem does exist. I guess my real lesson was not just about assuming a problem existed but making sure I was the right person to solve it in a way that people actually wanted.

If you’re curious, the old landing page is still up: https://brieflytics.vercel.app/. I’d love any thoughts on what I could have done differently there.

Also, my new project, GM Pro, is tackling a problem I validated firsthand—improving Google Meet with features like better chat UI, reactions, persisted messages, and transcriptions. You can check it out here: https://chromewebstore.google.com/detail/gm-pro/bfmgohplnhbl....

I've also seen some competition in the Google Meet extensions space, products like FellowApp, Spinach, and others, so I already know the idea is valid and there's a market for it

Would love to hear any feedback, whether on the old idea, the new one, or just thoughts on startup validation in general!

Glad you're enjoying it! Dark mode was a must-have for me too. Let me know if you run into any issues or have ideas for new features.

Always looking to improve GM Pro!