Over the last year, I ve been experimenting more with local-first patterns , apps that prioritize offline functionality and sync later instead of depending on constant server calls.
What used to feel experimental now feels surprisingly stable. Faster UI, fewer loading states, and a smoother user experience overall.
I rebuilt a small side project recently with a local-first approach, and the difference in responsiveness was noticeable. But it also introduced new challenges around conflict resolution and state consistency.
I keep seeing the same pattern across early-stage teams:
the MVP works until it really doesn t.
For many founders, the hardest part isn t getting something online it s everything that comes after: infra that cracks under real users code that no dev wants to touch rewriting the whole stack AI-built projects no one can maintain the moment you realize your prototype isn t a product
Hi everyone, CEO of Bolt here! Super excited to open up about our journey and offer any learnings and stories I can to help other makers on their journey. Within a span of 2 months we've grown to $20M in revenue and were recently featured in NYT as paving the way for vibe coding.
Hello everyone, Sumit here from the Himalayas. I hope everyone is having a relaxed weekend. My workflow with vibe coding has settled pretty well as I get more and more time out of desk while Claude Code builds the software. I wanted to offer any assistance to fellow founders. I have been vibe coding full-time for a little over 4 weeks. Wrote about it here. Please share your tools, or workflow and in particular what is not working for you. What is frustrating you in building software with vibe coding?
Every time I vibe code there is always this huge lift that I constantly have to go through. Authentication, billing, password resets, emails, signup, waitlist, landing page and when it s all said done and the app is ready then comes the marketing, the blogging, the social media automation, the product hunt launch etc etc etc . So much repetitive crap that I have to do just to get a simple app up and running. How do you guys handle all this?
Since I am a coder and a hammer sees everything as a nail, I decided to create all this code as a template so I can jump into building an app right away. There is actually a lot more than what I mentioned above e.g customer support, chat, roadmap for building in public, email flows and more coming.
if i use claude or codex, i constantly am screen capping to show bad padding / alignment / whatever. is there a defacto way to let claude or codex tool call to see the browser or render a page for themselves?
AI dev tools are moving stupid fast. Every few weeks, there s a new must-use. Some stick. Most don t.
Some vibe coders are developing full products with @ChatGPT by OpenAI+ @Replit. Others swear by @Cursor + @Claude by Anthropic . A few are mixing @Lovable , @v0 by Vercel , and @bolt.new . New and shipping way faster than expected.
I ve been refining my own vibe stack lately. Building with @Google Antigravity at the core. It keeps the flow clean when things get messy.
Recently stumbled across this Cursor pro-tip from Ian Nuttall on X: "1. ask it to recommend a folder structure
2. ask it to actually create the folder/files based on that this makes it 10x easier for me to get started and Cursor is more accurate using codebase cos it knows where to update files."
That got me thinking, what other pro tips are people using to generate better code, ship faster, organise your space better, etc. Drop em below:
