Drippler<\/a> is an app with Android related news and it also has a forum for Android related discussions. I’ve recently done a quick heuristic evaluation of the app. If you do not know what a heuristic evaluation is, check out my review of andoidpit.com<\/a> where I explain what a “heuristic” and a “heuristic evaluation” is.<\/p>\n In articles, a heart icon can be tapped to indicate that I like the article.<\/p>\n Problem Principles Severity Ideas to solve the issue In articles, under the headline, there is a byline.<\/p>\n Problem Principle Severity Ideas to solve the issue Articles start off with a main image, then a heading, a byline and the content. Often a panel with a link to an app is presented fixed to the bottom of the screen.<\/p>\n Problem: Principle Severity Ideas to solve the issue In Discussions > Tips and support (and other categories) each topic is presented with a heading, a preview of the text and data.<\/p>\n Problems Principles Severity In the forum I can create a new topic or reply to an existing topic.<\/p>\n Problem Principle Severity When one swipes down on the main stream of news the news items are sometimes animated with some latency, I.E. the card after the current one is \u201cslow to react\u201d to the swipe movement.<\/p>\n Problem Principle Severity When reviewing Drippler I found one “catastrophic” issue and two major problems.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"video","meta":{"_acf_changed":false,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[10,19,7,20],"tags":[],"series":[],"class_list":["post-601","post","type-post","status-publish","format-video","hentry","category-critique","category-interaction-design","category-problem","category-structure","post_format-post-format-video"],"acf":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/posts\/601","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/comments?post=601"}],"version-history":[{"count":4,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/posts\/601\/revisions"}],"predecessor-version":[{"id":644,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/posts\/601\/revisions\/644"}],"wp:attachment":[{"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/media?parent=601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/categories?post=601"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/tags?post=601"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/www.oninteractions.com\/thoughts\/wp-json\/wp\/v2\/series?post=601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n
\nWhen tapping the heart the app presents a dialog to give permission to create status updates on Facebook. This is very startling.<\/p>\n
\nAnticipation.<\/p>\n
\n4.<\/p>\n
\nThe app uses black overlays for onboarding. The same kind of overlay could be used to present the reason that the app should be allowed to post on Facebook. The actions on the overlay should be akin to \u201cOk\u201d and \u201cNot now\u201d or \u201cNo thanks\u201d. Clicking \u201cOk\u201d shows the Facebook dialog.<\/p>\n
\n
\nThe icon of the source publication, and the text \u201cRead Source\u201d are linked to the article on the source publication site. However, the icon and name of the publication is presented in the way persons are often presented. The standard behaviour of such items is to link the icon and name to a profile for the person. The \u201cRead source\u201d link is to low to be easily clicked.<\/p>\n
\nConsistency > Interpretation of user behavior.<\/p>\n
\n3.<\/p>\n
\nMake the icon and source name linked to a profile in the app. The profile can list all news items from the source, for example.
\nIf the source profile per above is not valuable, do not link the name or the icon to anything.
\nMake the tap target for the \u201cRead source\u201d link at least 33px high.<\/p>\n
\n
\nThe main image take up ~65% of my screen (Chrome on Nexus 5) without adding all that much information value. The heading I have already read in the list of articles. The byline and app panel each take up ~10% of my screen. Not even one line of the main content of the article is therefore visible before i swipe to see more.<\/p>\n
\nEfficiency.<\/p>\n
\n3.<\/p>\n
\nMake the main image smaller.
\nConsider letting the heading be smaller.
\nThe app download panel could appear after I have swiped a while \u2013 although this might be very annoying to readers so it needs to be tested very thoroughly.<\/p>\n
\n
\nThe preview is light blue on light blue which causes too low contrast. The data is presented with more visible icons\/labels then data.<\/p>\n
\nColor, Readability.<\/p>\n
\n2.<\/p>\n
\n
\nThese actions are closely related but they are visually presented in quite differing ways both as to how one invokes the form and how the form is laid out.<\/p>\n
\nConsistency.<\/p>\n
\n2.<\/p>\n
\n
\nWhile this animation can make the interface feel a bit \u201ccool\u201d it actually gave me a bit of seasickness and took away focus from the important part of the app: the individual news items.<\/p>\n
\nEfficiency.<\/p>\n
\n2.<\/p>\n","protected":false},"excerpt":{"rendered":"