You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I´m new here and understand this has propable been asked many times before but this feature is the only reason I spend more time on loveable.dev than bolt.new so its a big deal for me.
i'd like to suggest an important usability improvement for bolt.new: the ability to directly click and reference UI elements when working with the AI assistant.
Current Challenge:
Having to verbally describe which component or area needs modification is time-consuming
It's difficult to precisely communicate which part of the application needs attention
This creates friction in the development workflow
Suggested Improvement:
Add ability to click/select UI elements directly in the preview
Have the AI automatically understand which component is being referenced
Similar to how loveable.dev implements this feature
Benefits:
Faster development cycles
More precise communication with the AI
Reduced cognitive load for developers
Better overall developer experience
This would be a significant quality-of-life improvement that could help bolt.new better compete with other AI-powered development platforms.
Would love to hear if this is something on your roadmap!
The text was updated successfully, but these errors were encountered:
I´m new here and understand this has propable been asked many times before but this feature is the only reason I spend more time on loveable.dev than bolt.new so its a big deal for me.
i'd like to suggest an important usability improvement for bolt.new: the ability to directly click and reference UI elements when working with the AI assistant.
Current Challenge:
Suggested Improvement:
Benefits:
This would be a significant quality-of-life improvement that could help bolt.new better compete with other AI-powered development platforms.
Would love to hear if this is something on your roadmap!
The text was updated successfully, but these errors were encountered: