Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Latest commit 3d7d54c Feb 16, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
.google Auto-update May 17, 2017
Application Auto-update Feb 16, 2018
gradle/wrapper Auto-update Feb 16, 2018
kotlinApp Auto-update Feb 16, 2018
screenshots Auto-update Mar 9, 2016 Auto-update Mar 9, 2016
LICENSE Auto-update Feb 16, 2018
NOTICE Auto-update Feb 16, 2018 Auto-update Feb 16, 2018
build.gradle Auto-update Mar 9, 2016
gradlew Auto-update Mar 9, 2016
gradlew.bat Auto-update Mar 9, 2016
settings.gradle Auto-update Mar 9, 2016

Android MultiWindowPlayground Sample

This sample demonstrates the use of the multi-window API available in Android N. It shows the use of new Intent flags and AndroidManifest properties to define the multi-window behavior. Switch the sample app into multi-window mode to see how it affects the lifecycle and behavior of the app.


Android N introduces new APIs to support multiple activities to be displayed at the same time.

Activities that are started within the same task stack inherit their multiwindow properties from the activity that fired off the intent. The following features are available when an activity has been launched into a new task stack.

An activity can be set as not resizable through the android:resizableActivity property in the AndroidManifest. All applications targeting Android N or above are resizable by default.

In split-screen mode, an activity can be started adjacent to the launching activity by setting the Intent.FLAG_ACTIVITY_LAUNCH_TO_ADJACENT flag in its intent.

Sometimes activities may choose to handle configuration changes themselves (for example for games or OpenGL-based applications). In this case, setting android:configChanges=screenSize|smallestScreenSize|screenLayout|orientation in the AndroidManifest definition of the activity enables callbacks for all configuration changes that may occur during multi-window use for the Activity. See Handling Runtime Changes.

In freeform mode (where applications can be freely resized), activities can be started within a certain area of the screen using the ActivityOptions#setLaunchBounds call.

Alternatively, the preferred and minimum sizes can be set in a new layout property in the AndroidManifest.


  • Android SDK 24
  • Android Build Tools v27.0.2
  • Android Support Repository



Getting Started

This sample uses the Gradle build system. To build this project, use the "gradlew build" command or use "Import Project" in Android Studio.


If you've found an error in this sample, please file an issue:

Patches are encouraged, and may be submitted by forking this project and submitting a pull request through GitHub. Please see for more details.


Copyright 2017 The Android Open Source Project, Inc.

Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

You can’t perform that action at this time.