Large screen ready
Stay organized with collections
Save and categorize content based on your preferences.
TIER 3 — The basic, entry-level tier of the Large screen app
quality guidelines.
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
- Enable app to fill entire available display area
- Maintain state during configuration changes
- Support multi-window mode and multi-resume
- Support external keyboard, mouse, trackpad, and stylus
- Lock app orientation when full screen or in multi‑window mode
- Set a specific app aspect ratio
- Restrict app resizability
- Restrict camera preview dimensions or orientation
Guidelines
Follow the Tier 3 guidelines to get your app ready for large screens.
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.
Enable your app to run in multi‑window mode alongside other apps either in split‑screen mode or desktop windowing 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.
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.
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.
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.
For more information, see the Stylus overview.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-02-10 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-10 UTC."],[],[],null,["# Large screen ready\n\nTIER 3 --- The basic, entry-level tier of the [Large screen app\nquality](/docs/quality-guidelines/large-screen-app-quality) guidelines.\n\nTHE FIRST STEP in creating a great app for large screens is making your app\nlarge screen ready.\n\nLarge screen ready apps run full screen in landscape and portrait orientations,\nfull window in multi‑window mode. Apps provide basic support for external\ninput devices, including keyboard, mouse, trackpad, and stylus. Large screen\nready camera apps provide a camera preview that's always in the proper aspect\nratio and orientation.\n\nApp layout might not be ideal, but the app is never letterboxed, never runs in\ncompatibility mode, and users can complete all task flows.\n\nDo's and don'ts\n---------------\n\ncheck_circle\n\n### Do\n\n- Enable app to fill entire available display area\n- Maintain state during configuration changes\n- Support multi-window mode and multi-resume\n- Support external keyboard, mouse, trackpad, and stylus \ncancel\n\n### Don't\n\n- Lock app orientation when full screen or in multi‑window mode\n- Set a specific app aspect ratio\n- Restrict app resizability\n- Restrict camera preview dimensions or orientation\n\nGuidelines\n----------\n\nFollow the Tier 3 guidelines to get your app ready for large screens.\n| **Note:** Large screen ready apps also fulfill the [core app\n| quality](/docs/quality-guidelines/core-app-quality) requirements---especially the [UI and\nGraphics](/docs/quality-guidelines/core-app-quality#ui_and_graphics) requirements. \n\n### [Configuration and continuity](/docs/quality-guidelines/large-screen-app-quality#t3_configuration_continuity)\n\nMake your app large screen ready by retaining and restoring state and resuming ongoing processes, such as media playback, during device configuration changes.\n\nGuideline [LS-C1](/docs/quality-guidelines/large-screen-app-quality#LS-C1) \n\n#### What\n\nApp 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](/guide/topics/large-screens/large-screen-compatibility-mode#letterboxing). 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. \n\n#### Why\n\nConfiguration 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. \n\n#### How\n\nLearn how to handle configuration changes and maintain app continuity in the [Configuration and continuity](/guide/topics/large-screens/configuration-and-continuity) overview. \n\n### [Multi-window and multi-resume](/docs/quality-guidelines/large-screen-app-quality#t3_multi-window_multi-resume)\n\nEnable your app to run in multi‑window mode alongside other apps either in split‑screen mode or desktop windowing mode.\n\nGuidelines [LS-M1](/docs/quality-guidelines/large-screen-app-quality#LS-M1) and [LS-M2](/docs/quality-guidelines/large-screen-app-quality#LS-M2) \n\n#### What\n\nApp 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. \n\n#### Why\n\nLarge screens make multi‑window mode more usable. Multi‑window mode makes users more productive. \n\n#### How\n\nLearn how to develop for multi-window mode in the [Multi-window mode and multi-resume](/guide/topics/large-screens/multi-window-mode-and-multi-resume) overview. \n\n### [Camera preview and media projection](/docs/quality-guidelines/large-screen-app-quality#t3_camera_preview_media_projection)\n\nIf your app includes a camera preview, validate the preview for orientation and aspect ratio on large screens.\n\nGuidelines [LS-CM1](/docs/quality-guidelines/large-screen-app-quality#LS-CM1) and [LS-CM2](/docs/quality-guidelines/large-screen-app-quality#LS-CM2) \n\n#### What\n\nApp 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. \n\n#### Why\n\nLarge 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. \n\n#### How\n\nFor guidance about camera preview and media projection, see the [Camera preview and media projection](/guide/topics/large-screens/camera-preview-and-media-projection) overview. \n\n### [Keyboard, mouse, and trackpad](/docs/quality-guidelines/large-screen-app-quality#t3_keyboard_mouse_trackpad)\n\nSupport external input devices by enabling your app to handle keyboard, mouse, and trackpad actions.\n\nGuidelines [LS-I1](/docs/quality-guidelines/large-screen-app-quality#LS-I1) and [LS-I2](/docs/quality-guidelines/large-screen-app-quality#LS-I2) \n\n#### What\n\nApp 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. \n\n#### Why\n\nUsers often connect an external keyboard or mouse to tablets. Chromebooks come with built‑in keyboards and trackpads. \n\n#### How\n\nSee the [Keyboard, mouse, and trackpad](/guide/topics/large-screens/keyboard-mouse-and-trackpad-tier-3) overview to learn how to add support for external input devices in your app. \n\n### [Stylus](/docs/quality-guidelines/large-screen-app-quality#t3_stylus)\n\nEnable users to select and manipulate UI elements, including scrolling through lists, pickers, and other scrollable content, with a stylus.\n\nOn 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`](/reference/android/webkit/WebView) components using a stylus.\n\nGuidelines [LS-S1](/docs/quality-guidelines/large-screen-app-quality#LS-S1) and [LS-S1.1](/docs/quality-guidelines/large-screen-app-quality#LS-S1.1) \n\n#### What\n\nApp supports basic stylus input such as selecting and manipulating UI elements on stylus‑equipped tablets, foldables, and ChromeOS devices.\n\nOn Android 14 and higher and ChromeOS M114 and higher, app enables text input in [`EditText`](/reference/android/webkit/WebView) and `WebView` components, respectively. \n\n#### Why\n\nLarge screens are ideal for stylus‑enabled apps. Some large screen devices come equipped with a stylus. \n\n#### How\n\nBasic stylus input is the same as touch input, which Android fully supports. No special development is needed to provide basic stylus input.\n\nOn 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.\n\nFor more information, see the [Stylus](/guide/topics/large-screens/stylus-tier-3) overview."]]
