Desktop view
Canonical page for large-device layout: desktop vs forced mobile, split / master-detail, and how desktop nav interacts with lists.
What this is / when to use it
Section titled “What this is / when to use it”By default, large devices use LargeDeviceView.DESKTOP: wider lists, optional split (master-detail), and desktop navigation (TOP_TABS or DRAWER). You can force MOBILE so a desktop browser shows the phone layout.
Use split when operators should keep the list visible while they read or edit one row (support, receiving, approvals adjacent to a data list).
When not to force mobile on desktop: only for apps that are truly phone-first and look wrong when wide. Most portals should stay DESKTOP.
Before you start
Section titled “Before you start”The screen is a list, update list, or select-items screen if you want split. Forms have a separate how-to for submit placement.
Build it
Section titled “Build it”- Open Settings → Appearance or the desktop view control on the screen (both exist; appearance is the app default).
- Set large device view to
DESKTOPorMOBILE. - On a list, enable split / master-detail when you want the right pane.
- Set desktop nav on App Navigation.
- Preview at a desktop width. Publish.
Every control
Section titled “Every control”| Control | Options | What it does |
|---|---|---|
| Large device view | DESKTOP / MOBILE |
App-wide chrome. |
| Split | On / off | List stays; details or update fields open beside it. |
| Desktop nav | TOP_TABS / DRAWER |
See App Navigation. |
| Show mobile view on desktop | Same as MOBILE |
Old heading; this is the current explanation. |
| Theme preset | compact / comfortable / showcase |
Density. See Appearance. |
Show mobile view on desktop devices
Section titled “Show mobile view on desktop devices”This is the same control as large device view = MOBILE. A desktop browser then shows the phone column. Use it only for phone-first apps. Most portals should stay DESKTOP.
What users see
Section titled “What users see”Desktop. Wider cards, split pane when enabled, top tabs or a persistent drawer.
Forced mobile. Centered phone column even on a monitor.
Split. Clicking a row updates the pane without leaving the list. Bulk update still uses the list selection, not the pane.
Limits and plans
Section titled “Limits and plans”- Split is not a second details screen. It reuses the details/update configuration.
- Native automation screens have their own desktop layouts (see each screen guide). Do not expect this split toggle to rewrite Work Queue.
Example
Section titled “Example”Staff Requests update list: desktop split on, compact theme. Clicking a row edits Status in the pane. Bulk update still selects many rows on the left.
Fix problems
Section titled “Fix problems”| Symptom | Likely cause | What to do |
|---|---|---|
| Desktop looks like a phone | MOBILE is on |
Set DESKTOP. |
| Split missing | Not a list family screen | Use a list / update list. |
| Old customize-app URL | Product help updated | This page is current. |