Android Programming (03606351) PIET-DS
Mobile Information Architecture
Mobile devices have their own set of Information Architecture patterns, too. While the structure of a
responsive site may follow more “standard” patterns, native apps, for example, often employ navigational
structures that are tab-based. Again, there’s no “right “way to architect a mobile site or application.
Instead, let’s take a look at some of the most popular patterns: Hierarchy, Hub & spoke, Nested doll,
Tabbed view, Bento box and Filtered view:
Hierarchy
The hierarchy pattern is a standard site structure with an index page and a series of sub pages. If you are
designing a responsive site you may be restricted to this, however introducing additional patterns could
allow you to tailor the experience for mobile. Luke Wroblewski’s Mobile First approach helps us focus
on the important stuff first: features and user journeys that will help us create great user experiences.
Good for Organizing complicated site structures that need to follow a desktop site’s structure.
Watch for navigation. Multi-faceted navigation structures can present a problem to people using small
screens.
Hub & spoke
A hub and spoke pattern gives you a central index from which users will navigate out. It’s the default
pattern on Apple’s iPhone. Users can’t navigate between spokes but must return to the hub, instead. This
has historically been used on desktop where a workflow is restricted (generally due to technical
restrictions such as a form or purchasing process) however this is becoming more prevalent within the
mobile landscape due to users being focused on one task, as well as the form factor of the device, making
a global navigation more difficult to use.
Good for Multi-functional tools, each with a distinct internal navigation and purpose.
Watch for Users that want to multi-task.
Nested doll
The nested doll pattern leads users in a linear fashion to more detailed content. When users are in difficult
conditions this is a quick and easy method of navigation. It also gives the user a strong sense of where
they are in the structure of the content due to the perception of moving forward and then back
Devansh Parikh Page 1
,Android Programming (03606351) PIET-DS
Good for
Apps or sites with singular or closely related topics. This can also be used as a sub section pattern inside
other parent patterns, such as the standard hierarchy pattern or hub and spoke.
Watch for
Users won’t be able to quickly switch between sections so consider whether this will be suitable, rather
than a barrier to exploring content.
Tabbed view
This is a pattern that regular app users will be familiar with. It’s a collection of sections tied together by a
toolbar menu. This allows the user to quickly scan and understand the complete functionality of the app
when it’s first opened.
Good for
Tools based apps with a similar theme. Multi-tasking.
Watch for
Complexity. This pattern is best suited to very simple content structures.
Bento Box/Dashboard
The bento box or dashboard pattern brings more detailed content directly to the index screen by using
components to display portions of related tools or content. This pattern is more suited to tablet than
mobile due to its complexity. It can be really powerful as it allows the user to comprehend key
information at a glance, but does heavily rely on having a well-designed interface with information
presented clearly.
Good for
Multi-functional tools and content-based tablet apps that have a similar theme.
Watch for
The tablet screen gives you more space to utilize this pattern well, however it becomes especially
important to understand how a user will interact with and between each piece of content, to ensure that
app is easy, efficient and enjoyable to use.
Devansh Parikh Page 2
, Android Programming (03606351) PIET-DS
Filtered view
Finally, a filtered view pattern allows the user to navigate within a set of data by selecting filter options to
create an alternative view. Filtering, as well as using faceted search methods, can be an excellent way to
allow users to explore content in a way that suits them.
Good for
Apps or sites with large quantities of content, such as articles, images and videos. Can be a good basis for
magazine style apps or sites, or as a sub pattern within another navigational pattern.
Watch for
Mobile. Filters and faceted search can be difficult to display on a smaller screen due to their complexity.
Android Application Permission Model
App permissions help support user privacy by protecting access to the following:
Restricted data, such as system state and users' contact information
Restricted actions, such as connecting to a paired device and recording audio
Types of Permissions
1. Install-Time Permissions: If the Android 5.1.1 (API 22) or lower, the permission is requested at the
installation time at the Google Play Store.
If the user Accepts the permissions, the app is installed. Else the app installation is canceled.
2. Run-Time Permissions: If the Android 6 (API 23) or higher, the permission is requested at the run time
during the running of the app.
If the user Accepts the permissions, then that feature of the app can be used. Else to use the feature, the
app requests permission again.
Devansh Parikh Page 3
Mobile Information Architecture
Mobile devices have their own set of Information Architecture patterns, too. While the structure of a
responsive site may follow more “standard” patterns, native apps, for example, often employ navigational
structures that are tab-based. Again, there’s no “right “way to architect a mobile site or application.
Instead, let’s take a look at some of the most popular patterns: Hierarchy, Hub & spoke, Nested doll,
Tabbed view, Bento box and Filtered view:
Hierarchy
The hierarchy pattern is a standard site structure with an index page and a series of sub pages. If you are
designing a responsive site you may be restricted to this, however introducing additional patterns could
allow you to tailor the experience for mobile. Luke Wroblewski’s Mobile First approach helps us focus
on the important stuff first: features and user journeys that will help us create great user experiences.
Good for Organizing complicated site structures that need to follow a desktop site’s structure.
Watch for navigation. Multi-faceted navigation structures can present a problem to people using small
screens.
Hub & spoke
A hub and spoke pattern gives you a central index from which users will navigate out. It’s the default
pattern on Apple’s iPhone. Users can’t navigate between spokes but must return to the hub, instead. This
has historically been used on desktop where a workflow is restricted (generally due to technical
restrictions such as a form or purchasing process) however this is becoming more prevalent within the
mobile landscape due to users being focused on one task, as well as the form factor of the device, making
a global navigation more difficult to use.
Good for Multi-functional tools, each with a distinct internal navigation and purpose.
Watch for Users that want to multi-task.
Nested doll
The nested doll pattern leads users in a linear fashion to more detailed content. When users are in difficult
conditions this is a quick and easy method of navigation. It also gives the user a strong sense of where
they are in the structure of the content due to the perception of moving forward and then back
Devansh Parikh Page 1
,Android Programming (03606351) PIET-DS
Good for
Apps or sites with singular or closely related topics. This can also be used as a sub section pattern inside
other parent patterns, such as the standard hierarchy pattern or hub and spoke.
Watch for
Users won’t be able to quickly switch between sections so consider whether this will be suitable, rather
than a barrier to exploring content.
Tabbed view
This is a pattern that regular app users will be familiar with. It’s a collection of sections tied together by a
toolbar menu. This allows the user to quickly scan and understand the complete functionality of the app
when it’s first opened.
Good for
Tools based apps with a similar theme. Multi-tasking.
Watch for
Complexity. This pattern is best suited to very simple content structures.
Bento Box/Dashboard
The bento box or dashboard pattern brings more detailed content directly to the index screen by using
components to display portions of related tools or content. This pattern is more suited to tablet than
mobile due to its complexity. It can be really powerful as it allows the user to comprehend key
information at a glance, but does heavily rely on having a well-designed interface with information
presented clearly.
Good for
Multi-functional tools and content-based tablet apps that have a similar theme.
Watch for
The tablet screen gives you more space to utilize this pattern well, however it becomes especially
important to understand how a user will interact with and between each piece of content, to ensure that
app is easy, efficient and enjoyable to use.
Devansh Parikh Page 2
, Android Programming (03606351) PIET-DS
Filtered view
Finally, a filtered view pattern allows the user to navigate within a set of data by selecting filter options to
create an alternative view. Filtering, as well as using faceted search methods, can be an excellent way to
allow users to explore content in a way that suits them.
Good for
Apps or sites with large quantities of content, such as articles, images and videos. Can be a good basis for
magazine style apps or sites, or as a sub pattern within another navigational pattern.
Watch for
Mobile. Filters and faceted search can be difficult to display on a smaller screen due to their complexity.
Android Application Permission Model
App permissions help support user privacy by protecting access to the following:
Restricted data, such as system state and users' contact information
Restricted actions, such as connecting to a paired device and recording audio
Types of Permissions
1. Install-Time Permissions: If the Android 5.1.1 (API 22) or lower, the permission is requested at the
installation time at the Google Play Store.
If the user Accepts the permissions, the app is installed. Else the app installation is canceled.
2. Run-Time Permissions: If the Android 6 (API 23) or higher, the permission is requested at the run time
during the running of the app.
If the user Accepts the permissions, then that feature of the app can be used. Else to use the feature, the
app requests permission again.
Devansh Parikh Page 3
