


Assurant Pocket Geek (PG) App Integration
A seamless and accessible Android mobile app redesign that integrates Assurant's core features and services.
My Team
4 UI/UX Designers,
1 Project Manager
My Role
UI/UX Designer
Timeline
12 Weeks (2022)
Project Overview
What is our mission?
To redesign Assurant’s Pocket Geek mobile app by clustering core features and services using the user-centered design process, informed by user input and research.
-
How might we cluster Assurant Home, Mobile, Auto, Cloud, and Privacy into one
coherent app? -
Should we even cluster them in the first place?
What is our solution?
A stand-alone mobile app that unifies 4 Assurant core features - Home, Mobile, Auto, and Privacy - with re-envisioned information hierarchy based on thorough analysis of user feedback.
Who is our target audience?
Assurant PG is targeting 30-60-year-old Android users.
What is our impact?
Assurant considers our redesign as a potential solution model for PG mobile future development as they transition their "individual apps" to a coherent design. This major app adaptation strives to bring enhanced user experience to over 300 million PG customers world wide.
Final Prototype
Home page
Home page lets users navigate to different devices and community feeds. It is customized for users, allowing them to manage all their devices in one place.

Device page
The device page displays all the details of a specific device, whether it's a home device, mobile device, or automobile.

Claim page
The device page displays all the details of a specific device, whether it's a home device, mobile device, or automobile.

Adapted to different user enrollment plans
New user
Regular user
Premium user
Prioritized promotions of different features and services available from PG
More customized Ads for locked features, providing feature exposure without intimidation
Ads showcasing upcoming features with completely unlocked tool page
More about our redesign process
Card Sorting
Semi-structured Interview
Why: To discern clustering patterns of different Assurant features that users would be comfortable with
​
Method: 9 sessions of in 2 rounds, open and semi-open respectively
Why: To understand participants' motivations, expectations, habits, and other behavioral patterns
​
Method: 4 sessions with a diverse group of participants we found via personal connection


Card Sorting Examples
We found answers to 2 questions
Q1: Should we even cluster all the individual apps in the first place?
A1: Users prefer a one-bundle app that group all traditional insurance-related services together
Q2: How should we cluster the features?
A2: Users are likely to cluster features by product types (mobile, auto, etc.)
Therefore, we decided to cluster PG mobile, home, and auto together, while allowing users to access PG privacy (covering all device types) simultaneously.
Defining the structure and the flow

Information Architecture

User Flow
My thoughts on this project
My team skillfully distributed tasks among members and effectively communicated with stakeholders, making this project experience incredibly satisfying. As a result, the Assurant team endorsed our clustering solution as their application's potential future step toward broader and more effective influence.
​