React Device Mockup Frame
A screenshot floating on a page reads as a mock; the same screenshot inside a familiar bezel reads as a real product. That is the whole trade, and it is a good one. Three frames — a browser chrome, a rack-instrument face, and a phone — for the surfaces technical products actually ship on.
Installation
Props
| Prop | Type | Description |
|---|---|---|
| variant | MockupVariant | "browser", "instrument", or "phone" |
| url | string | Address shown in the browser bar |
| model | string | Model text on the instrument bezel |
| children | React.ReactNode | The screenshot to frame |
Chrome only, on purpose
There is no behaviour here — the traffic-light dots don't close anything, the instrument knobs don't turn. That restraint is deliberate: a mockup frame that half-works invites a reader to click the fake controls and feel the seams. Its job is to be a convincing, silent container for the real thing you built, which lives inside it.
The instrument variant is the one you won't find in a generic mockup kit — a brushed-metal bezel with a recessed screen, a ready lamp, and physical controls down the side, for the DAQ and bench-instrument software that Kelvin exists to dress. The browser frame keeps a locked-padlock URL pill for the SaaS shot; the phone frame is a clean notched slab for the companion app.
Feed it a static image, or — more powerfully — a live Kelvin component tree, so your marketing screenshots are the actual product and can never drift out of date.
New components every week
Get the week's new Kelvin UI components and templates in one short email. No spam, unsubscribe anytime.