<?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[What I Learned Building - Medium]]></title>
        <description><![CDATA[Stories from people who build things. Edited by:  @matthendrick, @paperkary, @SpanishCurls,  @mhauer, and @dustin. Get updates via twitter @LearnedBuilding. - Medium]]></description>
        <link>https://medium.com/what-i-learned-building?source=rss----facf36016a4d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*cF2i1ZosSP_UTJig.jpeg</url>
            <title>What I Learned Building - Medium</title>
            <link>https://medium.com/what-i-learned-building?source=rss----facf36016a4d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:04:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/what-i-learned-building" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Debugging iOS Outdoors]]></title>
            <link>https://medium.com/@dmzza/debugging-ios-outdoors-2f0e1c62ff3?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/2f0e1c62ff3</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[David Mazza]]></dc:creator>
            <pubDate>Thu, 25 Feb 2016 23:31:00 GMT</pubDate>
            <atom:updated>2016-02-25T23:31:00.788Z</atom:updated>
            <content:encoded><![CDATA[<h2>How to NSLog without connecting to Xcode</h2><h4>Clipboard as a Console for the iPhone</h4><p>There’s nothing quite like taking your app out into the real world where data and location services are spotty, battery life is limited and distractions are everywhere. But it isn’t so useful if you can’t see what’s going on when it misbehaves.</p><p>CloudClip records anything on your iPhone’s clipboard. That means that you can put timely snippets of text on the clipboard and see the history in CloudClip, just like console output in Xcode.</p><h4>Objective-C</h4><pre>UIPasteboard *pb = [UIPasteboard generalPasteboard];</pre><pre>[pb setString:@”Hello CloudClip!”];</pre><h4>Swift</h4><pre>let pb = UIPasteboard.generalPasteboard()</pre><pre>pb.string = “Hello CloudClip!”</pre><p>One limitation: it only stores the last 15 things from the clipboard. I’ve thought of two simple workarounds if you want a longer history.</p><ul><li>Put stuff on the clipboard in batches, or</li><li>Prepend each new line to a string in memory and put the whole history on the clipboard each time. Decent chance you will hit a wall eventually with too much output.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/1*O5pZoqWV6f8u2WUcaMLUzA.png" /><figcaption>A history of your clipboard. (Credit: CloudClip <a href="http://www.thinkbitz.com/cloudclip/">http://www.thinkbitz.com/cloudclip/</a>)</figcaption></figure><p>CloudClip is <a href="https://itunes.apple.com/us/app/cloudclip/id563356503?ls=1&amp;mt=8">Available on the App Store</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f0e1c62ff3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting and Running a Company are Completely Different]]></title>
            <link>https://medium.com/@collis/starting-and-running-a-company-are-completely-different-a24ca38954fb?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/a24ca38954fb</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Collis]]></dc:creator>
            <pubDate>Wed, 07 Oct 2015 02:01:36 GMT</pubDate>
            <atom:updated>2015-10-07T02:01:36.566Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*7fX67gAFb80bXeH3.jpeg" /><figcaption>Sailing by Epicstockmedia</figcaption></figure><p>After nine years of running <a href="http://envato.com/">Envato</a>, I often get asked what have been the biggest lessons and surprises. Invariably, mine all seem to come out sounding exceedingly obvious to my listener. Apparently I was a startup simpleton. That’s OK, we all start somewhere.</p><p>In all those nine years, I’ve more or less always had the same title: CEO. I thought that meant I’d be doing the same thing the whole way. Turns out, I couldn’t be further from the truth.</p><p><strong>Things I used to do:</strong></p><ul><li>Create</li><li>Design</li><li>Code (Front-end, and poorly)</li><li>Write Blog posts and Forum posts</li><li>Market</li><li>Communicate (Mostly externally)</li><li>Worry</li></ul><p><strong>Things I do now:</strong></p><ul><li>Meet, meet, meet</li><li>Email</li><li>Read Advices, Spreadsheets, Papers, and Slidedecks</li><li>Write Papers and Slidedecks</li><li>Present and Speak</li><li>Communicate (More internally)</li><li>Worry</li></ul><p>I don’t know what other startup founders experience along the way, but for me it’s been quite jarring.</p><p>For the longest time I felt like I was being unproductive whenever I wasn’t doing something in the first group. Things like email and meetings felt like they weren’t ‘<em>real work</em>’. And perhaps they weren’t. In the early days of Envato, the real work was … well, making Envato.</p><p>These days I have the opposite problem. When I sneakily open Photoshop, or make time to write, or chat on the forums, it feels suspiciously like I’m dodging the budget, avoiding my burgeoning inbox, or procrastinating on reading a tax report.</p><p><strong>For Everything There is a Season</strong></p><p>My mother says that in life there are seasons. She gave me this advice when our first son arrived. And like the first warm day of spring, or the initial chill of winter, his arrival was a definite shift in season!</p><p>Her words resonated with me, and I remember them whenever I reflect on what’s changed since I became a parent. Fatherhood has its ups and its downs, just like pre-parenthood had its fair share of good and bad. Neither is better than the other, they are just different.</p><p>In startup life too there are seasons. The beginning of a company’s life has some amazing bits to it. There’s the complete open world of possibility, the triumph of early wins, the excitement of creating something that wasn’t there before, and the fun of being the underdog. Balancing those are the money problems, the fear of failure, the difficulty of creating something that doesn’t yet exist, and all the lack of resources that come with being the underdog.</p><p>Some years ago, the season changed. Envato grew up and became a company. The number of people went from a handful to a few dozen, to a couple hundred. And with the new season came new positives and new challenges.</p><p>Today there is the magic of a great team, the satisfaction of watching a happy culture growing, the luxury of resources, and the confidence of achievement. But on the flip is the array of issues that come with a larger business, like the challenges of keeping culture healthy, the inertias of size, and the need to think about hairy stuff like cross-border tax landscapes!</p><p>Today is not yesterday.</p><p>Not the most amazing insight anyone has ever had. But that’s been a big lesson for me. Yesterday was a challenging but rewarding day. So is today. And call me an optimist, but I’m pretty sure tomorrow will be too.</p><p>I miss designing, and I think rather fondly about my terrible, terrible CSS. But its very exciting having a great team, and from time to time I have even enjoyed reading budget files.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a24ca38954fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Listen to Your Users]]></title>
            <link>https://medium.com/what-i-learned-building/the-user-is-always-right-eab73c620e7d?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/eab73c620e7d</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[travel]]></category>
            <dc:creator><![CDATA[Gillian Morris]]></dc:creator>
            <pubDate>Sun, 02 Aug 2015 19:09:09 GMT</pubDate>
            <atom:updated>2017-05-03T01:02:21.555Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V3ma4IL4hPY67Dw9PMBz8A.png" /></figure><h3>And other lessons from building a consumer-facing app</h3><p>Two years ago today, two friends and I sketched out an app, <a href="http://hitlistapp.com/">Hitlist</a>, that would alert you when there were cheap flights to places you wanted to go.</p><p>Since then Hitlist has helped a quarter million users in 163 countries book over $6m of travel. Almost none of that happened in our first year of existence. We were press darlings, our users tweeted and emailed their love, and the metrics we tracked were telling the right story. But no one was buying. This is how we figured out what we were doing wrong.</p><p>Maybe I should give some context. When I was 18, I took my life savings — made from babysitting, odd jobs, and (not weird at all) selling parakeets I bred in my parents’ basement — and bought a plane ticket to Paris. For the next year I worked as a singer and tutor and lived on around $500 a month. I managed to travel to four countries thanks to some creative travel hacks.</p><p>I fell in love with travel that year, and its ability to change us and the world around us for the better.</p><p>We built <a href="http://hitlistapp.com/">Hitlist</a> to make it easier for anyone to find affordable travel. Our <a href="http://hitlistapp.com/ios">app</a> and <a href="http://wandertab.com/">Chrome extension</a> inspire and enable people to travel more by alerting you when there are cheap flights to your dream destinations.</p><p>We comb through millions of flights a day and sort out just the ones that are relevant to you, then send them via email or push, so hopefully you actually take that trip you always dreamed of but never got around to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*fNMHNFmGmisPVxnnm744gw.png" /></figure><p>When we started working on Hitlist in the summer of 2013, we were three first time founders and had pretty much no idea what we were doing. Our first version was ready to release by November. It featured Tinder-esque interface because who doesn’t love Tinder, right?</p><p>We released the app and the reception was fantastic. <a href="http://thenextweb.com/apps/2013/11/19/hitlist-lets-you-know-when-its-cheap-to-fly-to-your-dream-destinations/">The Next Web</a> wrote an article about us, and it ended up getting picked up by <a href="http://lifehacker.com/hitlist-finds-the-cheapest-time-to-travel-to-your-dream-1469689028">Lifehacker</a>, and some <a href="http://www.lifo.gr/now/digital-life/37855">blog in Greece</a> that resulted in nearly 10k downloads, proving that at least some Greeks are budget-conscious. Then we got this awesome coverage in the <a href="http://intransit.blogs.nytimes.com/2014/04/21/planning-a-trip-thats-socially-acceptable/?_r=0">New York Times</a>, which looks great in a slide deck and made my parents very happy but wasn’t nearly as useful as The Next Web/Lifehacker coverage (we saw about 500 new users when that article came out and close to 10k between TNW and Lifehacker).</p><h3>Arianna Simpson on Twitter</h3><p>@gillianim Your app is addictive. I just went through like, a bazilion locations. Wanderlust levels up 1000x</p><p>More important than all the press, we were getting fantastic reception from users. We’d get tweets like the above all the time. We got love letters. And some things that made me a little uncomfortable:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*3TX4PXM8hnqUlJDslW4TFg.png" /><figcaption>Thanks, Tom</figcaption></figure><p>It was easy to get caught up in the good news. We poured so much into Hitlist and people were loving it. Right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*I7_C5b-L2TmoS4hlvvhuRw.png" /></figure><p>The only trouble was: they weren’t coming back. And they weren’t really telling their friends. After our download spike, we were barely growing any more — a couple dozen new registrations a day if we were lucky. And our churn (the rate at which users drop off) was absurdly high. Three months after launch, less than 5% of our registered users were still monthly active users (MAUs). Some smart people we knew told us that what we’d built was a gimmick. And we were closest to the product, and we found ourselves getting bored with it. You should not get bored with your own product. You should love your product so much that it’s <a href="https://instagram.com/p/3A0Aapmldp/">all you want to talk about on a first date</a>.</p><p>At this point we’d never done any paid marketing. We had one investor push us really hard to start buying Facebook ads to try and drive growth. But other (wiser) advisors pointed out that spending money on growth when we had 95% churn didn’t really make sense. My friend <a href="https://twitter.com/mtarun">Tarun Mitra</a> put this most memorably:</p><blockquote>If you invest in growth before you have retention, you’re renting users, not acquiring them.</blockquote><p>So we went back to the drawing board. We decided to completely change the design. The Tinder interface wasn’t right. A city is not going to ‘like’ you back. What kind of UX was going to be more effective for surfacing deals people might actually buy? We moved to a stream of content that’s dynamic, and changes according to your preferences. There’s some cool artificial intelligence behind this which I’m looking forward to developing more. The more you use the app, the more relevant the deals you see become.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ybIuflVo_Rv_SkpXqhFNg.png" /><figcaption>Also started using gold iPhone imagery, which makes everything sexier.</figcaption></figure><p>We also introduced an ability to filter flights, so you weren’t just getting alerts for cheap flights generally, but for the kinds of flights you wanted. So if you’re trying to plan a 7–14 day beach vacation in August, you can see just the flight prices for that particular search, rather than all-time low fares.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U3X4XXSG90Newb3FFyfO-A.png" /><figcaption>Seriously have you booked your August vacation yet?</figcaption></figure><p>We rolled out 2.0 in August 2014. Here’s what happened.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hOuygIl8f1n3OpYWQwE8EQ.png" /></figure><p>I got a bunch of nastygrams from users who missed the Tinder interface. We were also seeing a lot less love on Twitter. I tried, unsuccessfully, to pitch the new and improved Hitlist 2.0 to press, but the newspapers and blogs that had generated so much buzz around our initial launch had lost interest.</p><p>Then we looked at engagement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dpyrnWjCivOR500ru4uQsg.png" /></figure><p>The number of cities people added to their lists went from 41 in the Tinder interface to 5.6. That hurt. We’d counted cities/user as one of our key metrics, because we considered it valuable information on where people were interested in going.</p><p>However, when we dove into the data a little bit more, we found that nearly half the deals that people clicked on were never on their hitlists. What people said they wanted wasn’t what they were actually buying. If the point of our app was truly to help people find good travel deals, click through, and buy them, then the number of cities/user wasn’t really a relevant metric.</p><p>Meanwhile, our overall conversion/MAU was doing this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*em0SP2v00NvkG4TKMOaIOQ.png" /></figure><p>In other words, people are actually taking trips. At this point 10% of our monthly active users are clicking through to booking, some of them several times a month (which is why our total deal clicks/MAU above is closer to 20%).</p><p>Equally as important, our retention numbers are completely different. One week after using the app, 42% of users are actively using the app, compared to… actually we have no idea, because we weren’t measuring cohort retention before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sx0JpXisdIZEydCH8IpWgg.png" /><figcaption>Retention is an indispensable metric. Don’t be like us and not track it for the first seven months of your existence.</figcaption></figure><p>Though it seems obvious now, it took me a long time to realize that there are two things that matter for an early stage consumer app: conversion and retention. User growth is important too, but you can buy new users (plenty of people do, with the amount of venture capital that’s sloshing around these days). But again: if you invest in growth before you have retention, you’re renting users, not acquiring them.</p><p>We’re not there yet. We won’t be until Hitlist is on everyone’s phone and is the first place people come when they think of planning and booking travel. But v2.0 took us a step closer, and we’re experimenting, and getting better every day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/1*9aP1duX_7uVahP4DzruELQ.png" /></figure><p>So what did we learn? First of all, the user is always right… but sometimes it’s not what they say, but what they do. Of course you need to take user feedback into consideration, but remember that actions speak louder than words.</p><p>Secondly, don’t get caught up in what the press thinks. A good article can give you a nice boost in user numbers, but that doesn’t mean those users will stick around.</p><p>Most important of all: know the metrics that matter to your company. ‘Engagement’ is a fuzzy term. As we found out, the engagement metrics we initially tracked — cities/user, time in app — weren’t driving the thing that we actually cared about. The 2.0 design was demonstrably better at getting people to actually book travel. And the tweaks we’ve made over time (we’re now on v2.8) have helped increase our retention to the point where it makes sense to start investing in growth.</p><p>Speaking of which: please <a href="http://hitlistapp.com/">download Hitlist.</a></p><p><em>If you found this useful, please share it! You can find Hitlist on Twitter </em><a href="http://twitter.com/hitlist_app"><em>@hitlist_app</em></a><em> and me at </em><a href="http://twitter.com/gillianim"><em>@gillianim</em></a><em>. We’re also on </em><a href="https://angel.co/hitlist-1"><em>AngelList</em></a><em>. Visit </em><a href="http://medium.com/hitlist"><em>medium.com/hitlist</em></a><em> for company updates and spectacular gifs.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eab73c620e7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/what-i-learned-building/the-user-is-always-right-eab73c620e7d">Don’t Listen to Your Users</a> was originally published in <a href="https://medium.com/what-i-learned-building">What I Learned Building</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nine ways being a product manager is just like being a parent]]></title>
            <link>https://medium.com/@spacklr/nine-ways-being-a-product-manager-is-just-like-being-a-parent-302afbab749b?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/302afbab749b</guid>
            <dc:creator><![CDATA[Matt Pope]]></dc:creator>
            <pubDate>Tue, 21 Apr 2015 18:46:13 GMT</pubDate>
            <atom:updated>2015-04-21T18:46:13.184Z</atom:updated>
            <content:encoded><![CDATA[<ol><li>You can’t <em>control</em> the outcome. You can lead and guide, and establish conditions and practices to influence — in fact, you must! But, you can’t know the software will ship in ‘tip-top’ on a specific date any more than you can know the kids will mature to become wonderful, ready-for-the-world human beings by age 18.</li><li>You don’t have all the answers. If you pretend you do, your kids will openly call your bluff and quickly move on, with little harm done (so long as it’s not common). Your team may not. They’re more likely to determine that your input, designs or feature priorities are not credible. Be clear when you’re expressing an opinion vs. a fact, and where you have supporting data vs. not. Be clear when your ideas are intuition-based. Genuinely seek to understand the opinions and intuitions of others — yes, including your kids:-)</li><li>In fact, be very open that you <em>don’t</em> have many answers. Both your kids and co-workers will find you more approachable and more credible. Ask straight-up, clarifying questions. Tell good stories of struggles and failures. Use those stories to guide thinking and decision-making — as a tool for influence, they’re far more powerful than demands or unilateral decisions.</li><li>Give accountability. People are amazing, including and maybe especially young, little people! They’re capable of so damn much. But you’ll only ever know how much if you let them show you. I once heard a story of how Obama struggled earlier in his political career. His staff was there to passionately work with and for him, but because he was technically capable of doing each of this staffers’ jobs better than they were, he tried to do his job and all of theirs concurrently! He failed to scale, and the people working for him became increasingly frustrated — they wanted to do their job! The lesson is a simple one: let amazing people be amazing (regardless of whether they’re 10 or 40).</li><li>All problems are people problems, all people problems are communication problems. Be a super proactive communicator — that should go without saying when it comes to raising kids or leading as a PM. ‘How’ you communicate is <em>at least </em>as important as ‘what’ you say. Your spirit and approach often matter more than your actual words. A little <em>jois de vivre</em> goes a long way.</li><li>Worry never helps. Freneticism never helps. Anger never helps. Regardless the situation — be positive, be proactive. You can’t turn the clock back, so focus on always moving forward. Get positive, chill the hell out, enjoy the journey and help the people around you do the same.</li><li>Know your stage, and plan and act accordingly. The challenges in parenting a 2-year old are really different than those of a 15 year old. Similarly, the challenges of a seed-stage startup are really different than those of a public company. Know your stage and its likely challenges. It’s natural for a 2-year old to have a wailing meltdown. And, it’s natural for an early-stage startup to do significant product re-design as it learns how to improve usability and searches for market fit. In either case, don’t get upset about it, just work through it proactively and positively. Different stages, different problems, different bag o’ tools required. Which is great, because you will have the opportunity to learn and grow, right along with your kids or your company. Always be learning!</li><li>Support others’ interests. Harry Truman said: “I have found the best way to give advice to your children is to find out what they want and then advise them to do it.” Similarly, it’s important to support work that an engineer <em>really</em> wants to do, even if it’s hard to justify or prioritize in terms of imminent user impact. You can’t do this all the time, because customer impact is top priority, but never forget that people need to feel energized and motivated to be engaged and productive. Give a little discretion — sometimes more than a little — to really good and capable people. Like so many other things on this list, this is all ‘soft’ art and no science.</li><li>There’s no one way. Every kid is unique — even in the same house, what works for one may be very different than what works for another. And, every product or company is unique. Whether working with your kids or your product team, play to the unique, intrinsic strengths and motivations. In leading a product team, this applies all the way down to tooling. JIRA or Pivotal? Crittercism or Crashlytics? Slack or HipChat? I don’t know. There’s no one tool, no one way — consider what will work best given how your team likes to work.</li></ol><p>I hate to end this list with nine. Who has a #10?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=302afbab749b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build vs Integrate]]></title>
            <link>https://medium.com/what-i-learned-building/build-vs-integrate-c456977660e0?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/c456977660e0</guid>
            <dc:creator><![CDATA[Bhasker “Bosky” Kode]]></dc:creator>
            <pubDate>Tue, 24 Mar 2015 19:13:42 GMT</pubDate>
            <atom:updated>2015-03-24T19:13:41.803Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_0LwPGI73JRv2xzi7njL7w.png" /></figure><h2>Facebook needs “Help”. And so do you.</h2><p>I spent this weekend <a href="https://www.pinterest.com/inapphelp/">curating how several popular apps offer help &amp; accept feedback</a> from customers. Here’s a 30 second tour of Facebook’s in-app help for you to hire someone to go out and build in a weekend-to-6-months. But should you?</p><h4>Facebook (<a href="https://www.pinterest.com/inapphelp/facebook-in-app-help-screens/">view on pinterest</a>)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*O82nNWMtrUJ8962jQDOQCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*KSI6kfgIJ5yeGvcPs0nKPQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*I1rbH2qXzehb79X3uQ02Sg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*bnkDXTMhf0jPAsN__sjXqQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*lagCYJOIrN_VCXGmONu69A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*r4njL2jfs7Y3Wq81lXDV2w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*lPEQUwOYVTuMXGFL60WvTg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*1H89sAdVU0rgCFOPDyXoZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*xGrAuys57uaneheWg8Bsug.png" /></figure><p>Facebook can afford to have 1 full-time designer/developer at $100k+/year building itself this sweet in-app help center.</p><p>Even if you have the time and resources to build it in-house, it can be difficult to get right.</p><blockquote>ios/android/unity/web support, search &amp; indexing FAQ’s, syncing FAQ’s, theming, offline access, identity, uploads, the CMS to compose FAQ’s itself, a web-based agent dashboard, push notifications, rendering &amp; maintaining the chat thread, adding metadata &amp; tagging issues, analytics, reporting, exports, sharing, migration, i18n, ACL’s, doh!</blockquote><p>Trust me, these are interesting problems. <strong>But it may be time to let someone else worry about in-app help for you. </strong>Analytics has had its own set of challenges, and SAAS companies there too — <em>(if they can figure out their pricing </em><a href="https://news.ycombinator.com/item?id=8381083"><em>it seems from this interesting thread</em></a><em>) </em>can<em> </em>go beyond early adopters.</p><p><a href="http://supercell.helpshift.com/">Supercell</a>, <a href="http://tinyco.helpshift.com/">Tinyco</a>, <a href="http://wordpress.helpshift.com/">Wordpress</a>, <a href="http://flipboard.helpshift.com/">Flipboard</a>, <a href="http://acompli.helpshift.com/">Microsoft Outlook</a>, <a href="http://circa.helpshift.com/">Circa</a>, and a number of large and fast-growing startups have made this shift to let someone else power the experience when a user clicks <em>“Help”.</em> That’s a pretty powerful responsibility. The native SDK’s fit seamlessly within the app and looks great. Have a look for yourself. Here’s <a href="http://findery.com/">Findery</a>’s help experience:</p><h4>Findery (<a href="https://www.pinterest.com/inapphelp/findery-in-app-help-screens/">view on pinterest</a>)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*fQhnIJoam72QnFoRMIoLDQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Fm7aejcN9Br_2CoH1NpfGw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*_0TmIz1FuRhySUtDEsxmIQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*MXpwIu8KJ05HNJYr8QYCZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*-yV5swDJwspASLfcdoy96Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Egsm51fOAdO46Yq36UeFGA.png" /></figure><p>And here’s me getting a reply on one of the doubts I had about Microsoft Outlook. The experience is very chat like, and I got my issue resolved in under 2 minutes.</p><h4>Microsoft Outlook ( <a href="https://www.pinterest.com/inapphelp/microsoft-outlook-in-app-help-screens/">view on pinterest</a> )</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*p_R6IQy4pHjmD6ciHw8oRA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*OKYWtEJif4j1RxPcApCM5g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*BjymcL-yd_yRY1dEB40dwg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*gcHOFyhgL2axAtft2y-jPA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*tEsCqN10rNSJXAXOR9-sJg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*X5LCW8tkfkcYH-5Y9FShdQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*c48jQ7f0Dqhz1B5dCQ_8qA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Bthj1B4ABbLtELw5azVYwg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*7hofg9Bm383KDZlTbuE90w.png" /></figure><p>You can find the rest of the <a href="https://www.pinterest.com/inapphelp">40+ in-app help screens here</a>; filed under “in-app help” on Pinterest and organized by each app. Several of them surprisingly don’t have a native help experience or redirect users to Safari, or just initiate an email thread.</p><p><strong>Ladies and gentleman </strong>— its 2015. Much like in-app analytics, in-app help desk’s have crossed the chasm. Your users deserve a native and beautiful in-app help experience.</p><h4>Build vs Integrate</h4><p><strong>In other words, if someone in your team</strong> is spending more than a day a month doing <em>X</em> — you’re already doing too much. <em>X</em> could easily be substituted with any feature a typical SAAS company provides really. Analytics, Translation, Help, Packaging, Delivery, Payroll, Legal. You name it. It may sound like a good time to run a SAAS company, but it’s an even better time to be a customer : )</p><p><strong>If you’re a developer</strong> working on an <em>in-house X</em>, you should start looking to make something not just better — but exponentially better. Or perhaps find some other value-add to contribute to. I was there myself. When was the last time someone in your company worked on an SMTP server, a STUN or telephony PBX just to communicate with your users. On the other hand — the founders of Twilio or Plivo — came together to create these infra startups and that’s fine too, because you can go beyond helping just one company. <em>“course correction baby!”</em></p><p><strong>If you’re a startup founder, save that $50k</strong> (and send me a postcard!) Save those months of your Android/iOS developer’s time building a half-baked in-app help software OR <em>a “responsive” over the weekend quassi-web-mobile FAQ’s tweaked for webkit</em> just to re-invent the wheel.</p><p><strong>If your app does not have an in-app help desk,</strong> you can <a href="https://www.helpshift.com/blog/integrate-today-win/">integrate one in under 30 minutes.</a></p><h4>You will be surprised the first time you try out a native in-app help desk</h4><ul><li>Better customer satisfaction</li><li>Higher ratings for your app</li><li>Genuine feedback on where your product sucks/scores.</li><li>Quantified data to back feature/fix prioritisation.</li><li>Stats on which FAQ’s your users found useful, and more analytics</li><li>Ticket deflection if you organize your FAQ’s well.</li><li>And so much more.</li></ul><h4>It’s time to focus on newer and better problems</h4><p>Like a new user waiting for you to answer their questions about your app every morning. Or turning a refund request into an upgrade. Or getting your designer 1-to-1 UX feedback from passionate users. I kid you not — these are scenes our customers find themselves in every other day- <em>(more on the </em><a href="http://helpshift.com/blog/"><em>blog</em></a><em>)</em>. Some apps now even have large teams of player specialists, agents, editors and community specialists all working improving customer satisfaction and connecting with your community. Which is why they’re also flocking out of their traditional email based ticketing systems when they see how far ahead in-app help is today. Zendesk’s <em>“product debt”</em> won’t let them think beyond email, and nobody will call them out. Your customers deserve a native and beautiful experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tEfuoiGGicdnwM5fe4j88Q.png" /></figure><p><a href="https://www.google.com/search?q=in-app+customer+service">Pick any one!</a> It will change your customer’s expectation of customer satisfaction forever. In fact with billions of devices with apps that have an in-app mobile help desk already, it may already have.</p><p><a href="http://twitter.com/@bhaskerkode"><em>@bhaskerkode</em></a><em> builds stuff you’ll need tomorrow, today at @</em><a href="http://twitter.com/helpshift"><em>Helpshift</em></a><em><br>You can browse hundreds of in-app help screens curated for this post at </em><a href="https://www.pinterest.com/inapphelp/"><em>https://www.pinterest.com/inapphelp/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c456977660e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/what-i-learned-building/build-vs-integrate-c456977660e0">Build vs Integrate</a> was originally published in <a href="https://medium.com/what-i-learned-building">What I Learned Building</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Not Freak Out About Material Design]]></title>
            <link>https://medium.com/what-i-learned-building/how-to-not-freak-out-about-material-design-33cec7381b80?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/33cec7381b80</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Maxxxxxxx]]></dc:creator>
            <pubDate>Wed, 03 Dec 2014 01:29:59 GMT</pubDate>
            <atom:updated>2014-11-20T17:04:46.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*278tqw9zNPe2WCAz29Wzdw.jpeg" /></figure><h4>A sane approach to making your app Material</h4><p><strong>By Max Weiner, Android Lead at Pocket</strong></p><p>Adopting any new design language can quickly feel, well, overwhelming. Especially when that language is Material Design, with its paper and ink inspiration, bold colors, and whirling animations.</p><p>Having just wrapped up work getting Pocket’s Android app ready for the launch of Lollipop, we wanted to share our process for breaking down Material Design into a project our small team could quickly tackle. We are in no way saying this is the <em>only </em>way of going about the process, or that we nailed going Material right out of the gate. Rather, we hope our experience simply sparks some ideas on how to get started, and ultimately gets you excited about embarking on your own Material adventure.</p><h3>Should you go Material in the first place?</h3><h4>Let your design principles determine your decision.</h4><p>At the core of our design philosophy is the belief that great apps are beautiful, unique, and above all else, intuitive. This means we embrace the conventions and strengths of each individual platform we’re on — iOS, Android, Mac, Chrome, etc. — all while maintaining Pocket’s own unique visual style and brand language.</p><p>Striking a great balance between your app’s style and the core conventions of the device or OS you’re building for makes your app immediately feel thoughtfully-crafted and delightful to use. Your users will love you for it, and <a href="http://pocket.co/sK5Mf">even the seemingly subtle things can make a big difference</a>.</p><h4>Incremental design refreshes save your team time in the long run.</h4><p>Waiting to commit to a design refresh can quickly become a bit of a vicious cycle. The longer you wait to refresh, the more you’ll be required to commit to bigger and longer projects down the road that — let’s face it — you’ll simply want to keep putting off.</p><p>Refreshing your design in small increments makes it all the more easy to keep up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Oz5QLW6kl-UfUN8KBY28Q.png" /></figure><h3>How to Get Acclimated with Material</h3><p>There are now <em>tons </em>of resources at your disposal to help you begin exploring Material. The most important thing at this point is to simply get a high-level grasp of Material Design. No need to sweat the details just yet.</p><p>Here are our suggestions for getting your feet wet.</p><h4>Learn Material in theory.</h4><p>Check out these overviews, videos, and discussions to help wrap your head around what’s new in Material Design.</p><ul><li><a href="https://www.youtube.com/watch?v=wtLJPvx7-ys#t=13m51">I/O Material Announcement</a> (fast foward to 13:51)</li><li><a href="http://www.google.com/design/spec/material-design/introduction.html">Design Guidelines</a></li><li><a href="http://android-developers.blogspot.com/2014/10/material-design-on-android-checklist.html">Material Design Checklist</a></li><li>DesignBytes Videos: <a href="https://www.youtube.com/watch?v=p4gmvHyuZzw">Intro to Material Design</a>, <a href="https://www.youtube.com/watch?v=YaG_ljfzeUw">Paper and Ink</a>, and <a href="https://www.youtube.com/playlist?list=PLWz5rJ2EKKc_XOgcRukSoKKjewFJZrKV0">more…</a></li></ul><h4>Use Material in practice.</h4><p>Start checking out as many Material apps as you can. There are several apps out there, many from Google, that have had everything from minor design refreshes to full-blown product makeovers. And, there are more apps coming out with Material each and every day.</p><p>We recommend starting with the Google Suite: <a href="https://play.google.com/store/apps/details?id=com.google.android.gm&amp;hl=en">Gmail</a>, <a href="https://play.google.com/store/apps/details?id=com.google.android.apps.inbox&amp;hl=en">Inbox</a>, <a href="https://play.google.com/store/apps/details?id=com.google.android.apps.fitness&amp;hl=en">Fit</a>, <a href="https://play.google.com/store/apps/details?id=com.google.android.apps.magazines&amp;hl=en">Newsstand</a>, <a href="https://play.google.com/store/apps/details?id=com.google.samples.apps.iosched&amp;hl=en">I/O 201</a>4, <a href="https://play.google.com/store/apps/details?id=com.google.android.calendar&amp;hl=en">Calendar</a>, <a href="https://play.google.com/store/apps/details?id=com.google.android.apps.maps&amp;hl=en">Maps</a> and <a href="https://play.google.com/store/search?q=google&amp;c=apps">many others</a>.</p><h4>Monitor Material updates &amp; conversations.</h4><p>There will be a lot of new apps and design refreshes in the coming months, in addition to plenty of back-and-forth conversations within the design and dev community on best practices. These sites and blogs can help keep you up to speed on any new developments.</p><ul><li><a href="http://androidweekly.net/">Android Weekly Newsletter</a></li><li><a href="http://www.androidpolice.com/">Android Police</a> and other Android news sites</li><li><a href="http://www.reddit.com/r/Android/">r/Android</a></li><li>Follow Google Design Advocate <a href="https://twitter.com/romannurik">Roman Nurik</a> on Twitter</li><li>Follow the <a href="https://plus.google.com/+googledesign/posts">Google Design</a> page for updates on what’s new with Material</li></ul><h3>Dive In and Get Started</h3><h4>Conduct an App Audit.</h4><p>So you’ve now got a handle on Material Design. It’s time to turn your attention to your own app. Do a detailed audit and ask yourself the following:</p><ul><li>What parts of your app already match the new conventions?</li><li>What UX patterns (navigation, menus, toolbars, etc.) don’t match the new conventions?</li><li>What design elements could use a tweak, refresh or overhaul?</li><li>What new things could be added?</li><li>Where could you add animation to better communicate changes and transitions in your app?</li></ul><p>Don’t focus on exact solutions, just cast your net wide and make a list of everything you <em>could </em>do with Material Design. If you’re looking for a place to start, we recommend referencing the different sections of the <a href="http://www.google.com/design/spec/material-design/introduction.html">Material Design Guidelines</a> as a rough checklist.</p><h4>Ruthlessly Prioritize!</h4><p>Let me guess. You have a very, very, very long list of things you’d love to tweak, add, or update in your app. We had the same problem, and although it’s tempting to try and do it all in one massive release, it would mean you wouldn’t release anything for a long…long…time.</p><p>Hence, prioritization.</p><p>As you might have noticed, there are literally hundreds of extremely detailed specifications in the Material Design guide. <strong>Thankfully, these are guidelines, not rules.</strong></p><p>What they’re meant to do is serve as very finely crafted starting points and a way of fast tracking many of the design decisions you’ll encounter. What they’re not meant to do is override your own specific use cases, conventions or style, nor bog you down with endless details that could take a year to implement.</p><h4>Here’s What Worked for Us.</h4><p>We found the following criteria to be especially helpful in deciding what to include in our first Material update:</p><ul><li>What <strong><em>absolutely must change</em></strong>?</li><li>What will have the <strong><em>biggest design impact</em></strong>?</li><li>What will have the <strong><em>biggest UX impact</em></strong>?</li><li>What are the <strong><em>“nice-to-haves”</em></strong>?</li></ul><p>Since we were targeting to launch alongside Android 5.0, our list of things that <strong><em>absolutely must change </em></strong>involved Lollipop-specific bugs, crashes, and anything that just looked plain broken on the new version of Android. Basically, our task here was making sure Pocket functioned on Lollipop as well as it did on earlier versions of Android.</p><p>For the <strong><em>biggest design impact</em></strong>, we included any elements we felt as being essential to Material Design, like refreshing the App Bar, making UI updates for certain elements like text fields, icons and accent colors, and giving the status bar a little love and treatment. Even if at first glance, these changes look seemingly minor, we believe the devil is in the details and wanted Android users to instantly feel at home while using the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9yG2eYo1foitXEuQZoFucA.jpeg" /><figcaption>Even small UI refreshes, like increasing the padding of our App Bar and adding subtle animations, can make a big impact.</figcaption></figure><p>Anything related to navigation and UX patterns fell into the <strong><em>biggest UX impact </em></strong>bucket. This included everything a user interacts with while moving throughout the app — toolbars, tabs, nav drawers, menus, transitions, etc. We wanted these to be immediately intuitive to Android users opening Pocket for the first time.</p><p>Finally, we arrive at the <strong><em>“nice-to-haves.” </em></strong>Nothing on this list should be critical to launch, and you should pretty much just assume you won’t have time to fit them in. That being said, tackling these can be fun things you do as side projects or breaks from the bigger Material update.</p><p>For us, we were able to squeeze in a few icon transition animations. Though not necessarily mission-critical to launch, these types of subtle changes add a lot of polish and fun to your app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/337/1*DdlBciEesYVFfxIrxpyp0w.gif" /><figcaption>Animations are fun! Plus, they feel very at home in Material Design.</figcaption></figure><h3>Just Stay Focused</h3><p>There is <em>a lot </em>to Material Design. But that doesn’t mean you should feel like you need to tackle it all. With your priorities in mind, pick your deadline and fit in what is reasonable. If you prioritize and focus on the important things, your first step to “going Material” can be fit into a single release.</p><p>Good luck! If you’d like to keep tabs on what our team is up to, you can follow us at <a href="http://pocket.co/sKXSK">@Pocket</a>.</p><p>You can check out the new Pocket for Material Design at <a href="http://pocket.co/sKTGP">http://pocket.co/sKTGP</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33cec7381b80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/what-i-learned-building/how-to-not-freak-out-about-material-design-33cec7381b80">How to Not Freak Out About Material Design</a> was originally published in <a href="https://medium.com/what-i-learned-building">What I Learned Building</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Greek Startup: a Mythical Creature?]]></title>
            <link>https://medium.com/@alexchristod/greek-startup-a-mythical-creature-2b9c7f039517?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/2b9c7f039517</guid>
            <dc:creator><![CDATA[Alex Christodoulou]]></dc:creator>
            <pubDate>Fri, 25 Oct 2013 02:32:59 GMT</pubDate>
            <atom:updated>2014-06-10T17:11:08.001Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*k1dTRxIayvW-Jg2bTf_y8A.jpeg" /><figcaption>Death of the Centaur, ScotT Eaton</figcaption></figure><h4>Same dreams, more barriers</h4><p>Hey, fellow startupers. It’s 03:45am, and a brainstorm of good and bad thoughts keeps me up. It’s been a year now since I quit my 3 jobs in the middle of a crisis and committed to my startup, and the least I can do is to share all these interesting things I encounter.</p><p><strong>Why should anyone care about another noob startuper?</strong> Because I live in <strong>Greece</strong>. For you non-Europeans, I’m exotic. For you Europeans, I’m the black sheep of the EU. For me, I’m just another dreamer running a startup, trying not to feel like an exotic black sheep.</p><h3><strong>Let’s talk about exotic barriers</strong></h3><p>In this first blog post I want to just share the context of my startup experience, that is, my country, Greece.</p><p>Greek startups are not mythical creatures. They’re for real, and the challenges they face, are some kind of exotic.</p><h4>Success stories around you</h4><p>We all know the American Dream, right? You can start your life as an immigrant bodybuilder who cannot articulate 3 consecutive words, evolve to a Hollywood movie star and finally transform to the Governor of the homeland of technology, California. You can even be the president, but we don’t know that yet :P</p><p>All US citizens grow up with this role model of success. If you’re a startuper you can pick your own idol like <a href="http://en.wikipedia.org/wiki/Drew_Houston">Drew Houston</a> or <a href="http://en.wikipedia.org/wiki/Brian_Chesky">Brian Chesky</a> among hundreds of successful entrepreneurs.When things go bad as hell, you can bring these guys in mind and say “if they made it, I can make it too”.</p><p>In central-north European countries, the role model of success is that of companies like <a href="http://en.wikipedia.org/wiki/Ericsson">Ericsson</a>, <a href="http://en.wikipedia.org/wiki/IKEA">IKEA</a> or <a href="http://en.wikipedia.org/wiki/Skype">Skype</a>. Hard work, discipline, a heart of a <a href="http://en.wikipedia.org/wiki/Vikings">Viking</a>, and chances are you’ll succeed.</p><p>Well, here is the Greek Dream: get a permanent, safe job, and work as less as you can. The word “exit” is uknown in Greece, but we have an equivalent word for success: “pension”. That’s the greek “exit”. So, when things go bad as hell with your startup here, all you can bring in your mind is all those people around you that told you how stupid you were to leave your job and risk your “life”. So, you can either take the <a href="http://en.wikipedia.org/wiki/Red_pill_and_blue_pill">blue pill</a>,or isolate yourself in your own home country, and move on with your dreams.</p><h4>Hack your life or die</h4><p>You know what is legal and what is not. Right? Here it’s not like that. Our public sector operates in a non-deterministic way, with controversial laws written in an ambiguous manner and interpreted unpredictably, depending on the case and people you’re facing.</p><p>We’re hacking every day. Not computer systems, but our lives, in order to survive in a chaotic, unorganized, bureaucratic system. You need to hack the tax system in order to achieve a triangular transaction in your online marketplace. You need to hack the insurance system in order to get an intern with no salary. You need to hack your mother in order to keep her assured that you, her beloved son, are not mentally disordered with all this “startup” madness.</p><h4><strong>Homo Deprecated</strong></h4><p>I know how excited you are when a new, innovative service shows up. I know, because I’ve seen you in the movies, or YouTube. That’s the only places I can see in action what’s happening in the US market, 2-3 years before they - if they do so - arrive in my country. There’s no Pandora or Netflix here. No Uber. I cannot apply for Apple Developer Program online, I need to send a fax (!).</p><p>What every startuper experiences as an innovative service and inspires him or her to realize what the next trend will be, comes here after a few years, probably after the company that provides that service has gone public and the new trend is not a trend anymore, but a norm. We’re a deprecated country, with deprecated citizens.</p><h4>It doesn’t sound Greek, it IS Greek</h4><p>It’s a common phrase: “It sounds Greek to me”. Well, we speak Greek. We’re 10 million people, and noone else is speaking our language — even though many English words are of Greek origin. So, the first thing we do here, at the age of 10 — some start at 8 — is learning English.</p><p>No need to say how it feels to read all these “How to make a great elevator pitch” articles, and then realize that if you try to follow these advices you sound like <a href="http://en.wikipedia.org/wiki/Shaka">Shaka Zulu</a> defending his village from white invaders.</p><h4>Roller Coaster 2.0</h4><p>On top of that, we’re trying to innovate. You know how it feels? It’s like riding the same roller coaster every startuper does, with a mechanical fist punching you on random intervals. You can get a punch wherever you stand, bad or good moments.</p><p>I hate whining, but hey, it’s 05:20am and I have an interview in 3 hours in order to hire a designer, while my startup has run out of money, what did you expect? :)</p><p>Ride on, and keep an eye for the punches!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b9c7f039517" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Copy / Bad Copy (Tests)]]></title>
            <link>https://medium.com/@yammerproduct/good-copy-bad-copy-tests-ade7b3833c90?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/ade7b3833c90</guid>
            <dc:creator><![CDATA[Yammer Product]]></dc:creator>
            <pubDate>Mon, 11 May 2015 23:34:17 GMT</pubDate>
            <atom:updated>2014-03-31T23:03:25.012Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xBw3saG7RCnF_ktPR7DAuQ.jpeg" /></figure><h4>Kate Harris</h4><p>When I meet new people and the question “So, what do you do?” inevitably arises, my answer gets the same reaction nearly every time: “Oh. You write product copy… That’s your whole job?” This is usually followed by them asking skeptically if there’s really THAT much copy in the actual product to worry about other than a few headers and a handful of error messages. I’ve experimented with a few different responses—everything from “WELL, let me tell you about my day,” to “Actually, I just play a lot of foosball.” But in all honesty, you’d be astonished at the amount of copy there actually is, most of which would otherwise be written last-minute and late at night by a ship-hungry engineer. More importantly, it might also surprise you how one simple header can measurably change the way people interact with an entire feature on Yammer. And how do we know that? Because we A/B tested it.</p><h4><strong>Copy can impact A/B test results just as much as design can.</strong></h4><p>This we know, now. Of course, like many other tech companies, at Yammer <a href="https://about.yammer.com/product/development/">we A/B test the feature changes we make to our product </a>— to make sure our hypotheses are correct. But since we started testing copy strategically as an isolated design variable, we’ve seen some huge deltas in results that startle even our most seasoned product managers.</p><h4><strong>Okay, so we test copy. But should we test ALL the copy?</strong></h4><p>My goodness, absolutely not.</p><p>Let me run you through a familiar scenario at Yammer:</p><p><em>Person 1: “I think </em>notify <em>is better.”</em><br><em>Person 2: “I think </em>alert <em>is better.”</em><br><em>Person 3: “I don’t think it will affect engagement either way.”</em><br><em>Person 4: “Let’s test it!”</em></p><p>Hold your horses, Person 4. There are a couple of boxes we need to check before we get to copy tests.</p><p>Remember that A/B testing is expensive—in terms of time, manpower, and future work. You might assume that copy is easy to change and thus low cost to test, but there’s also QA testing, results analysis, and code complexity to consider. So if you’re testing the copy, treat it like a feature test and don’t let it muddy your codebase without a healthy hypothesis that can survive a good beating in product council.</p><h4><strong>So when SHOULD you run a copy test?</strong></h4><ul><li><strong>If the test validates a hypothesis that can inform future product decisions, regardless of a win or a loss. </strong>Test copy <em>concepts</em>, not copy <em>strings . C</em>oncepts can apply to more than one design, not just word combinations (i.e. test different user motivations, not sentence structures). Imagine all the possible results you could get from the test and figure out what you might learn from it. Will it be able to apply to future features and not just this one? If all you’re going to learn is that “Start here” performs better than “Get started”, it’s probably not worth a test… UNLESS—</li><li><strong>If the feature or interaction is heavily dependent on copy to drive user action. </strong>If the copy is the main design element that will help the user understand what your product is for and why they should use it, you probably want to test it. Think about it in terms of user motivations — if you’re depending on the copy to get users to take an action, you’ll want to see which one works best.</li></ul><h4><strong>When should you NOT run a copy test?</strong></h4><p>(You will encounter way <strong>more </strong>occasions that will fall into this category, so be prepared to sniff them out.)</p><ul><li><strong>If you are doing it because the team has been having a neverending argument about four words. </strong>This is by far the most common BAD reason to run a copy test. A/B testing should be used to help inform the product in the future, not resolve arguments. Copy is the canary in the coal mine for the user experience as a whole. Instead of defaulting to “test it,” go back to your UX designers — nine times out of ten you’ve got some thin spots in the ice of your design. This is because copy is the last line of UX defense and it usually takes the heat for weak parts of the interaction. If things are hard to describe, it might mean that the design isn’t carrying the user through the flow, and thus the weight of the explanation lands on the copy. Watch out for long, complicated explanations — what bit of faulty UX is it covering for?</li><li><strong>If you can only measure click through and open rates rather than long-term product engagement (they’re not correlated). </strong>I’m looking at you, email. A/B testing in product has a different goal than A/B testing in email marketing — it needs to tell you how certain changes influence the value a user is getting from the product, not if they will click on a button you put in front of them.</li><li><strong>If the results won’t tell you anything relevant to future features. </strong>Will these results get shoved somewhere on a shared drive where nobody will ever be able to make use of them again? Then it’s not worth even an engineer’s coffee break.</li></ul><p>So there you have it. The do’s (please <em>please</em> do’s) and don’ts of copy testing.</p><p>Now if you’ll excuse me, I’ve got a foosball game to get back to.</p><p><em>Kate Harris is a User Experience Writer at Yammer. She says she is a vegetarian but we all know that sometimes she goes to In-N-Out.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ade7b3833c90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Passion is Overrated]]></title>
            <link>https://medium.com/@Dima/passion-is-overrated-97fb47683e20?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/97fb47683e20</guid>
            <dc:creator><![CDATA[Dima]]></dc:creator>
            <pubDate>Wed, 25 Jun 2014 05:16:09 GMT</pubDate>
            <atom:updated>2014-04-23T07:48:23.705Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HAI0l8w06KLiUGE9Dw4rTw.jpeg" /></figure><h4>Commitment is not.</h4><blockquote><strong>Commitment is becoming the new currency.</strong></blockquote><p>Along with reputation and credibility, commitment is the number one trait we look for in someone before considering working with them.</p><p>We are inevitably moving towards the world where the most important question to ask becomes:</p><p><strong>“Will they be committed enough?”</strong></p><p>Our world is getting smaller.</p><p>Assessing whether one is capable of getting the job done is something we get better and better at.</p><p>Understanding what should be accomplished in order to succeed is something we do better and better.</p><p>Knowing where to find people who can be of help along the way is a problem that nowadays can be more or less considered solved.</p><p>Commitment, in its turn, becomes the key ingredient.</p><p>But there is the trick.</p><blockquote><strong>Where commitment is currency, passion is bond.</strong></blockquote><p>And know well what happens to the markets when too many bonds are issued.</p><p>Hint: They <a href="http://www.theonion.com/articles/wait-what-if-we-try-giving-people-home-loans-they,34930/">collapse</a>.</p><p><strong>Small bonds are helpful and healthy</strong>.</p><p>They increase one’s purchasing power. They can be used as a leverage to grow projects. They are indicative of stable economy and established trust.</p><p><strong>Large bonds are big red flags.</strong></p><p>The <a href="http://en.wikipedia.org/wiki/Ponzi_scheme">Ponzi scheme</a> in action. Often they are the signs of hype, bubble and a soon-to-come disaster.</p><p>When counting on passion, don’t let bonds go beyond the size that can be safely handled.</p><blockquote><strong>Genuine passion is an overpower.<br>Passion incepted is a time bomb.</strong></blockquote><p>Charismatic people are “experts” at making others passionate.</p><blockquote>… people, who would be persuading you to do something for them, are, in their turn, well trained in making you lower your defense and follow your intuition instead …</blockquote><blockquote>… people around you will try to abuse this fact. It would benefit you greatly if you are able to identify those “experts” and force them to play on your field of rational reasoning and critical thinking.</blockquote><p>Today I can elaborate on this thought from my very first, very long and <a href="https://medium.com/better-humans/669abfe8843e#a2a6-686fd62af00c">very boring blog post</a>.</p><p><strong>Calling out for passion is nothing but a way people admit they are out of rational arguments.</strong></p><p>Unfortunately, human beings are still finding it hard to not react to the old “<a href="http://www.youtube.com/watch?v=gKosmXx1gkc">nothing but a little chicken</a>” argument. Sigh.</p><p>All I can do is to wish us to Live Long and Prosper.</p><blockquote><strong>Do not let people </strong><a href="https://raw2.github.com/dkorolev/press/a9795dec742be4d249dd5a739e75492cd1637c6d/pictures/passion-imposed.jpg"><strong>make</strong></a><strong> you passionate.<br>Wait until you </strong><a href="https://raw2.github.com/dkorolev/press/a9795dec742be4d249dd5a739e75492cd1637c6d/pictures/passion-genuine.jpg"><strong>become one</strong></a><strong>.</strong></blockquote><p>On the one hand, it is great to be driven by inner passion. For focused, creative people this might well be the best way to live.</p><p>Fact is, it is so great that passionately moving forward is a state close to an euphoria. Difficult to acknowledge once into it.</p><p>On the other hand, it feels miserable to realize that the passion was not natural but imposed. The ingenuity of everything will always make its way back around.</p><p>We deserve more than being drawn into becoming passionate about something only because the idea has been a high-quality sale.</p><p>Instead of getting addicted to fake, imposed values people around are quick to sell us, <strong>I would like to encourage each and every one to deeper search within ourselves and to find what we would genuinely wish to be doing.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97fb47683e20" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Video Lesson is not a Weather Forecast]]></title>
            <link>https://medium.com/@itisclear/video-lesson-is-not-a-weather-forecast-4ccb1723bd6e?source=rss----facf36016a4d---4</link>
            <guid isPermaLink="false">https://medium.com/p/4ccb1723bd6e</guid>
            <dc:creator><![CDATA[Kirill Shikhanov]]></dc:creator>
            <pubDate>Thu, 13 Feb 2014 12:09:53 GMT</pubDate>
            <atom:updated>2014-02-13T13:48:34.536Z</atom:updated>
            <content:encoded><![CDATA[<h4>A lesson to make a video lesson</h4><h3>What’s wrong with TV Weather Forecasts?</h3><p>How often did you want to share the video of a presenter forecasting weather in front of a map?</p><p>Like the way “Oh man! Must see! 6 degrees in Aberdeen!” Especially when you are from Glasgow, the recipient is from Edinburgh and 6 degrees in Aberdeen is not that bad.</p><p>Or “Check this out! Fingers! 10 fingers! OMG!”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*45LCoemR7c_W7Qh-2ff65A.png" /><figcaption><a href="http://en.wikipedia.org/wiki/BBC_Weather">http://en.wikipedia.org/wiki/BBC_Weather</a></figcaption></figure><p>No way.</p><p>Ever wanted to watch a weather broadcast on a daily basis? The whole 3-5-10 minute video?</p><p>You probably do this on a daily basis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*scHW8ner5dYBKZVmGm7awQ.jpeg" /><figcaption><a href="http://movies.apple.com/media/us/ios/2013/c9d61301_0529_4348_aaa2_0e0689ee3551/weather/weather.mp4">http://movies.apple.com/media/us/ios/2013/c9d61301_0529_4348_aaa2_0e0689ee3551/weather/weather.mp4</a></figcaption></figure><p>3 seconds max.</p><p>Just the weather. Nothing more.</p><p>2 seconds max to swipe for another city.</p><p>Have you ever rewatched any TV Weather Forecast?</p><p>Most probably the answers are <strong>no</strong> and <strong>never.</strong></p><p>But you may want to share and see again a weather gag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yx_czma5czKoDaPOc4sfUg.jpeg" /><figcaption>An example of a weather gag.</figcaption></figure><p>TV Weather Forecasts were replaced by weather apps to inform you and by memes to entertain you.</p><blockquote>So if weather video forecasts have changed</blockquote><blockquote>why have video lectures not?</blockquote><h3>What’s wrong with Video Lessons?</h3><p>The very first video lessons truely replicated real school/university lectures. It was necessary as learners were not used to a new format of education.</p><p>That is why teachers were acting like they were in lecture auditoriums.</p><p>Showing something on the board behind.</p><p>And taking up a significant amount of the screen with their bodies.</p><p>Making the audience feel as if teachers were present.</p><blockquote>Lecturers tried so hard to keep the telepresence in their video lessons</blockquote><p>And it was all right at first. But not for long.</p><h3>Inflation of interest to video lessons</h3><p>As it often happens over time the interest began to lower.</p><p>That video format palls on its audience.</p><blockquote>And teachers started pumping the video lecture bubble.</blockquote><p>The telepresence format was covered with multiple effects. What reminds the infamous TV weather forecast.</p><p>First there was a single camera.</p><p>Then two cameras.</p><p>Afterwards different angles.</p><p>Video tricks.</p><p>Various decisions from blockbusters (i.e. camera arc trajectory in The Matrix).</p><p>Special video effects.</p><p>Changes in the background.</p><p>Different sceneries (i.e. street, roof, etc.)</p><p>Visual effects (i.e. a teacher writes a text in the air)</p><p>And finally there was nothing left to surprise the audience.</p><blockquote>It was like upgrading horseshoes when automobiles were about to appear.</blockquote><p>In the end a TV weather forecaster can’t teach us anything.</p><h3>What makes a good video?</h3><p>Are there any benchmarks in videos that could be applied to lectures?</p><p>Video = sound + animated images.</p><p>As almost all video lessons are pretty good at sound, they fail at images.</p><p>A viewer should see every second what’s going on.</p><p>Every microimage.</p><blockquote>A viewer must not look aside.</blockquote><blockquote>Every shot is important.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FzDZFcDGpL4U%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DzDZFcDGpL4U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FzDZFcDGpL4U%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/01462ca97f5e371de11ca26315694c65/href">https://medium.com/media/01462ca97f5e371de11ca26315694c65/href</a></iframe><p>Every video should carry one message.</p><p>One single message.</p><p>There might be more than one.</p><p>But one is a must.</p><p>It may be a plot summary or 2 * 3 = 6 or that this digital production studio makes great stuff.</p><blockquote>A viewer must watch the video and say:</blockquote><blockquote>“This cat wanted to eat”.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fw0ffwDYo00Q%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dw0ffwDYo00Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fw0ffwDYo00Q%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f358731e934aae3fbd38ddf7a136b6fe/href">https://medium.com/media/f358731e934aae3fbd38ddf7a136b6fe/href</a></iframe><p>Video lesson should be like a teaser.</p><p>Wow-effect.</p><p>To leave an impression.</p><p>A showreel.</p><blockquote>A viewer must say:</blockquote><blockquote>“Awesome, I barely got it, need to see it again right now”.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F70032068&amp;url=http%3A%2F%2Fvimeo.com%2F70032068&amp;image=http%3A%2F%2Fb.vimeocdn.com%2Fts%2F443%2F074%2F443074787_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/3769891f4f3842d5c5aeeb4758cba5e9/href">https://medium.com/media/3769891f4f3842d5c5aeeb4758cba5e9/href</a></iframe><h3>Make a video lesson this way</h3><p>10 advices to sum up.</p><h4>VIRUS</h4><p>Make it shareable. Every video item.</p><p>Make it viral. Yes, we’re talking about one of many lessons.</p><p>Go viral or die trying.</p><h4>EMOTIONS</h4><p>Make learners wanna watch the lesson again and again.</p><p>Make them smile. Make them laugh.</p><p>Make them feel.</p><h4>DYNAMIC</h4><p>Make it short. Not more than 5 minutes.</p><p>30-150 second is excellent.</p><p>Add actions. Capture the audience’s attention.</p><p>Make it atomic, divide the materials into smaller pieces.</p><blockquote>This one video lesson is a nice try.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F82398070&amp;url=http%3A%2F%2Fvimeo.com%2F82398070&amp;image=http%3A%2F%2Fb.vimeocdn.com%2Fts%2F458%2F851%2F458851371_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/9d183bb4f8cd0bbd5e4532d7d47e88e5/href">https://medium.com/media/9d183bb4f8cd0bbd5e4532d7d47e88e5/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ccb1723bd6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>