I keep needing to find this out, so I thought I’d post it here so I can refer to it. This is the geometry of the UILabels for each of the UITableViewCellStyles:
UITableViewCellStyleValue2
textLabel: 10.000000 : 14.000000 : 68.000000 : 16.000000
detailTextLabel: 83.000000 : 12.000000 : 207.000000 : 0.000000
I thought I’d post the latest stats I have for my sales of Subnet Calc:
Notice that there is a distinct jump towards the present. This was when I switched category from Utilities to Business. I thought it was quite surprising that it made such a difference just changing category, but it seems to have made a fair difference.
I had the need to code sign using a different developer accounts and my initial thoughts were that it was going to be tricky. But it seems that Apple have actually made it easy now!
The problem comes that during code-sign, it searches for certificates by the name, which leads to “iPhone Developer: Matthew Galloway” matching both certificates you have installed (one for each developer account). But Apple have at some point changed their certificate signing process and they add a number of the end of the common name on the certificate. This means that each certificate is unique even if it’s for the same physical developer.
One thing to note is that I used the same private key to generate the CSR for both certificates. I’m not sure what the implications would be for using separate private keys, but I can’t imagine it would make a difference.
I guess Apple had to do this really because lots of companies would have ended up with problems I’m sure.
So for anyone wondering if they can use multiple developer certificates, then just go for it, it should work!
I estimate I am between 2 and 4 days from reaching my next monetary target which I set myself for my apps. To mark this occasion I have decided to do something which Malcolm Barclay talked about at the last iPhone and Smartphone Publishers and Developers meet up. It’s nothing too exciting, just I want to give it a try!
In other news I currently have 5, yes FIVE, apps in review with Apple. I’ve been quite busy over the past couple of weeks as I’ve been between jobs. I’ve released updates to 4 apps (another update to Subnet Calc Pro off the back of comments from users) and 1 completely new app which will be interesting for anyone out there who uses a Zen Internet broadband connection!
I’m continually impressed by Apple’s ability to keep the iPhone platform going so strong. It would be interesting to try doing it full time, but I don’t want to take that risk at the moment as I can’t guarantee I’d have enough money coming in and I actually am very much looking forward to starting my new job on Monday!
UPDATE:
Well I reached it! And I have now almost reached my next target! I also have released the app for Zen broadband customers, it’s called ZeBbUs (Zen Broadband Usage) and it lets you know how much of your Zen broadband plan you have used this month.
I am having a strange issue with UIImagePickerController which is really bugging me. I’ve also found someone else with the same problem so I know it’s not just me!
When using UIImagePickerController, and the imagePickerController:didFinishPickingImage:editingInfo: delegate method gets called, I find that sometimes the returned image is nil, which depending on what you do with the image will cause a crash or at least not do what you expected. It seems to be a memory issue because when you reboot the iPhone and try again, it works and returns the image correctly. Also, I’ve not have the problem on iPhone 3G S which has more RAM, indicating again to a memory issue.
I’m wondering it the new imagePickerController:didFinishPickingMediaWithInfo: delegate method will work – as the other has been deprecated in 3.0 anyway.
But has anyone else had, and fixed, this problem?
I have a theory about Twitter and the iPhone in that once Apple’s push service is released (presumably with 3.0) it will pave the way for things like a Twitter client which informs you of new tweets in much the same way that the iPhone itself does with SMS messages. Therefore I can see the future being that iPhone users will increase their tweeting even more, thus not having to use SMS which has 2 advantages. One is that Twitter is free, and two is that if you happen to be on your PC rather than have your phone in front of you then you can receive messages or send messages using your favourite desktop Twitter client.
The problem comes of course that you still have to have polling in there somewhere because Twitter don’t have a push notification themselves, but perhaps Twitter will try to cash in and create their own iPhone app and add Apple’s push service to their own backend service.
Who knows…
This weekend has been surprising for me. Firstly, it has seen the start of some contract iPhone application work which I managed to pick up. Secondly, I have been contacted about joining with a couple of people to start looking into the market potential for mobile applications. And thirdly, I have been contacted asking if I’d like to apply for a job developing mobile applications.
All of these points have made me realise just how big the market is for mobile applications, and just how much of a growth area it is likely to be over the coming months / years. It’s very exciting and I am looking forward to being part of such an exciting industry. I’ll try to keep blogging about things I find out and hopefully others can learn from my thoughts or just enjoy reading what I am finding out.
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.
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.
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?
I started using the lovely json-framework for the iPhone but then suddenly found that if I compiled for anything greater than 2.1 for a device, that it would pop up with:
Codesign error: “object file format invalid or unsuitable”
It took me a long time to figure out what was going on, but thanks to a blog post, the fix is this:
On the project settings, on the build tab, search for “Code Signing Resource Rules Path” and set “$(SDKROOT)/ResourceRules.plist” as its value.
I’m not sure how it works as it looks like that is the path it already has, but hey, it seems to work!