Feedback: Preview tool needs device/viewport presets, better stability, and UX polish
Summary
I've been using the built-in Preview while actively developing a Next.js project, and overall the experience has been frustrating. It feels under-invested compared to the rest of Claude Code, and a few small improvements would make a big difference to day-to-day development. I'd love to see the team give this some attention in a future update.
Pain points
1. No quick way to switch viewports / device sizes
There are no buttons or presets to switch the preview between common viewport sizes (mobile, tablet, desktop, custom widths). Responsive work is a huge part of front-end development, and right now testing different breakpoints is clumsy. A simple device/viewport toolbar (like browser dev tools have) would solve this instantly.
2. Instability during development
The preview is unstable while developing — it disconnects, freezes, or stops responding at times, which interrupts the flow and forces reloads/restarts. For a tool meant to give fast feedback, reliability is essential.
3. General UX / ease of use
Beyond the two points above, the preview is generally harder to use than it should be. The controls feel limited and the workflow isn't smooth.
Why this matters
None of this seems particularly hard or expensive to improve — viewport presets and stability fixes are well-understood problems with well-understood solutions. The payoff in developer experience would be significant. Please consider prioritizing some polish here in an upcoming release. 🙏
Suggested improvements
- [ ] Add a viewport/device-size toolbar with presets (mobile / tablet / desktop) + custom dimensions
- [ ] Add a quick rotate (portrait/landscape) toggle
- [ ] Improve connection stability so the preview doesn't drop or freeze during long dev sessions
- [ ] General UX polish to make the controls more discoverable and easier to use
Thanks for all the work on Claude Code — it's a great tool, and this part just needs some love.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗