Mobile Presenter is a Chrome extension that shows any website inside realistic mobile, tablet, and desktop device frames — directly in your browser, without opening DevTools or handing someone a phone. It's built for frontend developers, designers, QA engineers, and agencies who need to present or review a responsive layout quickly and professionally.
Mobile Presenter loads a live URL or local build inside a chosen device frame — mobile, tablet, or desktop — and switches into a fullscreen presentation mode with no browser chrome visible. It's designed for the moment you're already in a client meeting, a design review, or a QA pass and need to show, not describe, how a page behaves at a given size.
[[TODO: paste 3–6 real feature bullets from the Chrome Web Store listing, e.g. number of built-in device frames, custom resolutions, presentation mode, screenshot capture — replace the <ul> below]]Spot-check breakpoints without leaving the browser or reopening DevTools mid-flow.
Compare a live build against a Figma mockup across device sizes.
Reproduce and verify responsive bugs across a consistent set of frames.
Present a build to a client in a device frame instead of a raw browser tab.
Full docs are being written per the Phase 1 roadmap. Planned pages: Getting Started, Interface Overview, Device Frames, Presentation Mode, Keyboard Shortcuts, Permissions & Privacy, Browser Compatibility, Troubleshooting.
These become standalone pages under /mobile-presenter/guides/ in Phase 1–2 (see the roadmap). Listed here first so the hub is a complete map from day one.
A Chrome extension that presents websites inside realistic mobile, tablet, and desktop device frames, for responsive review, QA, and client demos.
It's a Chrome extension — it runs inside your browser, no separate app to install.
Frontend developers, designers, QA engineers, and agencies who need to present or review responsive layouts.
[[TODO: confirm pricing before publishing]]
Chrome. [[TODO: confirm Edge/Brave/other Chromium support]]
[[TODO: back-fill real version history here once available, oldest → newest, using Keep a Changelog format — see the reference doc §05]]