[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# Configuration and continuity\n\nTIER 3 --- Large screen ready\n| **Objective:** Make your app [large screen ready](/docs/quality-guidelines/large-screen-app-quality#large_screen_ready) by meeting the [LS-C1](/docs/quality-guidelines/large-screen-app-quality#LS-C1) and [LS-C2](/docs/quality-guidelines/large-screen-app-quality#LS-C2) configuration and continuity requirements of the [Large screen app\n| quality](/docs/quality-guidelines/large-screen-app-quality) guidelines.\n\nConfiguration is a combination of device state and system state. Device state\nincludes screen orientation, display size, folded or unfolded state of a\nfoldable device, external keyboard availability, attached displays. System state\nincludes display modes, such as multi-window and multi-display, and user-defined\nsettings, such as font size and locale.\n\nConfiguration changes are device or system state changes---a rotated device,\nresized app window, unfolded device, connected peripheral, or updated user\nsetting.\n\nLarge screen devices undergo all the same configuration changes as small screen\nphones, but large screens also have unique configuration changes such as:\n\n- Device folding and unfolding\n- Resizing of free-form, desktop-type windows in multi-window mode\n\nActivity recreation\n-------------------\n\nAndroid handles configuration changes for apps by destroying and recreating the\nactivity that's running when the configuration change occurs. Android recreates\nthe activity with settings and resources that accommodate the new configuration.\n\nDesign your app with responsive/adaptive layouts that support a wide variety of\nscreen and app window sizes and aspect ratios, and the Android framework's\nconfiguration handling will provide the optimal presentation of your app on\nlarge *and* small screens.\n\nDo-it-yourself configuration management\n---------------------------------------\n\nFor special cases, such as app-specific optimizations, enable your app to handle\nconfiguration changes rather than letting Android destroy and recreate your\napp's activities.\n\nSpecify the configuration changes your app handles by setting the\n[`android:configChanges`](/guide/topics/manifest/activity-element#config) attribute of the [`\u003cactivity\u003e`](/guide/topics/manifest/activity-element) element in your\napp manifest.\n\nFor example, enable your app to handle multi-window configuration changes: \n\n \u003cactivity\n android:name=\".MyActivity\"\n android:configChanges=\"orientation|screenSize|smallestScreenSize|screenLayout\" /\u003e\n\n| **Note:** Android handles any configuration changes you don't specify in `configChanges`; that is, the system destroys and recreates your app's activities.\n\nState management\n----------------\n\nWhether Android handles a configuration change for you or you do it yourself,\nyour app must maintain context and state. After a configuration change, users\nshould be able to resume interaction with your app without a disruption in\ncontinuity and without losing data, for example, when a configuration change\nhappens during media playback or data entry, respectively.\n\nNext steps\n----------\n\nFor more information about how to handle configuration changes and maintain app\ncontinuity, see the following developer guides:\n\n- [Handle configuration changes](/guide/topics/resources/runtime-changes)\n- [Save UI states](/topic/libraries/architecture/saving-states)"]]