Subscribe
Sign in
Launched on March 13th, 2025
Launched on February 13th, 2025
Hey p/bolt-new community,
I recently started building Couples Hub (https://coupleshub.io/) a React-based application and Next.js based landing page using Bolt.new. Couples Hub is a product of my hobby brand "MD Meets Techie" which I've run for the past four years, creating digital products specifically for couples. Given my technical background, diving into Bolt.new was kind of a fun experiment (esp given how drab and boring my day job is). I noted several challenges along the way and I thought I'll share a few tips on what I've learned thus far.
Feel free to add your insights or ask questions to make this post even more comprehensive! By no means do I claim to be an expert on anything mentioned below so I welcome critique as well :)
General Advice & Managing Your Bolt Codebase
Bolt works well initially but can struggle as your codebase grows beyond roughly 100-200 prompts. Keeping your components short (under 300 lines each) helps manage complexity and Bolt's understanding of your code.
Bolt uses the Claude Sonnet 3.7 model, which tends to be overly creative, suggesting unnecessarily complex solutions. Explicitly instruct Bolt, "I value simplicity and prefer straightforward implementations," to guide it towards simpler, practical solutions.
Giving Bolt ambiguous prompts with multiple possible implementations often results in it choosing an unnecessarily scalable (and complex) approach that it might struggle to complete. Simpler is almost always better in Bolt.
Maintaining markdown files that document your app’s current data model, product roadmap, and overall vision helps Bolt make more informed decisions—especially in the early and mid stages of development. (Once you're moving toward production, these references become less essential.)
Tactical Prompting Tips
Explicitly instruct Bolt with phrases like, "Do not make code changes," during brainstorming sessions to prevent it from immediately jumping into code. This has been helpful for me when I just want to talk through a problem.
Keeping a secondary AI assistant (like ChatGPT or Claude) available, and feeding it markdown reference files from your Bolt project, provides clearer, context-driven advice. This is especially useful in the later stages of a project when Bolt is often overwhelmed by the complexity of your codebase.
When you're stuck, using terms like "think holistically" or "weigh the pros and cons in your approach" in your prompts encourages Bolt to approach problems more broadly, and has magically helped me break through blockages about 80% of the time.
Authentication
Implement "Sign in with Google" as your primary authentication method, covering approximately 80-85% of typical user bases.
Additional authentication providers like Microsoft or Apple usually add minimal extra coverage and are rarely necessary unless specifically required by your audience.
Consider "Sign in with GitHub" for applications targeting developers or tech-savvy audiences.
UI Considerations
I often find the hero section for my landing page from https://21st.dev/ and Bolt is able to handle the implementation fairly seamlessly.
Bolt has the tendency to make landing page sections overly "Boxy". Just prompt it to give you another layout.
UX Considerations
Be prepared to iterate multiple times on UX with Bolt. Initial versions are rarely perfect but improve significantly with continuous feedback and adjustments.
Bolt often struggles with intuitive UX layouts. For instance, it's helpful to consider things like Hick’s Law (fewer choices = quicker decisions) and that users typically notice elements placed in the top-left first.
Regularly seek external feedback from friends, users, or tools like ChatGPT or Claude to brainstorm and refine your UX design.
Learning basic UX design principles significantly helps improve how intuitively your app presents information to users.
Don't blindly use the suggested landing page copy recommended by Bolt. Iterate separately with ChatGPT or Clause based on the persona you're targeting. Bolt also tends to assume your app is already in production with "millions of users" - so you might want to make double check your copy to make sure it's not not blatantly lying.
Adding a Blog to Your Landing Page
For scalable blogging on your landing page, I've experimented with solutions like Storyblok and Contentful but found them overly complex and more tailored towards marketers.
I've had success converting Markdown directly to blogs, maintaining simplicity and scalability. If you need specific steps on how to achieve this, please reach out directly.
I also figured out a hack to auto-generate and post my blog using a cron job that calls an API on a set schedule. It’s a pretty loaded topic, so I’ll share more details in a future post :)
General SEO Tips
Don't overthink this too much. Just ask Bolt to take the necessary steps to implement SEO best practices. Just make sure you're asking it to do all things step-by-step rather than everything in one go.
Custom CMS and Data Management
You can easily build a custom content management system within your Bolt application to preload and manage data in your Supabase database.
Bolt can quickly create interfaces for uploading CSV or Excel files directly into your database, a helpful feature for applications requiring initial or bulk data uploads.
Email Integration (Using SendGrid)
Bolt doesn't support native email capabilities yet. I successfully integrated SendGrid to handle user-related emails such as welcome messages and notifications.
There's a learning curve, but manageable—I learned how to do this one one productive Saturday morning. If you're struggling or need guidance, feel free to reach out directly - it's a fairly loaded topic.
Analytics & Building Your Own Admin Tools
Easily integrate Google Analytics by simply inputting your measurement ID into Bolt for basic user insights. Remember to ask it to track key events across your application.
Alternatively, build your own internal admin-only analytics dashboard for more detailed engagement tracking, such as daily and monthly active users, and specific engagement metrics.
Once your app is live, monitor feature that are getting used the most and proactively prune features that are no longer needed. This keeps your codebase clean, your UX sharper, and helps avoid a bloated app.
Performance & Security
Before implementing complex features (for example: a SendGrid integration), always explicitly ask Bolt about secure and efficient methods to do so. For example, prompt it with: "What’s a secure but simple way to implement this? Do not make code changes yet"
Bolt often defaults to generating numerous Supabase hooks, which may impact performance negatively. Clearly distinguish when to use backend APIs versus Bolt's default Supabase hooks to maintain optimal performance and security.
Hosting, Domain, and Deployment
Do not embed API secrets like OpenAI keys directly into your client-side code. Always use Supabase Edge Functions (or Netlify functions or any other API solution) to handle these securely.
Initially, I created a separate Netlify project exclusively for server-side functions before Supabase Edge Functions became available. Now, I strongly recommend using Supabase Edge Functions for backend APIs, especially to securely handle sensitive integrations like OpenAI APIs.
Supabase Edge Functions make it easier than ever to run cron jobs and call external APIs like OpenAI in a secure and maintainable way. This significantly reduces the need for workarounds like separate Netlify functions.
Use Namecheap for inexpensive domains (~$10-$15) and link them to Netlify for straightforward hosting.
Handling Roadblocks
There are two main ways to handle roadblocks with Bolt:
Export and Debug Elsewhere: Export your project to Cursor or Windsurf. Tokens on Cursor and Windsurf are significantly cheaper than Bolt, making experimentation and debugging financially feasible. These tools also allow you to target specific files that you suspect are causing issues. Once you've found the issue and a potential fix, have Cursor or Windsurf craft a detailed prompt that you can directly feed back into Bolt to implement the solution. You don’t have to re-import the full project—just use the prompt.
Rollback Approach: Bolt has built-in backups allowing you to revert to a previous stable state. Rollbacks, although frustrating, can save significant time compared to debugging complex issues when Bolt is overwhelmed. Just keep in mind that while Bolt can rollback code, it cannot rollback your Supabase database changes, so plan accordingly when deciding to fork an earlier version.** Bolt has built-in backups allowing you to revert to a previous stable state. Rollbacks, although frustrating, can save significant time compared to debugging complex issues when Bolt is overwhelmed.
While you can target specific files within Bolt, I’ve found it less effective than doing so in Cursor or Windsurf when debugging issues.
Advice for Fellow Learners (Pseudo-Technical Founders)
Bolt is excellent for users with partial technical knowledge, such as product managers, technical founders, or students. Treat it as a knowledgeable yet inexperienced junior developer; guide its decisions explicitly, especially regarding complex integrations.
Don’t expect this post (or any one guide) to teach you everything—your own intuition and learning will only sharpen as you build. Just start building.
Unfortunately, I've limited advice to give on marketing and monetization as those are things I'm still figuring out. If anyone has advice on creating social media posts via code generation, please let me know!
One final note: Bolt is shipping updates at an insane pace. Everything I've written here might become partially or completely obsolete in the next 6–8 weeks. So if you're reading this later, take all of this with a grain of salt! I'm still learning, so please feel free to share your experiences or ask directly for more specifics! :)
I hope this detailed breakdown helps those building or considering Bolt! I'm still learning, so please feel free to share your experiences or ask directly for more specifics.
Happy building!
Tonight, we are hosting a small hackathon in Phoenix in partnership with @bolt.new! All the hackers get free credits to build whatever they can imagine during the hackathon. Thanks Bolt for the hookup! In this forum thread, all the hackers will submit their projects and vote on their favorite one (they can't vote on their own).
The top project will get hunted on @Product Hunt by me! If you want to follow along, come back to this thread in an hour or so and the submissions will start rolling in.
Feel free to vote yourself if you feel compelled even if you aren't here hacking with us.
Let the hacking begin!!!!!!
🚀 Just built my entire website — helloaria.in — using bolt.new, and I’m seriously impressed.
Let me walk you through the journey 🧵👇
1/
I started using @boltnew as an experiment… but it quickly turned into my go-to platform. Within hours, I had a live prototype. Within 3 days, a full-blown website. The speed is unreal.
✨Here’s a sneak peek of helloaria.in:
2/
The UI building experience is 🔥
You can design, prompt, deploy — all in one place. No boilerplate, no setup stress. Just flow.
It felt like Figma + code + hosting had a baby 🤯
3/
That said… as much as I loved it, the token usage caught up with me 😅
By the time I fully shaped helloaria.in, I had used around 50M tokens — and yeah, it got a bit expensive for me as a solo founder.
4/
Bolt is changing the way we build.
If you’re a maker, a founder, or even just curious about no-code/AI-code — you’ve got to try it at least once.
🌐 Check out the final site: helloaria.in
Huge shoutout to the team behind @bolt.new 🙌
Excited to see where this goes next. PS: My site is still under construction 🚧
