Logic and syntax
Problem area: Selecting a contact is confusing and doesn’t follow ios conventions
“Oh, uh, I guess I’ll scroll through and find the gas company. Or… no? I… type?”
Problem area: Scheduling recurring payments feels cumbersome and out of order.
Proposed fix: Make “repeat” a toggle button. Have options for recurring payments show up only when “repeat” is on:
The sending money section has been really making me struggle, and I’ve had the hardest time figuring out why. I feel like I’m on repeat, going over and over one section, unsure if anything is changing or getting any clearer.
This morning, right after sitting with my coffee, I sleepily started making a to do list for the day. I didn’t get very far when I realized I was trying to create this app in a way that didn’t really make sense to me:
Dyslexia isn’t all about spelling. I make connections differently than other people. I see systems differently. This wireframing process has been a process of translation that I am very familiar with in life. I feel like every action I’ve taken is an attempt to say “This makes sense to you, right? The story I’m telling is clear?” It has been very helpful for me to put each piece in order and make some kind of logical sense of it. In thinking about the Send Money section more today, I thought about how I would actually say the proposed action to a person I was paying:
“I’ll send you $100.”
“I’ll send you $100 a week, starting next Friday.”
My previous design read: “I’ll send you $10 on Friday, and then I’ll keep doing that every week, probably also on Friday?” Much less clear!
Going forward, I’m going to think more about the way people speak, the way people think about money in their lives. Banks are are not human. Banks do this function, and that function, and that one over there, all to move money. Banks are centered on money, but need to serve people whose whole identity and self-worth and ability to do what they need are wrapped up in what amounts of money are moving in and out of their bank accounts. Credit cards are much easier to use than they are to manage. If I aim to clarify use of a banking app, do I hide the fine print or blow it up? If I expect a bunch of jargon from my bank, is not having it confusing? If I dread opening my bank app as it is, why am I creating something else that would be tiresome for me to use?
I only know the answer to the last question: I’ve been building this for other people because I know I think differently than the majority of the population. But, trying to develop a worldview that ignores your point of view is ridiculous and impossible. There’s not much more exciting to me than realizing that the way I’m seeing something is a new possibility. I feel like I’m getting to a point in these wireframes where I can start to question each part. So what can I do going forward?
-Think about syntax.
-Recognize my point of view as a strength.
-Consider how I can make this app easier and more appealing, without losing functionality. (Clearly label flows, follow visual conventions for hierarchy, give a few clear options for locating specific functions or flows, eliminate visual noise)