The good people over at AppCraver read my blog post about pricing and asked to do a short interview. They asked some great questions that further illuminate the challenges iPhone developers face. If you’d like to take a look you can find the whole article here.
Over at the Apple iPhone Group at Yahoo, a discussion has cropped up about application prices in the AppStore. We think (and hear) about this a lot, so I want to take a minute to talk about application pricing (on any mobile platform). It is a topic that is important to developers, retailers, and customers alike.
So, if you’re curious to hear a developer perspective on pricing, read on after the jump! AppStore Pricing: The Debate Rages On
The pricing of applications in the AppStore is a favorite topic of debate in online communities. Are the apps too cheap? Are they too expensive? What is the correct price point? Should there be a premium store? Typically, the debate falls out something like this:
High Prices = Good for Developer
Low Prices = Good for Customers
Unfortunately, nothing is that simple.
A Disclaimer We have mobile device applications for sale ranging from $29.95 to Free, and frankly we’re doing great. The AppStore is no exception. The iPhone and iPod touch have been great platforms for us. I say this because I don’t want what I say below to be taken as “He’s just bitter because he didn’t succeed.” We have succeeded, and we’re pretty dang happy with how things are going.
What I’ve written below comes from retailers, developers, customers, and the hard earned experience we’ve acquired over the past 12 years. There are always exceptions, but what I’ve written below is, on the whole, how things are in this industry.
$.99 Apps Make $500K!!!!!
Yep, and a kid playing guitar at his high school can become a rock star. These stories (like the Trism Tale) make fantastic press, but just like the music industry, professional sports, and Hollywood, those are the exceptions, not the rules. The majority of folks will never sell enough of their 99 cent app to even turn a profit, much less make it to the “big time.”
Unfortunately, people start to think that these big money makers are how the store works, since these stories make better news for Wired and better commercials for Apple. There are tons of amazing apps that never sell well because they just didn’t have that lucky combo of good app/good timing/lucky placement in an Apple ad/etc. etc. So, yes. Some applications get lucky, but for the rest of them, a 99 cent price tag will put them out of business.
Lower Prices = More Profit This just isn’t true. Lower prices typically DO mean more sales, but it doesn’t necessarily mean more profit. The math is pretty simple. You need to sell enough additional copies to make up for the lost revenue of the lower price. Sometimes this works - usually it doesn’t. Often you make less than you did before, even though you are making a lot more sales. And this cost is multiplied by the fact that more customers = more overhead (support/sales database work/etc.), so now you’re making the same amount of money and have twice as many customers! When the final tally comes in, you’ve actually lost money! There is always a sweet spot but finding it is tough. Just going cheaper isn’t the answer.
No Profit = No Updates AppStore bargain prices worry me. Although a low price might seem like the best deal, don’t expect to see your favorite cheap app get many updates as the years roll on. This is probably fine for small, casual games, but what about an information manager that you spend a lot of time entering data into? Do you want to switch software every year or two? What does an hour of re-entering data into an app cost you time wise? More than the 10 bucks to buy something more stable?
Here are some of the things you typically WON’T get if your favorite app can’t turn a strong enough profit:
- New versions to keep it working when the OS gets updated.
- New versions for new platforms when they come out
- Bug fixes after the first month or two
- New features
- A sequel to that game you love but have played 1000 times already
- Support
So again, cheap may SEEM cool - but it has a cost.
Free = Someone Else Pays Too often folks compare free apps with paid apps saying something like:
“If Facebook can make their cool app and give it away, why do you charge 99 cents for your game?”
Simple - someone ELSE pid for the FaceBook app for you. An advertiser or other investor provided Facebook with the revenue. That free app you got is simply a machine that helps them to generate more income from those peripheral sources. The advertiser bought you the app. That 99 cent game, however, has no such luxury. Unless the gamer developer can find someone else to buy the game for you (difficult to impossible if you aren’t as big as facebook), you have to shell out the cash directly.
Cheap App Support = Phone a Friend In general, cheap apps and truly free apps either don’t have support, or the developer gives up on support after a month or two. If you have a problem with the application it’s unheard of to have a phone number to call with live support and highly improbable that you’ll get a personal email response. Again, maybe this isn’t a problem for your favorite fart noise generator - but as soon as your application is doing something important to you, you NEED that person there to help if anything goes wrong.
AppStore Prices Are Dirt Cheap I’m always amazed by the comments like:
“You’re charging $1.99? Stop trying to rob me!”
Compared to any other platform (DS, PSP, Game Consoles, Desktop, BlackBerry, Windows Mobile) iPhone software prices are INSANELY cheap. Bargain basement cheap. Unable to support most developers cheap.
The reality is that Super Monkey Ball set the bar. At the time that it came out, SMB was the most amazing thing on the device - more levels, better graphics, better gameplay - and it was $9.99. If you wanted to charge more than $9.99 you had to look like your app was a LOT more complex than SMB. Never mind that SMB was made by a large company with the resources to support a lower price point - never mind that MANY applications priced at $9.99 and less can never make enough money to pay for themselves - this was the price and that is what we’ve been stuck with.
The end result is a market where customers expect REALLY low prices. Is that good? Bad? Only time will tell. But that’s the reality of this market.
Wrapping It All Up
I love cheap applications as much as the next guy. Seriously, I have a ton of freebies and 99 cent apps on my phone. I am, however, worried about the iPhone platform as a long term platform for software development. Windows Mobile has been great because over the past 12 years the prices have sustained ongoing development and innovation in the software market. Conscientious developers willing to work hard and support their customers are able to make a career in that market.
But is that true for iPhone? Can you put 6-12 months of development into an application and have any hope of a return for an iPhone application? And if not, isn’t that a terrible disservice to the customer? Will we be left with nothing but fart apps?
Yes, right now we still have a gold rush mentality. Everyone wants to make their fortune and they are willing to take risks to make it happen. The customer benefits from a huge list of apps. But what about two years from now? Or three? Here at Ilium Software we take the long view. We’ve been around for over a decade. We expect to be around for another 10+ years. Will the iPhone provide us with a market that will support the development, maintenance, and improvement of top quality applications over the long term?
Only time will tell. At this point, I think it could go either way.
Just a quick update on eWallet for Mac. Contrary to what I’ve seen posted in some of the blog comments, we are in fact making eWallet for Mac. As a matter of fact, we’ve ALWAYS planned to make eWallet for Mac at some point. This is something we’ve had in the works for a few years - pre-iPhone even. If you want to know more about eWallet for Mac, check out the rest of the post after the jump!
Disclaimer: In all of my posts I’ve always been very honest in what I tell you - brutally so at times. That won’t change here. Everything I’m writing in this blog post is a business side analysis. I AM IN NO WAY MAKING A JUDGEMENT ON THE QUALITY OF THE MAC OS. Frankly, it’s an incredible OS. This blog, however, is about the business of making software and not my personal feelings about the quality of an operating system.Mac and Me
Before I get too far into things I want to give you a little history about Mac and Me. Before I graduated from the University of Michigan I’d used two types of computers - Commodores and Macs (OK - I’ll admit, I played Civilization and Doom on Windows towards the end of college but that was it). I was a Mac guy through and through. I owned the top of the line PowerMac and LOVED it. Three things moved me away from Mac. 1st - I couldn’t get software, hardware, or anything else for it. :( 2nd - I used Windows for my work. 3rd - Price. After college I had no money. When the ol’ PowerMac died I moved on to a Windows machine.
And for those who don’t know, even our founders are “Mac People”. Just making clear that decisions about Mac are unrelated to how much we like the OS.
SO, ON TO THE PRESENT DAY….
Why a Mac Version of eWallet and Why Now?
As I mentioned above, we’ve always planned to release eWallet for Mac at some point. The problem was that for a long time the market didn’t support this. Just looking at desktop OS use alone and even today it comes out to something like this:
Making and maintaining Mac software is no easier than making and maintaining Windows software. At the same time, a Windows product has a potential market more than 10 times that of a Mac product. This is a HUGE difference. Simple math demands that we put our emphasis on Windows. 11+ years down the road that decision has proven a wise one.
But there is even more to it than that. We aren’t a desktop software company. Yes, our desktop software rocks, but our primary focus is Mobile Software. The desktop system used by most Mobile Device users has long been Windows. This further reduced the potential market for a Mac version, since people typically buy our desktop software to add-on to their Mobile experience - and these people used Windows.
So for a VERY long time, Mac just didn’t make good business sense based on our company focus.
Enter, the iPod (thought I was going to say iPhone didn’t you?) Suddenly, huge numbers of people were being introduced to the world of Mac devices. Apple got cool rather than fringe. Next came the iPhone! Now we had a full blown mobile device running Apple software.
So here are the factors that changed the market:
The iPod becomes THE music device. Apple is now everywhere.
The iPhone/Touch took the world by storm - and moved Mac into our area - Mobile Software
The internet becomes one of the most used “applications” cutting the importance of the OS
The latest Macs really CAN run Windows well, offering the “best of both worlds”
Suddenly, the Mac becomes a valid platform (financially) for us to invest in. I see the Mac market share continuing to grow over time, especially as young people who have grown up with white earbuds attached to their skulls go out and buy their first post-college computers. The name recognition alone will drive sales.
But There is a Catch! The Cold Hard Facts…
Look back at those market share numbers I posted. Even though Mac has been around for a long time, from our business perspective it is still an “emerging market.” Mac still commands less than 1/10th the market share that Windows does. No matter how much excitement surrounds the iPhone, we still have to remain realistic about what we will get back on our investment into Mac software.
I mention this due to blog comments saying “why aren’t you throwing everything you have at Mac?” Simple - we’d be completely abandoning the enormous market that pays our bills. Windows is WHY we have the opportunity to make a Mac version. Without Windows and Windows Mobile, we simply couldn’t afford to make a Mac version.
This means that when I sit down and mete out the limited resources available to me, I can’t drop everything to focus on Mac.
Now don’t get me wrong - when we do something, we do it right. Our Mac version is already INCREDIBLY cool. I’m totally geeked about it. And once it is out we plan to support it 100%. I just can’t afford to pull resources from the things that pay the bills to push Mac out faster.
Which Brings Us To the Big Question…When Will It Be Out?
My initial guess was by the end of the year. Now before I go on, I would like to clarify something.
Although it is possible I mispoke at some point (seriously, we aren’t in the business of trying to trick people or mislead them - it’s bad business and goes against our ethics), I always did my best to say “Our hope is that it will be out by the end of the year” and “We are shooting for the end of the year.” I did this because frankly, we don’t do “release dates” (See the other post for more about why release dates and software don’t mix.) As it stands right now, knowing what I know about how long it takes to get things done, I doubt it will be done by year end.
How long until it is ready? Sorry, but I’m not going to try to guess. Recently, my guesses have been interpreted as release dates so I’m going to have to stop doing that. I will say that we have a working version, the UI is coming along, and we actually have people outside Ilium Software using it right now.
Can you show us a screenshot? Nope, sorry. Trade secrets. Seriously, people like to copy our stuff so we seldom reveal it in advance.
So there you have it. We’re definitely going to release eWallet for Mac, but I’m not sure of the exact release date. You can be assured that as soon is it is ready, though, you’ll hear about it here!
There is a perception out there that iPhone users are Mac users. Now before I say more, let me make it clear right now that this is NOT a “Which OS is best?” article. From a business perspective, the quality of the OS doesn’t matter to me as much as how many users of a particular OS are out there, and whether they will buy our software. I PREFER a high-quality OS because of the cool stuff we can do with it, but in the end its about which OS will pay the bills.
O.K., Disclaimer complete!
I’m still looking for a solid study on this, but from everything I’ve seen so far (based largely on our own sales information) it just isn’t true that iPhone User = Mac User. I think part of the reason for this is that according to one estimate, the total number of Mac users in the world (adjusting for recent increases in market share) is around 22,750,000. This doesn’t adjust down for the number of these Macs that are sitting on desks in computer labs of schools. So the number is probably lower. We’ll go with it though.
The total number of iPhones expected to be sold by end of this year is at least 14,000,000. This doesn’t account for the fact that a lot of the 3G sales were 1st gen users replacing their old phones. Still, like the 22m number, we’ll go with it.
So, what is a reasonable estimate for the number of Mac users who are buying iPhones? 20%? I’m betting this is high, based on what I know about smartphone ownership in general, but let’s go with this as a conservative number. I say conservative because 20% is 2 to 3 times the marketshare (depending on the estimate you use) of Mac in the computing market. So with 20% adoption rate I’m suggesting that Mac users are 3X more likely to buy an iPhone than a Windows user.
So, even at 20% adoption rate among Mac owners, this means that only 4.5 million of the 14 million iPhone users have Macs. That means that twice as many iPhone users have PCs. Throw in the fact that we also have a VERY big Windows Mobile market, and you can see why Windows has to be our first priority. To put it simply, Windows iPhone users are (at the moment) still where the money is.
At the same time, we absolutely see the value of Mac as a platform for our products. (I just saw a new build of eWallet for Mac the other day and it’s really coming along.) The reality though is that Mac isn’t a “core” platform yet. It falls into the “emerging” category. Of course as you all know, we don’t ignore emerging markets. Where you go, we go. It’s just that most folks aren’t there yet.
I hope that this article will help folks who say “Seriously, dude. Why on Earth do you have an iPhone version but no Mac version?” to better understand the numbers behind our decision making process.
I know everyone is waiting with bated breath for the release of the sync component for iPhone. I’ve heard the grumbling and I don’t blame people for being impatient. And what I talk about here isn’t meant to make you feel happy or wash away frustrations. I just want to address these concerns, especially for folks new to dealing with Ilium Software, so you understand the way we do things.
I’m also writing this because when we first created this blog, we told you that we’d give you a little insight into what happens behind the scenes at Ilium Software. The things I talk about here really highlight the sort of decisions and challenges we face everyday. So if you’re interested, read on after the jump!
So let’s talk about releasing software. Here is my philosophy…
First and foremost, I will never release an application that isn’t ready. Period. If that means releasing it a week, two weeks, or even a month late, then that’s what I’ll do. I hate to do it. It screws things up here when we release past our deadline, it is frustrating for folks waiting for it, but quality is the number one most important issue when it comes to our software.
Of course that leads to the question of “then why did you release eWallet without sync?” I’ve actually addressed this a few times - same answer. While some folks can’t even use eWallet without sync, a lot of folks are perfectly happy with a device only solution. So, for those people, eWallet without sync was everything they needed and we could give that to them on day one. And the application we released is, in my opinion, the best in class. Sync for iPhone is a “new feature” and not a requirement for eWallet to be a fantastic product on its own.
Second, I hate giving release dates and generally I don’t. In fact up until this iPhone release, we have never given release dates for anything. And after this release I doubt you’ll see release dates given for other products. We’re not stopping because of this release, but for the same reason we never posted release dates in the past: software releases aren’t like building a car. You can’t predict exactly how long it will take to put all the parts together. Unforeseen problems come up. Glitches happen.
So why did we give a release date for this and the original release? Well for the initial release, we gave a date because Apple said “It will be out on this date!” Seemed safe to us. Ah well. Live and learn. And for the sync release, we wanted to assure our loyal customers that we really were going to release a sync component. We wanted to assure folks that sync wasn’t just a cool idea we had but something we were working on.
And boy, did we work on it. As I’ve said before, not only did we work on this thing constantly, putting in many extra hours to get it done, we even brought in contractors. We take our promises very seriously. Did we get it out to customers by the end of August as we’d predicted? Sadly we didn’t. I’m really sorry about that and it frustrates me. At the same time, the entire project was complete by August 27th and considering the challenges we faced along the way (we killed three computers during development - we must have overworked them!) I’m really pleased at the speed with which the team here got the work done. (My thanks to all of them!)
Third, whatever we do should treat the customer right. We gave out a LOT of free desktop software to thank folks for buying early (just ask Kevin, Lee, and Don who had to fulfil all of those requests!) We effectively halved our potential revenue as a way to show our customers that they always come first. Did we take a major hit? Absolutely. Do we think it was worth it? Without a doubt. This is how we’ve done business since day one and I like to think that this is part of the reason we’re still here 11+ years later. Now for some folks, it isn’t enough. I understand and respect that, but at least I know we did all that we could to help out the folks who supported us.
I’ll close by saying I don’t blame folks for being frustrated. I know this software is important to a lot of people. I also know that for some folks, sync makes the difference between eWallet being useful or memory filler on their phone. I also want to make clear that I don’t blame Apple. After the initial release we knew just what to expect from Apple. So does that mean it’s our fault? You bet. In fact as Product Manager I take full responsibility for a late release.
But at the same time, while I’m sorry for the wait, I wouldn’t have done it any different. The end result is a fantastic product we’re all very proud of, and one that we really believe is going to make folks lives easier. Releasing the stand alone version first made a lot of people really happy. Releasing the sync component a little bit late means we’re releasing the best software we could build that will work properly the first time you use it.
In the end, folks that purchase eWallet will have the best product in its class, that works every time they use it, with the best support in the industry to back it up.
Let me start by saying I think it’s great that Mike at Mobile Jaw and Chris from GearDiary are doing this. It’s a neat idea and I’m looking forward to the results. At the same time, while I think this idea is interesting, it also has some inherent flaws. Again, I’m not saying their idea is a bad one or that the results won’t be interesting. I just feel that since our app is one of the ones being used in the experiment, and could thus be blamed if the device still crashes, that I need to say a thing or two about this idea.
So if you want to hear my take on device stability and the “No Reboot Challenge”, read on!
So the theory goes something like this:
Instability in the operating system is not a result of bad design by the OS manufacturer but rather a result of badly designed third party applications.
The goal, as I understand it, is to prove that MS gets way too much grief over the instability of its operating systems (mobile and otherwise.) I think this is true and I think proving this is a laudible goal. Unfortunately, I’m not sure that the methodolgy of the Challenge is sound. Not only might it fail to prove the point, but (and this is what worries me) it could wrongfully implicate a developer in the process.
That said, here are the potential problems that I see. I resisted going into specifics (*cough* WM memory management *cough*) because frankly, a lot of this applies to any OS, not just MS products.
Impossible to Prove Unfortunately, it will be impossible to pinpoint the source of instability, even with very few applications installed. A flaw in the OS might only rear its ugly head when an application is installed, not due to any failure on the part of the developer. It could be that the flaw remains hidden until an app is run.
It’s like building a bridge and watching it collapse when the first car goes across. Do you blame the car or its driver for driving across the bridge improperly? I mean, the bridge was working fine until the first car drove over it so it must be the car’s fault, right?
It Isn’t Easy to Screw Up the OS Some will surely disagree, but in my experience it isn’t easy to botch up an operating system accidentally. You’ve got to work really hard to mess up your software so much that the entire OS suffers. Crash your own application? Sure. But screwing up the whole OS is something else entirely.
And let’s be frank about this. The times I’ve seen our applications cause what appeared to be a wide-spread issue (and these were VERY rare and never made it out the door), in the end we discovered that some aspect of the OS was not working as advertised. Perhaps it was a custom method the device had for handling images that failed, an out-dated library, or a missing piece the hardware manufacturer didn’t think was important and cut. In the end, we wrote work arounds to avoid problems with the OS. Had we released the software without addressing this, to anyone on the outside it might have looked like “we broke the OS”, but that simply wasn’t the case.
Failure to Lock-Up the Dogs
But let’s say that some application really IS screwing up the OS. Shouldn’t there be some sort of “police officer” built in to protect the user from this sort of thing? Isn’t it the responsibility of the OS manufacturer to provide customers with a stable user experience? If they are giving applications access to portions of the OS that can cause the entire system to perform badly, is that really the sign of a good OS? I’m all for freedom and flexibility for developers, but someone has to be the boss and say “You can ride in the car but you can’t drive it!”
So there you have it folks……my take on the No Reboot Challenge. It’s a cool idea and I hope something cool comes of it, but I’m very concerned about the conclusions folks may come to if things go south.