App patterns explained: content views

Canonical

Canonical

on 22 February 2013

When designing an app, an important thing to consider in your app is how to display content.

In our design guidelines, we have provided three standard views: Grid, List and Full screen which we think will cover most situations.

Grid view

Content divided into rows and columns is referred to as a grid view.

  • The grid view extends vertically.

List view

Content divided into rows is referred to as a list view and can attain a variety of appearances and behaviours.

  • The list view extends vertically.
  • List items can be grouped and styled differently.

Thinking of using this one? Look at the “List items” building block.

Full screen view

When a single piece of content is the main focus of the user’s attention, you should consider displaying the content in full screen view using the full screen layout.

This view looks like it needs some navigation

To navigate back to the previous view, use the page stack navigation structure.

And what about scrolling?

Scrollbars are hidden until you actually need them, so they appear on touch. The scrollbar is applied automatically whenever there is content out of view.

Ask us about content views!

Join our mailing list. We’d love to hear from you!

Talk to us today

Interested in running Ubuntu Desktop in your organisation?

Newsletter signup

Select topics you’re interested in

In submitting this form, I confirm that I have read and agree to Canonical’s Privacy Notice and Privacy Policy.

Related posts

A fresh look for releases.ubuntu.com

Updating the design of the Ubuntu Releases website using Vanilla Framework

Design and Web team summary – 04 February 2019

Welcome to the latest work and updates from the design and web team. Web squad Three new homepage takeovers This iteration we designed three, built two and are showing one new homepage takeover. Branded snap appstores is live Broadsign and…

Our new team practices site, and the democratic repository behind it

A month ago, we published our web and design team practices website, from the repository that we’ve been building up for nearly two years now. I’ll try to explain why I am so proud of it. Why practices? A strong team needs…