Large screen ready

Tier 3 icon

TIER 3 — The basic, entry-level tier of the Large screen app quality guidelines.

Depiction of three tiers with the bottom tier, tier 3, highlighted.

THE FIRST STEP in creating a great app for large screens is making your app large screen ready.

Large screen ready apps run full screen in landscape and portrait orientations, full window in multi‑window mode. Apps provide basic support for external input devices, including keyboard, mouse, trackpad, and stylus. Large screen ready camera apps provide a camera preview that's always in the proper aspect ratio and orientation.

App layout might not be ideal, but the app is never letterboxed, never runs in compatibility mode, and users can complete all task flows.

Do's and don'ts

  • Maintain state during configuration changes
  • Support multi-window mode and multi-resume
  • Support external keyboard, mouse, trackpad, and stylus
  • Lock app orientation to either portrait or landscape when full screen or in multi‑window mode
  • Restrict camera preview dimensions or orientation

Guidelines

Follow the Tier 3 guidelines to get your app ready for large screens.

Configuration and continuity

Make your app large screen ready by retaining and restoring state and resuming ongoing processes, such as media playback, during device configuration changes.

Guideline LS-C1

What

App fills the available display area—either the entire screen or the app window in multi‑window mode—in both portrait and landscape orientations and is not letterboxed. App handles configuration changes and retains or restores its state as the device changes orientation, the app window resizes, or the device folds or unfolds.

Why

Configuration changes such as device rotation, window size changes in multi-window mode, and folding or unfolding a foldable device can cause users to lose context or (even worse) data.

How

Learn how to handle configuration changes and maintain app continuity in Configuration and continuity.

Multi-window and multi-resume

Enable your app to run in multi‑window mode alongside other apps either in split‑screen mode or free‑form mode.

Guidelines LS-M1 and LS-M2

What

App fills the app window and is fully functional in multi‑window mode. App supports multi‑resume in multi‑window mode. App updates its UI and ongoing processes, such as media playback, when the app is not the top focused app. App manages access to exclusive resources such as cameras.

Why

Large screens make multi‑window mode more usable. Multi‑window mode makes users more productive.

How

When your app is in multi‑window mode, use the WindowMetrics API to accurately determine the size of the app window. See also Multi‑window support.

Camera preview and media projection

If your app includes a camera preview, validate the preview for orientation and aspect ratio on large screens.

Guidelines LS-CM1 and LS-CM2

What

App provides a properly proportioned and oriented camera preview in landscape and portrait orientations, folded and unfolded device states, and multi‑window mode. App supports media projection in all device configurations in the proper orientation and proportions.

Why

Large screen foldables in portrait orientation can have a landscape aspect ratio. Multi‑window mode can display apps in portrait orientation in a resizable window when the device is landscape.

How

Camera preview — See the following developer guides:

Media projection — To get the correct bounds for your large screen media projection, use the WindowMetrics API introduced in Android 11 (API level 30) or, for compatibility down to API level 14, the Jetpack WindowManager WindowMetrics API.

See also Media projection on large screens.

Keyboard, mouse, and trackpad

Support external input devices by enabling your app to handle keyboard, mouse, and trackpad actions.

Guidelines LS-I1 and LS-I2

What

App supports text input using an external keyboard. When an external keyboard is connected or disconnected, app switches between physical and virtual keyboards without relaunching the app. App supports basic mouse and trackpad input.

Why

Users often connect an external keyboard or mouse to tablets. Chromebooks come with built‑in keyboards and trackpads.

Stylus

Enable users to select and manipulate UI elements, including scrolling through lists, pickers, and other scrollable content, with a stylus.

On Android 14 (API level 34) and higher, support writing and editing text in text input fields using a stylus. On ChromeOS M114 and higher, enable users to write and edit text in text input fields in WebView components using a stylus.

Guidelines LS-S1 and LS-S1.1

What

App supports basic stylus input such as selecting and manipulating UI elements on stylus‑equipped tablets, foldables, and ChromeOS devices.

On Android 14 and higher and ChromeOS M114 and higher, app enables text input in EditText and WebView components, respectively.

Why

Large screens are ideal for stylus‑enabled apps. Some large screen devices come equipped with a stylus.

How

Basic stylus input is the same as touch input, which Android fully supports. No special development is needed to provide basic stylus input.

On Android 14 and higher, EditText components support input using a stylus by default; no special development required. On ChromeOS M114 and higher, WebView components support stylus input in text fields by default.