Dev.to AI πŸ€– Ai πŸ‘ 0 πŸ“– 3 min read

Why your Bolt.new or Cursor app works for you and breaks for everyone else

There is a moment in every Bolt.new or Cursor build where the app stops being a demo. Up to that point it is fun. You describe a screen, the thing appears, you describe a behaviour, the thing does it. The demo video wri

There is a moment in every Bolt.new or Cursor build where the app stops being a demo.

Up to that point it is fun. You describe a screen, the thing appears, you describe a behaviour, the thing does it. The demo video writes itself. Then you let one real person use it, and you find the parts that only ever worked because you were the one using it: the seed data that only exists on your laptop, the API call that fails silently when the response is empty, the rate limit you hit on the free tier of some third-party service at 9am on a Tuesday.

This is the part where most AI-built apps quietly die, and the reason is not technical incompetence. It is that the model optimised for the screen, and the screen is not the product.

The four failures that are really one failure

Seed data instead of a database. The app shows a list of three items. They were put there by the seed script, or by hand, or they are hardcoded in a file. A real user sees three items too, because the three items are in the bundle. Nothing about this looks broken until you submit the fourth item and watch it vanish.

The empty state that was never designed. The list renders items, so the empty state was never built. When the real user has no items - because they are new - the screen is blank, or it throws, or it shows "undefined". An empty state is not a polish detail. For a new user it is the first and only thing they see.

The third-party API with no failure path. Payments, email, maps, storage, AI inference, auth. Each one will fail at some point, and each one fails differently: a timeout, a 500, a rate limit, a schema change nobody announced. If the code calls it without a fallback, the user sees a spinner that never resolves.

The deployment that only you can deploy. It works because you run it. The other person cannot, because the environment variables live in a .env file on your machine, the database is a local file, and the build step assumes a folder that only exists on your laptop.

The order that saves the most time

Do not start with the polish. Start with making it run somewhere that is not your machine.

  1. Deploy it for real. A URL somebody else can open, with the connection string in the host's environment, and the migrations run by the deploy step. If you cannot do this, nothing else you fix will be visible to a user.
  2. Point it at a real database and delete the seed. Then add the fourth item yourself, from the deployed URL, in a private window. If it is not there, you have found the real problem.
  3. Build the empty and error states. Not a spinner. A sentence that says what happened and what to do next.
  4. Give every third-party call a timeout and a fallback. A payment provider that is down should produce an error the user can act on, not a blank screen and a support ticket about nothing.
  5. Then the last 10%. The animations, the settings page, the nice empty state with the illustration. These matter, and they are also the part you can do last without the product being broken.

What to check before you call it done

Can a user who has never seen the app sign up, do the one thing the app is for, and get the result they expected - without you watching? If you cannot answer that, the app is a prototype with a landing page.

If you would rather hand the checklist to someone who does this every day, https://www.appstuck.com/platforms/bolt covers Bolt specifically, and there is a page for each of the other builders - Lovable, Replit, Cursor, Base44 and v0 - with the same troubleshooting material. The work is the same on every platform; only the tool names change, and the last 10% is still the last 10%.

Disclosure: I work with the team behind AppStuck.

πŸ“° Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.