---
title: "Responding to orientation\n    | Ubuntu"
description: 'We have just published a new chapter on our App Design Guides : how
  to handle orientation. To cater for the different orientations of a range of touch
  devices, we need to design apps for Ubuntu in a responsive way. Phone orientations
  The primary orientation for an app on the phone is portrait. Consider using landscape
  orientation when we  […]'
url: https://ubuntu.com/blog/responding-to-orientation?format=md
keywords: index, follow
---

1. [Blog](https://ubuntu.com/blog)
2. Article

---

[Canonical](https://ubuntu.com/blog/author/canonical "More about Canonical")

26 April 2013

# Responding to orientation

[app design](https://ubuntu.com/blog/tag/app-design)
[app patterns explained](https://ubuntu.com/blog/tag/app-patterns-explained)
[Design](https://ubuntu.com/blog/tag/design)

---

Share the article

We have just published a new chapter on our [App Design Guides](http://design.ubuntu.com/apps) : how to handle [orientation](http://design.ubuntu.com/apps/get-started/responding-to-orientation "Responding to orientation").

To cater for the different orientations of a range of touch devices, we need to design apps for Ubuntu in a responsive way.

## Phone orientations

1. The primary orientation for an app on the phone is portrait.
2. Consider using landscape orientation when we want to have a full screen experience for a single piece of content, such as watching a video, looking at a photo or gaming.
3. A phone app automatically fits in the tablet’s side stage, with a flexible height.

## Tablet orientations

1. The primary orientation for an app on the tablet is landscape.
2. Consider portrait orientation when it will help the user engage with your app; for example reading a magazine or writing a long email.
3. By supporting portrait, your app automatically supports split screen.

## Responsive strategies

Use these strategies to make your app work on screens of both different sizes and orientations.

### Position graphic elements relatively

For ease of use we space graphical elements relatively; to both one another and the screen edges.

### Decide how your app might show more or less content

* An app on the tablet’s main stage might show more content than on the phone.

* An app on the phone with a list of content, such as a feed, would show much more content in the side stage as it is taller.

* If your app’s content is larger than what fits in view, for example a map, you might consider showing more or less content depending on shape and orientation.

* If your app’s content is fixed in shape then it can simply scale up or down. For example the same amount of content on the phone would be scaled up on the tablet.

## A few last things

1. **Use extra space constructively**
Consider what content your app could show in extra space, be it the history of a calculator, a list of missed calls or even high scores!
2. **If your phone app does not scale, it will remain a fixed height in the [side stage](http://design.ubuntu.com/apps/get-started/ui-model#side-stage "Side stage").**

Hope this helps – and as ever please let us know what you think, these guidelines are a work in progress and will grow over time. Feel free to get in touch with us on the [Ubuntu Phone mailing list](https://launchpad.net/~ubuntu-phone) and the [IRC channel](http://webchat.freenode.net/?channels=ubuntu-touch).

[Get in touch

Interested in running Ubuntu in your organization?](https://ubuntu.com/about/contact-us/form)

## Newsletter signup

Get the latest Ubuntu news and updates in your inbox.

Work email:

\*I agree to receive information about Canonical's
products and services.

By submitting this form, I confirm that I have read and agree to [Canonical's Privacy Policy](https://canonical.com/legal/data-privacy).

Sign up

## Share on

---

## Related posts

[### Challenges designers face in open source (and how to fix them)](https://ubuntu.com/blog/challenges-designers-face-in-open-source-and-how-to-fix-them)

Open source powers up to 90% of modern software, yet many projects lack usability. Canonical’s Design team surveyed 115 cross-functional professionals to uncover the 4 core...

[Kola Ojoodide](https://ubuntu.com/blog/author/kola-ojoodide)

26 June 2026

[### Template: Streamlining open source design contributions](https://ubuntu.com/blog/template-streamlining-open-source-design-contributions)

As designers working at Canonical, we’re always thinking about open source. We believe that encouraging more designers to contribute to open source benefits everyone, from the...

[Nina Rojc](https://ubuntu.com/blog/author/ninarojc)

16 June 2026

[### Decoding design: How design and engineering thrive together in open source](https://ubuntu.com/blog/decoding-design-how-design-and-engineering-thrive-together-in-open-source)

Open source thrives on engineering-driven processes. Fast feedback loops, terminal tools, Git workflows: they’re the lifeblood of how we build software in the open. But for...

[Miguel Divo](https://ubuntu.com/blog/author/mdivo)

22 May 2026

[### Why web engineering is great](https://ubuntu.com/blog/why-web-engineering-is-great)

Hi, I’m Johann! I’m an engineering manager in Canonical’s web team. For the larger part of my 15 years of work experience as engineer, I’ve been working in web development....

[Johann Wolf](https://ubuntu.com/blog/author/johannwolf)

27 April 2026
