android:screenOrientation="portrait" to the activity in the AndroidManifest.xml. For example:
<activity android:name=".SomeActivity" android:label="@string/app_name" android:screenOrientation="portrait" />
Since this has become a super-popular answer, I feel very guilty as forcing portrait is rarely the right solution to the problems it’s frequently applied to.
The major caveats with forced portrait:
- This does not absolve you of having to think about activity
lifecycle events or properly saving/restoring state. There are plenty of
things besides app rotation that can trigger an activity
destruction/recreation, including unavoidable things like multitasking. There are no shortcuts; learn to use bundles and
- Keep in mind that unlike the fairly uniform iPhone experience, there are some devices where portrait is not the clearly popular orientation. When users are on devices with hardware keyboards or game pads a la the Nvidia Shield, on Chromebooks, on foldables, or on Samsung DeX, forcing portrait can make your app experience either limiting or a giant usability hassle. If your app doesn’t have a strong UX argument that would lead to a negative experience for supporting other orientations, you should probably not force landscape. I’m talking about things like “this is a cash register app for one specific model of tablet always used in a fixed hardware dock.”
So most apps should just let the phone sensors, software, and physical configuration make their own decision about how the user wants to interact with your app. A few cases you may still want to think about, though, if you’re not happy with the default behavior of
sensor orientation in your use case:
- If your main concern is accidental orientation changes mid-activity that you think the device’s sensors and software won’t cope with well (for example, in a tilt-based game) consider supporting landscape and portrait, but using
nosensorfor the orientation. This forces landscape on most tablets and portrait on most phones, but I still wouldn’t recommend this for most “normal” apps (some users just like to type in the landscape softkeyboard on their phones, and many tablet users read in portrait – and you should let them).
- If you still need to force portrait for some reason,
sensorPortraitmay be better than
portraitfor Android 2.3 (Gingerbread) and later; this allows for upside-down portrait, which is quite common in tablet usage.