WWDC 2026: Get the most out of Device Hub (Session 260)

Use Device Hub in Xcode 27 to control, organize, configure, diagnose, and reproduce issues across physical devices and simulators.

Watch on Apple Developer

TL;DR

Device Hub ships with Xcode 27 as a standalone app for working with both physical devices and simulators without launching Xcode.
It provides compact and full-window modes with live device interaction, contextual hardware controls, zoom, physical-size viewing, resize mode, and keyboard capture.
The sidebar and inspector support device inventory management, pairing, app/container management, profiles, appearance settings, simulated conditions, and diagnostics.
A bug-reproduction workflow shows how to collect logs and app data from a real device, then mirror device model, app data, orientation, location, and text size on a simulator; devicectl covers automation and CI use cases.

Device Hub is a new app that ships alongside Xcode 27. It is intended as a central place to work with physical devices and simulators, whether you are developing, testing configurations, or managing a device inventory.

When running to a simulator from Xcode, Device Hub launches automatically and shows a live, interactive compact window. The same toolset is designed to apply consistently across devices and simulators.

Compact mode focuses on the device screen plus essential controls.
Full-window mode expands into a sidebar, central canvas, and inspector for broader control and configuration.
Device controls are contextual: examples include Apple TV navigation and play/pause, Apple Vision Pro environment and camera movement, and Apple Watch side button and Digital Crown controls.

Control devices from the canvas

The canvas in the full Device Hub window provides a live display of the selected device or simulator. Developers can click, drag, scroll, and use natural trackpad gestures directly against the displayed screen.

The canvas also exposes controls that are not available in compact mode, making it useful for UI inspection, hardware-keyboard testing, and resizability work.

Zoom in or out, or snap to one-to-one physical size to evaluate real-world dimensions.
Use resize mode to freely transform an app's dimensions; the session points to "Modernize your UIKit app" for more detail.
Capture keyboard routes Mac keystrokes directly to the device, which helps test key commands and hardware keyboard support.
Switch back to compact mode when only the live screen and essential controls are needed.

Organize device and simulator inventory

The sidebar shows the full inventory of connected devices and available simulators in one place. It is built for workflows that involve many devices, multiple simulator sizes, or paired device sets.

Use the filter menu to control which devices are visible.
Sort and group the inventory using several sidebar options.
Context-click devices for quick actions such as restarting or pairing an iPhone and Apple Watch simulator together.
Open multiple devices as tabs or as standalone compact windows to compare layouts across screen sizes.

Configure settings, apps, profiles, and diagnostics

The inspector area contains panels for changing device configuration and collecting information needed to investigate issues. The session emphasizes avoiding repeated trips through on-device Settings by changing common test parameters directly in Device Hub.

Device settings include appearance options such as Dark Mode and text size, condition simulation such as location, and audio options for levels and I/O.
Diagnostic reports include crashes, spins, and other logged diagnostics, making this a starting point for hangs and crashes.
Info shows quick device details such as storage, model, and serial number.
Apps supports installing, uninstalling, managing apps, and downloading or replacing app data containers.
Profiles manages configuration profiles and provisioning profiles.

Reproduce bugs by mirroring the reporter's environment

The demo workflow starts with a location-based workout app bug: recovery advice text is clipped in landscape. The first developer collects enough context from a real iPhone and Apple Watch setup for another developer to reproduce the problem on a simulator.

The reproduction succeeds only after matching a combination of factors: corresponding device model, app data container, landscape orientation, simulated location, and large text size. Device Hub is presented as the place to collect and apply those variables consistently.

Pair nearby devices from the sidebar, including pairing an Apple Watch with the Mac.
Install a Core Location logging configuration profile through the Profiles panel, then reboot the iPhone for privacy reasons.
Capture evidence such as screenshots, sysdiagnose output, copied text, and the app data container.
On the simulator, verify the model in the Info panel, replace the app's data container through the Apps inspector, rotate the simulator, simulate the reported location, and match accessibility-related appearance settings such as text size.

Automation with devicectl

For scripting and automation, the session recommends devicectl, a command-line tool based on the same underlying technology as Device Hub. It is positioned for test environments, scripts, and CI workflows.

Use devicectl to list devices, install apps, change settings such as light or dark appearance, retrieve device information, and capture diagnostics.
Use the json-output option when structured output is needed for scripts or CI integration.
Consult the Device Hub documentation and devicectl documentation for exact commands and options.

devicectl capabilities mentioned

The session names devicectl operations-listing devices, installing apps, changing settings, getting device information, and capturing diagnostics-but does not show exact command syntax.

Resources

Device Hub

Get the most out of Device Hub