Smart Profiler Overview

SMART PROFILER (DRAFT)

**INTRODUCTION**

The Smart Profiler is a pattern created as part of the Viento project. It's goal is to tune apps to the needs of individuals living in various parts of Latin America whom are often using cheap Android phones with limited data plans.

**SMART PROFILER OBJECTIVES**

To smartly conserve battery, network and storage to create lighter, less consuming apps.
To make apps more efficient and personalized in their behavior.

**PREMISE: ONE SIZE DOES NOT FIT ALL**

People have different needs. There’s no one default. The smart profiler provides a flexible system to know the individual and to tune the app foreground and background activities to their needs, rather than having a one-size fits all solution for settings.

**HOW TO DETERMINE A CUSTOMIZED DEFAULT**

**FACTORS**

**Phone Quality (Low-end, Average, or High-end)**: Determined by screen resolution and memory)

**Storage**: Determine amount currently available and if there is an SD card

**Network (2G, 3G, 4G, none or wifi)**: This info helps us learn about which type of network the user is typically using, and helps us make an assumption about the quality of their data plan.

**Data Available**

**ASSUMED DESIRED BEHAVIORS BASED ON FACTORS**

**Low-end Phone** = resolution between x and x, memory between x and x

If a low-end phone...

Default settings should ...
Assume that the user has a limited data plan, poor battery and minimal storage.
Offer storage, battery and data options

**Average Phone** = resolution between x and x, memory between x and x

If an average phone...

Default settings should ...
Check available storage before offering storage options
Offer data options

**High-end Phone** = resolution between x and x, memory between x and x

If a high-end phone...

Default settings should ...
Assume that data is not an issue for the user; offer the options in settings, but don't prompt them to act.
Check available storage before offering storage options

**UI PATTERNS**

Something about ... UI patterns are designed to be flexible. Use the touchpoint that makes the most sense in your app. Also, something about how the style should match your app (tbd).


**ONBOARDING**

Something about when to use this UI.

Tapping on 'Limit space used by this app' takes the user to the storage options in settings.


**SNACKBAR PROMPT**

When to use it. Something about the state of a user's phone changing (ex: running out of storage or data).

Tapping on 'Fix It' takes the user to their options for storage in settings.


**SETTINGS**

We recommend following the Android guidelines for the style of settings. We've created a set of all of the possible settings. Choose the ones that apply to your app. While all of the options to tune the app are available in settings, remember that very few users will go directly to settings. This is why is important to use one of the UI patterns above to make the user aware of their options.

No implementation files, tests, or entry points are named. Start by reviewing the Viento project structure and determine whether this draft is intended as documentation or an Android implementation; completion would require resolving the placeholders and defining the profiler factors, defaults, UI patterns, and settings guidance.

Written by the indexing model from the issue text.