Instead the official recommendation is to make the splash image a stripped down version of your app's home screen - for an address book, this would be the main screen without any data, for example. This gives the app a more immediate feel, and also effectively hides a lot of the load time, since there is also no visible transition between the loading and ready states.
Of course, this is far from the reality of things - a lot of apps use splash screens for a variety of reasons, and most do not gracefully transition between splash and ready states (e.g., that empty address book splash screenshot will just magically pop into a ready view, instead of animating into said state).
- "Try it now for free" is great for showing me the value prop but ultimately I want to see a pricing sheet. I'm not willing to invest a lot time into what I see as the quick/cheap solution (compared to a custom design) for my app's website without knowing A: how much it's going to cost and B: what the limitations are. I can see that smore is in beta so maybe you just don't want to scare people off with unfinalized pricing -- for me at least no price is much scarier.
- Building the page off of the app store content is a great idea. But I need a website before I launch my app. If you support that maybe you could do a better job showing me that as an option from the start. (I'd still like to use the same content as for iTunes connect)
I want to be able to focus on the app I'm working on and not the web landing page - but for me the stuff missing is too important for this to be an option yet. I do like the direction.
Although, I wonder how exciting or lucrative this market really is when Venture backed App.net abandoned it in pursuit of other ideas
http://pandodaily.com/2012/02/02/apple-tells-developers-to-s...
Now if only they allowed me to pay a few bucks a month to remove all the smore links on top, i would probably use it as the main landing page for my sites.
FYI: Just noticed you have a bit of duplicate markup in your head - the dns-prefetch links are duplicated
This is really well done. It's easier to use than App.net and the pages look a little nicer. Well done.
Also, you also have severe alignment problems. See http://www.chrisnorstrom.com/2011/05/quick-fix-up-redesign-o... The width of the header, the body, and the footer are all different.
My app generated an error. I presume its because its not available in America (only UK):
http://itunes.apple.com/gb/app/cycle-paths-for-british-isles...
Apparently, when you try to submit a form that was not added to the body, FF and IE will just silently fail, while Chrome deals with it like a champ.
That's what you get with last-minute optimizations :/
We're in the process of deploying a fix.
"Like ous on Facebook ..."
I am never sure if there is a contest for noticing these things. lol
