The Case for Universal Apps
Release your iPhone/iPad app as a Universal app in the App Store-- it’s better for you, and it’s better for users. We’re going to give you some juicy iTeleport sales data and user anecdotes since the iPad launch to back that claim.
If you’re a developer both for the iPhone and iPad, you have a choice to make when releasing your app in the App Store. Do you release separate iPhone and iPad apps or do you release a Universal app, which runs on both the iPhone and iPad?
There are a couple of different ways to look at it. First, there’s the financial perspective: which approach results in better sales? Second, there’s the user perspective: which approach makes the most sense to users, pisses them off the least and causes less support issues? We think that Universal apps are better from both perspectives.
The Financial Perspective
As a developer, you want to be able to recoup the investment of time and money you put into developing the iPad version of your app. Developing for a new device requires a significant effort, and you want to be fairly rewarded for that effort. The question is: are total sales better when you release two separate apps (that are perhaps also priced independently), or a Universal app? A first-pass answer to this question would be: well, clearly in the Universal case you are effectively giving away two apps for the price of one. If a user buys the app for the iPhone, they get the iPad app for free, and vice versa. It doesn’t make sense for me to give away my work for free, you say.
We say: yes it does! It turns out that Universal apps are far more appealing to users than apps that target just one platform, and so a Universal app is likely to generate more sales than two separate iPhone / iPad apps combined.
We have a particularly unique perspective on this, because we initially released iTeleport for iPad this April as a separate, non-universal app, even though iTeleport for iPhone has been on the App Store since July 2008. There wasn’t a grand plan here; the reason for doing this was that we wanted to get the iPad version out on launch day, and we had changed enough of the code that integrating those changes with the iPhone version to make a Universal app wasn’t possible in the time we had. We were committed to making these updates available for free to our existing users, and we explained this clearly on our website and on the App Store, and so a few weeks later, we made the iPhone app (iTeleport: Jaadu VNC) a Universal app. The biggest reason for doing this was actually from the user perspective, which we’ll talk about in a second.
So we have data that we can look at and compare these two options in a nice, clean way. This chart shows the sales data for iTeleport for iPad and iTeleport: Jaadu VNC for iPhone from April 1 to April 26:
Pretty good. An exciting launch week spike, followed by a respectable 2.5x jump over the pre-iPad average. Looks like this is the way to go -- keep the two apps separate, and let users pay twice.
But looks can be deceiving. The next chart shows sales data for the Universal version of iTeleport: Jaadu VNC since its release on April 26 to June 1:
Surprisingly, the total sales increased to almost 4x the sales average for March. Here's all the data put together in one nice, big chart:
So from a purely financial perspective, it's clear that Universal apps are the way to go.
The User Perspective
We weren’t necessarily expecting this. We sort of stumbled into it because of the second perspective we talked about: what do users want? Answering this question is a little bit trickier, because not all users want the same things, and not all users talk to you. However, we decided one thing very clearly before we launched the iPad version: we wanted to reward our existing iPhone users with a free upgrade to the iPad version. We made that as clear as possible to our users, both on the iTunes App Store description for the iPad app, and on our website. We didn’t really commit to a specific mechanism for the upgrade, because we weren’t sure exactly how we'd do it, and whether we were going to go the Universal app route. We were also considering trying an in-app unlocking model, where we would keep track of which users had the iPhone version before a certain date, and upgrade them for free. We could also do fancier things like give future users discounted upgrades from iPhone to iPad and vice-versa.
After we released iTeleport for iPad only, however, our users really forced our hand. They were clearly confused, impatient, frustrated and sometimes upset. Some users never saw our upgrade promise, and wrote angry letters (which, to their credit, they quickly and apologetically retracted when we pointed out that we'd promised a free upcoming upgrade). Some users, even if they were aware of the upgrade path, were hounding us a week after launch saying: Where’s that upgrade, iTeleport? Several users just didn’t get how it would work. A few savvier users asked us directly: Why don’t you guys make the app Universal?
This forced us to ask ourselves: Yeah, why don’t we? In-app unlocking was an option, but a little bit of thinking exposed a lot of potential complexity, significant development work, and no clear benefit to us or our users. On the other hand, there was the Universal option, which was easy for us development-wise, and well-understood by users. The only issue for us was: now that we have two apps out there, if we make one of them universal, is that going to piss off users who bought the other one? We actually thought about this a lot, and decided that going Universal would probably upset some users in the short term, but would be better for us and for our users in the long-term, from a support and less-product-confusion perspective.
We turned out to be right on both counts: making iTeleport for iPhone a Universal app did upset some users, and we believe it will be better for us in the long-term. Obviously, the users that got upset were the ones that bought the iPad-only version, and saw that iPhone users were getting both for free. Or, they bought both the iPad and iPhone versions separately, and were (understandably) angry about having to pay twice for something they could now get for the price of one. We did our best to be open and accommodating to these users, suggesting refunds and even offering promo codes in some cases. Some users understood; some not so much. It was painful for a few weeks, but we’ve gotten through it now. Now, about a month after the launch of the Universal app, we are happy with our decision. Users are very happy to see (and pay for) Universal apps, and there’s less confusion.
We wouldn’t recommend going down this road of putting out separate apps and then going Universal. We sort of stumbled into it, but since we found a clear winner in terms of the best approach, we thought we’d put that out there in this post. Hopefully this helps other developers when they’re making similar choices.
So if you were on the fence about going Universal, we hope this makes your decision easier. It's easier for you, easier for your users, and you potentially end up earning more in either case. We hope this helps you, your users, and the entire ecosystem. Let us know what you think!






Comments [2]