支持大屏设备
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。

第 3 层级 - 大屏设备应用质量指南中的基本入门层级。

要打造适合大屏设备的出色应用,第一步是让应用可以在大屏设备上运行。
支持大屏设备的应用可在横屏和竖屏模式下全屏运行,在多窗口模式下全窗口运行。应用为外部输入设备(包括键盘、鼠标、触控板和触控笔)提供基本支持。支持大屏设备的相机应用可提供相机预览,且预览始终保持正确的宽高比和屏幕方向。
应用布局可能并不理想,但应用从不采用信箱模式,也不要在兼容模式下运行,并且用户可以完成所有任务流程。
正确做法和错误做法
- 让应用填充整个可用显示区域
- 在配置变更期间维护状态
- 支持多窗口模式和多项恢复
- 支持外接键盘、鼠标、触控板和触控笔
- 在全屏模式或多窗口模式下锁定应用屏幕方向
- 设置特定的应用宽高比
- 限制应用可调整大小
- 限制相机预览尺寸或屏幕方向
指南
遵循第 3 层级准则,让您的应用支持大屏设备。
在设备配置变更期间,保留和恢复状态以及恢复正在执行的进程(例如媒体播放),让应用支持大屏设备。
指南 LS-C1
内容
在纵向和横向模式下,应用均填满可用的显示区域(整个屏幕或多窗口模式下的应用窗口),且不采用信箱模式。应用会处理配置变更,并在设备改变屏幕方向、调整应用窗口大小或设备折叠或展开时保留或恢复其状态。
原因
诸如设备旋转、多窗口模式下的窗口大小变化、可折叠设备的折叠或展开等配置变更,可能会导致用户丢失上下文,更糟的情况下甚至会丢失数据。
具体做法
如需了解如何处理配置变更以及保持应用连续性,请参阅配置和连续性概览。
让您的应用能够在多窗口模式(如分屏模式或桌面窗口模式)下与其他应用一起运行。
指南 LS-M1 和 LS-M2
内容
应用会填满应用窗口,并在多窗口模式下完全正常运行。应用支持多窗口模式下的多项恢复功能。当应用不是位于最前面的聚焦应用时,应用会更新其界面和正在执行的进程(例如媒体播放)。应用会管理对摄像头等专属资源的访问权限。
原因
在大屏设备上,多窗口模式更易于使用。多窗口模式可提高用户的工作效率。
如果您的应用提供相机预览,请验证在大屏设备上的屏幕方向和宽高比的预览效果。
指南 LS-CM1 和 LS-CM2
内容
应用在纵向和横向模式、设备折叠和展开状态以及多窗口模式下提供适当比例和朝向的相机预览。应用支持在所有设备配置中以合适的屏幕方向和比例进行媒体投影。
原因
屏幕方向为纵向的大屏可折叠设备可以有横向宽高比。当设备处于横屏模式时,多窗口模式可以在可调整大小的窗口中纵向显示应用。
让您的应用能够处理键盘、鼠标和触控板操作,以支持外部输入设备。
指南 LS-I1 和 LS-I2
内容
应用支持使用外接键盘输入文本。当连接或断开外接键盘时,应用无需重新启动即可在实体键盘和虚拟键盘之间切换。应用支持基本的鼠标和触控板输入。
原因
用户通常会将外部键盘或鼠标连接到平板电脑。Chromebook 带有内置键盘和触控板。
让用户能够使用触控笔选择和操控界面元素,包括滚动浏览列表、选择器和其他可滚动内容。
在 Android 14(API 级别 34)及更高版本中,支持使用触控笔在文本输入字段中填写和修改文本。在 ChromeOS M114 及更高版本中,让用户能够使用触控笔在 WebView
组件的文本输入字段中填写和修改文本。
指南 LS-S1 和 LS-S1.1
内容
应用支持基本的触控笔输入,例如在配备触控笔的平板电脑、可折叠设备和 ChromeOS 设备上选择和操控界面元素。
在 Android 14 及更高版本和 ChromeOS M114 及更高版本中,应用可分别在 EditText
和 WebView
组件中启用文本输入。
原因
大屏设备非常适合支持触控笔的应用。一些大屏幕设备配有触控笔。
具体做法
基本的触控笔输入与触控输入相同,Android 完全支持此类输入。无需进行特殊开发即可提供基本的触控笔输入。
在 Android 14 及更高版本中,EditText
组件默认支持使用触控笔输入;无需进行特殊开发。在 ChromeOS M114 及更高版本中,WebView
组件默认支持在文本字段中使用触控笔输入。
如需了解详情,请参阅触控笔概览。
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-27。
[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],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."]]