Posted on Wednesday, Oct 22, 2008 by Rene Ritchie
File Under:App Store Apps, Development, News; Tags: app store, apps, daring fireball, developers, gigaom, gruber, long tail, pcalc

(“Unique” by Hamed Masoumi, licensed under Creative Commons)
On Monday, TiPb Senior Editor Dieter Bohn debuted his new bi-weekly feature, TiPb of the Avalanche, by asking about the iPhone App Store and the “Long Tail” business model.
Looks like he’s not alone. PCalc developer James Thomson (via Daring Fireball) recounted his struggles with Apple’s new policy of listing Apps by original release dates, ignoring update dates, and forcing older Apps to the frozen hinterlands of the last few pages in a list growing well past 5500. Under the old model:
Sales started to slow down over time, but with each of the 1.0.1 and 1.0.2 updates they went back up into the stratosphere as PCalc moved to the front page of the Utilities section again.
And now?
As it stands, the App Store is too crowded to find anything if you don’t know exactly what you are looking for by name.
So while, according to Apple Insider, the App Store may still be climbing faster than iTunes Music did, GigaOm is pishing the posh on the iPhone bump in general.
During Apple’s Q4 conference call, Steve Jobs said that the App Store would reach 200 million downloads today spanning over 5500 Apps in 62 countries. How will Apple’s (continuing?) tweaks on App Store organization help or hinder developers moving forward? And will they, as Dieter is suggesting, have to start putting as much time, money, and effort into marketing as they do coding? Or are there no easy answers?

Om Malik says Apple is clueless about scaling MobileMe:
There is no-unified IT plan vis-a-vis applications; each has their own set of servers, IT practices and release scenarios. Developers do testing, load testing and infrastructure planning, all of which is implemented by someone else. There’s no unified monitoring system. They use Oracle on Sun servers for the databases and everything has its own SAN storage. They do not use active Oracle RAC; it is all single-instance, on one box, with a secondary failover. Apparently they are putting web servers and app servers on the same machines, which causes performance problems.
John Gruber retorts, with the US’ #1 online music retailer firmly in his corner:
But the iTunes Store does gangbuster traffic and has a terrific track record for uptime. The message I read from yesterday’s reorg that put MobileMe under Eddy Cue (Apple’s VP for iTunes) is that MobileMe could and should be as responsive and reliable as the iTunes Store.
The crazy thing is, MobileMe should have been an iTunes-learned breeze for Apple in terms of meeting service levels, given their pedigree. But then iTunes uses WebObjects (which I believe is old school Java-based) and MobileMe uses SproutCore (which is all dressed up in Ajax-y 2.0 objectivity), and the pretty much disastrous July 11th launch, which took down both iTunes iPhone activation, and slammed the MobileMe servers into weeks of problems, show something clearly is different with the new kit on the block.
Hopefully Cue will bring some of the iTunes luster to MobileMe, but only time will tell. What do you think? Which blog wins this round?

Om Malik says GPS on the iPhone is locked and loaded:
[T]here is one thing that’s for sure: The new iPhone has Global Positioning System (GPS) built into it, thanks to legal requirements put in place by the FCC.
The GigaOmster further says that new-to-the-space-space Broadcom has nailed the contract, which is great for them but panic-inducing for the stand-alone GPS market. (We know Google sees positively HUGE maps usage from the GPS-less iPhone already, so that makes the kind of sense that does.)
But Brian Lam of Gizmodo thinks the whole GPS on the iPhone thing is pretty poorly thought out:
No thanks. Don’t need it. I’m fine with the current location technology. It works for walking and that’s all I need it for.
Lam’s reasons? Current cell and WiFi location services are much quicker than GPS, they better suit walking and the iPhone is less useful while driving anyway, GPS kills battery life dead, and GPS chips would significantly fatten up the iPhone.
Personally, both 3G and GPS are still bleeding edge tech when it comes to realistic day-to-day usage in everywhere, USA when not hooked up to a generator, so while nice to have as an option, and fetishized by the tech media and the blogphere commentorati, neither will have the impact on my life that the 2.0 software update likely will. It just ain’t mainstream enough for me to be melodramatic about yet.
What do you think?
[More on the Broadcom GPS story, with thanks to reader southerntraveltourism]