Browse catalog

Mockups

Device and browser frames for screenshots — a browser-window chrome, a generic device bezel, an iPhone shell, and a coverflow phone showcase.

Device Mockup

Preview

Controls

Theme

Surface

Direction

Viewport

Device view renders in an isolated frame so real responsive breakpoints apply. Switch to Full for overflowing popovers.

Installation

terminal

php artisan ui:add device

Registry contract

Install confidence

php artisan ui:add device writes only the generated targets below. The CLI validates each file hash before writing and prompts before replacing local changes unless --force is used.

Version: 1.0.0
License: open
Stability: stable
Contract: v2
Foundation: ≥ 1.0.0

Type	Generated target
blade	resources/views/components/ui/device.blade.php

Registry dependencies

None.

Package dependencies

composer: jml/brok:^1.0

Guidance

Expressive and showcase effect

Support brand expression or a showcase moment.

Use when

Use only when visual expression supports storytelling, brand differentiation, or a clear showcase moment. Do not place heavy effects in task-dense workflows where clarity, speed, and readability matter more.

Avoid when

Avoid using device as a default simply because it is available in the library. Choose it only when its interaction cost, visibility, and behavior match the job to be done.

Task length: short
Interaction cost: medium
Interruptiveness: low
Input precision: none
Mobile / touch risk: high
Accessibility risk: high
Needs background context: No
Comparison needed: No

Preferred alternatives

Static content-first presentation

Anti-patterns

Heavy effects in forms or task-dense workflows
Motion that interferes with reading or focus

API

manifest knowledge + registry-derived coverage

Props

Prop	Type / values	Default	Description
type	string	phone	Declared by @props in the registry Blade source.
color	mixed\|null	null	Declared by @props in the registry Blade source.

Slots

default — Primary Blade slot rendered by the component.

Data slots

device

Capabilities

wcag-2.2-aa-target responsive rtl darkMode localized

Behavior

Uses server-rendered Blade and semantic HTML.
Declares registry capability flags: a11y, responsive, rtl, darkMode, localized.

Usage

previews.components.device.default.blade.php Blade

<div class="flex flex-wrap items-end gap-10">
    <x-ui.device type="phone">
        <div class="h-full w-full bg-gradient-to-br from-primary/20 to-primary/5"></div>
    </x-ui.device>

    <x-ui.device type="laptop">
        <div class="h-full w-full bg-gradient-to-br from-primary/20 to-primary/5"></div>
    </x-ui.device>
</div>

Accessibility & localization

WCAG 2.2 AA RTL-ready data-slot Keyboard focus-visible Localized labels

Accessibility target: wcag-2.2-aa-target.
Uses semantic HTML and a stable data-slot attribute for styling/scripting hooks.
Focus-visible rings use the ring token so keyboard focus is always visible.
Disabled and invalid states are conveyed to assistive tech, not by color alone.
Targets WCAG 2.2 AA; verify contrast in light, dark, admin and customer surfaces above.
Labels go through __() and the component uses logical properties (ms-*, text-start, start-*) so it mirrors correctly — flip the preview to RTL to confirm.

Source

The exact, editable file ui:add writes into your app — copy it or own the whole thing. Previews render this same code; there are no preview-only components.

Changelog

Current version: v1.0.0. See the site changelog for the full release history.