I kept buying furniture I thought would look great, only to realize it didn't fit the space at all. Every design tool I tried felt like homework. I just wanted to say "design my dining room, replace with this table I want to buy"
We now look at actual code less and less. What does your developer experience look like now that we are getting closer to a non-IDE world? I am using @Superset and am loving it so far. In my corporate job, I have 10-15 repos going at once and it's all super organized. What are you all using?
Hi everyone, when not busy in the corporate world building software, I spend time trying to get as many side projects as possible to stick. This is the first one that I am personally addicted to myself. I built Lattice AI because I kept buying furniture that never looked right in my home, now I can "preview" furniture before I buy it! As an added benefit, I found that the AI generated designs also do a fantastic job at giving styling ideas.
The idea came from pure frustration. Every time I tried to cook something new, I'd open a recipe site and get hit with pop-ups, ads, and a 2,000 word life story before seeing a single ingredient.
It featured individuals who managed to build significant profit while running their businesses solo, without employees. Until now, I ve seen these more as exceptions rather than the norm.
I ve been spending more time vibe coding recently, and I ve started to question something I initially took for granted. Most of the conversation around vibe coding is about speed. Like how quickly you can go from idea to prototype, or how fast you can iterate. And to be fair, that part is real. The barrier to building has clearly dropped.
But the more I use these tools, the more it feels like speed isn t the limiting factor anymore.
The real constraint seems to be taste.
what do you choose to build?
what do you keep vs discard?
what actually feels right vs just working ?
what is genuinely useful vs just impressive in a demo?
I've built my product around traditional SaaS pricing (monthly tiers), but I m starting to wonder if that model is getting outdated, especially with more AI-powered and compute-heavy tools entering the market. That shift requires real architectural changes, instrumentation, metering, billing logic, and UI changes, not just pricing tweaks. It s something I m starting to seriously think about for my own product.
In particular, AI usage has real COGs (every prompt costs money), and I m seeing more platforms experimenting with usage-based models, or hybrids like SaaS base + usage + overage.
For those of you building AI or compute-intensive tools:
I might be missing some but I've been pretty much in love with @Lovable, @Cursor, @bolt.new and have been trying to use @Replit more and I honestly haven't touched @BASE44 too much but have heard good things. @chrismessina has nudged me to use @Windsurf for whenever I build another Raycast Extension! Currently I use: - @bolt.new / @Lovable - @Cursor - @Warp Curious what everyone thinks is the top one so far!
