Maximum to Minimum Data Collection | User Assumed Contextual Information - Faves Mobile App

The Faves mobile application begins with a sign-up flow that asks users to provide a telephone number that can be collected for location based targeting if we choose to add in-app advertising for monetization. 

The skip button allows users to opt out of this data collection and takes them to a data collection page that uses the phones local capabilities for data collection. 

However users may opt even out of this feature taking them to the create account page which collects at minimum an email address.

 

Faves is an app that helps you remember all of your favourite things (raindrops, roses, whiskers on kittens) when someone asks. The mind always goes blank when people ask. 

The app also has semi social media capability allowing you to follow other users and explore trends based on your location.

From the profile page (pictured above left) you can select which of your or others faves you want to view: Movies, Music, Fashion, and others.

The user is assumed to be aware of the function of the app. By building from this assumption and that users will navigate to the profile pages, the user is further assumed to understand the information presented on the secondary page directly correlates to the previous page.

It is because of such there are only four pieces of information presented on the parent page: a title, a number next to a heart, which indicates the amount of users have added the page to their faves, and an image identifying each movie by theme or scene. 

Once clicking into each segment the user is presented with further information including: genre, summary, and reviews. None of this secondary information is absolutely necessary to what a user needs to understand at what they are looking on the previous page, in this case, titles of movies popular on the application && liked by the user of the viewed profile.