Bolt alternatives

People looking for an alternative are almost never complaining about that. They have hit the next limit, the one that shows up when the demo has to become a product.

When to stay

• you want to show an idea this week. Switching tools here costs more than it returns;
• the app is for you, with no other people's accounts and no billing;
• the problem is the quality of the output. Before switching, change the request: say who uses each screen, who can see what, and what happens when the form is submitted. The distance between a vague request and a specific one is greater than the distance between two good tools.

What is table stakes and not a reason to switch

Generating an app from a conversation, a database, login, an admin panel and web publishing: every tool in the category does this, at different levels of maturity. Switching for any of those is switching for nothing.

The alternatives, by the reason for leaving

If you left because the app has to be in the stores

The output is a web app. It does not appear in App Store search, cannot sell subscriptions through the store's system, and depends on the person adding it to the Home Screen to get notifications on iPhone. If being in the store is part of the product, the criteria are different, and they are in native app, PWA or website.

If you left because you need to charge your customers

Billing brings plans, pending states, refunds and the question of who sees what. Here the variable is not generation speed, it is what already comes built for subscriptions, gateways and permissions.

If you left because you want the code

Ask two things before subscribing to any alternative: can I export, and does the published app depend on a platform runtime. Those two answers define the cost of leaving, and they are independent of each other.

If you left on price

Compare by running the same request on both tools. One charges per message, another per credit, another per published app; the number on a pricing page is not comparable across different units.

What you take, and what you rebuild

You take the code, when you have access to it. You rebuild the database, login, integrations and publishing, in any switch, between any two tools. That is why switching early costs little and switching late costs a lot, and why the two questions above belong before, not after.

The summary

• Bolt wins on speed to the first screen, and that remains true;
• the common limit is becoming a product: accounts, permissions, billing and stores;
• generating from a conversation is table stakes, not a reason to switch;
• ask about export and runtime dependency before subscribing;
• what gets rebuilt in every switch is the configuration, not the code.