What Features Do You Need That Lovable & Bolt.new Lack?
AI dev tools like Lovable & Bolt.new are great, but are they missing something you really need?
A must-have feature that’s not there?
A pain point they haven’t solved?
Drop your thoughts below! Let’s discuss.
Replies
Both tools are solid, but I’d love to see better integration with third-party APIs and more customization options for workflows. A built-in debugging assistant could also be a game-changer. Curious to hear what others think!
A smarter UI would help! I’d love a dashboard that adapts to my coding style.
A proper mobile-friendly interface would help! I'd love to code on the go.
Odience
Streak Hunter
A good way to build my design like my Figma screen
@denisss lovable integrates with Figma through builder.io
Sometimes, I need more transparency in how AI generated code is built a breakdown of decisions would be helpful
Handling complex projects can be tricky. A way to manage larger co debases more efficiently would be nice
minimalist phone: creating folders
Suggestions for improving the website (it could e.g. take into account the best designs and UX) and according to that tailor the better suggestions for missing elements or improvements.
AI sucks at maintaining dev and production environments, managing deployments, etc. the stuff after you scaffold an app. I would like to help fix that.
Scene
Both great, pushing AI dev tools forward, but features aside the real question for me is are they just accelerating old workflows, or actually changing how we build?
The ability to handle unlimited sizes of projects, so the tool looks at relevant files and context, when a project grows too latrge, these tools creates more problems than solutions, not just Bolt and Lovable, Curser, Mgt etc. Too.
Being available for Android Studio
We need them to be smarter. They need to automatically take care of whatever they need to do to reset the context window so we can have effective workflows reducing the amount of errors.
If they can't do that at least show a progress bar of where our context window is at so we know we need to refork or something.
Lovable and Bolt need to let us choose which Supabase account to use on a per project basis and not on an account basis.
Both platforms need to let us use other Database Solutions like Local Databases, SQLite and other options, a lot of our projects would be fine with a more straightforward database, we not always need all the complexity of Supabase, so why forcing us? We could even work well with a Google Sheet as a Database!
Transparency about which model is being used is crucial, sometimes we don't need complex models, or why not allow us to plug our own models and use our own tokens. Charge us for the service, not for the tokens!
End to end Github deployments, separate versions: Staging, Production and Development.
Better at design, not everything looking very similar.
Give us better prompting clues about how we should talk to the agent.
Bolt is missing the Chat functionality which has been proven to be very useful on Lovable.
Both have to keep in mind, these platforms are NOT for developers, so when they give instructions like: "Split the project in multiple parts and then merge it if its too big" how the heck do we do that if we are not developers? They seem to forget these are no code platforms for no coders, otherwise we would be using Windsurf or Cursor.
Fixes should be free.
Claude 3.7 Sonnet.