<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Julie Shukla on Medium]]></title>
        <description><![CDATA[Stories by Julie Shukla on Medium]]></description>
        <link>https://medium.com/@julie.shukla?source=rss-fa153beb9349------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Isx5PPDnOtcYzAQrj_AuWw.png</url>
            <title>Stories by Julie Shukla on Medium</title>
            <link>https://medium.com/@julie.shukla?source=rss-fa153beb9349------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:14:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@julie.shukla/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[LastPass password manager: usability review]]></title>
            <link>https://medium.com/@julie.shukla/lastpass-password-manager-usability-review-460b6060b713?source=rss-fa153beb9349------2</link>
            <guid isPermaLink="false">https://medium.com/p/460b6060b713</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[cognitive-walkthrough]]></category>
            <category><![CDATA[usability-review]]></category>
            <category><![CDATA[lastpass]]></category>
            <category><![CDATA[password-management]]></category>
            <dc:creator><![CDATA[Julie Shukla]]></dc:creator>
            <pubDate>Tue, 12 Feb 2019 11:15:42 GMT</pubDate>
            <atom:updated>2019-02-12T11:58:55.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MLygILqwq1KdbJQJezTXEg.jpeg" /></figure><h4>I chose to do a usability review of the LastPass application on Android (free plan — version 4.8.3450). As a passwords vault, this tool centralizes all the user’s account credentials and with the help of one master password, speeds up the login process of third parties apps and websites. This application is available on mobile devices as well as a browser extension.</h4><p>This usability review is a combination of a cognitive walk-through and an evaluation based on the <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 heuristics for User Interface Design</a> by Nielsen and Molich.</p><h3>Cognitive Walk-through</h3><p><strong>Scenario 1: </strong>Create an account after installing the app for the first time</p><p>The user just installed the app and is looking forward to start using it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RGzfia7Zkv2f7gZsx0zhww.jpeg" /><figcaption>LastPass screen flow to create an account</figcaption></figure><p>After installing the app, the user goes through a series of slides that informs him about the product’s benefits. Following this, he fills a multi-pages account creation form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pFEhOwirLOmhQ5lWpVphXA.jpeg" /><figcaption>Cognitive walk-through of account creation in LastPass</figcaption></figure><p>Through the on-boarding and account creation processes the user sees different button labels all meaning the same thing: sign up, create my account, create account. It lacks consistency and the user might doubt at what point his account will actually be created.</p><p><strong>Scenario 2:</strong> Add a site manually</p><p>The user wants to enter manually a username and password combinaison directly in the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bqLKgdDjno3rjF5EU6nPaA.jpeg" /><figcaption>LastPass screen flow to add a site</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rdB4Oug1WtjSGPM98MPYmA.jpeg" /><figcaption>Cognitive walk-through of adding a site in LastPass</figcaption></figure><h3>Heuristic Evaluation</h3><p>This usability evaluation is based on the 10 usability heuristics of User Interface Design (Nielsen and Molich).</p><p>Rather than going one heuristic by one, I chose to review the whole app by section (menu, form, sites page, settings page etc.) and points the heuristic violations I found.</p><h4>On-boarding</h4><p>On-boarding defines the whole set of techniques that make users familiar with a product. It is a critical step in setting users up for success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6f38nn6PsPYDOcPbS6ySoQ.jpeg" /><figcaption>Swipe-through slides to introduce LastPass’s benefits</figcaption></figure><p><strong>1. Skip the swipe-through and access tutorials anytime:<br></strong>A swipe-through needs to be short and focused as users cannot remember too much information at once, especially when they have not used the app yet. And most of the time, users just want to start using the app. So imposing a tutorial without possibility to skip it, is blocking the users from using the product.</p><p>In the meantime, it’s not because users skip the swipe-through that they should be abandoned in the app. LastPass is a passwords manager but also provide other useful related features so it does a good thing by providing content to empty states but on-boarding could be taken one step further by providing user-guided tour that would trigger appropriately during their exploration of the app.</p><p>Another option is to give access to tutorials from the main menu (see Evernote example below).</p><p><strong>Heuristic violations</strong>: User Control and Freedom &amp; Recognition rather than Recall</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*fd_kGx50RItawUWWRgUuGA.jpeg" /><figcaption>Evernote app gives access to tutorial cards from the main navigation menu and also provides an interactive tour as the user discovers the app and its features</figcaption></figure><h4>Floating Action Button</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U7H1Yt99YZxAgmLADJo1ew.jpeg" /><figcaption>The floating action button opens to the same set of stack icons from the Sites, Secure Notes and Fill Form Profiles screens</figcaption></figure><p><strong>1. Context over consistency:</strong><br>The floating “+” action button present on “Sites”, “Secure Notes” and “Form Fill Profiles” pages, opens to the same stack of icons and text labels (to add a site, a secure note or a form profile) wherever it is present.<br>Even though I knew the floating button opened to these 3 options, I couldn’t help myself and used to go to the page that listed the items I wanted to create (let’s says the secure notes), click the “+” and got annoyed that it used to open to these 3 options. It was slowing down my process. It should be tested with users but maybe it would be better that as the user is on a certain page, when he clicks the button he can directly create an item of the nature of this page.</p><p>On Dashlane, a direct competitor to LastPass, I found this design and thought it made more sense. If the user has reached a particular page, the chances are great that he has interest in the particular elements of that page and not all the elements from other pages.</p><p>Consistency is an important element of usability but in some cases giving preference to context is doing a favor to your users.</p><p><strong>Heuristic violation: </strong>Match between System and the Real World</p><h4>Menu</h4><p>LastPass uses a hamburger navigation menu. It is arguably not a usability issue but a tab bar menu could present advantages in term of navigation: it shows the user where he is in the app and shows him where he can go from every screen. Tab bar menu encourage the discoverability of functionalities.</p><p>In the LastPass menu, for some items, the first letter of each word use a capital (Generate Password, etc.) and some don’t (Form fill profiles, etc.). Again not a major issue, but it would be better to show consistency here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*hdyUm9w_mWX7oYCb_2gqPQ.jpeg" /><figcaption>LastPass hamburger navigation menu</figcaption></figure><p><strong>1. Menu items’ labels are difficult to decipher:<br></strong>Users’ end goals when using LastPass is to store their passwords in a safe vault and not having to remember all of them but instead accessing them with a one master password. <br>Using “Sites” is not explicit enough: users will take more time to infer the meaning of “sites” than “passwords” (as Google does) or “accounts” that refers more directly to the user’s end goal. The term “Sites” is closer to the system’s jargon than the users’ metal model and could be mistaken for say a bookmark manager.</p><p>The same goes with “Form fill profiles”, the term takes more time to interpret than “payment methods” or “addresses and more” would (see how Google does it below).</p><p>I believe the label “Emergency Access” doesn’t match with what that feature does. Emergency Access to me, refers to “how to access my account if I forgot my master password” or “what are the alternate ways I can access my account in case of emergency”. What that page actually does, I think (cause it was not explained very well), is to grant access to other app users. So maybe a label like “Grant Access” or “Share Access” would be a better match.</p><p><strong>Heuristic violations:</strong> Consistency and Standards &amp; Match between System and the Real World</p><p>For example, Google refers to “passwords” (even though the website’s URL or username are stored as well) or “payment methods” and “addresses and more” for the form automatic fill. Google understood what were users end goals and they named it plain and simply:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*G8HCjjmASp078b4mOXjLwg.jpeg" /><figcaption>In Google settings, the menu items match users’ end goals</figcaption></figure><p><strong>2. Log out button’s placement:<br></strong>In mobile apps, the log out (or sign out) button is expected to be found at the bottom of the list and in many apps, it is placed at the bottom of the settings’ menu to avoid login out by mistake. Another option, as logging out is related to the account, would be to logically keep this exit button in the account section.</p><p><strong>Heuristic violation</strong>: Consistency and Standards</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*I9jP6dRJX8YyRMw9f8VPZQ.jpeg" /><figcaption>In the Evernote app (left) the sign out button is kept in the account section whereas in the Medium app (right) the sign out button is kept under the settings section, both times it is located at the bottom of the list</figcaption></figure><p>Another issue with the log out button: there is no prompt indicating to the user that is about to log out from the system. When clicked, the user is directly logged out and taken to login page.</p><p><strong>Heuristic violations: </strong>User Control and Freedom &amp; Error Prevention</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/359/1*rAUT_gl5tc7SVTmmjn44hQ.jpeg" /><figcaption>In LastPass the Help section is accessed from the Settings menu</figcaption></figure><p><strong>3. Help and Support location in the navigation:<br></strong>The “Help and Support” is an important functionality especially for the novice users. They need to find it quickly and effortlessly. The Help section should be placed in the main menu navigation.</p><p><strong>Heuristic violation</strong>: Help and Documentation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/276/1*J0ZYJ2iB6xqNkNQGmStBtA.jpeg" /><figcaption>Help is accessible from the main navigation menu in the Medium app</figcaption></figure><h4>Forms</h4><p>LastPass requires to be populated with data from the users. When users login for the first time to a 3rd party app, LastPass will automatically propose to save the credentials. But if the user wishes to enter data directly in LastPass, the forms that make this possible, need to be clear and easy to fill.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/1*SIIbaRYrBS1vc67Mup4hhw.jpeg" /><figcaption>LastPass prompts error only after form validation</figcaption></figure><p><strong>1. Errors are informed after form submission:<br></strong>In LastPass, the form entries are not validated until after submission. The error message displayed is out of context with no actionable recommendations. Also there is no indicator for required and/or optional fields.</p><p>Real time inline validation informs the user immediately and don’t cut his flow as it gives actionable error message. And if a majority of fields are optional, the required fields needs to be made visible.</p><p><strong>Heuristic violations: </strong>Error Prevention &amp; Help users Recognize Diagnose and Recover from Errors</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*BKlYmzW1HHFU3MK8Q5SYMA.jpeg" /><figcaption>Real time inline validation informs the user immediately and before the form is submitted</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*cVxCkT2JHV1qcUdh74yvoQ.jpeg" /><figcaption>LastPass Form Fill Profile page</figcaption></figure><p><strong>2.</strong> <strong>Form readability:<br></strong>Visually the forms lack discoverability:</p><ul><li>labels are red and red tend to be associated with error messages</li><li>labels seems to equal distance from the previous input and the next</li><li>inputs fields are represented by a single line (low discoverability)</li><li>grey section titles (“profile information”, “personal information” etc.) have less visibility, especially with the red labels</li></ul><p><strong>Heuristic violation:</strong> Consistency and Standards</p><p>Some solutions include:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*K3fu7MEemE_wRCN2zOLdUA.jpeg" /><figcaption>Providing containers to the text fields improve their discoverability</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/175/1*bSDuRSJgXjYCVShVQY1gVw.jpeg" /><figcaption>Providing better visibility to section titles allows the user to scan the form with better efficiency</figcaption></figure><h4>Visual Consistency</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*JSpv4zCwH1O8Uz2ec0zaBQ.jpeg" /><figcaption>LastPass section titles have visual inconsistencies</figcaption></figure><p><strong>1. Section titles’ inconsistencies:<br></strong>In the settings the section (or partition) titles are small and red and in the forms the section titles are grey and indented, whereas the input label are red.</p><p><strong>Heuristic violation: </strong>Consistency and Standards</p><h4>Sites</h4><p>It is in this section of the app that are listed all the username and passwords combinations. Like I mentioned in the menu part of this article, the term “Sites” might not be the best choice to represent this feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*EwRXcm7hGXNfCX7aOfrMlg.jpeg" /><figcaption>LastPass stores users’ password in folders</figcaption></figure><p><strong>1. Creating folders only from new entry:<br></strong>When it identifies a website, LastPass automatically organizes the sites (or passwords) in category folders or gives the possibility to users to create their own folders. But creating folders is only possible from a “Add Sites” page and once a folder is created, it’s impossible to modify or delete. I found that quite frustrating and restrictive.</p><p>On desktops for example, we are used to create folders on the go and store documents inside with the possibility of renaming or deleting them. It’s very flexible in comparison. In LastPass there should be a more flexible design solution to organize the users’ passwords.</p><p><strong>Heuristic violations:</strong> Match between System and the Real World &amp; User Control and Freedom</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/1*TZzeVP9yOfl1aOtMpDrqag.jpeg" /><figcaption>In LastPass, feedback on saving an entry is not appropriate</figcaption></figure><p><strong>2. Inappropriate feedback on saving an entry:</strong><br>After pressing the “save” button, the page’s content is scrimmed and a dialogue prompts containing only a circular progress indicator and a “Please wait” message. The dialogue box disappears within few seconds and the user is taken back to the list of sites.</p><p>This type of feedback on saving an entry has been also observed in the “Secure Notes” and “Fill Form Profiles” sections.</p><p>Dialogues are highly interruptive as they disable all app functionality to attract users’ attention and in practice as their name suggest, they require at least one action from the user (text button for example).</p><p>When the system needs to give an informational feedback to the user, for a short amount of time, about occurring actions (or for actions that just occurred) and with no action required from the user’s side, it is better to use a snackbar. They catch just enough attention from the user to let him know what is going on (or just happened) and they don’t cut his flow.<br>Also the text displayed must state clearly the occurring actions (or actions that just occurred), such as “Saving the Site”.</p><p><strong>Heuristic violations: </strong>Visibility of System Status &amp; Consistency and Standards</p><p>In comparison, the Evernote app, upon saving an entry, displays a snackbar at the bottom of the screen with the text “Saving note in [location]…”.<br>The message informs the user with better precision and is not so much interruptive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/348/1*-Al40qCcLnro_pV41t7eNw.jpeg" /><figcaption>Evernote app’s feedback doesn’t cut the user’s flow</figcaption></figure><h4>Secure Notes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*55CPqInhJOA_KwGD1TtyzA.jpeg" /><figcaption>LastPass Secure Notes enable users to store digital records (such as Insurance cards, memberships, WiFi passwords, etc.)</figcaption></figure><p><strong>1. Missing information regarding the categories:<br></strong>When the user click on “Add Secure Note” he is expecting to be taken to a form to make a new entry. Instead a list of items are presented to him. It would be good to explain what are those items and what he is supposed to do. For example “select a category” for the new secure note.</p><p><strong>Heuristic violation</strong>: Help and Documentation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/1*3oZ8MgjsERIziBr-6JrS0w.jpeg" /><figcaption>LastPass list of Secure Notes does not provide categories filters</figcaption></figure><p><strong>2. Category filters missing:</strong><br>No filters, users can only jump from folder to folder. When the user creates a new secure note he is prompted (compulsory) to choose a category for his note, so the least would be to allow him to sort his notes by category. The only mean of sorting the secure notes are by folder but the folders can only be managed inside a “add secure note” page.</p><p><strong>Heuristic violations</strong>: Aesthetic and Minimalist Design &amp; Flexibility and Efficiency of Use</p><h4>Form Fill Profiles</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SVGNWkSCkAUj0DLxjLX5SA.jpeg" /><figcaption>LastPass Fill Form Profile allows users to save and auto-fill more than just login form credentials</figcaption></figure><p><strong>1.Feedback on conditional formatting</strong>:<br>Some inputs seem to require special pattern to be validated (such as email). If the user does not enter a value that matches the pattern and he submits the form absolutely nothing happens.<br>There are no error messages indicating that a particular entry wasn’t matching any pattern, there are no real time inline validation around the text field. <br>The only feedback is that the save button doesn’t respond.</p><p><strong>Heuristic violations</strong>: Visibility of System Status &amp; Help users Recognize, Diagnose and Recover from Errors</p><p><strong>2. Phone numbers:</strong><br>On the right side of the phone numbers labels there are arrows pointing down. But they seems inactive or to have no use, because nothing happens when clicked. In other fields (such as “Title”), when clicked, a drop down opens.</p><p>The presence of the “+” sign on the left side of the phone numbers inputs are confusing. Is it to indicate that the next input if for country indicative (the next input label says “phone number” so no)? Or is there the possibility to add more numbers (nothing happen when clicked, so no)?</p><p><strong>Heuristic violations: </strong>Visibility of System Status &amp; Match between System and the Real World</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s77iOOknZDdbnB88tgaJgA.jpeg" /><figcaption>The “Form Fill Profile” form (here titled 90°) requires a lot of scrolling</figcaption></figure><p><strong>3. The length of the form:</strong><br>Like it is seen on the above screenshot, the form is way too long. It represents a lot of scrolling and can scare off users as they decide what they should fill in.<br>It would be a good idea to use accordion for some parts of the form. Or even better, instead of having one long form that contains every possible entries, propose like for the Secure Notes, categories of commonly found forms, that users can relate to, such as addresses, payment methods, custom forms, etc. It will reduce the length of form and will not overwhelm users.</p><p><strong>Heuristic violations: </strong>Aesthetic and Minimalist Design &amp; Match between System and the Real World</p><h4>Security Challenge</h4><p>The Security Challenge audits the user’s passwords and uses gamification (with ranking and scores) to help them improve the strength of their passwords.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/393/1*Dkp6lrb9QN0RytWFjuEOeg.jpeg" /><figcaption>LastPass Security Challenge is a gamification type of audit of all the user’s passwords strength</figcaption></figure><p><strong>1. Unnecessary repetitive action:</strong><br>Every time the user closes the app, he has to reload the data by pressing again the “start the challenge” button.<br>Once he clicks “start the challenge” the information about the LastPass Security Challenge displayed on the tutorial page are not visible anymore (until he closes the app and opens it again).</p><p>In the mean time, these information would be quite useful on the ”Summary” page as there is no indication of what the score is, what the rank is etc. It would be better to remove the “tutorial” page and keep the tutorial’s information on the page’s content.</p><p><strong>Heuristic violations</strong>: Recognition rather than Recall &amp; Help and Documentation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UogpP5r9Hd4K0dREjaRWfQ.jpeg" /><figcaption>The LastPass Security Challenge’s presentation of data can quickly overwhelmed users rather than encouraging them to act of it</figcaption></figure><p><strong>2. Poorly design data overview:</strong><br>There is a lot of non-actionable raw data and users cannot make out what are the most important ones. As a result, we don’t understand what is the purpose of this page: it’s hard to focus and get a clear overview.</p><p>It would be nice to have a pleasant analytical dashboard that would provide glance overview of crucial information that would be useful to the users and would be visually appealing to drive them to decision making.</p><p>From the dashboard users could provide actionable controls, for example if there are duplicate passwords for a same account eliminate those (maybe test which one of the duplicate is the actual current password and eliminate the obsolete ones). When a password present a poor strength score, propose the user to change it for a stronger one, if it’s technically possible (would require to change the record on the 3rd party app/website) or at least accompany him to do so.</p><p>Another idea would be to make this dashboard the homepage of the application and the user could navigate the application from there (much like a bento box navigation).</p><p><strong>Heuristic violations:</strong> Consistency and Standard, Aesthetic and Minimalist Design, Recognition rather than Recall &amp; Flexibility and Efficiency of Use</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/237/1*d8fQbJIDeS3Vqeb3wjkaQA.png" /><figcaption>Dashlane, a direct competitor to LastPass, propose a dashboard of password’s strength that encourages the users to be proactive and efficient</figcaption></figure><p><strong>3. Icons inconsistencies:</strong><br>The “i” or information icon, when clicked, will display information in 3 different ways so the user will never know what to expect with this icon.<br>In some cases, the “i” has a extendable/collapsible function but gives no indication of that: once the information revealed the “i” button remains the same. Sometimes it will open a dialogue box.</p><p>In addition, the information that are then displayed are getting over complicated and quite long.</p><p><strong>Heuristic violation: </strong>Consistency and Standards</p><h4>Browser &amp; Search</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*r4rRAvMmwAunrgMHN2EElQ.jpeg" /><figcaption>LastPass Browser and Search feature</figcaption></figure><p><strong>1. Functional redundancy:</strong><br>In LastPass, the “Browser” (which has a dedicated landing page) and the “Search” feature (accessible from other pages such as “Sites”, “Secure Notes” and “Fill Form Profiles”) propose both the same functionality: perform a search in the “vault or web”.<br>User interface complexity increases when a single feature is present in multiple ways. Users rarely understand duplicates as such, and often waste time repeating efforts or visiting the same page twice by mistake.</p><p>Avoid functional redundancy and merge this functionality in one entity for more simplicity. We can also question the use of having a browser in this app: what is its use? what does it bring to the users? it is really one of the users’ end goals? I feel it brings more confusion than benefits to the app. If the app owners saw a benefit in this feature, they failed to explain or show what it is; they failed to reduce the Golf of Execution.</p><p><strong>Heuristic violations: </strong>Match between System and the Real World &amp; Aesthetic and Minimalist Design</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RPOB5Qpvfehbl8TXLpvtrw.jpeg" /><figcaption>When the user reaches the browser (from the search screen), if he presses back button the app closes</figcaption></figure><p><strong>2. Violation of the go-back button expectation:</strong><br>The user can perform a search from either of the following pages: “Sites”, “Secure Notes” or “Fill Form Profiles”. From the “Search” results page, if the user chooses to visit a web result, he is redirected to the LastPass’s Browser.<br>If the user decides to use the go-back button the app closes.</p><p>This violate the user’s go-back button expectations, because as he did not leave the LastPass app, the user would expect to be taken back to the “Search” results page.</p><p>This is another clue that the functional redundancy of the “Browser” and the “Search” brings to much complexity to the app.</p><p><strong>Heuristic violation:</strong> User Control and Freedom</p><h4>Generate Password</h4><p>This LastPass’s feature creates random complex and secure password strings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/369/1*XQ_jhceO2LbjNVraeti2mA.jpeg" /><figcaption>LastPass generates secure password strings</figcaption></figure><p><strong>1. Low actions discoverability:</strong><br>The icons for re-generating a password string and copy to clipboard are barely noticeable. I personally missed them the first few times I opened the password generator and was wondering how can I copy this password string.</p><p>There is a need to increase the discoverability of this icons: find a new placement, new color to make the icon more noticeable on the screen.</p><p>Moreover, a user’s understanding of an icon is based on previous experience. Text labels are necessary to communicate the meaning and reduce ambiguity.</p><p><strong>Heuristic violations:</strong> Visibility of the System Status &amp; Aesthetic and Minimalist Design</p><p><strong>2. Misleading button label:</strong><br>The label “Save” is misleading. When the user presses it, he is taken to a “Add Site” page. So the use of the term “save” can be confusing to the user as he might assume some of the following: does it copy? Where does it save?</p><p>The action button should affirm what task the user will perform when he clicks that button. It should be clear and specific to the task.</p><p><strong>Heuristic violation: </strong>Consistency and Standards</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*Ru35o_LmtqGMSxnbjGJSUQ.jpeg" /><figcaption>LastPass makes users adjust the password’s length with a slider</figcaption></figure><p><strong>3. Slider is difficult to manipulate:</strong><br>LastPass provides a slider to select the desired password’s length. The issue is that it is very difficult to use: it is imprecise and it becomes frustrating to select a accurate number.</p><p>On touch screens, sliders should be use only when the precise value doesn’t matter (for selecting approximate range for example a price range) as they are difficult to manipulate and imprecise.</p><p>Consider a different element that allows users to tap or type to specify their choice.</p><p><strong>Heuristic violations: </strong>Aesthetic and Minimalist Design &amp; Consistency and Standards</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*S0ky0cSnP_yhUd5k8JM2LA.jpeg" /><figcaption>The Settings section cannot be collapsed back</figcaption></figure><p><strong>4. Settings are not collapsible:</strong><br>When the user clicks on the text button “Settings” a section with settings to customize the password opens but the “Settings” text button disappears.</p><p>It removes context to the content that just appears and prevents the users from closing back this section.</p><p><strong>Heuristic violation:</strong> User Control and Freedom</p><h4>Sharing Center</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6JpPuqq6qohun-minkJtkw.jpeg" /><figcaption>LastPass Sharing Center doesn’t seem to be working</figcaption></figure><p><strong>1. No perceived signifier:<br></strong>The empty state’s content informs us that the Sharing Center is where users can share folders with people on their team. So there is a fact that this action is true and possible (affordance). But besides not being sure what those folders are and what the team is, I perceive no signifier on the page to proceed in sharing items (no button, no options from the overflow menu).</p><p>So either the affordance is hidden: the signifier is missing from the screen and this is a bug. Or it is a false affordance: there is information that leads the user to think he can do something when actually he cannot. Maybe because this feature is not available in the free plan but if it is the case it should be explained to the user and made disabled.</p><p><strong>Heuristic violations</strong>: User Control and Freedom &amp; Help and Documentation</p><h4>Emergency Access</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*RFMi31guu_DsjMXKBp0i0Q.jpeg" /><figcaption>LastPass Emergency Access manages the user’s vault access to person of trust</figcaption></figure><p><strong>1. Confusing terminology:<br></strong>I found the choice of terminology a bit confusing and not too straightforward, especially the “People who trust”. There is clearly a word missing there.<br>But maybe the two tabs are too similar and are only differentiate by the subjects “I” and the “who”, so not too noticeable.</p><p>Also, when the user makes an entry he is prompted to enter an email address (a LastPass account is linked to an email address), not a first name or a last name, not a picture or any information that refers to “people” but rather to a “contact”.</p><p><strong>Heuristic violation</strong>: Match between System and the Real World</p><p>In Dashlane, they refer to “Your emergency contacts” and “Added you as an emergency contact”. I am not a linguist, but I found the Dashlane terminology more intuitive, noticeable and clear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*keZDfMXJ7H3utaz7IK_9cA.jpeg" /><figcaption>Dashlane terminology in the Emergency Access section is more clear and straightforward (desktop view)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/367/1*qSwEKaJjONF3Deey8SCcCA.jpeg" /><figcaption>LastPass’s Add Access dialogue box</figcaption></figure><p><strong>2. The Add Access dialogue:</strong><br>From the “People I Trust” page, when the user presses the add floating button, a dialogue box opens to grant access through email address. First the user is presented with a text field input to enter an email address and then a paragraph explaining what this feature is about. I feel like this first paragraph would be of better use if placed before the email address input.</p><p>The rest of the instructions are very confusing: I am on the “Add Access” page and I am told about “when my trusted contact requests emergency access, I can decline”, then I am asked to chose a “Wait time”... I think this is again system jargon and LastPass failed to explain the rest of this critical feature in a way that users can understand quickly and effortlessly.</p><p><strong>Heuristic violations:</strong> Match between System and the Real World &amp; Help and Documentation</p><h4>Settings</h4><p>I found the settings section to be daunting. It is a part of the application very difficult to understand, very confusing. It can and should definitely be improved.</p><p>There are a lot of settings options, sometimes repeated twice across screens or settings options are not explained properly and feels like two options do the same things.</p><p>There are so many settings options I couldn’t go in details of each and every one of them so instead I am showing the ones that gave me the most issues.</p><h4>Settings — Account</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQ37UGiKBriFxJkSBMhv2Q.jpeg" /><figcaption>LastPass account settings screens</figcaption></figure><p><strong>1. Deep navigation in the account settings:</strong><br>At this point the user went through the “Settings” menu, then selected “Your LastPass Account” and yet, he still have to click again “Account Settings”. And once he clicks “Account Settings” he has access to a single big red button saying “Change Master Password”.</p><p>The navigation should be broad and shallow rather than deep. It is more likely the users will need to have access to “Change Master Password” more than upgrading their plan. So it doesn’t make sense to keep it one level down in the navigation. And keeping one whole page for a big red button doesn’t make sense also.</p><p><strong>Heuristic violation: </strong>Consistency and Standards</p><h4>Settings — Security</h4><p>I have found some issues in the security settings. For example, I have toggled on the “Lock when screen is turned off”, if I close the app, lock my phone, open my phone, open LastPass, I am not prompted to enter the password again! So either I didn’t understand that setting properly or it is a big security issue. Either way, there is a problem there.</p><p>Also I didn’t understand the difference between the “Lock” and “Log out” setting”. How each of these settings will affect differently the way I access the app? Because, they seems quite the same to me. As I am not sure how this Security section work, I am not able to propose a solution to improve it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/413/1*SFbuGZMP-_6WU4bexYzjVA.jpeg" /><figcaption>LastPass security settings</figcaption></figure><p><strong>1. Confusing instructions:</strong><br>This setting’s description (among others) is unclear: the user would have to guess what is an “item re-prompt”. Also the default option for this setting makes it even more confusing: the “skip” is “disabled” (double negation). It increases the user’s cognitive load.</p><p><strong>Heuristic violation:</strong> Match between System and the Real World</p><h4>Settings — AutoFill</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*k7KGWPLopNnmSD8_C4aw-Q.jpeg" /></figure><p><strong>1. Term “Miscellaneous” is too vague:</strong><br>Miscellaneous is not a term users are used to find in a settings menu. It is too vague and gives no clues what is it be found under that section.</p><p>And then once inside this Miscellaneous page there are some options about showing the “fill helper bubble” for browsers and apps. I haven’t still found what it does exactly. Some instruction regarding this feature would be helpful.</p><p><strong>Heuristic violations:</strong> Match between System and the Real World &amp; Help and Documentation</p><p><strong>2. Menu item naming consistency in the navigation:</strong><br>This menu item “Autofill notification settings” text does not match the title of the page it opens “Show fill helper for apps”.</p><p><strong>Heuristic violation:</strong> Consistency and Standards</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*uE3609XTqlngcAePF8Xuhw.jpeg" /></figure><p><strong>3. Functional redundancy:</strong><br>The same functionality can be found under two setting menu items: “App settings” and “Autofill notification settings”. The user can “Show (or hide) Fill Helper” for a given account (or site).</p><p>The only differences are:</p><ul><li>the function “Show Fill Helper” can be applied to all accounts (or sites) in the “Autofill notification settings”</li><li>another function “Do not show fill window” is available in “App settings”</li></ul><p>Duplicating functions increase user interface complexity and will confuse the user. Merging the both screens into one feature and renaming it in something more familiar to the users would bring simplicity and would bring confidence to use the feature.</p><p><strong>Heuristic violation:</strong> Consistency and Standards &amp; Match between System and the Real World</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*Jz1lvSPUizBbTDgNX_G8SA.jpeg" /><figcaption>In the LastPass Autofill Settings screens many system objects seems to mean the same thing but are named inconsistently</figcaption></figure><p><strong>4. Naming convention consistency:</strong><br>In the AutoFill settings section, many terms are quite similar to each other and yet we are not sure what they refer to and if they refer to the same thing or something different.</p><p>System objects should be named consistently across the whole interface and speak user’s language.</p><p><strong>Heuristic violation:</strong> Consistency and Standards &amp; Match between System and the Real World</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a2kGcCclSRXegUw5oLVE3Q.jpeg" /><figcaption>The same LastPass Autofill settings menu changes name depending from where it is accessed</figcaption></figure><p><strong>5. Menu item label inconsistency:</strong><br>This menu setting can be accessed either from the Settings menu or from the sticky notification that appears in the phone when logged in LastPass. The only issue is that the name of the title of this settings page changes according from where it was access.</p><p>I got confused at first I thought it was a whole new menu accessible only from the sticky notification.</p><p><strong>Heuristic violation:</strong> Consistency and Standards</p><h4>Settings — Search</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/1*nAfP-0MwpZiOYZqvStlq1Q.jpeg" /></figure><p><strong>1. Inaccurate instructions:</strong><br>This setting’s instruction doesn’t communicate clearly its function. Maybe it’s just me, but it took me time and testing to understand that it allows the search string query to parse in the content of the Secure Notes (not only in the note’s title).</p><p>This setting option needs a redesign so there are no doubts to what it does.</p><p><strong>Heuristic violation:</strong> Match between System and the Real World</p><h4>Settings — Browser</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fCQRMEWsIGbxCLqjrm1O7w.jpeg" /></figure><p><strong>1. Grouping similar functions together:</strong><br>“Launch to” setting gives 2 options: either to select the LastPass browser or the Default Browser (whatever it means).<br>There is also another setting to “Set default browser”, at the bottom of the settings’ list.</p><p>These two settings seems linked to each other, they should be grouped together. To bring more clarity, maybe merged the two settings into one.</p><p><strong>Heuristic violation: </strong>Match between System and the Real World</p><p><strong>2. Unclear dialogues lead to failure to set the default browser:</strong><br>The instructions could not be more unclear and confusing: first the user that presses on “Set default browser” will expect to be able to select a browser app that will open when he opens a web page from LastPass app.</p><p>Instead, a pop-up opens with a message that isn’t explicit enough and a only a “OK” button with no other choice: the user’s only option is to agree to vague instructions. Finally once he presses “OK” he is redirected to a browser’s homepage.</p><p>The communication style needs to match with the context and should speak the user’s language.</p><p><strong>Heuristic violations: </strong>Match between System and the Real World &amp; Help and Documentation</p><h4>Settings — Actions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*sW0Tc6yEUv146cEC1uSd_Q.jpeg" /></figure><p><strong>1. Unclear terminology:</strong><br>The term “actions” is ambiguous and too wide in meaning.</p><p>Rename this section “maintenance” or “vault maintenance”.</p><p><strong>Heuristic violation:</strong> Match between System and the Real World</p><p><strong>2. Hidden potentially important feature:</strong><br>The action “Refresh vault” seems to be an important feature: refresh implies that the content is not automatically up-to-date and the user might need to perform this action if he used the app from another device. If the content needs to be refreshed, a button and instructions should be present on the content’s page itself.</p><p>The refresh button should be visible from the vault instead of requiring the user to think about how to perform this action.</p><p>In addition, there is no feedback when this setting is pressed: we don’t know if it worked or failed.</p><p><strong>Heuristic violations:</strong> Recognition rather than Recall &amp; Flexibility, Efficiency of Use, Help Users Recognize, Diagnose and Recover from Errors &amp; Visibility of System Status</p><h4>Settings — Help and Support</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/1*gS0Dr5MlfBB9MXYSdG1Leg.jpeg" /></figure><p><strong>1. Hidden hyperlinks:</strong><br>The item “User manual” takes the user to an external link with no prompt. There is no indication that it is an external link (missing signifiers).<br>The item “Report a problem” acts like a “mailto” and on pressing it a email draft opens a blank email with a pre-filled LastPass email address.</p><p>The labels need to give a better description of the action that will happen when clicked on, such as “Open online user manual” and “Write to us”.</p><p><strong>Heuristic violation:</strong> Flexibility and Efficiency of Use</p><h4>Settings — Advanced</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZQopvd631NVFVHV5dd5ukQ.jpeg" /></figure><p><strong>1. Options unclear:</strong><br>Like other settings’ pages, the instructions are unclear and use ambiguous terminology (system jargon): among the worst are “Enable LastPass input method”, “Default site action”…</p><p><strong>Heuristic violation: </strong>Match between System and the Real World</p><p><strong>2. Unclear and confusing storage settings:</strong><br>The “Local data location” settings only gives two options: “Default” or “Memory card”. By default, I must assume that “default” means the phone’s internal storage. <br>Also there is no possibility for the user to choose the path of folder where to save “local data”. If it’s for security reasons, then the user should be informed about it.</p><p>In the same manner the “Local attachment location” proposes a “Default” option and an “Internal memory” option. So the default option would be the memory card here?</p><p><strong>Heuristic violation: </strong>Match between System and the Real World &amp; User Control and Freedom</p><h4>With 3rd party apps</h4><p>LastPass is not just about storing passwords in a safe vault, it’s simplifying their users’ life by not having to type the password: it automatically fills it in the login forms and theoretically other type of forms (bank cards, addresses etc.).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u6m-r1P7m1GzQWi89C0klA.jpeg" /><figcaption>LastPass presentation of its password Autofill feature</figcaption></figure><p>I tested on the Myntra app the LastPass password Autofill:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*rp-jucPtFOyeOnM8aLmSPg.jpeg" /><figcaption>On 3rd party app, LastPass autofill prompts only when reaching the password’s input (here Myntra app)</figcaption></figure><p><strong>1. Autofill does not prompt until the user reaches the password input:</strong><br>LastPass Autofill feature prompts only when the user put the cursor on the password input. Sadly, all login forms first input is the one that identify the user (email, phone number, username etc.) and then comes the password input. A hack is to first press the password input and then it will propose to autofill all the inputs.</p><p>The first time users might think something is not working properly or doubt their skills as they would expect the feature to work as soon as they arrive on the first input.</p><p>Design solutions should comply with users’ expectations.</p><p><strong>Heuristic violation: </strong>Consistency and Standards</p><p>The autofill of forms was tested on Swiggy (address form):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*ERaDgSYHKjLBFNrdFCbfqQ.jpeg" /><figcaption>The Autofill does not prompts for the forms (here Swiggy app)</figcaption></figure><p><strong>2. The autofill of form did not prompt:<br></strong>I have checked the (complicated) settings but I was not able to have an autofill of the address I had saved in LastPass in my Swiggy app. Maybe it works only in the browser (not in apps) or only on desktop?</p><p>Nonetheless, it didn’t work and users would be disappointed and confused as they wouldn’t know the reasons, doubting their skills.</p><p><strong>Heuristic violation:</strong> Consistency and Standards</p><h3>Conclusion</h3><p>Overall the app is quite system jargon oriented and is over-complicated. It is especially true for the settings.</p><p>The settings section is really overwhelming and needs to be redesign: less options, better documentation and with words that users will understand. To be able to personalize their environment gives a sense of control to the users.</p><p><em>Disclaimer: I am not affiliated to LastPass or any of its competitors.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=460b6060b713" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pill Trakk: medication reminder - UX case study]]></title>
            <link>https://medium.com/@julie.shukla/pill-trakk-medication-reminder-ux-case-study-abbcb31169b9?source=rss-fa153beb9349------2</link>
            <guid isPermaLink="false">https://medium.com/p/abbcb31169b9</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Julie Shukla]]></dc:creator>
            <pubDate>Thu, 27 Dec 2018 11:29:14 GMT</pubDate>
            <atom:updated>2019-06-11T10:29:13.046Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dLEc8uz940UOoi4PLBgKBw.jpeg" /></figure><p>This article proposes a design concept for a medication reminder app.</p><p>This first version of this project is based on user hypothesis and hopefully, in the future, I would propose another version enriched with actual, from the field, user research. Nonetheless, this case study contains support material for user research, such as behavioral variables and interview questions. The primary persona developed is a proto-persona (or persona hypothesis, based on the support material of user research).</p><p>This document contains the following deliverables:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mfxoAE75zZOET2sS4AgLHg.jpeg" /><figcaption>Case study deliverables</figcaption></figure><h3>1. Research</h3><h4>Scope definition</h4><p>This project addresses the issues of medication non-adherence.</p><p>Medication adherence usually refers to whether patients <strong>take their medications</strong> as prescribed (e.g. twice, daily etc.), as well as whether they <strong>continue to take</strong> a prescribed medication. Failing to do so (non-adherence) will be prevalent and associated with adverse outcomes and higher costs of care as the medical situation could worsen.</p><h4>Topic research</h4><p>In order to propose adequate solutions, we need to understand what are the causes of non-adherence to medical plans. What are the pain points that prevent a patient to follow its prescribed treatment?</p><p>According to the World Health Organization the causes of non-adherence to medical plan can be grouped in 5 dimensions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5RTFHr30PUAaRd03pzuR-w.jpeg" /><figcaption>5 dimensions of non-adherence causes</figcaption></figure><p>In a survey of 10,000 patients from the Boston Consulting Group, the most common reported reason for missing medications was forgetfulness (24%), followed by perceived side effects (20%), high drug costs (17%), and perception that a prescribed medication would have little effect on their disease (14%).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FHi_ZX_Jnq9AE08H8Xs4rA.jpeg" /><figcaption>Results of BCG’s survey on causes of non-adherence</figcaption></figure><p>The forgetfulness factor would be levied with the help of a reminder in form of an alarm when intake is to be taken, which is the purpose of the app.</p><p>To counter the non-adherence related to perceived side effects, adverse drug reactions, health literacy, characteristics of the disease, the app could also educate the user about the drug form the prescribed medication plan. For this, it is assumed that there will be access to a large worldwide database of documentation about medication in circulation. This way, the user will be able to know what are the known side effects of the medication he or his dependents are following.</p><p>For the high drug costs concern, gain access to a worldwide database of medication would be required. The idea would be to propose a cheaper alternative to medication (called generic). Usually, a prescriber will write a prescription for a specific brand of drug. Generic drugs are the same molecule as a prescribed brand drug, they have the same effect and purpose to cure illness but are cheaper, less known. It could be good to propose to the user these alternatives.</p><p>To address social support and cognitive functioning, the reminder could include the family members’ treatment plans of the app user, such as children or elderly dependents.</p><h4><strong>Competitive analysis</strong></h4><p>3 direct competitors were selected for the competitive analysis: Medisafe, CareZone and Mango Health. All these competitor’s product aim to be a pill reminder but they all have different visions on the features that should be proposed to the users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2bbl-b5iwaBptqjq0cRuow.jpeg" /><figcaption>Competitive analysis</figcaption></figure><p>Medisafe clearly stands out in the market. As compared to other, it focuses on its main goal which is to be a pill reminder. Its solution is very straight to the point, no extra features and even though the drug database is for USA crowd, it can be easily used by worldwide users.</p><p>Another point that came out from the competitive analysis is that, strangely, any overview or data visualization is quite profile oriented. When it comes to a pill reminder app, everyone would want to add many patients to the list of drug recipients: like a parent would want to be able to add its children. But on a daily overview of upcoming intakes, none of the competitors propose that feature where all intakes, for all recipients can be seen.<br>So is it a mistake from their side? Or is there a reason for that?</p><p>Our solution could focus on users that are in charge of many dependents and have a need to see quickly all those intakes, without having to switch from dependent’s profile to dependent’s profile. That could give a competitive advantage.</p><h4>User inquiry support material</h4><p>As explained earlier, this version of the design process will solely be based on the persona hypothesis. To prepare as best as possible a future version based on user research, I have prepared support material such as behavioral variables and drafted alongside, interview questions. These documents will help in understanding the users’ behaviors, goals, motivations, and frustrations once completed with user research.</p><p>As for now, persona hypothesis will be developed and design will be based on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gmxTyCZh4aJ7fvQdOCru1A.jpeg" /><figcaption>Behavioral variables</figcaption></figure><p>Finding what causes medication non-adherence during the background research helped in shaping the behavioral variables. In addition, to understand where a user stands in the spectrum of non-adherence causes, the behavioral variables show the level of ease users might have in using the proposed solution (medication reminder) and the knowledge they have about the competitors’ products.</p><p>The behavioral variables will become the basis of the persona hypothesis (or proto persona). With actual user research, we could see behavior patterns coming up and define our personas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZtgeDj6bqkgtQ-OzgwrRIg.jpeg" /><figcaption>Interview questions</figcaption></figure><p>The interview questions are based on the behavioral variables and are meant to gather data on users’ goals, motivations, frustrations, habits etc.<br>Market research (not performed for this document) could be used to select an appropriate range of interviewee in order to get sufficient data and see emerge significant behavior patterns.</p><p>The interview questions are more of a guideline, more like a topic related set of topics to follow. As the topics might evolve in the course of the interviews, the researcher should not be restricted to religiously follow this list, but it should mostly cover the conveyed concerns.</p><h3>2. Modeling</h3><h4>Context of use</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SFsZr96plxAUfnhinNbj9Q.jpeg" /><figcaption>Context of use</figcaption></figure><h4>Proto-persona</h4><p>From our research support material, we can anticipate what our primary persona would be (proto-persona or persona hypothesis).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJ5XaRm8cofyf1eFQ9u_rQ.jpeg" /><figcaption>proto-persona</figcaption></figure><h3>3. Requirements definition</h3><h4><strong>Problem statement</strong></h4><p>Medication nonadherence is a growing concern to healthcare systems.</p><p>To date, measurement of patient medication adherence and use of interventions to improve adherence are rare in routine clinical practice.</p><h4>Vision statement</h4><p>Overcome the identified difficulties that prevent following a medication plan with the use of digital devices. Smartphones are widely used and it makes the perfect tool to get a reminder. Smartwatches could also be considered as complementing, but in this version, it will not be used.</p><h4>Requirements</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TSvS2lDRsdqMAH92cC4yDw.jpeg" /><figcaption>Requirements</figcaption></figure><h4>Context scenarios</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oWbfviyH1AmMOHaLNsER8Q.jpeg" /><figcaption>Context scenarios</figcaption></figure><h3>4. Design framework</h3><h4>Information architecture</h4><p>A simplified-type-of data model helped as a reference to get a clear picture of the relationships between the data objects (their role and how they relate to each other).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*W1HpW9E75Z3ZV5E9BbruBQ.png" /><figcaption>Simplified data model</figcaption></figure><p>Task flows helped refine the sitemap and they prepared the ground for the wireframes, especially accompanied by low-fidelity sketches and navigation. Later, the hamburger menu was changed to a bottom navigation menu as there were only a few important links.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nHEV2Uhv9Dv8lO5cu-QaMA.png" /><figcaption>Task flows</figcaption></figure><p>The simplified data model and task flows helped to find anomalies in the product’s navigation and complete the sitemap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kyjFcM-zkvSx5D8ZT_t9lA.png" /><figcaption>Sitemap</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g0CiM2FhDUsG6BFL9zED3w.png" /><figcaption>Sketches</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C_FEnz0cTbn9n6Cr1PzniA.jpeg" /><figcaption>Colors &amp; typography</figcaption></figure><h3>5. Detailed design</h3><h4>Wireframes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BWGAzfEOm5BW8IGLCIaOWQ.png" /><figcaption>Mid-fidelity wireframes</figcaption></figure><h4>Mockups</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UVxwrYyop8TJCasBFU2tVw.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K17CrJ-4ZyM4OIWPstbvzg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e_m5W_zrc27e-4lrEWfG5A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q1LBGQuD5E_rJYrZkqTFiA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zl3gLSo8C26LN0yynkQQ_Q.jpeg" /></figure><p>Thank you for reading!</p><p>I am looking forward for your comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abbcb31169b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>