SUWAVE is an audio transcription App that allows you to record audio on the go and get high quality transcriptions with easy-to-edit text instruments.
My husband suffers from chronic back pain. To manage his back pain, he needs to take notes multiple times every day. This is very tedious for him, and he doesn’t want to spend hours per day on it. Instead, he prefers multitasking, as he can’t sit or stand for long periods of time which results in him doing a lot of work while walking. The proposed app would alleviate the frustration he has encountered while making and reviewing his voice-notes.
As an influencer at bowsandtulle, I do a lot of writing, and sometimes I have my best ideas come to me when I don’t have access to a keyboard. I have found myself taking a lot of voice-notes but have also faced a problem of it taking a lot of time to convert the audio to text.
I teamed up with a Product Manager and we started to work on SUWAVE.
As a result of our brainstorming, we decided that we want to give users immediate audio recording even if they do not have an account.
STRUCTURE OF THE APP
Based on sketches and our meeting, I decided to systemize the app functions in a diagram. I have applied the ARIS BPM methodology to identify which functions we would need to develop as screens and which ones should be developed as system components.
I have used wireframes to explore questions concerning architecture and selection UI and have experimented with how much information is appropriate to reveal at every step. I have constructed a user flow diagram, seen below:
Systemize IA is one diagram that has helped me to learn the importance of low fidelity prototyping during the early stage of the project. For example, in the first version of prototyping user flow, I created a screen that will show when the user is waiting for the transaction. After I systemized the app functions in a diagram, I saw that display transaction status should be a component.
As a result of our follow-up meeting with the Project Manager, we have defined key design goals.
Very easy to start a new recording - user was afraid to miss the moment of inspiration
Easy editing navigation - transcription errors could happen anywhere in the file, so standard rewind/forward controls are not enough
Visually pleasing - note taking is rather intimate and needs to feel good
Easy to export outside of the app - the app was not meant to be a repository of notes, most users already use something advanced like Evernote or OneNote
DESIGN TO COVER DESIGN GOALS
The user can navigate transcriptions by directly clicking on a word. The highlighted text is
played back on a loop, allowing editing of hard-to-hear fragments without repeatedly
pressing the back button. The user can still use classic back and forward controls if
transcription word timestamps are incorrect.
A common frustration with voice recording apps is that they do not support external input devices. To avoid cluttering the experience, this menu shows up only when there is an external device connected.
Voice notes are often slow paced, so replaying them at a higher speed can expedite the review experience.The user can define their playback speed and back and forward step lengths.
What I learned. I learned that the more you sketch,
the better - wireframing is an important technique for avoiding mistakes and additional costs when developing. Clickable prototyping helps to understand users and engage with the product faster.