Small app, sales still strong

May 17th, 2009

When I released Subnet Calc Pro, I worked out how many hours work I did on it and therefore how much money I would like to get back from it. Then I decided a price based upon how many sales I thought that I would get. I managed to achieve my money goal after just under 3 months of selling which I thought was extremely quick as I had imagined it would take more like a year to do that!

That is one thing that shocked me, but the other thing which shocked me is that my sales have been steady throughout the whole time I have been selling Subnet Calc Pro, with no sign of stopping yet. There was a spike around the time I released an update to Subnet Calc (the free version) which now has an up-sell page on it to encourage users to upgrade to the paid version. If there is a trend at all with my sales then it’s an increasing trend as well, which I am obviously very pleased with!

Here is the graph of my sales from 1st February 2009 until today, 16th May 2009.

Subnet Calc Pro Sales

The bottom line is that this has proved to me, and I hope others who read this, that the iPhone platform is a great platform to work with because you can go from never written a line of Objective-C to a full paid application, earning £££/$$$ a month. OK my app won’t support me fully, but it certainly is some very handy pocket money which will enable me to continue in my iPhone efforts and hopefully produce even more apps.

Posted in Business, Subnet Calc Pro, iPhone Apps | No Comments »

2.x apps on 3.0

May 5th, 2009

Since the release of the first beta of the 3.0 SDK I’ve been checking if apps built for 2.x can run on it. Clearly this is something which Apple really should do, but a hint in the latest (beta4) release notes says this:

FIXED: Previously, the compiler incorrectly allowed synthesis of ivars belonging to a superclass. This caused crashes or other undefined behavior when the size of the superclass changed (such as running an application compiled against an older OS on iPhone OS 3.0.) The fixed compiler now generates an error when it encounters this condition. If you have shipped an application to customers, Apple recommends compiling against the 3.0 SDK and updating your existing application if the problem exists.

Now, does that mean that you’re going to have to release an update for apps which exhibit this problem for people on 3.0 to be able to use the app? Surely that cuts out people who upgrade, and if you update your app then it cuts out people who don’t upgrade? Lose-lost situation?

Posted in iPhone SDK | No Comments »