Throughout my 10 weeks in the class, I studied visual accessibility, cognitive ergonomics, usability heuristics, and inclusive design, and had the opportunity to put my learning into practice through this accessible redesign of the iOS Mail App.
In the United States, approximately 4.8 million people between the age of 18-22 own an iPhone. Many individuals in this demographic consist of college students, who use Apple Mail as a way to easily access multiple inboxes from personal to work to school emails.
Many features and functions within the mail app are clunky and not easily identifiable or intuitive to use. How might we redesign the Apple Mail App to make it intuitive, convenient, and fast?
We did a deep-dive into and redesigned the Mail App's task mechanics and visual signifiers for three main features: checking the inbox, composing a new email, and searching for old emails.
When our team first decided to take on the challenge of redesigning the entire Mail App, we found ourselves overwhelmed with such a huge, complicated task. So, in order to simplify our overall goal of redesigning the entire app, we decided to narrow down our scope by asking our intended audience of college students about the specific tasks they used the Mail App for.
After talking to students, we found that there were 3 main tasks that they used the Mail App to accomplish and decided to focus in on the usability issues within these specific task flows. These 3 tasks were:
After defining our design scope, we completed in-depth hierarchical analyses for each task to get a closer look into the task mechanics and to gain a deeper understanding of all of the minute, yet significant steps that go into completing them. Additionally, these task analyses would later serve as guides for future user testing.
Here is a closer look at our hierarchical task analyses for each of the three features:
For our first round of user testing, our team recruited 6 college students, having each student test 1 out of our 3 previously identified tasks. Each user was instructed to think out loud while completing each task, and was also asked about their general thoughts immediately after.
After each user was tested, our team then analyzed our notes by identifying the specific steps in the hierarchical task analysis users tended to struggle. This was an essential step when it came to pinpointing exactly where the users' biggest pain points were located within the app's overall task flow.
The data from one of our user tests is shown below:
Analyzing the task results also allowed us to identify the following pain points:
The majority of students enjoyed personalization in their organizational tools, such as color coding their digital calendars, creating their own digital, organizational spaces using management tools like Notion, and hand-writing their schedules through bullet-journaling.
After hearing this from so many students, we knew that we wanted our final product to include some type of personalization to make the Mail App not only more usable, but also more enjoyable for our target audience.
Even though we could have brainstormed using online tools like Figma or Mural, we chose traditional pen and paper to keep us from becoming distracted by pixel-perfect mockups, allowing us to be more playful and creative with our ideas.
Some sketches from this first round of ideation are show below:
In order to further narrow down these ideas for user testing, we decided to condense our favorite ideas into two concepts.
In this first concept, we decided to focus on increasing functionality to show to users. In short, we wanted to make it easier foe to show to users. In short, we wanted to make it easier fo see the most important information to them firstr and make it easier for them to find what they need later. After revisiting our first round of ideation, we felt that the following features we sketched out fit best with our priorities for Concept A:
For the second concept, we wanted to focus on aesthetics and visual accessibility. This meant reducing the users' visual and cognitive loads whenever they wanted to perform any of our 3 main tasks within the Mail App.
To begin our paper prototyping phase, it was essential for us to first figure out the flow of our redesigned application using what we’ve learned about our target users’ experiences, pain points, and needs. To define the flows of our two concepts in better detail, we created 6 flow diagrams, 1 for each task in each concept. These flow diagrams are shown below:
With our flow diagrams set, we were now able to create fully-fleshed out paper prototypes for testing. We opted for creating these prototypes on pen-and-paper so that we, as designers, could better focus on the information architecture of our designs without getting distracted by the visuals.
We decided to do our first testing round this way because we wanted to uncover as many errors as early as possible from people familiar with design and usability before we moved on to higher fidelity testing with a more general audience. This would allow us to get quick, yet expensive feedback as we further iterated our designs. One heuristic evaluation performed on our prototypes for sending an email can be seen below:
For our next set of prototypes, we wanted to allow our users to more seamlessly interact with the different features and flows we came up with. So, in order to do this, we decided to design medium fidelity, interactive prototypes using Figma, and used previously designed UI kits to maintain visual simplicity.
With these prototypes, we made sure to focus on scale, groupings, spacing, layout, shape meaning, and component consistency, since these were all visual elements that directly contributed to the usability of the app. To maintain our focus on usability and to keep users from getting distracted by visuals during future user testing, we did not include color, branding, photography, or micro-animations in this iteration.
To ensure the accuracy of our usability test, we wrote a detailed interview script with pre-test, task, and post-test questions. We planned on reading the script word-for-word to ensure that each participant had the same testing experience and wouldn’t be unintentionally biased.Since our target user for the app was
However, users often had a hard time distinguishing the identity of icons, as well as which ones were clickable. This prevented them from discovering some of our redesigned features, and led to us needing to guide them to the correct buttons.
At this point, the changes we had left to implement in our final iteration were all cosmetic, and mainly consisted of adding bolder and more recognizable signifiers in the form of utilizing appropriate colors and icons.
Using the issues that we identified during the usability test, we created a final list of changes to include in our final, high-fidelity prototypes.
Now that we were creating our final iteration of our iOS Mail App redesign, it was finally time to decide on the aesthetics of the app! Drawing upon previous user feedback, we knew that college students enjoyed color coding as a form of organization, and also remembered that users enjoyed apps, such as Outlook, that used colors to make their pages “pop”.
These pieces of feedback inspired us to include unique, bright, and high-contrast color schemes for each of the users’ inboxes. These color schemes would be automatically generated based on the profile picture chosen for the specific mailbox.
This upper-screen menu allows users to seamlessly navigate between their different accounts and folders by clicking their account icon or the Inbox label at the top of the screen. In order to lessen confusion and make the correct components look clickable, the relevant icons are surrounded by tiles.
To show the user’s current account and folder, we included colored borders and labels. Numbered labels are also included to show the number of unread emails in different accounts and folders.
This expanded email view allows users to quickly view the previous email threads leading up to their selected email. To further preview a specific email, the user can either click on the email they have already expanded or a previous email from the thread. Once the user previews a screen, they can either choose to expand to the full email, or go back to the previous thread view. All of the views before expanding the full email keep the email in an unread status — a feature multiple users expressed a need for during our previous tests.
This attachment bar, located under the To/Bcc/Subject lines at the top of an email draft, allow the user to keep better track of the attachments they add to their drafted emails. The attachments are shown as movable bubbles with delete buttons to allow users to easily reorder or remove attachments. The bubbles are also shown in a bright, highlighted color to ensure that users can easily tell when they have forgotten to add an attachment. When users begin typing in the attachment bar, attachment, easily distinguishable icons appear at the top of their keyboard so that they can quickly add the files they desire.
This search bar, quickly accessible through the main navigation bar at the bottom of the app screen, allows users to search within a specific folder in their current mailbox. The feature is accessible at all times through the navigation bar to ensure that users do not struggle to locate the search box. The search filters allow users to specify whether they are searching for email contents, sender names, event titles, or file names. With further development, we would also like to add add a way for users to search through all folders and inboxes at once.
These inbox filters allow users to filter their current mailbox folder to show only unread emails, flagged emails, or emails they are specifically mentioned in. This specific filter icon was chosen because it easily recognizable as a filter visualization, and is also placed at the top right corner to ensure that users can easily locate and utilize the feature.
When my team and I first started brainstorming our redesign for the iOS Mail App, we were quickly overwhelmed by all the directions the project could go in. But, once we broke the app down into 3 main tasks to redesign, envisioning the next design steps became so much clearer!
This same methodology proved to be useful further down the design process as well, when we simplified all our feature brainstorms into two concepts and tested each concept with our users. Even when we were conducting our final user tests with only one main concept to test, our team still tested users by asking them to complete each of the 3 predefined tasks, which allowed us to get more rich, directed feedback than if we had just asked them to blindly test the entire app.
As someone who highly values beauty and aesthetics, taking a class focused solely on usability came with a steep learning curve for me. At first, I found it really difficult to refrain from making our low and medium fidelity prototypes as beautiful as possible and focus on things like task flows, affordances, and signifiers instead.
Seeing this project from its conception to our final prototype, however, has shown me how helpful it was to save aesthetics for last. Keeping aesthetics out of the way until the final iteration allowed me as a designer to pay more attention to the specific pain points users experienced and pinpoint those pain points to the specific structural issues within the design system’s task flow.