Reimagining the mint.com Experience 1/2
Just a quick, raw design exercise, as I look into building a UX case study for Intuit’s mint apps on iOS and iPadOS. I’m interested in improving the mint experience, as I’ve been a long-time user ever since launch and have observed several iterations of the UI—good and bad. I’ve spotted a number of problems that have nagged me since the most recent iOS redux. These include way too many entry points for any single area of the app such as Transactions; a convoluted mess of directional gestures that I find rather disorienting; and little consistency in form and function between the mobile and tablet apps.
Here is a mobile home screen concept that prioritizes Bills and Accounts, followed by a Credit Score mention. A quick report on Paid Interest comes next, with discreet jumps to personal loan offers and educational content from mint’s Blog—which is nonexistent in the apps despite content being one of the main drivers of adoption and securing trust with new users. More to come.
That beautifully welcoming geometric typeface is Venti CF by Connary Fagen
Reimagining the mint.com Experience 2/2
Here is a wireframe sketch of a userflow within a Transactions screen. The aim in this exercise is to address the problem of categorizing transactions across all your financial accounts, quickly when the algorithm isn’t able to and rules aren’t predefined by the user. The ease of use with this functionality will feed into a separate exploration I’m musing over that revolves around Daily Budgeting—a feature that I feel would provide daily value to users, which in turn can stabilize user-retention rates of the app.
Tactically, I’m leveraging the swipe interaction behavior/patterns from Intuit’s Quickbooks Self-Employed iOS app and merging that with similar interactions/patterns from Apple Mail’s app on iOS. With Quickbooks, the interaction is meant to simply categorize a transaction as either Personal or Business. In Mail, the interaction allows the user to do a number of actions relevant to the message, such as reply, flag, mark as read, move/archive, trash, etc. This design would allow the user to quickly categorize a transaction into 3 commonly used categories, or open an Overflow menu/card that gives them either the full gamut of options (see “Typical Data Fields/Actions” list) or a list of categories (not pictured—ran out of time, but you get the picture). Higher-fidelity mockups to come.
— click to open full image —