Built with Bolt?
Fixes for the problems Bolt apps run into once real users arrive, each checked against Bolt’s own documentation. Start with taking a Bolt app to production.
Bolt app slow: is it the preview, the published site or the database?First work out which part is slow. The Bolt preview runs a development server inside your browser using WebContainers, so it depends on your computer and is slower than the published build. If the published site is slow, look at image weight, database queries and row level security policies, and check the Logs page within the hour.Bolt auth not working: fixing sign-in, Google login and reset emailsMost Bolt login problems trace back to four things: the Site URL and URI allow list in the database's Authentication settings, testing Google sign-in inside the preview instead of the published site, the default limit of 2 auth emails per hour, and table policies that never check who is signed in. Fix them in that order.Bolt database issues: permission errors, paused databases and missing dataMost Bolt database issues come from how Bolt Cloud behaves, not broken code. New tables are private by default since 30 October 2026, unpublished projects pause after six days of low use, restoring a version rolls back code but not the database, and duplicates start with an empty copy. Find which one you hit, then fix permissions, restart, or realign the schema.Bolt mobile layout broken: fixing a Bolt web app on phones, and when you need ExpoCheck the layout in Bolt's Responsive mode and on a real phone using the published site, then fix overflow, fixed widths, viewport height and tap targets in the code. If you need an app-store app rather than a website, Bolt's docs say web projects don't easily switch to mobile, so start an Expo project with the words mobile app in the first prompt.Bolt SEO: why your Bolt site isn't showing up in Google and how to fix itIf your Bolt project is a client-rendered Vite app, crawlers that don't run JavaScript see one near-empty HTML file with the same title on every URL. Publish publicly on a custom domain, use real paths instead of #/ URLs, give each route its own title and description, add robots.txt and a sitemap in public/, and prerender the pages that need to rank.Bolt Stripe payments: setting up checkout that works in productionBolt has a built-in Stripe integration. Add login and a Bolt or Supabase database first, then click your project name, Integrations, Stripe, paste a test secret key and pick your products. Bolt creates the server functions for checkout and webhooks. Test on the published site with Stripe test cards before you swap in a live key.Export code from Bolt: what you get, what stays behind and how to run itIn Bolt on desktop, click your project title and choose Download, unzip it, then run npm install and npm run dev. The zip holds your code only. Secrets, database rows, users, uploaded files and deployed server functions stay in Bolt Cloud, so plan how each one moves before you rely on the export.
See if BlackFig fits what you’re building (it probably does)
A quick 20 minute call. No slides, no hard sell. You leave with a clear next step either way.