How Limitations Led To My Biggest App Store Success and Failure

How Limitations Led To My Biggest App Store Success and Failure

• By Ben Johnson


• July 28th, 2014


• AppsCase StudiesiOS


• 1 Comment

Look during your calendar. If you’re anything like me, all we see are meetings, places to go, things to do, people to accommodate and not a lot of white space. Few people adore their calendar. So, we set out to change that, and we schooled a lot in a process.

Our app is an iPhone app that flips your calendar upside down and lets we concentration on a free time in your day, instead of all a bustling time. The app itself has been around given 2011, yet a story of how it came to be and what a group eventually schooled is one that we have been wanting to tell for utterly some time. It’s a story of how stipulations led to my biggest success in a App Store — and my biggest failure.

¹

This is a story of how a App “Free Time” came to be and what a group eventually schooled in a process. (View vast version²)

Embracing Limitations

At a core, a app (called “Free Time”) is all about accurately that, giveaway time. But, as many program projects tend to go, while it was recognised in morality (answering a question, “When am we free?”), Free Time came into a universe with a few some-more facilities than approaching and a lot some-more complexity. We were in college when we came adult with a idea. we was bouncing behind and onward between classes, swapping schedules from one day to a next, and perplexing to find time to get together with my friends. In 2010, some-more than a few companies were perplexing to solve a same scheduling problem (Tungle.me³, Doodle⁴, When Is Good⁵, Scheduly⁶, etc.). Everyone was grappling with a same elemental issue: When are people giveaway and how do we get them together?

Most of those companies spent or continue to spend millions of dollars building formidable infrastructure to support in-the-cloud calendar scraping and mutual time fortitude (i.e. reckoning out when dual people, in potentially opposite time zones, are both available). It sounds elementary yet it unequivocally isn’t, and thankfully we didn’t know that.

This brings me to my initial vital takeaway: Embrace your limitations. At a time, a stipulations seemed significant:

• We didn’t have any funding.


• We didn’t know how to build a server.


• We had no suspicion how formidable calendars and time-based calculations were.


• We had never sole an app in a App Store.

Limitations can be tricky, yet they can also reason dark benefits. we couldn’t compensate anyone, so my crony and engineer Houston schooled to pattern for mobile; my beginner roommate, Nathan, schooled about calendrical calculations and C++; and we schooled Objective-C. We were scrappy and bootstrapped, yet we finished it work.

Because a 3 of us didn’t have any income and we didn’t know how to build a server, we built all within a app (even a mutual time resolution), and we launched a product that is forever scaleable and that, to this day, has no fundamental costs other than Apple’s annual developer fee. Not many app developers in this day of hyper-connectivity can make this claim.

Because we had no suspicion how formidable calendars are, we indeed suspicion this app was going to be a travel in a park. It wasn’t, yet if we had famous a details and outs and complexities of time, we have no doubt we wouldn’t even have started.

So, if you’re feeling singular or constrained, don’t. Limitations can make a vast disproportion and could eventually lead to your many artistic moments.

37signals likes to consider of constraints differently⁷:

Constraints are mostly advantages in disguise. Forget about try capital, prolonged recover cycles, and discerning hires. Instead, work with what we have.

The Launch

We launched roughly 8 months after we started building a app. It was nights and weekends mostly for a 3 of us, yet we finished it, put it adult in a store and breathed a duration whine of release.

The Calm Before a Storm

We were in examination for 7 prolonged unpleasant days. we had submitted a few tiny apps before, so we knew a drill, yet this time a wait was excruciatingly long. On a seventh day (coincidentally, a same day we were graduating from college), we got a pull display from iTunes Connect: Free Time had been authorized and was in a App Store. There was a lot of high-fiving and celebration; we told a friends to download a app, and we posted about it on Facebook and Twitter. At a time, we didn’t unequivocally have a selling plan; we had talked to a few people yet hadn’t unequivocally drummed adult a lot of seductiveness so far. As distant as we were concerned, graduating from college and rising an app was copiousness for one week.

We graduated on a Thursday, and by Friday 3 hundred people had downloaded a app. We were blown divided and went to nap that night assured that this was a first-day portion and that no one else would find it. The subsequent day, a same thing happened, another 3 hundred people. This kept adult until Apple featured it as a “New and Noteworthy” app one week after it strike a store.

Being featured in a App Store is like throwing gasoline on a fire. It set off an blast of downloads, support emails (both certain and negative), media requests, etc. It was one of a many sparkling and terrifying experiences: make-up adult a belongings, meditative about “the genuine world,” and removing emails from people in Qatar who were regulating a app and anticipating a lot of bugs.

The subsequent few weeks were pell-mell as we pushed out new updates, responded to media inquiries and attempted to figure out what had usually happened.

The Results

Eventually, things quieted down. We kept pulling out updates to residence user concerns, and a few years later, here we are. we like when developers share numbers, so here are some fun ones from Free Time:

• Downloads
  
  To date, some-more than 200,000 people have downloaded a app. Other than a website and amicable pages, we haven’t finished any marketing.


• Countries
  
  The app has been used in some-more than 150 countries around a universe (and we still usually support English). Surprisingly, a US accounts for usually 48% of all income and 35% of users.


• Time spent
  
  Since we started tracking unknown eventuality use dual months after launching, users of Free Time have spent a sum two years regulating a app — a small mocking deliberation that it’s all about saving people time.


• Accolades
  
  The app has been created about and profiled by CNN, ReadWriteWeb, Lifehacker and AppAdvice and has been featured by Apple a handful of times.


• Money
  
  The app was giveaway when we started out, that is partial of a reason given it was downloaded so much. Even so, by in-app squeeze and eventually a paid model, income from Free Time has paid for a crater of coffee for a 3 of us any day for a past 3 years — positively not adequate to means any of us, yet something to be unapproachable of nonetheless. In further to revenue, a work on Free Time helped any of us find a pursuit that pays a bills.

⁸

We did a few things right, yet this essay is about what we did wrong. (View vast version⁹)

So, we did a few things right, yet I’d rather tell we about what we did wrong, and what we schooled in a process.

Throughout a routine of building a app, rising it in a App Store and traffic with a assault of users (and complaints) from opposite a world, we schooled a good understanding about a shortcomings of a app and about a existence of a approach people consider about their apps and their calendars.

1. Changing Perspectives And Letting People See Between The Lines Is A Great Way To Stand Out

When we started prototyping a app, we built it to be a unequivocally discerning approach to dispatch an email to a crony or co-worker who wants to know your accessibility on a sold day. That was it, zero more. To capacitate this behavior, a time between your events became a symbol that we could daub to share. That indeed finished adult inverting a weight of a calendar’s UI and fixation some-more significance on a opposite (the giveaway time).

¹⁰

The time between events became a button, inverting a weight of a calendar’s UI and fixation some-more significance on a a giveaway time. (View vast version¹¹)

By inverting what was traditionally approaching of a calendar UI, we stranded out, and any time we showed off a app, we got a same response: “That’s unequivocally neat and creates a lot of sense.” To be honest, we stumbled on it, yet that altered viewpoint enabled us to see something we all knew in a new and engaging way. As a result, we garnered a lot of courtesy with a comparatively elementary change to something that everybody takes for granted.

Drew Olanoff of The Next Web said:

Free Time will totally change a approach we demeanour during your calendar.

Apps don’t need to be new and novel ideas, and they don’t have to emanate an attention out of skinny air. The approach to build a good app is to concentration on something simple, even something that everybody takes for granted, and afterwards make it better. The travel app Uber is novel and singular for a lot of reasons, yet during a finish of a day it’s usually a softened approach to accost a cab. All that a developers did was change people’s viewpoint and make something better.

2. Get Ready To Iterate

Initially, we designed and redesigned a app some-more times than a engineer Houston would have liked. When building your possess app, learn to welcome this, given iteration and excellence are pivotal mixture of a successful app.

¹²

Our initial iteration is on a left, and what we finished adult rising is on a right. While a functionality remained mostly a same, a pattern importance and navigation altered dramatically. (View vast version¹³)

Don’t be fearful to start in one place and finish adult somewhere totally different. With any iteration, we attempted to incorporate new training and new feedback. By removing a severe explanation of judgment out to beta testers early, we were means to brand some pivotal flaws in a display and concepts.

Our First Notion of Sharing

In a early iterations, pity was a detached activity, and given we had started with a tabbed architecture, putting pity in a possess add-on finished sense. Through early beta testing, we fast satisfied that we mustn’t let a user act on their day yet a context of what is function on that sold day. The perspective we started with usually showed availability, yet yet a surrounding events, a testers were confused and incompetent to relate their accessibility with a calendar.

¹⁴

Without a surrounding events, a testers were confused and incompetent to relate their accessibility with a calendar. (View vast version¹⁵)

A New Inline Approach

This second iteration not usually adopted a new tone intrigue to yield softened contrariety between giveaway time and bustling time, yet also incorporated giveaway time right on tip of a unchanging calendar.

¹⁶

The second iteration supposing softened contrariety between giveaway time and bustling time. (View vast version¹⁷)

This softened context, and it gave users a information they indispensable to act on their giveaway time yet carrying to change tabs and switch context. It also enabled users to see their calendar in a new approach and gave many a value they were looking for even if they didn’t wish to act on that giveaway time.

The Final Product

In a final iteration, we increasing a calendar space to uncover as many events as possible. We also finished pity a modal activity that users could toggle from any screen. By focusing some-more on a calendar’s UI, we were means to incorporate a thought of selectable giveaway time right inline and in a approach that would be gentle for users who are informed with Apple’s Calendar app.

¹⁸

In a final iteration a calendar space was increasing to uncover as many events as possible. (View vast version¹⁹)

But iteration never stops. Now that we were finished with a app, we had to refurbish a icon.

²⁰

After being finished with a app, we had to refurbish a icon. (View vast version²¹)

3. Iterate Doesn’t Mean “Add More”

We also unsuccessful to comprehend in a iterations that we could have (and should have) private facilities and functionality that a testers found reduction compelling. We never identified a smallest viable product. Ultimately, we focused a iterations on elaborating a product, when we should have spent time enlightening a core value proposition, “When am we free?” This led to an unavoidable grow of features, that diluted a product and eventually compulsory us to emanate a extensive user walkthrough that explained a nuances of a app and what it does. The walkthrough was 6 screens, and when we launched we forgot to embody a “Skip” symbol (a vast mistake).

²²

Not including a “Skip” symbol in a 6 shade walkthrough was a vast mistake. (View vast version²³)

In a final year, usually 42% of new users finished it by this initial walkthrough on initial opening a app. All of these users had consciously motionless to squeeze a app and waited for it to download and install; so, this walkthrough is catastrophic in a acclimatisation numbers.

Holding behind when you’re ardent about something is intensely hard, yet it is equally critical to commend that a miss of functionality (more agreeably referred to as simplicity) is as considerable as extent of functionality. While a initial judgment was to capacitate users to concentration on a giveaway time in their day, we finished adult rising with a following features:

• People could see their accessibility on tip of their calendar.


• A discerning filtering apparatus enabled people to use tradition accessibility searches to find giveaway time during sold meals, days and durations. To support this, we authorised users to mention a time of any of their meals.


• Users could mention work hours, in further to their waking hours, in sequence to slight down their giveaway time.


• People could change a calendars that influenced their Free Time.


• People could mention a lengths of a blocks of time that were displayed, and we built formidable algorithms to establish how to separate adult sold blocks of time to fit user preferences.


• People could see a discerning perspective of their accessibility for any given meal.


• People could hunt for giveaway time during sold time ranges, on sold days, during sold dishes and for specific durations.


• People could share their giveaway time by dispatching an email, duplicating it to their clipboard, component an SMS-specific chronicle with condensed calm and — approbation — bumping phones (that was a thing then).


• Once dual users had common time, a certain record form authorised them to see any other’s accessibility and perspective a dedicated shade of their jointly accessible times.


• Oh yeah, and we upheld all of a actions you’d design a calendar app to support, like modifying events, formulating new events, displaying all-day events, doing events that overlie and seem on tip of one another, and so on and so on.

It turns out only one underline unequivocally mattered: vouchsafing people see their accessibility in a new way. According to a analytics, 95% of a time, people usually wish to demeanour during their calendar, see their accessibility and act on it in their possess way. They don’t unequivocally filter (only 8% of users did that), they don’t share (only 2% of users did that), and they positively don’t strike phones to find out when they’re both giveaway (only 0.002% of users did that).

4. Solve A Worthwhile Problem, But Don’t Expect Your Problem To Be Anyone Else’s Problem

Being ardent about what you’re formulating is important. If we can’t build a product that we would use, you’ll never be means to build a product that anyone else would wish to use. So, build something that solves your possess problem, scratches your possess eagerness or satiates your possess need. This will give we a passion to do what it takes to emanate something valuable. At a finish of a day, even if it doesn’t take off, you’ll have something that we can use.

But don’t design a problem we are elucidate to be anyone else’s problem. When we started, we suspicion a app’s ability to solve dual calendars and benefaction jointly accessible time would be a game-changing underline for offline use. We wanted to excommunicate a vast players in a space, a Tungles and Doodles of a universe that force users to promote their accessibility all of a time and that need costly servers and broach a muted experience. we can’t even start to sum adult a volume of time we spent building a database structure and modifying a app to concede for this mutual time resolution. It simply took adult an whole month of a eight-month growth process. Since launch, 179 of those 200,000+ users have used it, many usually once. In box we don’t wish to do a math, that’s 0.000895% of users.

For comparison’s sake, while 179 people have used a mutual giveaway time feature, 2900 users have common their giveaway time in some way, figure or form; 15,000 have filtered for their giveaway time, many usually once; and a other 150,000+ seem calm usually to see their giveaway time laid out on tip of their calendar.

This is a tough indicate to get opposite and an even harder one to avoid. So, what do we do? Trust your instincts, yet rage your excitement. Build something that we love, yet don’t design others to adore it a approach we do. When pull comes to shove, let go.

5. Build For The World, Not Just Your World

We never internationalized a app to support any languages other than English. This was a second biggest mistake. Two years ago, rising an app that doesn’t support a rest of a universe competence have been acceptable. Today, if we are building your possess app for a App Store, build it for a whole universe from a start.

²⁴

The map above shows Free Time use around a universe in 2013. (View vast version²⁵)

Even today, a US accounts for usually 48% of Free Time’s sum income and usually 35% of a users. Had we motionless to interpret and support other locales, a financial lapse would have been higher.

Be Careful With Time, a Strange and Complicated Concept

We always suspicion of Free Time as a cross-platform app, and we creatively suspicion that a mutual time fortitude was a biggest underline (remember?). So, we blending a plan to accommodate that use case. As a result, we built a underlying calendar-parsing engine in C++, a denunciation that compiles to both iOS and Android. It also didn’t harm that Nathan knew some-more C++ than Objective-C, so it was a healthy fit for him as well.

Without a assistance of any complement libraries like NSDate or NSCalendar, we set out to build a possess cross-platform calendar database and reinvent a circle in a process. Never do this. The fundamental complexities of time make this arrange of try a monolithic plea homogeneous to rebuilding an whole city section by section usually given we don’t like a location. If we can leverage someone else’s work and not reinvent a wheel, do that.p

²⁶

(Image credit: Smythe Richbourg²⁷) (View vast version²⁸)

You need to consider of a few scenarios if we are building an app that has anything to do with calendars or time-based calculations.

30 + 20 is easy, simple math. Day 30 of this month + 20 days isn’t so easy. OK, maybe we consider that that calculation is comparatively easy and that a answer is substantially a 19th or 20th of a subsequent month. It seems easy until we consider about people in Egypt and find out that their subsequent month is Pi Kogi Enavot (“the small month”), that is usually 5 days long!

Another fun thing we found out was that midnight on certain days in certain countries never exists. Most of a all-day events we stored began during midnight on a certain day and finished during 11:59:59. We suspicion that this was a flattering judicious and candid approach to store an event, yet we forgot about illumination assets time in Brazil, that jumps from 12:00 am to 1:00 am, instead of 1:00 am to 2:00 am as it does here in a US. Therefore, midnight never exists, and as a result, for during slightest for one day any year, a app would pile-up on launch for users in Brazil.

Oh, and Leap Day in 2012 was one of my favorite days. Almost any active user sent us an email or twitter vouchsafing us know that a app was off by a day (as it remained for a month).

²⁹

The stream year in a Buddhist calendar is 2557. (View vast version³⁰)

We also had a lot of difficulty with opposite general calendars that differ not usually in their translations, yet essentially in their stream year, month and day. We have a startling volume of users in Saudi Arabia and Qatar, and one emanate with Free Time is that it doesn’t support a central calendar there unequivocally good (the Islamic Hijri calendar). The stream year in that calendar is 1435, and a days of a month are all totally opposite given it is a lunar calendar, not a solar calendar. we can tell we with a high grade of certainty (even yet we haven’t attempted it myself) that mutual time fortitude between someone on a Gregorian calendar (the many common of calendars used) and someone on another calendar will destroy spectacularly. Thankfully, no one seems to use that feature!

Languages and Dates Are Only Part of a Problem: Culture Makes Up a Rest

Building for a universe isn’t usually about internationalizing your app, though. Consider also opposite use cases for populations and cultures around a world. When we launched Free Time, we baked in a judgment of weekdays (Monday by Friday) and weekends (Saturday and Sunday). We also insincere that many users work Monday to Friday and have opposite waking hours on weekends than on weekdays. In hindsight, this was an apparent oversimplification, yet during a time we weren’t meditative about a universe —we were usually meditative about a world, and that is accurately how a universe works.

³¹

The Monday-to-Friday work week was primarily hardcoded into a app. (View vast version³²)

We shortly detected that this arrogance was wholly improper in many countries via a Middle East, where a weekend starts on Thursday and ends on Saturday (Qatar and Saudi Arabia are dual such countries). As a result, we had to concede users to mention their work week and selectively capacitate work hours.

³³

On a left is a chronicle we launched with, and on a right is a simplified UI that allows we to make changes on sold days. (View vast version³⁴)

Inadvertently, in building for a world, we also alienated another partial of a population, people who work a night shift. Because we compulsory users to tell us when they arise adult and when they go to nap (so that we could infer their series of giveaway hours), we built a control to name those hours that extended usually from 12:00 am to 12:00 am. We didn’t consider of a people who work a cemetery change and need to set their “day” and operative hours somewhere between 12:00 pm and 12:00 pm.

³⁵

Our resolution for workers on a cemetery change was to extend a slider. Unfortunately, a slider’s increasing operation finished it a bit harder to name a time of day. (View vast version³⁶)

These are usually a few of a eye-opening corner cases that calendars, time-based calculations and a different and general assembly finished us consider about. Apple does a lot to assistance developers support these use cases out of a box and directly from a handling system, yet usually if we let it.

Build for the world, not usually your world, and don’t reinvent a wheel.

6. Invest Time In Subtle Details — People Will Notice

Here’s something we did right. We spent a lot of time improving and perfecting a loading animation and other pointed animations via a app (such as for updating settings, filtering, etc.). This turn of gloss was forward of a time and unequivocally set a user knowledge apart.

Perfecting animations via a app was forward of a time and set a user knowledge apart.

Animations in apps are some-more hackneyed these days and are apropos some-more of a requirement with a new UI paradigms introduced in iOS 7. Still, a well-crafted animation is still a illusory approach to set your app detached from a pack. Finding a right change between facilities and subtleties that warn and pleasure users is an critical step in formulating a noted experience. When we pronounce with people about Free Time, many of them remember a spinning cloud and a time hands and zero else. They vaguely remember that it has to do with calendars, yet they always remember this animation.

Think critically about what kinds of noted practice we can create, and make them wonderful.

7. Keep Pushing — Great Ideas Deserve To Live

This was a biggest mistake. Great ideas merit to live, and giving adult on one too fast does a harm both to your users and to a idea. While full-time jobs and nascent careers took dominance for all of us after graduating, a miss of continual excellence and updates over a years is one of my biggest regrets.

³⁷

A graph chronicling a disappearing use of Free Time over 2013. New users are highlighted in red. (View vast version³⁸)

With usually 6 updates given 2011, use has depressed dramatically due to concentration bugs, OS updates and a detriment of faith in a ability to say a product:

• Only 50% of people use a app for some-more than 6 days.


• Only 15 to 20% lapse after one month.


• Between 2012 and 2013, sessions declined by 59%; a normal eventuality length declined by 55% (down to 1 notation 34 seconds); and users declined by 61% (down to 20,000).

People form an romantic bond with a program they use. Throughout Free Time’s life in a App Store, we have continued to accept emails from people who go out of their approach to demonstrate how many they adore regulating a app and how it has totally altered a approach they demeanour during calendars. When building an app that people will use any day, consider about how we will develop it over time and adjust to your customers’ needs.

Just final week, we got this email:

Are we ever going to refurbish Free Time? we work dual jobs and scheduling is tough, yet this app helps. Just vouchsafing we all know a app is good and we would adore to see it continue!

Recap

So, we did a lot of things right and a lot of things wrong, yet a genuine beating for us and a users is that we never unequivocally softened a app over a initial few months. We could have built an Android version, an iPad version, a web chronicle and a Mac version, and we could have experimented with a pricing indication to softened fit a users, yet we didn’t. For several reasons, life got in a approach and we gave adult too quickly. I’m certain we could have incited it into a viable business, yet we opted to pursue other things.

Thankfully, we aren’t finished with a app, and we’ll be rising chronicle 2 in a entrance months after a prolonged hiatus. We’ve schooled utterly a bit, and we’re changing a lot: a calendar perspective is now front and center; a concentration is on anticipating Free Time, not pity it; and a series of facilities has been drastically reduced (much to a chagrin).

³⁹

A screenshot of a beta chronicle of Free Time 2. (View vast version⁴⁰)

As we build your subsequent good suspicion or even build an suspicion that usually scratches your possess itch, remember a following:

• Embrace your stipulations and use them to your advantage.


• Create something that changes people’s perspectives, so that they never forget you.


• Don’t be fearful to iterate often, yet conflict a titillate to supplement some-more during any iteration.


• Trust your instincts and build something that we will adore (even if others competence not).


• Build for the world, not usually your world.


• Don’t give up.

Oh, and consider twice about building a calendar app. It could be a genuine empty on your giveaway time!

You can pointer adult to hear some-more about Free Time 2⁴¹, or check out Free Time in a App Store⁴².

(al, ml)

Footnotes

1. 1 http://www.smashingmagazine.com/wp-content/uploads/2014/07/01-free-time-banner-opt.jpg


2. 2 http://www.smashingmagazine.com/wp-content/uploads/2014/07/01-free-time-banner-opt.jpg


3. 3 http://www.crunchbase.com/company/tungle


4. 4 http://doodle.com/


5. 5 http://whenisgood.net/


6. 6 http://www.scheduly.com/


7. 7 https://gettingreal.37signals.com/ch03_Embrace_Constraints.php


8. 8 http://www.smashingmagazine.com/wp-content/uploads/2014/07/02-free-time-featured-opt.jpg


9. 9 http://www.smashingmagazine.com/wp-content/uploads/2014/07/02-free-time-featured-opt.jpg


10. 10 http://www.smashingmagazine.com/wp-content/uploads/2014/07/03-freetime-calendar-zoomed-opt.jpg


11. 11 http://www.smashingmagazine.com/wp-content/uploads/2014/07/03-freetime-calendar-zoomed-opt.jpg


12. 12 http://www.smashingmagazine.com/wp-content/uploads/2014/07/04-free-time-before-and-after-opt.jpg


13. 13 http://www.smashingmagazine.com/wp-content/uploads/2014/07/04-free-time-before-and-after-opt.jpg


14. 14 http://www.smashingmagazine.com/wp-content/uploads/2014/07/05-ft-share-concept-early-opt.jpg


15. 15 http://www.smashingmagazine.com/wp-content/uploads/2014/07/05-ft-share-concept-early-opt.jpg


16. 16 http://www.smashingmagazine.com/wp-content/uploads/2014/07/06-ft-share-concept-middle-opt.jpg


17. 17 http://www.smashingmagazine.com/wp-content/uploads/2014/07/06-ft-share-concept-middle-opt.jpg


18. 18 http://www.smashingmagazine.com/wp-content/uploads/2014/07/07-free-time-sharing-opt.jpg


19. 19 http://www.smashingmagazine.com/wp-content/uploads/2014/07/07-free-time-sharing-opt.jpg


20. 20 http://www.smashingmagazine.com/wp-content/uploads/2014/07/08-icon-comparison-updated-opt.jpg


21. 21 http://www.smashingmagazine.com/wp-content/uploads/2014/07/08-icon-comparison-updated-opt.jpg


22. 22 http://www.smashingmagazine.com/wp-content/uploads/2014/07/09-free-time-walkthrough-opt.jpg


23. 23 http://www.smashingmagazine.com/wp-content/uploads/2014/07/09-free-time-walkthrough-opt.jpg


24. 24 http://www.smashingmagazine.com/wp-content/uploads/2014/07/10-free-time-usage-opt.jpg


25. 25 http://www.smashingmagazine.com/wp-content/uploads/2014/07/10-free-time-usage-opt.jpg


26. 26 http://www.smashingmagazine.com/wp-content/uploads/2014/07/11-confusion-opt.jpg


27. 27 https://www.flickr.com/photos/tsmyther/48428707/


28. 28 http://www.smashingmagazine.com/wp-content/uploads/2014/07/11-confusion-opt.jpg


29. 29 http://www.smashingmagazine.com/wp-content/uploads/2014/07/12-buddhist-calendar-opt.jpg


30. 30 http://www.smashingmagazine.com/wp-content/uploads/2014/07/12-buddhist-calendar-opt.jpg


31. 31 http://www.smashingmagazine.com/wp-content/uploads/2014/07/13-free-time-weekends-opt.jpg


32. 32 http://www.smashingmagazine.com/wp-content/uploads/2014/07/13-free-time-weekends-opt.jpg


33. 33 http://www.smashingmagazine.com/wp-content/uploads/2014/07/14-free-time-select-hours-opt.jpg


34. 34 http://www.smashingmagazine.com/wp-content/uploads/2014/07/14-free-time-select-hours-opt.jpg


35. 35 http://www.smashingmagazine.com/wp-content/uploads/2014/07/15-free-time-work-hours-opt.jpg


36. 36 http://www.smashingmagazine.com/wp-content/uploads/2014/07/15-free-time-work-hours-opt.jpg


37. 37 http://www.smashingmagazine.com/wp-content/uploads/2014/07/17-declining-usage-opt.jpg


38. 38 http://www.smashingmagazine.com/wp-content/uploads/2014/07/17-declining-usage-opt.jpg


39. 39 http://www.smashingmagazine.com/wp-content/uploads/2014/07/18-free-time-opt.jpg


40. 40 http://www.smashingmagazine.com/wp-content/uploads/2014/07/18-free-time-opt.jpg


41. 41 http://signup.freetimeapp.com


42. 42 https://itunes.apple.com/us/app/free-time/id429232593?mt=8

↑ Back to topShare on Twitter

How Limitations Led To My Biggest App Store Success and Failure