可供大螢幕使用
透過集合功能整理內容
你可以依據偏好儲存及分類內容。

等級 3:「大螢幕應用程式品質」指南的基本入門等級。

針對大螢幕製作優質應用程式的第一步,是讓應用程式支援大螢幕。
支援大螢幕的應用程式可在橫向和直向螢幕模式下以全螢幕執行,並在多視窗模式下開啟整個視窗。應用程式可為外部輸入裝置提供基本支援,包括鍵盤、滑鼠、觸控板和觸控筆。支援大螢幕的相機應用程式,應一律提供採用適當顯示比例和螢幕方向的相機預覽畫面。
應用程式版面配置可能不理想,但應用程式一律不會加上黑邊,一律不會在相容模式下執行,且使用者可完成所有工作流程。
注意事項
- 讓應用程式填滿整個可用顯示區域
- 在設定變更期間保留狀態
- 支援多視窗模式和多視窗運作
- 支援外接鍵盤、滑鼠、觸控板和觸控筆
- 在進入全螢幕模式或多視窗模式時,將應用程式方向鎖定
- 設定特定應用程式的顯示比例
- 限制應用程式可調整大小
- 限制相機預覽畫面的尺寸或方向
規範
遵循等級 3 的指南,讓應用程式準備好支援大螢幕裝置。
請在裝置設定變更期間保留及還原狀態,並繼續執行進行中的程序 (例如播放媒體),讓應用程式支援大螢幕體驗。
指南:LS-C1
狀況說明
無論螢幕方向是直向或橫向,應用程式都不會加上黑邊,而會填滿可用的顯示區域,即整個螢幕或多視窗模式下的應用程式視窗。應用程式會處理設定變更,並在裝置變更螢幕方向、調整應用程式視窗大小,或改為摺疊/展開型態時,保留或還原狀態。
理由
設定變更包括裝置旋轉、多視窗模式下的視窗大小變更,以及闔上/展開摺疊式裝置,這類變更可能會造成使用者遺失內容,甚至可能導致資料遺失。
方式
請參閱「設定和連續性」總覽,瞭解如何處理設定變更及維護應用程式持續性。
請確認應用程式支援多視窗模式,能透過分割畫面模式或電腦視窗模式和其他應用程式一起執行。
指南:LS-M1 和 LS-M2
狀況說明
應用程式會填滿應用程式視窗,並在多視窗模式下完整運作。應用程式可在多視窗模式下支援多視窗運作。應用程式會在並非處於主要聚焦狀態時,更新其 UI 和進行中的程序,例如媒體播放程序。應用程式會管理相機等專屬資源的存取權。
理由
大螢幕環境更適合使用多視窗模式,而多視窗模式可提高使用者工作效率。
如果應用程式包含相機預覽,請在大螢幕上查看預覽畫面,檢查顯示方向和顯示比例。
指南:LS-CM1 和 LS-CM2
狀況說明
無論裝置的螢幕方向為橫向/直向、狀態為摺疊/展開,還是處於多視窗模式,應用程式皆可提供適當比例和方向的相機預覽畫面。應用程式可採用適當的方向和比例,在所有裝置設定下支援媒體投影功能。
理由
大螢幕摺疊式裝置可能會在直向模式下使用橫向顯示比例,多視窗模式則可在裝置為橫向時以直向顯示應用程式。
讓應用程式可以處理鍵盤、滑鼠和觸控板操作,支援外部輸入裝置。
指南:LS-I1 和 LS-I2
狀況說明
應用程式支援使用外接鍵盤輸入文字。連接或拔除外接鍵盤時,應用程式會切換實體和虛擬鍵盤,不必重新啟動應用程式。應用程式支援基本的滑鼠和觸控板輸入功能。
理由
使用者通常會將外接鍵盤或滑鼠連接至平板電腦。Chromebook 有內建鍵盤和觸控板。
讓使用者可使用觸控筆選取及操控 UI 元素,包括捲動清單、挑選器和其他可捲動的內容。
在 Android 14 (API 級別 34) 以上版本中,支援使用觸控筆在文字輸入欄位中書寫及編輯文字。在 ChromeOS M114 以上版本中,讓使用者以觸控筆在 WebView
元件的文字輸入欄位中書寫及編輯文字。
指南:LS-S1 和 LS-S1.1
狀況說明
應用程式支援基本的觸控筆輸入功能,例如在配備觸控筆的平板電腦、摺疊式裝置和 ChromeOS 裝置上選取及操控 UI 元素。
在 Android 14 以上版本和 ChromeOS M114 以上版本中,應用程式可分別在 EditText
和 WebView
元件中支援文字輸入功能。
理由
大螢幕裝置很適合搭配可支援觸控筆的應用程式。部分大螢幕裝置隨附觸控筆。
方式
基本觸控筆輸入功能與 Android 完整支援的觸控輸入功能相同。您不需要進行特殊開發作業,即可提供基本觸控筆輸入功能。
在 Android 14 以上版本中,EditText
元件預設支援使用觸控筆輸入內容,無需進行特殊開發作業。在 ChromeOS M114 以上版本中,WebView
元件預設支援文字欄位中的觸控筆輸入功能。
詳情請參閱「Stylus」總覽。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間:2025-07-27 (世界標準時間)。
[null,null,["上次更新時間: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."]]