<?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 Appico on Medium]]></title>
        <description><![CDATA[Stories by Appico on Medium]]></description>
        <link>https://medium.com/@appico?source=rss-66dc39446e1e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hB_xFNJaYBm5YOMz0OewNg.jpeg</url>
            <title>Stories by Appico on Medium</title>
            <link>https://medium.com/@appico?source=rss-66dc39446e1e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:34:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@appico/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[Provide solutions, not features]]></title>
            <link>https://medium.com/@appico/provide-solutions-not-features-ac8b8028d2e2?source=rss-66dc39446e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac8b8028d2e2</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Appico]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 15:00:05 GMT</pubDate>
            <atom:updated>2017-06-13T15:00:05.387Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to approach design with the user in mind</h4><p>We always challenge our designers to solve a problem, rather than just designing a feature because it looks great or uses the latest technology. The first approach is <strong>user centric</strong>. It adds value. It serves the people using the product and represent the core of the business. The second approach is <strong>“I”</strong> <strong>centric</strong>. It is supposed to impress other designers and thereby is very tempting.</p><p>In order to produce the best for work the user of a given product, we apply the following four steps as a checklist for everyone working on product:</p><ol><li><strong>Here is a problem I want to solve for the user</strong></li><li><strong>Here is how we know that this is a real problem</strong></li><li><strong>Here is the data or research to back it up</strong></li><li><strong>Here is the solution to it</strong></li></ol><p>Let’s break this down in more detail with an example from project we worked on. A mobile postcard app called <a href="http://www.getpostly.com/">Postly</a>.</p><ol><li><strong>Here is a problem I want to solve for the user<br></strong>We found that almost no users send cards with multi-image layouts. Meaning the feature is either not relevant to the user group or too complicated to use.</li><li><strong>Here is how we know that this is a real problem<br></strong>A user poll answered our questions. After the users created their cards and decided on their layout we asked them for a quick one-tap answer as to why. This confirmed our suspicion that while they liked the idea of the feature, it was too much work to use.</li><li><strong>Here is the data or research to back it up<br></strong>Next up our analytics team confirmed the user poll results with usage data: The layout editor had a high drop off rate and this was directly correlated to users who chose multi-image layouts.</li><li><strong>Here is the solution to it<br></strong>So far we learned that users like the multi-image feature but don’t like the implementation of it. We then started to simplify the feature. From now on, the app will suggest matching layouts depending on the amount of images selected. All the user needs to do is select an image from his camera roll and he’ll get a variety of populated layout options to choose from. No more empty canvases, no more overwhelming layout complexity.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VpK1EBXMkXXDfHmZYGTBGQ.png" /><figcaption>The old multi-image editing on the left, compared with the improved version on the right.</figcaption></figure><p>The result was 18% less churn, an increase in multi-image postcards of nearly 60% and 22% more cards sent overall. The economic value of this design solution was huge for <a href="http://www.getpostly.com/">Postly</a> but more importantly the impact on the overall user experience and happiness was even bigger.</p><p>Designing for people is hard and most of the times not as pretty as the “i” centric approach. But keep in mind that the best digital products and experiences out there did not start with a finished beautiful visual design on day one. They first started with solving real problems by caring about the user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac8b8028d2e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Underneath the interface]]></title>
            <link>https://medium.com/@appico/underneath-the-interface-52f2751dc502?source=rss-66dc39446e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/52f2751dc502</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Appico]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 10:42:12 GMT</pubDate>
            <atom:updated>2017-06-13T10:42:12.234Z</atom:updated>
            <content:encoded><![CDATA[<h4>The overlooked impact of engineers on user experience</h4><p>We recently had a lunch discussion on how engineers don’t get credited half as much for their work as designers. The often complicated and hard work of many engineering teams simply isn’t as visible as an interface forefront done by designers.</p><p>Users always expect a service to work perfectly. They take the hours of improvements for granted. A cute little animation here or there will most certainly win over an invisible 6% performance improvement if you cast a user poll.</p><p>With that said, no designer should underestimate the impact an engineering team has on the actual user experience. Just because there is no “<em>design</em>” in their job title does not mean that they are not <em>designing</em> the experience as well.</p><p>Let’s take a look at an example: smart conversation replies. You probably won’t argue that this is a very clever and convenient feature from a user experience point of view. It looks so small and simple, and yet all that lies beneath the surface is great engineering. The experience for the user is very much created and influenced by engineers. And while you rarely actually <em>see</em> their work, you get touched by it all the time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hYP3UpPzRSldEVsnGwjh3Q.png" /><figcaption>You can’t create simple, without managing the complex — Luke Wroblewski</figcaption></figure><p>Or think about another very familiar example — streaming. Would you argue that the time it takes to buffer something on a platform like Netflix (hopefully you have no buffering at all) has a huge impact on you as a user? We’d go as far and say that the time it takes to buffer has the biggest impact on a streaming service user. And while the engineering team is responsible for great compression and minimal buffer times, they again have no “<em>design</em>” in their job title.</p><p>This applies to any experience that includes data loading, especially on mobile devices. Users are getting more and more impatient. We live in a NOW era. Everything is expected to be instant. Instant delivery. Instant loading. Instant coffee. Okay maybe not so much instant coffee. But there’s a reason Facebook and others have introduced skeleton screens, a blank version of a page into which information is gradually loaded. The two graphics below underline the impact mobile waiting times have on the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l7vxID6bcYCQ6NGaoqUeRg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GZ8vdwTOlsXAOw2hZCh63Q.png" /></figure><p>A great user experience is simply not just created by designers alone. It is a mixture of the right expertise with different point of views. The best teams we know have one thing in common: They are working with each other rather than alongside each other and share one common north star — the user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52f2751dc502" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>