Redesigning Recurring Payment Flow
We are working on designing wireframes for banking apps in our Rapid Ideation class. Last week, I added action buttons to the Account page based on feedback from user testing.
This week, I did an overhaul of the Account page to make everything that’s a button look more clearly like an IOS button. I added a header for “Accounts” to separate them from the mini action menu above. I added a log off option to this page.
In my last iteration I had a series of screens, or a flow, specifically for setting up Recurring Payments. When I thought about this flow, I decided to merge it with “Send Money,” as I think looking specifically in a menu for “Recurring Payments” would be unnatural for the user.
Choosing accounts and recipients in the screen above was confusing to most testers I talked to. “I guess I search for an account here?”
In the new iteration, I added a screen to allow users to select the type of payment first,
and then select a recipient:
I like the idea of a calendar to choose the day a recurring payment starts. The calendar I used in the previous iteration was much too small. This week, I experimented with scroll menus that are often used for dates in IOS, but I think I will continue searching for a way to use a larger calendar that will allow people to plan further in advance.
Previously, I used checkboxes for users to select the frequency of their recurring payments.
This week, I switched to a dropdown menu, to give the user more flexibility.
I moved the “Cancel” button away from “Save” after getting feedback that the original placement may be confusing and cause users to accidentally cancel their payment.
While the new iteration is easier to read and simplifies some choices that the user will make, I still have work to do in clarifying menu labels, styles, and making sure the user is getting all the information they need from these screens.