• When an array has more than 1 entry, it is serialized correctly
• When the array has only 1 entry, it is serialized not as an array, but as a single dictionary.

Firstly, lets explain why this has occurred
If you consider the following XML:

<team>
    <employee>
      <name>Joe</name>
      <surname>Bloggs</surname>
  </employee>
  <employee>
    <name>Jane</name>
    <surname>Doe</surname>
  </employee>
</team>

A typical XML to JSON converter will convert this as follows:

{
  team:{
    employee:[
      {
        name:'Joe',
        surname:'Bloggs'
      },
      {
        name:'Jane',
        surname:'Doe'
      }
    ]
  }
}

I.e It is converted to a Dictionary, with a key called ‘team’ whose value is a Dictionary, with a key called ‘employee’ which is an array of Dictionaries (with keys of ‘name’ and ‘surname’).

Great.
However if the XML was a team with a single entry:

<team>
    <employee>
      <name>Joe</name>
      <surname>Bloggs</surname>
  </employee>
</team>

The XML to JSON converter has no context on Employee. It has now way of knowing that this is potentially a repeating group (especially if it has no XSD to consult), so it converts the XML to the following JSON:

{
  team:{
    employee:{
      name:'Joe',
      surname:'Bloggs'
    }
  }
}

So, this is now a Dictionary, with a key called ‘team’ whose value is a dictionary with a key called ‘employee’ whose value is a Dictionary.

The problem here is when we go to parse, we expect the value of ‘employee’ to be an array (which it isn’t), and this can lead to problems in the code.

And..due to Objective-C loose approach to type, the following code will run:

NSArray *array = [teamDict objectForKey:@"employee"];


In those cases where there team has a number of employees, the above code works fine, and the pointer, array stores an array. In those cases where a team as a single employee, the above code runs, however the pointer, array will actually point to a NSDictionary. So the following code (for example)

int numEntries = [array count];

Will sometimes work, and sometimes lead to a runtime error, which on iPhone will manifest itself as a crash.

So how do we fix this?
Well, if you have control over the server side, the simple question is to fix it in the first place. Note: This is a common problem with JAXB, a popular java XML binding mechanism often used in REST services written in Java. We’ve come across some examples on how to work around it here and here.

If you have no control over this, you may be able to handle this in your Objective-C code. Here’s some sample code we’ve started to use; It checks the data type at runtime, and if necessary, converts it to a single element array

+(NSArray *) getArrayFromJSONDictionary:(NSDictionary *)parent
               forKey:(NSString *)key {
  id obj = [parent objectForKey:key];
  if([obj isKindOfClass:[NSArray class]]) {
    return obj;
  }
  if([obj isEqual:[NSNull null]]) {
    NSLog(@"Warning: object for key %@ is null", key);
    // Return an empty array
    return [[[NSArray alloc] init] autorelease];
  }
  NSLog(@"Warning object for key %@ is of type %@",
        key, [[obj class] description]);
  NSArray *ret = [NSArray arrayWithObject:obj];
  return ret;
}

1. iOS Running on iPhone, iPod Touch, iPad and most likely AppleTV
2. Android, running on handsets from Samsung, HTC, Sony Ericsson, Motorola (and many others), and a plethora of Tablets
3. Windows Phone 7 – Running on handsets from Nokia, Samsung, LG, Dell and many others

If you’re a brand manager, and you are considering a mobile strategy, you probably want to ensure that your mobile strategy has the widest reach possible, so will probably want your apps on all of the above. This is possible, but costly.

Allow me to get technical for a moment. iOS is developed in Objective-C, using a Mac, with Tools supplied by Apple. Android is based on a Java Eco System, and Windows Phone 7 is based on a .NET ecosystem.

This may be gobbedlygook to you, but what this means is they are very different, and very little crossover occurs. An app written for iPhone essentially needs to be re-written (at similar levels of effort an cost) for Android, and again for Windows Phone 7.

And at this point we usually get asked a fairly obvious and sensible question

Isn’t there some sort of tool that can publish on multiple platforms?

Here’s the definitive answer to this:

NO. There isn’t

But, this needs elaboration. There are plenty of toolkits out there that claim to offer this. Be careful. If you want to use these you can but the results always end up the same.

I’m cynical about these toolkits for very good reason. This is pretty much the third time around for this kind of thing for me. In the early 90′s there were a slew of toolkits that offered compatibility across X/Windows, Microsoft Windows and Mac OS. In the early 2000s the Eclipse people gave us SWT the “Standard Widget Toolkit”, and in fact, there a few others such as QT or wxWindows I can name.

The one thing that always stood out when they were used was

You could spot them a mile off

Applications written using SWT looked like an SWT application, not a Windows application when running on Windows, and a Mac Application when running on Mac.

These cross platform toolkits always ignored one thing

When you attempt to provide something that runs on many platforms, the best you can hope for is “least common denominator”

So the end result? Consistency – Yes. But consistently bad.
Applications written using cross platform toolkits work consistently bad on all platforms. So you end up with a rubbish application on Windows, rubbish application on X/Windows and, you guessed it, a rubbish application on Mac (or.. a rubbish application on iOS, Android and WP7)

I think this can only get worse on Mobile. The devices are so specific, with a broad range of capabilities. Trying to cross them is just folly. In addition to this, the “good taste” barrier has leapt upwards since the introduction of the iPhone. Imagine giving an “android 2.0″ experience in an iPhone app, or attempting the “iPhone experience” on Android – Neither user will thank you.

And let me get back to the Brands. If you’re a brand manager, your job is to enhance the brand. If you put out something which gives a poor experience on any mobile device you’ve done worse than not releasing – you’ve in fact tarnished the brand. Now if you do that across many mobile platforms, the damage will be multiplied.

So do yourself a favour; If you want quality, and a native experience for your end users there’s only one way to go. Get it developed natively, and avoid the short term savings a cross platform toolkit claims to get you.

You’re reading the tapadoo blog. Did you know that as well as publishing our own applications, we offer iPhone development services and consultancy? If you have an idea, project or something you think we can help you with, please get in touch through our contact page.

There’s the option of using Three20 to get good looking buttons. Its an option, but frankly, it feels a bit like using a sledgehammer to crack a nut. You end up with a large addition to your code, just for nice buttons. OK, you could go to the trouble of stripping out what you don’t need, but that again is more work.

All iPhone developers know about UIGlassButton – Its an undocumented API for making nice looking buttons, that exists only on the simulator and not on the iPhone itself. Why couldn’t we just have that for iPhone OS? I dunno, but its not there.

At some point in the past, I came across a nice snippet of code that used undocumented techniques for creating a glass button, and then saving the image to disk. This could then be used as a background to a “custom button”, producing the nice glass buttons I’ve been looking for. I think it was schwa on twitter; Nice. Full credit where it’s due.

So, building upon this, I’ve thrown together a simple single-screen app for creating the images for glass buttons using that technique. Basically, it allows you set the RGB values, and the size. Hitting “Save” writes the pngs to the application’s documents directory.
Now, you’ll have two png files, which you can use as images in custom buttons. Hey presto. Very simple UIGlassButtons.
Here’s a screen shot:

Our very simple button maker

Full source is available on github. Comments welcome.

You’re reading the tapadoo blog. Did you know that as well as publishing our own applications, we offer iPhone development services and consultancy? If you have an idea, project or something you think we can help you with, please get in touch through our contact page.

That project is Firepit.

What is Firepit?
Firepit is

1. A web based framework
2. For bands going on tour…
3. ..which allows them to produce iPhone applications..
4. ..that are “virtual tour programmes”

We just got out the first Firepit release today: The App is “Ultravox – Return to Eden II“, and it is on release on the app store worldwide.

We’re delighted that Ultravox are on board. They’ve been an avid supporter of the project for some weeks, getting behind the idea, and supplying some great exclusive content. A quick look over Midge Ure’s Twitter stream shows he’s being doing some beta testing, and bigging up the app.

Hope y’all like it.

Ehhhhh. No.

There will be an iPhone killer. But it’s not going be today tomorrow. The iPhone is just far too advanced of any competition.

Why? Apple have one thing in spades that no other computer or handset manufacturer has: Taste.

This seems to be lost on most non-iPhone owners. The arguments for the competition are usually about specifications. That’s just silly. Most people don’t know megabytes from kilohertz so don’t give a monkeys about specifications.
I’ve often listened to arguments about x device having a faster processor, or doing background processing. But these people never ever do what almost every new iPhone owner does : tell me how much they love their phones.
Try it: borrow a buddies iPhone and play with it. 2 things will happen : you’ll say “yeah…it is lovely” and your buddy will start to twitch; we don’t like letting our iPhones out of our reach for too long.
You don’t get that reaction from a new Sony Ericsson, Nokia, Samsung or Android for that matter. In fact the most common utterance I hear from nokia owners are

“look I just want to make calls and send texts”

not

“I love this phone”

Every time I try out a new other vendors phone I usually finding myself not liking it. sometimes the annoyances are subtle like just slighlty too slow to respond or jerky scrolling. That just tells me that someone in the company, high up, with the final say said

“it’s good enough.”

That’s understandable; getting the last 5% so that something goes from “good enough” to “perfect” may well take ages or cost the earth.
But thankfully, Apple don’t do “good enough”. They take the “it’s gotta be perfect” approach as a matter of course. And for that…we have the iPhone

So when’s that iPhone killer coming?
Consider this: for a few years, every new mp3 player was being dubbed an “iPod killer”. It hasn’t happened yet and nobody even writes about iPod killers anymore.

So far the only iPhone killers have been, well…newer iPhones.

It won’t last forever; it never does. Walkmans were toppled; iPhones will be, but it will take new technology that I can’t imagine right now. iPhone could easily dominate for a decade……

We are engaging with a number of potential partners with a view to a long term solution and hope to be able to announce something shortly.

Apologies for the inconvenience caused.

Balsamiq

Balsamiq mockups from Balsamiq Studios plain and simple rocks. What is it? It is a very rapid prototyping tools for UI and User Experiences.
They’ve added specific iPhone stencils into the product so you can create mockups really, really quickly.
Why do I like it? Lots of reasons:

1. Its runs everywhere. Its an Adobe Air application, which though is not native to Mac, it runs nicely on the desktop. But, they’ve also got an edition that runs in a web page, so you can deploy it on your wiki, or any other collaborative web server you may use. They’ve even got a hosted edition which you can play with for free (go here, have a play)
2. Doing up stuff is fast. It is genuinely as quick as using a pen and paper. Just last week I was working on a proposal; the client had given me his ideas, and I already formed my opinion on how it would look. I mailed him back my response as a bulleted point list (It was a small project!). He wasn’t convinced. So…I spent a bit longer, and did up a couple of pages of a proposal. I used mockups to illustrate my ideas. Without spending too much time, I had gone from a boring e-mail response, to a professional, well thought out one, which immediately struck a chord with the client.
3. It is focused on function rather than detail. I really like this. It produces mockups that look like they are hand drawn. It avoids details like colour, animation etc. This means when working with the client we can focus on what the app does ( not “Shouldn’t that button be bluer?”). We get across high level ideas, get them across well, and by being low on a lot of details, it means we can get more feedback with the client. I love the phrase Balsamiq use themselves:
   

   A low fidelity look which encourages hones feedback. We call it “a look no-one is afraid to criticize”

4. They have an agile approach to their product; They update their application on a regular basis, based on feedback taken through GetSatisfaction

Enough of my rambling; Here’s a mockup.



iPhone Application Sketch Book

Next is…an actual sketch book. Its available on amazon, but you can find details about it on www.mobilesketchbook.com. I think this is a great one for grabbing ideas, or scribbling down initial design thoughts.
I like this because it is a low-tech answer; Each page is lined graph paper, with a full-size image of on iPhone on it. The screen area is blank, so you can draw on it to capture your app ideas.

You can have this in your laptop bag, and use it when an idea comes to you. (when travelling, for example).

Having this along at a client meeting is great. It shows the client that you are doing this often, and you are serious about capturing the ideas

I know there’s others out there, based around Powerpoint or Keynote, but frankly, these two are my favourites right now.

If you’ve other tips, please leave a comment with your favourite tools for iPhone design and development.

---

You’re reading the tapadoo blog. Did you know that as well as publishing our own applications, we offer iPhone development services and consultancy? If you have an idea, project or something you think we can help you with, please get in touch through our contact page.

]]> http://tapadoo.com/2009/two-tools-if-youre-developing-iphone-apps-for-clients/feed/ 1 http://tapadoo.com/2009/a-simple-credits-screen-with-core-animation/ http://tapadoo.com/2009/a-simple-credits-screen-with-core-animation/#comments Thu, 01 Oct 2009 19:10:16 +0000 dermdaly http://www.tapadoo.com/?p=243 Whilst working on my latest iPhone project (not yet announced), I wanted to do up a useful credits screen. This project had more than just myself involved and I wanted to ensure everyone got a mention.

I was also conscious of the exposure my apps were getting through apps.ie, so wanted to do something that would link back too. So..I’ve put together a simple credits screen which uses Core Animation to show the individual credits. This post explains the code, and how it works. There’s a gotcha or two in there as well.

How does it look?
Before I start, here’s a quick preview.



Data Structure
For the purposes of a credit, I wanted to be able to store

• The person’s name
• What they did
• Their twitter id
• The web site
• An avatar

That’s easy – I wrote a class called AppCredit, which is a pure data structure. It doesn’t do anything beyond store the above details.

The View On The Data
So, how would I visualise the data structure ? I had an idea of how this should look, so I created a CreditsView (in fact a view controller XIB), which layed out the information in a way that I thought looked nice:





I wanted the twitter name and the web address to be tappable, to take you away to the relevant website. To achieve this, I overlayed the labels with custom buttons (essentially invisible buttons). I wired up their touchDown (so we can highlight), and their touchUpInside so we can actually open the relevant URL. We also followed good UI principals, in that we have an alert box pop up to warn that the user is about to leave the application. All of this is handled in the class CreditsView, along with the relevant nib file CreditView.xib

So where’s the animation?
Well, I wanted that the entire view just described would fade in and out repeatedly, for each of the credits, so I wanted them showing as part of a larger container. This is the CreditsViewController.
The CreditsViewController is the UIViewController for the overall credits page. It consists of

1. A large label to show your application name
2. An area for the animated credits
3. A scroll area to store a brief description of your application
4. A “bottom third” with a description of apps.ie, along with another “invisible button” to take you there

In addition, in the sample code, I added a toolbar, with a “Done” button to be able to dismiss the credits screen. For the purposes of this example, I worked of XCode’s standard “Utility application” template, and replaced the flipside view with my CreditsViewController. This meant adding some way to dismiss the credits view (In my actual app, it shows on a separate tab, so does not need a dismiss capability). The Done button is wired up the sample as the XCode sample, and should be obvious.

Supplying the data for the credits view
I adopted a delegate approach to this. So theres a CreditsViewDelegate protocol, which we assign to the CreditsViewController. Once you implement this, and assign it to your CreditsViewController.delegate, it will ask the delegate for the necessary data as it needs it.

The actual animation
The actual animation is quite simple. In a nutshell, it animates the first credit, when this is complete it animates the next one…and so on. When all have been animated, it just starts again. Here’s the detail

1. When the CreditsViewController is loaded, it also loads up a CreditsView from the nib file
2. As it is about to appear, it asks its delegate for the necessary data, and fills in the labels
3. Once it has appeared, it starts to animate the CreditsView. It does this using the following code

-(void) animateNextCredit
{
  // Use animation to fade it in
  CABasicAnimation *animation =
      [CABasicAnimation animationWithKeyPath:@"opacity"];
  animation.fromValue = [NSNumber numberWithFloat:0];
  animation.toValue = [NSNumber numberWithFloat:1];
  animation.repeatCount = 0;
  animation.duration = 2;
  animation.autoreverses = YES;
  animation.delegate = self;
  // Ok...Start showing our credits
  [self getCredits];
  if(credits != nil) {
    AppCredit *credit = [credits objectAtIndex:currentCredit];
    [creditsView setAppCredit:credit];
    [self.view addSubview:creditsView.view];
  }
  currentCredit++;
  if(currentCredit == [credits count]) {
    currentCredit = 0;
  }
  [creditsView.view.layer
       addAnimation:animation forKey:@"credits"];
}

Basically all that is happening here is we are telling the CreditsView (i.e. the small pane) to vary its opacity from 0 to 1 and back again, over 2 seconds. We set up self as the delegate to the animation, which means a method called animationDidStart will get called when we start, and animationDidStop when the animation completes. So..when animationDidStop gets called, we know we can move on to the next animation:

- (void)animationDidStop:(CAAnimation *)theAnimation
       finished:(BOOL)flag
{
  creditsView.view.layer.opacity = 0;
  if(flag) {
    // This means that animation ran to completion.
    //  I.e. Was not interrupted
    // e.g. by removeAllAnimations
    // Cool - time to start another
    [self animateNextCredit];
  }
}

Gotchas
There were a few problems I encountered when writing this code. Firstly, when the animation completed, there was an annoying flicker just before the second one started. This was caused because I had set the opacity to 1 in the CreditsView – Once the animation completed, the CreditsView was refreshed briefly back to full opacity. The fix was to set the opacity to 0. Once complete (i.e. faded out), if it were shown, it would be shown with full opacity, and therefore invisible.
However, this led to a second problem. With the opacity set to 0, the CreditsView was essentially hidden, and so did not respond to taps. I couldn’t jump off to my twitter url, etc. I could see my view (because it was being animated from 0 to 1, but I could not interact with it).

This is caused by the fact that the actual state of the view and the displaying of it are independent; I could see it animating, but its opacity value was actually 0. When its opacity is 0 it is considered hidden, and therefore won’t respond to user input.
To get around this, I experimented with very low values of opacity which would still respond to input, and found this to be around 0.02. So putting both of the above together: In animationDidStart, I set the opacity to 0.02. In animationDidEnd, I set the opacity to 0 (to avoid flicker). This all seems to work well.
The next issue I found was another part of my app was slow after I ran my credits screen. I guessed that the animations were never cancelled. This was easy to fix, In my viewWillDisappear method, I just had to cancel my animations:

[creditsView.view.layer removeAllAnimations];

Note however that this will result in your animationDidStop method being called (which was where we started the next one, right?). But we can tell if we completed or were interrupted by the second parameter sent to animationDidStop, so this was easy to ensure we didn’t re-start. That’s what the if(flag) bit above is all about.

Improvements
So how could I improve the code? There’s a couple of obvious points:

1. In the credits view, I could extend UILabels and make them respond to input. This would negate the need for invisible UIButtons. Thanks to @stroughtonsmith for that one. (Oh and for helping me with other gotchas).
2. I’ve done no internationalisation. Again, should be straightforward

So that’s it. You can get the code It looks better than the video on the simulator, and better still on the iPhone or iPod touch.

The code also uses a technique for doing a gradient background, as outlined by Matt Gallagher in his excellent “Cocoa With Love” blog. There’s two source files from that blog post in the code, unchanged.

If you’re an Irish Developer, you may consider using this as a basis for your upcoming projects, so it will link back to apps.ie. If you’ve come from elsewhere, welcome!

Feel free to use this code as you wish. If you’ve any comments, questions, or improvements, I’m happy to hear about them. Use the comment section below to leave feedback.

---

You’re reading the tapadoo blog. Did you know that as well as publishing our own applications, we offer iPhone development services and consultancy? If you have an idea, project or something you think we can help you with, please get in touch through our contact page.

]]> http://tapadoo.com/2009/a-simple-credits-screen-with-core-animation/feed/ 3 http://tapadoo.com/2009/the-problem-with-revenue-share/ http://tapadoo.com/2009/the-problem-with-revenue-share/#comments Fri, 21 Aug 2009 18:06:00 +0000 dermdaly http://www.tapadoo.com/?p=194 As an iPhone developer for hire, I get regular approaches from people with ideas that they would like to turn into realities. I sign non-disclosure agreements and then get brought into their confidence to explain their idea.

Some turn out to be better than others. Those with a broad appeal may become successes; those with a niche appeal will most likely not make much money; they possibly won’t turn a profit, but one man’s great idea, doesn’t appeal to another so generally I try to not make an early judgement call.

At some point in the conversation we get around to ballpark figures. This is usually when I explain why we will need to go into more detail. In fact, I typically cite my own blog post about pricing. The potential client usually sees the benefit in what I am suggesting, but 9 times out of 10, they will still want ballpark pricing. I understand this. They really want to know if I think their projects is a €500 project, a €10,000 project or a €250,000 project; They are basically asking for scale and if their budget will work.

In many cases, the potential client starts to talk about doing the project on a revenue share. The logic goes like this:

1. They’ve put time into developing their idea; its a good one, and it is going to sell like hot cakes
2. All that needs to be done is to knock the code together, get it on the app store, and await for the money to start rolling in


Picture Credit: Flickr User amagill


There’s a big problem with this approach. It ignores one large part of the problem.

Risk

If we work together on your idea, I’ve to put a great deal of effort into the software development. Software development is complex, detailed and a good programmer has very real talent, which has taken many years to hone. (I’ve never met a great programmer who wasn’t already at it from around 12 years old). Experienced programmers know that the devil is in the detail

So lets look at the proposition from another perspective. When did your idea come to you? While lying awake trying to go asleep? Perhaps you sat at home, with a pen and paper over many nights, scribbling ideas, honing them, refining them…
or

perhaps it came to you while you were sitting at your desk in work…getting paid.

And when am I going to do the work? Well, during my working day..when other customer’s should be paying me, so aren’t, because I am working on your idea, but that’s ok, because its gonna sell like….well..I’ve already explained that.

So..Imagine all goes well…and the sales do well…From day 1 we’re splitting the spoils, and this has really paid off. The customer who was going to pay me has gone to a competitor, but hey…I’m doing ok out of “very cool idea 1.0″. Version 2.0 will probably make even more anyway.

Or

It hasn’t sold well…I’m behind on my mortgage…The customer who was going to pay me has gone to a competitor..and he’s not coming back.

How are things with you?…..Oh…this was actually just a side project…so all is well; you’re still in your day job. Hey…nothing ventured, nothing gained right?

Ehhh…..

A good idea is valuable. If there’s real evidence of work being done to develop or prove the idea, that mitigates the risk. If you’ve crunched the numbers, even better. (If its that good, you’d be crazy to be giving chunks of the revenue away).

Tell you what. I’ve another model. Lets use some hypothethical figures. We’ve knocked around your idea. Its going to cost €10k to develop, and you’re interested in a revenue share. Now…lets consider the risk element.

Here’s a deal: I’m taking all the risk, and I see the value of your idea. So how about I do it for €5k, and there’s some compensation for the risk. There’s two things we can do. How about the first €10k it makes goes 100% to me, and after that we go 50/50 ? Or…How about we reflect the risk in the revenue share from day 1. So…Your investment is only €5k, but the revenue split is 70% to the developer, 30% to you.

Still interested?



Pic Credit: flickr user texaseagle

Hey…..where’d ya go?

]]> http://tapadoo.com/2009/the-problem-with-revenue-share/feed/ 16 http://tapadoo.com/2009/some-things-to-expect-after-your-app-gets-launched/ http://tapadoo.com/2009/some-things-to-expect-after-your-app-gets-launched/#comments Fri, 29 May 2009 09:41:11 +0000 dermdaly http://www.tapadoo.com/?p=157 OK. So you’ve made it through the ADC signup process. You’ve managed to get an itunesconnect account. You’ve even managed to get some contracts into place, submitted and had your app approved, and now it is on sale!

Well done. This post is to give you some ideas about things to expect from release onwards. I went through all of these questions, and either helpful xcakers, or patience got me the answers. Hopefully, you’ll read this, and be able to relax.

Question 1: Where is my app ? I can’t see it.
When you app goes on sale, it will be available on itunes via the direct link. So firstly, lets see if it is available on its own link. You can find this in itunesconnect. When your app is ready for sale, itunes connect has a little arrow link next to the icon.

This is the direct itunes link. Click on this, and itunes should open up on your apps page. Phew!

Question 2 – But are some of my users complaining that they can’t follow the link?
The itunesconnect link you copied for your landing page may have begun itms:// If you installed itunes after your browser, it will have installed a protocol handler such that the browser knows to launch itunes. If however the browser was installed after itunes, it is not going to know how to open itunes links. Actually, the fix is simple: Change the url scheme from itms:// to http:// – the link should work everywhere now.

Question 3: Great – But how are people going to find it?
Relax. You app will be indexed and searchable soon. It takes a few hours after going on sale, but it will be searchable based on the description you have given it. This means you may need to think about the words you use in your description. For example; my app “Ireland’s Phone Book” did not show up in searches for “Ireland” but it did for “Irelands”. This was fed back to me, so I updated the description to ensure that the word “Ireland” was in the description. Now it is found for this search term.
Of course, your application will also be available in the “recent releases” section, provided you followed my advice on this post.
Thirdly, your app will be searchable within the category in which you’ve submitted it. If you can’t find your app after a few hours, relax. Have a cup of tea. Come back a few hours later, check again.
Incidentally, searches take into account popularity, so the more popular your app is, the higher it will appear in search results.

Question 4: When will my downloads/sales info be available ?
Download and sales figures will show up on itunes connect typically by mid morning of each day. So, check around 11am the day after you go live and see if there’s some data in there. There’s a nugget of information on sales figures at the end of this post, stay tuned.
Sometimes, this is later, so again…relax if its not there…give it a couple of hours.

Question 5: When can I read my reviews? It says there’s some present, but I don’t see them.
Don’t get me started on the reviews. Ok. Here’s the deal as far as I can see.

1. They appear to be somewhat moderated, so may take some time to get through. Don’t expect to read reviews for a few days (my first ones showed though after about 5 days I think).
2. The number of review seems to be incorrect most of the time. Perhaps the number of reviews is in fact the number of ratings + the number of reviews. Example: It says today the iePhoneBook has 128 reviews. If I drill in, there are 57 reviews that I can read. You’ll learn to ignore the figures, and just read the reviews.

Question 6: What can I do about unfair reviews?
Not a lot I’m afraid. You can report a concern about a review, but I don’t know how much this helps. For example, 1 review of my apps was more like a personal ad in “In Dublin”. Its actually inappropriate, so I won’t reproduce it here.
I have reported a concern about this by marking it as “not a review” and it went away after about 10 days.

Question 7. How can I promote my app?
Well there’s lots of things you can do. You’ve just released a piece of software like any other. If you’ve budget, hire the mansion house, buy a load of champagne, and get someone famous to talk about it. I’m guessing you don’t, so here’s what I did:

1. I ensured I had a dedicated landing page for details about my app. This page includes an itunes store link, an iPhone graphic with my screen shots, and the “Available on the App Store” badge. As previously mentioned, you need to sign a license agreement to use these graphics.
2. I twittered about my release, including my landing page. Some xcakers where kind enough to Retweet, which meant that there was a couple of thousand people made aware of its existence on day 1. This definitely helped.
3. I sent a note to friends who have iPhones. I asked them for reviews. What I basically asked was: If you like this, please give it a 4 or 5 star review. If you don’t think its worth of this, please don’t review, but get in touch to tell me why it doesn’t deserve the rating. I think this is fair – You’re not asking people to lie on your behalf, and you are asking them for feedback if they think it is rubbish.

I’ve got to say however, that the best form of marketing for your app is getting a prominent place in the various itunes charts:

1. If you get to number 1 free app in any category, your icon gets used as the icon for the category when browsing the app store in the phone. Very nice. This gives you prominent positioning on the store. I would suspect that this could potentially be another reason why free apps are good publicity for pro editions.
2. If you get to number 1 overall in any country, your app will be on the front page of itunes. Exposure like this is very hard to get, and worth its weight in gold.


I know this is a chicken-and-egg scenario, but basically, doing well will bring more sales/downloads.

Question 8. How can I get feedback and engage my users
That’s the holy grail for iPhone developers. Im still learning that one. I hope to blog on this in the future.

Other Good Stuff
You’d be surprised to see who uses your app and feedback that you may get. These two took me pleasantly by surprise.
I got the following review a couple of days after launch:

5 Star
PaoloTullio
If you’re fed up paying 11811 every time you need a number, here’s the answer. A really well designed app that does exactly what it says on the tin. Only one question arises – why is it free? I would happily have paid for this.

Who? Paolo Tullio? The well-known restaurant critic? Dagnammit, I shoudda opened a restaurant. Getting 5 Stars from Paolo Tullio would do my restaurant no end of good.
(I got in touch with Paolo’s website, and got a very nice mail explaining that it was him who left the review).

Then, a couple of nights later, whilst on twitter, I got a tweet from “TheBlizzards”

Wicked PhoneApp man !

Oh. How cool is that.

I didn’t expect feedback from people in the public eye, but it was nice.

OK. I promised a nugget. Fellow Xcaker,Padraig pointed me at The App Sales application. Download it, install it on your phone.
You might also want to get Review Scraper application
Both of these do the grunt work of getting information out of itunes. Run the app sales one once a day – remember after 11 am or so!

Hope you find this useful. If you’re an iphone dev and you’ve other useful pointers, feel free to add them to the comments section.

]]> http://tapadoo.com/2009/some-things-to-expect-after-your-app-gets-launched/feed/ 3