SketchyMedical iOS

May 2018 - Mar 2019

SketchyMedical is creating a mobile application for users to review content, take quizzes, and review flash cards on the go. I created hand-off material for our remote iOS engineer to facilitate implementation and went beyond the scope of replicating core features by adding visual design and gamification.


Redesign existing screens and complete remaining flows


2 Engineers, 1 Designer

MVP Solution

Included gamification and progress features to MVP solution


Vision for stronger community and engagement

Next Steps


What is SketchyMedical?

SketchyMedical offers time-lapse videos that illustrate a scene. These scenes or sketches are accompanied by narration to tie crucial concepts in medicine to symbols. This method is highly effective in committing information to memory and speeding up the process of knowledge acquisition.

Students aren't just learning in classrooms anymore

The majority of learning no longer happens in the classroom, but on bus rides, walks, and places outside of lecture halls. To align ourselves with this shift, SketchyMedical is creating a mobile application for users to review content, take quizzes, and review flash cards on the go.

How might we translate SketchyMedical's desktop experience into an iOS application that can be used in many contexts?

💡 Speak to unique capabilities and context of mobile engagement and follow Apple's Human Interface Guidelines


Contexts of mobile learning

Now that the majority of Americans own smartphones, they're connected to the internet "on the go". This creates more opportunity for people to learn new things, no matter where they are.

More students are opting to learn virtually over in-person lecture

The Association of American Medical Colleges (AAMC) administers the Medical School Year Two Questionnaire (Y2Q) each year to all active, second-year medical students.

I combined findings from 2014 to 2018 to illustrate interesting trends in medical education. I also grouped together participants that chose "Often" and "Most of the time" for these graphs for a more clear visualization of "yes" and "no".

Defining iOS capabilities


I broke down SketchyMedical's core capabilities on web before prioritizing features. On desktop, student's can watch videos, review symbols that are mentioned in the videos, and create quizzes based on the videos.

Due to constraints defined by the PM, the iOS app would not have the capability to stream videos for students for its launch. With data showing that the majority of users watched videos on desktop, we decided to leave out streaming for the first version. Instead, it would allow users to review symbols and have all Quiz taking capabilities so that they could effectively test themselves on mobile.

Feature prioritization

Capabilities that I would take from desktop and implement into the mobile application:

  • Review symbols of sketch - view symbol name, description, and location on each sketch
  • Shortcut to quiz through Review - quickly create a quiz with questions specific to the video
  • Quiz History - view complete quizzes and resume incomplete quizzes

Market differentiators

Based on feedback gathered from users and research focused on flash card usage in medical school, we included 2 new features in the mobile application: flash cards and search. I hypothesized that students would use these features frequently due to high demand for these tools.

  • Flash Cards - creating a system for users to study symbols after finding out that competitors take symbols from SketchyMedical to create their own flash card decks
  • Search - requested by students, allowing them to arrive at results quicker and solve the problem of manually searching for recurring symbols

Design Process

Previous designs

To give an idea of the direction I would be taking, these were some of the screens I was given from the previous designer to work off of:

Creating detailed flows

I went back and created visual flows for tasks in Review, Quiz, and Flash Cards. Within each flow, I created notes for interactions, behaviors, and requirements.

Developer handoffs

To communicate with our remote iOS developer, I used a combination of Zeplin and Airtable to keep and maintain files in one place. I organized all assets in the Airtable, linking to each file in Google Drive. I also used InVision to communicate flow.


Quiz details

User should be able to preview the details of the quiz when going through Review, such as last performance, number of correct and incorrect questions, and which video topic the quiz is on.

Reviewing quiz questions

Our doctors had created about 10 questions for each video topic. Students must be able to view the question stems, the status of the question, whether they've favorited it, and review the answers.

Editing flashcard content

Each side of the flash card can be edited to show an image of the symbol, and or a text description of the symbol definition. Text can be edited by the user.

MVP Solution

Releasing without Search

We were cutting it close to our deadline and spreading ourselves thin so I suggested pulling back features to the project manager. We decided to remove Symbol Search so that we could pay more attention to Review, Quiz, and Flash Cards. Version 1 was the planned implementation, while the 2nd filled in the gaps when Symbol Search was removed from the app.

Screens for symbol search that would be pushed for future versions

Selected features

Reviewing a symbol in a sketch

When viewing a sketch, tapping on a symbol will pull up its name and definition for quick review

Preview a quiz

View past performance on quiz questions that correlates to the topic selected through Review

Creating a flashcard

A user can create a flash card using the symbol from Review and also view flash card related activity

Selecting sections for offline access

To decrease the amount of data students use, users can choose which topics they’d like to download for offline access


Review symbols and create a flash card

In a sketch, a user can skip around using arrows buttons and tap hotspots to view symbol descriptions. They can create a flash card from each symbol they view.

Quickly take a quiz by going through Review

Review organizes all the videos by course, unit, and chapter. A user can quickly create a quiz focused on a single video by going through Review. Tapping on a choice while taking a quiz will reveal correct and incorrect answers with their explanations.

Choose topics and number of questions in Quiz

A user can select which topics and how many questions they would like to include in their quiz. Before beginning, they can review the topics and settings for their quiz.


Alongside our iOS developer, we accounted for each iOS device, following the Human Interface Guidelines and discussing differences in design. I included designs for iPad, iPhone X and iPhone 8.

Next steps

Testing and refining

After successfully implementing Review, Quiz and Flash Cards, we will prioritize bugs with our remote iOS developer using Airtable. From there we will gather participants for user testing and plan for the second phase (expanding learning mediums to audio and video for mobile use).

Success metrics

To measure success we will track:

  1. More completed quizzes to illustrate engagement with videos.
  2. Number of symbols viewed in each sketch
  3. How consistently the app is opened throughout the day to measure frequent activity


Challenge product design process and prioritizations

The project owner suggested that all the features be included in the initial launch of the iOS app so that we could create incentive for new users. I pointed out that aiming to ship all the features would increase time and cost in development and QA. I mentioned the benefits of launching the iOS app with core features as an MVP solution so that we could begin testing.

Being detailed in engineering hand-off

Working with a remote iOS developer, I further refined asset organization and standardization for communication and implementation. This helped us navigate through the correct sizes and formats.

Our consistent Zoom meetings gave me the opportunity to explain flows and reinforce them with artifacts. These conversations helped me learn more about the various constraints in iOS development.