FACTUAL: ENGINE MOBILE APP

Self-Tracking Locomotion Data

ROLE Product Designer

WORK Information Architecture, Interaction & Visual Design

TEAM PM, Front End Engineer

Do companies trust Factual’s ability to deliver accurate data?

Sometimes they may not, which is why the Engine App was built as a supplementary app to Factual's Engine web product. With Engine Web, a customer can build a marketing campaign around a location. These campaign locations can then be viewed in the Engine app.

Additionally, the Demo app also provides a way for users to test Factual's data accuracy by showing them a timeline of where the user has gone since downloading the app.

Besides fleshing out the design logic and functionality, one big goal of mine in this project is to make the app as simple and as easy to understand as possible, especially given that it is a lightweight demo app.

How might we design a lightweight demo app that helps companies trust the quality of our data?

FEATURE REQUIREMENT

After speaking with my PM and the head of our UX team, we came up with these four features for this project:

Timeline tab

Keeps a timeline of where the user has been since downloading this app

Campaign Map tab

Allows the user to view their campaigns and send a sample push notification that models their campaign's location

Activity Summary tab

Shows the user an insightful breakdown of their locomotive activity

Settings tab

Includes account details, list of campaigns, privacy policy, and other app-related content

Final Solution

After some exploration, evaluating design tradeoffs, and narrowing down scope, below is the finalized design.

PLEASE PLAY AT MAX RESOLUTION

Onboarding + Timeline tab

 

The timeline is composed of locations with individual profiles and transitory information (i.e. walking/in vehicle).

To train the app's tracking model, users can confirm the accuracy of these locations.

Activity Summary tab

 

The Summary tab shows users a breakdown of their activity by day and by category.

Every category page contains times and locations that relate to the given category, as well as a visual comparison of how much time is spent doing the activity relative to other categories.

Campaign Map tab

 

The Campaign Map tab allows users to search for their existing campaign locations and push a test notification to the their phones as though they were there in person.

Settings tab

 

The Settings tab includes the user’s account details, information about the Engine product, a list of the campaigns created within the Engine Web app, location data integrations, and supplementary information about how the app functions.

Reflection

This app originally began as an annotation job where I had to connect the mockups together and write important notes for developer handoff.

However, as I began annotating, I quickly realized that there were a number of logical flaws and unoptimized design decisions that could be cleaned up. That realization then turned into Linda, our UX Director, handing me the project to redo. With this responsibility, I proceeded to design it to the best of my abilities and came up with the design solutions above.

I’m really grateful for her trust because it’s not everyday that an intern gets the opportunity to redesign a product that was about to be shipped.

 

Thank you!

This app was a collaborative effort with our UX Director Linda. She graciously guided me through fixing the app and making sure that the solutions were compact yet simple and easy to use.

I'm also grateful to our PM David for trusting me with this opportunity to redesign a project that was important for him to accomplish over the quarter.

 This is the end of the case study – 

Thank you for reading!

Previous
Previous

Places Insights