Report tells IT departments not to support iPhones
A recent Forrester Research report has offered corporate IT departments 10 reasons they shouldn't support the iPhone, and calls for Apple to release some case studies of its own.Read More...
-
Forrester declares iPhone wrong for enterprise users
Filed under: Enterprise, iPhoneCIO magazine recounts a Forrester Research report from last week on "The iPhone is Not Meant for Enterprises," a $280 piece of critical business intelligence that tells IT departments something they a) wanted to hear and b) already knew: the iPhone is not a Blackberry (quel suprise!). Without key features such as remote kill, data encryption, and full Exchange support, Forrester says the iPhone is DOA in BigCo environments; despite this, IT folk need a strategy for handling the iPhones that make their touchable way in the revolving doors.Nobody expects IT to embrace the iPhone with both arms, but the tale of the numbers suggests that the warmth of the welcome may be irrelevant: the iPhone is here in a big way. With sales data suggesting that the iPhone has passed Windows Mobile in share, vendors like Visto promising full Exchange integration, and an SDK around the corner for blessed development, corporate technologists may have to settle for a policy of benign discontent as the shiny pretty things invade.[via Macworld]Read | Permalink | Email this | Comments
-
I've got nothing against the iPhone. I just wouldn't want my daughter to marry one.
Guess who's coming to dinner at IT's place?! Well, not the iPhone if Forrester Research has anything to say about it! According to Forrester (tip o' the antlers to Blackfriars' Marketing), the iPhone isn't ready for enterprise use. Well! That must bet the final word on that! Because it's not like Forrester's ever written something so completely bass-ackwards that it made you think about hanging up a shingle and becoming a high-priced technology consulting firm because, holy hell, if they're giving out advice like that, how hard could it be? ZDNet's Larry Dignan has rundown of Forrester's Top Ten Reasons Why The iPhone Is Teh Suxx0r. That's right, Forrester's report is in the same format as a late-night comedy routine. Even Dignan takes some of these items to task, but not as much to task as Mark Goble, who actually deployed iPhones in an enterprise and was interviewed about it by the Wall Street Journal. Doesn't that guy know that Rob Enderle said the iPhone was really just for teenagers? Hmm. Maybe his account managers are all teenagers. Well, whatever. Let's go to the list. 1. The iPhone doesn't natively support push business email and only checks for mail every 15 minutes compared to 1 minute on other devices. The connectivity with business email looks to be on Apple's radar as AppleInsider noticed an interesting job posting (tip o' the antlers this time to Daring Fireball). As for the time interval, if one minute is a feature, it's a broken feature. The Macalope can't tell you how many meetings he's been in with Crackberry addicts who are not paying attention to the discussion but instead are emailing their buddy in accounting to ask "Hey, did you get that thing I sent you?!" Obviously, if you're a heart surgeon or nuclear engineer or Jack Bauer, you're going to want to get that critical email before you hear "CODE BLUE" or "CORE BREACH" or "Deet-doo... Deet-doo... Deet-doo..." But -- and the Macalope really hates to be the one to break it to you -- the odds are your job isn't so important that you can't wait another 14 minutes for an email. Doesn't anyone call anymore? It is a phone after all. 2. The iPhone doesn't have third-party apps. Dignan seems to think the SDK coming early next year "may alleviate the situation". The Macalope will go not very far out on a limb and say that not too long after the SDK's release, the iPhone will have better third-party applications than any other cell phone platform (unless Apple supplies some kind of broken authentication model). 3. You can't encrypt data on an iPhone. As Goble notes, other "enterprise phones" don't encrypt data either. Also, it's a really good thing that enterprises make sure every laptop and cell phone they currently hand out is encrypted. That's a joke. They don't, of course, which is why you hear so many stories about social security numbers and medical records and human genomes being lifted from stolen laptops. Many enterprises do encrypt for users who have really sensitive data, but not all phones need to be encrypted. 4. The iPhone can't be erased remotely if it's stolen. No, but Goble believes for his business the ability to delete the user account is good enough. Dignan says Sarbanes-Oxley "will put the kibosh on iPhone adoption in some companies". Probably. But Sarbanes-Oxley doesn't say anywhere that companies must be able to remotely erase cell phones. It's about mitigating risk and documenting control points. Again, for some companies the iPhone isn't a fit, but for many it is. 5. The iPhone's software keyboard leads to input errors. Dignan smacks this down perfectly: This complaint is a red herring. I don't see it being an enterprise issue. Cubicle jockeys with a hard keypad still send mobile emails that don't make a lot of sense. 6. The iPhone is tied to AT&T. AT&T needs to open the iPhone to business accounts. But this has little to do with one of the key concerns of Forrester's piece -- how to answer users who ask IT to support their iPhones. Also, while AT&T's lack of support for businesses is a "headache", Goble manages to deal with it creatively by using several family accounts. 7. The iPhone is too expensive. Hey, know what's more expensive? Deploying difficult-to-use phones to average users and then having them avoid using them because they can't figure them out. The Macalope has seen it happen again and again. IT loves deploying Treos and Blackberries with dozens of tiny little keys that can do anything! Yay, technology! And then the executive leaves it in her drawer. 8. The iPhone is still in its first generation. So what? What if -- as it is -- it presents a compelling business case based on ease-of-use, feature set and the fact that users are more likely to use it? Dignan says that European companies will want to wait for a 3G version. Fine. But again, just because the iPhone isn't appropriate for some companies does not mean it's not appropriate for all companies. 9. No removable battery. Dignan: What company is going to be trapped into a loop of buying iPhones repeatedly? Goble: This never crossed Goble's mind. When pressed, he asked us how many spare batteries we carried around for our BlackBerry. Indeed. What is Dignan saying, that iPhone batteries are known to repeatedly fail and that such failure is out of warranty? That's ludicrous. IT departments are going to get AppleCare and they're going to swap out the phone before the battery life becomes an issue anyway. 10. There aren't any examples of companies deploying the iPhone. Except for Goble's company. Hey, you know who writes those white papers on how to successfully deploy technologies? Companies like Forrester. They could have written one o' them fancy papers, but they're more interested in providing cover for knee-jerk IT department reactions to anything with an Apple logo on it. Remember when "IT professionals" were warning companies about how dangerous iPods were? Flash drives were fine as long as they didn't have an Apple logo on them. This is not a list of reasons. It's a list of excuses. In Forrester's defense, giving IT excuses not to deploy Apple technology probably sells more reports. There are definitely going to be situations where the iPhone is not appropriate. But there are also situations where deploying the iPhone would present a compelling business case. It's not so much that the iPhone isn't ready for the enterprise, it's that the enterprise isn't ready for the iPhone.
-
Gartner acknowledges iPhone enterprise mojo in new report
Filed under: Enterprise, iPhoneCIOs and IT pros pay money -- a lot of money -- for the opinions of the Gartner Group. Since I'm not shelling out $95 to buy "Gartner Changes It's iPhone Enterprise Recommendations," even though I'm sure it would be worth a giggle or two, I'll just point you to some folks who have read the new report. Short summary: author Ken Dulaney acknowledges that the circumstances leading to Gartner's original "burn it, it's a witch!" stance on the iPhone for enterprise use have changed, and with the additional support for Exchange and ActiveSync coming in June there are far fewer reasons to take a strict stand against iPhones in corporate settings.Since Dulaney was the principal author of Gartner's first report, we commend him for sticking with the issue and setting the record straight. Now, about all those C-suite folks who already have iPhones... well, as Gartner describes the support levels required to handle idiosyncratic devices, there's "concierge," "appliance" and "platform" levels of support, with "concierge" being the most hands-on and resource-intensive (the iPhone is moving from "concierge" to "appliance" status with the June 2.0 update). How much do you want to bet that CEOs, CFOs and CIOs who go off the reservation and buy themselves iPhones and MacBook Airs are already getting, and will continue to get, "concierge"-level support from their IT departments? Yeah, that's what I thought too.Read | Permalink | Email this | Comments
-
Microsoft's Zune, Vista, and Windows Mobile 7 Strategy vs the iPhone
Daniel Eran Dilger What secret partner has Microsoft discovered to bail water from the deck of Zune and its Zune Marketplace music store in a last ditch attempt to take on Apple's iTunes, the iPod, and iPhone? Microsoft's own Windows Mobile, of course, with some help from Windows Vista! Who Else Will Help Zune? Certainly not Nokia, as one Zune fansite tried to suggest last week. Nokia has nothing to gain by promoting the Zune. A more credible sounding rumor, as long as we're inventing stuff, would be to instead suggest that it could be Sony Ericsson that is interested in putting the Zune software on its new phones. At least Sony has already demonstrated its complete failure at selling music on its own, and actually has a Windows Mobile phone in the works. The simpler reality is that Sony Ericsson may have no choice in the matter. Microsoft is clearly out to wed the Zune with Windows Mobile in a effort to get the two failures to prop each other up in its âI'm not dead yet!â fight against the iPhone. Microsoft is likely to make inclusion of its Zune Marketplace a mandatory feature that its Windows Mobile partners will have to swallow, just as it forced its PC licensees to bundle its Internet Explorer browser and later Windows Media Player, while prohibiting them from seeking their own bundling deals with other companies. Microsoft took quick steps to block Compaq's licensing of QuickTime, for example. Those deals were bad for HP, Compaq, Dell, and the other PC makers, bad for competition within the tech industry, and subsequently bad for consumers. However, they did enable Microsoft to use its powerful Windows monopoly position to push proprietary standards and or anti-interoperable technologies designed to expand its monopolized control, while making big money selling Windows in a market that lacked any alternatives. Will Nokia Rescue Microsoftâs Zune? Haha No. Apple in the Web Browser Wars: Netscape vs Internet Explorer Microsoft's Plot to Kill QuickTime A Lot Has Changed. This time around however, all Microsoft has to leverage is Windows Mobile, a struggling platform with little respect in the industry, now in a distant third place. Further, the technology Microsoft is trying to push is essentially its Windows Media DRM, which has already been swept up and trashed by Apple's iTunes, QuickTime, and the iPod. The dismal fate of Windows Media was sealed with the failure of PlaysForSure. The Zune's new, albeit incompatible, reincarnation of Windows Media DRM never stood any chance of making any headway. However, the most problematic part of Microsoft's strategy of pushing its Zune Marketplace store on its Windows Mobile partners is that music stores don't make money. Apple's iTunes Store is the biggest online music store on Earth, and does tremendous volumes of sales. Still, Apple reports minimal profits from the store. It recently warned its investors that it's now selling so much through iTunes that the low profit, high volume venture may have a negative impact on the company's overall profit margins. As problems go, that's certainly a nice one to have. Apple is not at all worried about turning a big profit with iTunes because it runs the store exclusively with the intent of ensuring new content for the iPod, iPhone, and Mac. That in turn sells its hardware. However, Microsoft doesn't have hardware sales to nurture. It has barely sold two million Zune units, many at fire sale prices (compared to 150 million iPods, 93 million of which have been sold since the Zune's release). It now faces impossible odds in tilting against the momentum of iTunes' rapidly spinning windmills, with no possible upside in terms of eventual music store profitability. There's simply no way that any amount of investment in the Zune Marketplace could deliver profits, because Microsoft is competing against Apple's non-profit motivation behind iTunes. Further, Windows Mobile is similarly a big loser with no potential because Microsoft has little ability to profitably license its mobile software. It's competition is the iPhone OS, which Apple develops for free to sell iPhone hardware (Microsoft does not sell its own phone hardware); RIM's mobile OS, which is also free for BlackBerry hardware; the Symbian OS, a partnership between hardware makers; and various mobile distributions of Linux, including Google's Android, all of which are also run as profitless ventures to support hardware sales (or in Google's case, service sales). The Great Google gPhone Myth Why Microsoftâs Zune is Still Failing 10 FAS: 7 - Appleâs Hardware and Dvorakâs Microsoft Branded PC Good Money After Bad. All that unpleasant reality hasn't phased Microsoft. Its executives haven't found a way to make money in consumer electronics yet, and the company's attempts just keep getting more and more expensive. Barron's recently featured the speculation of one Microsoft investor who hoped the company would spin off its hemorrhaging online services division as well as its profitless entertainment and devices unit, which includes the Zune, Xbox, and Windows Mobile. The investor calculated the value of Microsoft's other businesses (its high profit Office, Windows, and server divisions) and decided that the market wasn't assigning any value at all to Microsoft's consumer electronics and services products divisions. No wonder; they're nothing but a huge drain on Microsoft! Even so, the investor seemed to think there must be some value to obtain from selling off the black holes, citing the market value of the highly profitable Nintendo. The investor's real intent seemed to be finding a way to âdiscourage the company from overinvesting in the business.â Microsoft's stock has only appreciated by 6.3% over the last decade. Apple has appreciated 1,822.6% in the same period. Microsoft is trying to develop new markets as Apple has, it's just failing to do so. Microsoftâs Outrageous Office Profits Strength in Bundles. Microsoft has always been interested in promoting its products by using strong ones to prop up weak ones. From the start, it bound its strong Mac apps to the rather weak Windows offering to invent the PC platform, and has since tied Word and Excel to a suite of otherwise fair to marginal apps under the Office banner. Once Windows became established, the company tied in an unfinished, third-rate web browser and was able to rapidly build it into a strong competitor through market inertia. On the server side, Microsoft similarly ties in tragic products into package deals that often (but not always) enable the weak bits to gain some traction. So Microsoft is again working to stitch together its various properties to support each other, but now most all of its recent products are in flames and desperately need reinforcement. There's only so much one failure can do to support another. Even worse, Microsoft's historic strengths are no longer working. The Windows monopoly was supposed to brace up Windows Media Players, Windows Media Center, Windows Mobile, Windows Live Search, Windows Live Soapbox, and a series of other cobranded products that haven't gone anywhere. Office Wars 3 - How Microsoft Got Its Office Monopoly Office Wars 4 - Microsoftâs Assault on Lotus and IBM Why Does Microsoft Really Want Yahoo? Certifiable Failure. Windows itself is now in the throes of crisis, as the failed launch of Vista nearly two years ago has signaled the undoing of Microsoft's ability to rely on its desktop monopoly to advance failures into strength. Is Vista going to put out the Zune's flames by beating with its own flame-engulfed wings? That's part of Microsoft's current strategy, which included rebranding PlaysForSure as 'Certified for Windows Vista.' The Zune is also Certified for Windows Vista, despite not being compatible with the Certified for Windows Vista PlaysForSure. Confused? You needn't be for long, as the remnants of Microsoft's one-time strategy for creating an 'ecosystem of hardware, service, and software partners' to provide choice and freedom in the music industry is pretty much dead now. All of Microsoft's significant PlaysForSure store partners, including AOL MusicNow, MTV URGE, Musicmatch Jukebox, Wal-Mart Music, Yahoo Music, and Microsoft's own MSN Music have now unplugged their PlaysForSure stores, ironically making the brand among the least accurate names for a service ever. The remaining stores making use of PlaysForSure music, principally Rhapsody and Napster, are now on death's door. PlaysForSure video stores such as CinemaNow, which once worked with Microsoft's PlaysForSure-certified Portable Media Players no longer do. Even Amazon's UnBox service, which is supposed to sync with some devices that are PlaysForSure-certified, has not bothered to get certified under Microsoft's program. Incidentally, the failure of Yahoo Music and Microsoft's MSN Music (and the company's outrageous plan to simply unplug its customers from DRM authentication) caused CNET to wonder if Apple might be next in line to make users' music purchases unplayable, echoing the poorly conceived idea that Microsoft's Vista failure, its mobile platform incompetence, and desktop viral malware security crisis all somehow also predict a similar certain doom for Apple at some point in the future. For some reason, CNET saw no connection between the failure of Yahoo and MSN (hint: PlaysForSure), and no reason to speculate about the future of other media stores facing actual failure and likely disbanding in the near future, including Rhapsody, Napster, UnBox and Microsoft's own Zune. Nearly all of the recent DRM deactivation controversies, including Major League Baseball's, have been related to Microsoft's software, although Google decided to similarly to dump users of its paid video when it pulled the plug on Google Video last fall. Rise of the iTunes Killers Myth Forrester Research: Epic Terror of iTunes and Apple TV But Wait, What About This Ecosystem Failure Sounds Familiar? The complete failure of Microsoft's PlaysForSure hardware and software licensing program paints a damning prophetic picture foreshadowing the fate of Windows Mobile. Pundits often dance around this fact by spewing Microsoft's talking points: Window Mobile has lined up scores of hardware partners! Windows Mobile has lots of software partners! Choice is good! Oh wait, that's the same stuff they said about PlaysForSure in explaining why the iPod couldn't stand a chance once Microsoft could deliver its Windows Media Player reference designs and the Windows Media DRM that would enable PlaysForSure stores to open their doors. The only real difference between PlaysForSure and Windows Mobile is that the former was expected to prove that the Windows licensing model would work well among mobile devices, while the latter has already proven for some time now that it can't. Windows Mobile has been a snowball of failure ever since it launched a half decade ago with clumsy-looking phones running buggy, poorly architected software with abysmal battery life that makes the iPhone 3G look exceptional in comparison. Windows Mobile simply shares too much in common with the PlaysForSure failure to escape the event horizon if its blackhole. Pairing software from one vendor to hardware from another is problematic in the PC market, but completely untenable among highly integrated mobile devices. Microsoft tried to blame PlaysForSure incompatibilities on its music store and hardware partners, but the real problem was the model. Microsoft's own software problems didn't help either of course. The issue on Windows Mobile is even more significant because having functional mobile phone service is far more critical than being passively entertained by an MP3 player. Unchecked diversity among the devices of a platform is a bug, not a feature. The mantra of choice and freedom, hailed among Windows enthusiasts and homebrew hackers alike, makes for a great mission statement but in reality delivers products that just don't work. It's great to be able to compile your own servers from free and open source software, but most consumers don't want the accountability that comes along with that freedom when trying to dial 911 from their phone. For that matter they don't even want to troubleshoot the installation of a firmware update, or deal with why software designed for a tall screen looks awful on a square screen. With an integrated product like the iPhone, they can complain to Apple for a fix. With Windows Mobile, you get passed around by Microsoft from the mobile operator to the hardware maker to the third party software developer. Everyone is responsible but nobody is accountable. The Spectacular Failure of WinCE and Windows Mobile Count the Flames of Windows Mobile. And so, in terms of failing platforms, Windows Mobile is closer to PlaysForSure on the flames meter than it is to the only smoldering Vista, which is a moderate success by comparison. If attaching the Zune, Microsoft's phoenix on fire, to Vista's train wreck didn't have any impact on the relative salvageability of either, what will Windows Mobile 7 do for Zune 3 a year and a few months from now in late 2009 at the earliest? That's Microsoft's current schedule, barring any customary delays. By then, Apple will have had the iPhone in international distribution for more than a year, the App Store will be a year and a half old, and the WiFi iTunes Store will be more than two years old. What in Windows Mobile 7 will make a difference for smartphone buyers? According to Microsoft: copycat touch controls hobbled by an interface trying to look like Vista (below, and yes they did spell Internet Explorer wrong, as well as putting a space in ActiveSync), and no doubt a major new push to force Zune Marketplace media sales down the throats of Windows Mobile users in imitation of Apple. Microsoft is no Apple. The problem of course, is that the market for Windows Mobile phones is almost exclusively among corporate IT users, who don't give a rats ass about downloading music from the Zune store. So there's really little potential for cross pollination between Windows Mobile and the Zune. In contrast, Apple originally marketed the iPod and iPhone to consumers, who do buy up music to the tune of billions of tracks every year. Apple now has success to build upon, and has targeted its year-old iPhone platform toward the enterprise, with development tools, a software deployment infrastructure, and management utilities that in most cases meet or exceed what Microsoft has delivered over past decade on WinCE and Windows Mobile. On top of that, the iPhone platform has a far superior, standards-based web browser, development frameworks recognized to be easier to use than Microsoft's mobile .NET, and a core OS that is simply more stable, not to mention a user interface that's designed to look good and be simple to use rather than to match the flashy branding of a failed desktop OS. WWDC 2007: Kevin Hoffman Presents .Net vs. Cocoa The Other Problem: Windows Mobile is Going Down. Anyone banking on Microsoft's promises to deliver Windows Mobile 7 on time by the end of 2009 should also consider the company's track record in delivering Windows Mobile updates. The company initially intended to get Windows Mobile 5 out next to Longhorn [Vista] in mid to late 2004. Windows Mobile 5 was actually released in May 2005, and Vista finally popped out âofficiallyâ at the end of 2006, although one couldn't actually buy it until it was relaunched to consumers in early 2007. Even after Microsoft âreleasedâ its subsequent Windows Mobile 6 nearly a year later (based upon the same underlying WinCE 5), it took six months or more for many of Microsoft's partners to approve it and set up distribution so that users could actually get the software on their phones. In contrast, Apple releases regular iPhone updates every month or two that are always available to users immediately after their release, directly from Apple. Microsoft doesn't exactly have years of leisure at its disposal. Windows Mobile has already been hit hard by competition from the iPhone and from other rivals, including RIM in the enterprise market and Symbian internationally. That competition has resulted in Microsoft's mobile market share slipping year over year. This year, Microsoft failed to meet its frequently repeated goal of selling âmore than 20 million unitsâ through all of its various hardware partners, and instead only sold 18 million. Microsoft senior vice president Andy Lees blew off the missed goal as a ârounding error.â He cited numbers from IDC that indicated Windows Mobile had grown from 11% to just under 13% of the worldwide market for smartphones, growing faster than the overall market, and that unit sales of Windows Mobile phones have both outpaced sales of BlackBerry phones and outsold the iPhone by a factor of two. Windows Mobile misses target Oops, Microsoft Fibbed a Bit There. Canalys reports that Microsoft actually started out with a 23% share of the smartphone market in Q1 2004, which fell to 18% in Q1 2005, then down to 12% in Q1 2006, where it remained in its Q4 2007 figures. Apple ranked at 7% worldwide in Q4 2007, but that was based on sales in one market, of one model, and on one mobile provider, after only being on the market for six months. Smart mobile device shipments hit 118 million in 2007, up 53% on 2006 (Canalys press release: r2008021) If the best Microsoft can do is to claim victory for selling twice as many phones as Apple, worldwide across all of its partners despite having a many years long head start and that great ecosystem of manufacturers behind it, then it should probably just not say anything. Incidentally, with the release of the iPhone 3G, AT&T is reporting having doubled its sales volumes, not to mention all of the other new markets the iPhone 3G is now being sold in worldwide, at half the price of the original model. Within just the US smartphone market, which was Apple's only market last year and is also Microsoft's strongest market for Windows Mobile, the iPhone grabbed a 27% share in its debut third quarter of 2007, and maintained a 28% share in the fourth quarter 2007, behind RIM with 41%, but ahead of Palm at 9%. Adding up all of the Windows Mobile manufacturers selling in the US, Microsoft could only claim to have its software on 21% of the phones sold, a significant step behind Apple. Canalys, Symbian: Apple iPhone Already Leads Windows Mobile in US Market Share, Q3 2007 iPhone Grabs 27% of US Smartphone Market Also, all of these figures bundle in all of the âconvergenceâ Pocket PC mobile devices sold by Microsoft's partners, but none of the iPod touch units Apple sells, which are likely to be in well in excess of its iPhone sales. So Apple's mobile WiFi platform is actually far larger and growing much faster than market statistics companies report under their smartphone category. Anyone hoping that Windows Mobile 7 to going to reverse that trend when it arrives over a year from now is seriously delusional. Did you like this article? Let me know. Comment here, in the Forum, or email me with your ideas. Like reading RoughlyDrafted? Share articles with your friends, link from your blog, and subscribe to my podcast (oh wait, I have to fix that first). It's also cool to submit my articles to Digg, Reddit, or Slashdot where more people will see them. Consider making a small donation supporting this site. Thanks!
-
Real business owners don't let IT dictate what phones they use
Forrester released a rather poorly argued report yesterday describing why IT shouldn't support Apple's iPhone. Why do I claim it is poorly argued? Because the summary promptly contradicts the lede of the article saying that C-level executives will insist on deploying iPhones anyway. So why should IT be fighting that process? To make matters worse, Fortune picked up the story and and retitled it as "Top 10 reasons IT won't support the iPhone". Well thankfully, a reporter over at the Wall Street Journal did what Forrester should have: they dug up a senior executive of a company who had deployed iPhones as business tools, and ran Forrester's 10 reasons past him. That produced a nice rebuttal story that proves many of Forrester's reasons false or at least moot for real applications. Admittedly, one point does not make a sample, but for anyone who has actually used an iPhone in a business setting, the Journal article is much more credible than Forrester's was.My two cents: Forrester got it wrong for the second time this month. Whoever is in charge of research how at Forrester now needs to take a look at its research and editorial methods. Something is broken.Technorati Tags: Apple, iPhone, Wall Street Journal
-
Will Google's Android Play DOS to Apple's iPhone?
Daniel Eran Dilger Today's broad array of smartphone operating system contenders are offering lots of potential answers to a problem that only requires one. It appears the market has two options ahead: either pool generic hardware makers behind a single operating system and deliver a smartphone marketplace that resembles the Windows PC market, or watch them fall to a dominant leader and have a smartphone market that resembles Apple's iPod ecosystem. This decision isn't going to be made by a class of intellectual elite, or by government mandate. it's going to be made by the market itself. Here are the factors that will influence the outcome, either marginalizing Apple's iPhone into a niche as the company has twice experienced previously at the hands of DOS in 1981 and Windows in 1991, or positioning it as the dominant leader as Apple has achieved for itself with the iPod since 2001. The third segment in this series looks at Google's Android and the Open Handset Alliance as a possible âDOS-attackâ against Apple's iPhone. Subsequent segments will look at Nokia's newly opened Symbian and other mobile contenders challenging the iPhone. Will the iPhone Meet its Match from a Modern Day DOS? Will Windows Mobile Play DOS to Appleâs iPhone? Will Google's Android Play DOS to Apple's iPhone? Will Symbian Play DOS to Apple's iPhone? Google Acquires Android. In 2005, Google purchased a startup named Android, which had been in business for nearly two years. The secretive startup was known only to be working on software for mobile phones. It was being run by a who's who of mobile industry veterans, including Andy Rubin, the founder of Danger. Rubin had earlier worked at WebTV along with Chris White and Andy McFadden, both of whom had also joined Android. Richard Miner of Orange and Nick Sears of Tmobile also brought their mobile provider experience to Android. At the time of the acquisition, Google didn't announce any plans for Android and instead only told BusinessWeek, âWe acquired Android because of the talented engineers and great technology. We're thrilled to have them here.â It appeared that Google was only going to be expanding its search services for mobile phone users, along the lines of the Google SMS answer system it had recently released. Google Buys Android for Its Mobile Arsenal - BusinessWeek Windows XP Media Center Edition vs Apple TV: The Fall of WebTV The GPhone Myth. As reports began to leak out about talks between Google and hardware makers throughout 2007, rumors began to fly about âthe GPhone,â a competitive offering that was supposed to take on the iPhone. Some phone enthusiasts hoped Google would jump in to rescue the struggling OpenMoko project and turn it into a viable project that could attack Apple's new smartphone. In October 2007, I printed the Great Google GPhone Myth, taking apart the idea that Google would be directly competing against the iPhone, and describing that Google was really working on a free alternative to Windows Mobile as a conduit for getting its search and related services on a broader variety of mobiles. Google's services were already on the iPhone. In November, Google played its hand: it had organized a consortium of companies called the Open Handset Alliance to develop open standards for mobiles. The first product from the group would be Android, a mobile operating system built on the Linux kernel. Google wasn't getting into the phone handset business at all; it was only making sure that its mobile search products would not risk being marginalized by the threat of Windows Mobile on phones in the same way Microsoft had been working to leverage its PC monopoly to push Google search off the Windows desktop. The Great Google gPhone Myth Introducing Android: Leader of Linux. Two weeks later, Google released an early version of the Android software. On top of a Linux kernel, Android uses a specialized version of a Java Virtual Machine that takes Java language code and turns it into what Google calls âDalvik bytecodeâ rather than Java bytecode as a standard JVM would. This allows Google to leverage existing and familiar Java language tools without paying Sun for a Java license. Like Mac OS X and its fraternal iPhone OS, Android includes a variety of open source libraries, including SQLite and WebKit. On top of that, Google developed a series of frameworks that handle the tasks Cocoa Touch does on the iPhone. Android also bundles a set of applications. While Apple adapted its existing Mac OS X to work in a mobile environment to create the iPhone OS, Android is more like a customized Java environment running on a specialized mobile Linux variant: elements of maturity in an otherwise experimental new platform. What is Android? -Google Android was by no means the first mobile OS using Linux. Both Palm and its amputated ACCESS software arm have Linux-based mobile platforms. Nokia has Maemo, which it uses in its Internet Tablets, and also recently acquired Trolltech and its Qtopia mobile Linux platform. Motorola has teamed up with MontaVista Software to use its Mobilinux. Intel created the Moblin project for mobile Linux, aimed at Internet devices. Google's OHA also isn't the first consortium to attempt to standardize a mobile Linux platform. The OSDL started the Mobile Linux Initiative to define requirements for hardware; the Consumer Electronics Linux Forum (CELF) then worked to define various phone profiles aimed at the Japanese market; the Linux Phone Standard (LiPS) Forum tried to do the same thing in Europe. In 2007, LiPS was folded into the new LiMo Foundation, along with the OSDL. All of these committees have had some overlap and some complementary features. Several of Google's OHA partners are also LiMo members, including NTT DoCoMo, Wind River, and Motorola. So why didn't Google just join LiMo? âLiMo, very candidly, wasn't moving fast enough,â OHA board member John Bruggeman told CNET. Google hopes to herd the Linux cats into a progressive, structured platform that can battle against Symbian and Windows Mobile to succeed as the new DOS of smartphones. Will Google fracture or unify mobile Linux? The Presumption of the Necessity of DOS. The previous segment examining Windows Mobile pointed out how the PC industry as a whole assumed that Microsoft's desktop Windows monopoly would easily take over dominance in the MP3 player market, pushing Apple into a niche position. This was expected because DOS had pushed Apple's early computers into a reduced role starting in 1981, and Microsoft had repeated this again in 1991 when the DOS world migrated to Windows, effectively pruning Apple's Macintosh into a Bonsai platform. The inability of one company to dominate any product category has been frequently repeated by PC industry pundits as a given, despite the fact that history is full of examples of this happening. Sony dominated personal music players for two decades under the Walkman brand even while equally large competitors tried to push it from this position; Nintendo has similarly owned handheld gaming despite ill-fated efforts to grab a piece of its pie by products running a generic platform such as Microsoft's WinCE (Gizmondo), Linux (GP32), and Symbian (N-Gage). In fact, outside of the Windows/DOS PC, there are actually few examples of a generic platform taking over an industry. Nearly every other consumer-facing product uses proprietary platforms: car makers, stereo equipment, appliances and so on typically all use designs custom to their maker. The paradox of the Windows PC market has been that Microsoft's broadly licensed software supposedly saves hardware makers from investing in software development while ensuring compatibility, when in reality it adds significant costs to PC makers while limiting their ability to differentiate themselves. That explains why PC makers have been perpetually merging together and going out of business while Microosft has rolled in money over the last two decades. Parallel efforts to copy Microsoft in broadly licensing an operating system have regularly failed: IBM's OS/2, Apple's Mac OS, Palm's PDA OS, even Microsoft's own efforts to duplicate Windows dominance in other markets, from copy machines to PDAs to smartphones to SPOT watches to music players. The closest copy may be Symbian, but its customers are partners, not simply consumers of a generic third party's operating system as Windows licensees are. That indicates it is not necessary to duplicate the dominance exercised by Microsoft over the PC industry in the smartphone market. Google's Android and Symbian exist more as technology sharing pacts among manufacturers, but both aspire to take Microsoft's DOS role among smartphones. However, the idea that Apple's iPhone must be dethroned by a modern-day DOS, whether Windows Mobile, Android, or Symbian, is not just debatable, but does not sync with the reality of more recent events. Apple's recent history of the iPod further refutes the idea that a software analog to Microsoft is needed. The iPod Emergence: Apple & Pixo vs IBM & Microsoft. Apple's iPod in 2001 made no effort to clone the DOS business model; it actually did the opposite. When Apple entered the market, there were a number of existing MP3 devices using custom software, hardware designs, and DRM codecs. The iPod used off the shelf components to deliver a custom MP3 player using third party software, but Apple also added its own technologies: easy to use sync with iTunes, a fast Firewire interface that made uploading music far faster than the prevailing USB 1.0, and an attractive industrial design. With the iPod, Apple played the role of IBM in 1981, using Pixo's embedded operating system to enter the market quickly, just as IBM had used DOS. The difference was that Apple didn't direct any market attention toward Pixo and added a lot of value on top of that core embedded OS. A modern day Compaq couldn't simply clone the hardware and license Pixo to run on it in order to compete against the iPod, because the iPod was much more than just generic hardware running Pixo software. As the iPod developed, Pixo's role diminished and was eventually displaced. Just like IBM, Apple jumped into a new market just as demand was beginning to explode. Apple made MP3 players far more attractive to a general audience by delivering greater playback capacity than most entry level devices offered, along with an ease of use that encouraged buyers to jump in at the higher end of the market. That left Apple with not only the lion's share of the market, but also by far the most profitable segments of the market. Two decades prior, IBM badly fumbled its play with the early PC and ended up irrelevant in the PC world by the late 80s, sideswiped by Microsoft's DOS and the cloners who were licensing it in parallel, notably Compaq and later HP and Dell. Steve Jobs had witnessed that happen, and was determined to not let it happen again to Apple. Rather than being manipulated by a software middleware vendor as IBM had, Apple worked to incrementally develop the iPod market itself. After consuming the hard drive-based player market, Apple took on the Flash RAM-based market with a tiny hard drive system used in the iPod Mini, and followed up with Flash-based devices of its own in the Nano and Shuffle. This allowed Apple to progressively serve an increasingly wider market, incrementally growing upon an established foundation. With the iPod, Apple became, in effect, an IBM with its own internal Microsoft. Microsoft's Failure Despite Features. In contrast, Microsoft entered the music player market by promoting music player hardware reference designs around WinCE. However, it was unable to ship a finished design until the iPod had become firmly established around 2005. Later branded as PlaysForSure, the devices were sold by various hardware makers and all purported to support the same DRM and the same music subscription services while also offering a broader array of hardware that presented video before the iPod did, supported wireless before the iPod, and so on. Despite these unique features, all of those PFS designs still failed. Microsoft blamed the failure of PFS upon its music store and hardware partners and decided to take Apple on itself in 2006. It relaunched a Toshiba PFS player as its own device under the Zune brand, adding WiFi music sharing features and a larger display than the current Pods had. It failed dramatically as well. Did Microsoft's attempts to float a new DOS among music players fail because of Apple's success, or due to Microsoft's own problems? The failure of the Zune, which followed the iPod model rather than the DOS model, seems to suggest that Microsoft itself was to blame. Consider too that Microsoft's Windows Mobile phones, which use the same underlying operating system as its failed PlaysForSure music players and the Zune, had similarly flopped even before Apple could release a charismatic phone equivalent to the iPod. Of course, when the iPhone was released, it hit Windows Mobile hardest. The iPhone made Windows Mobile Smartphones look ridiculous and underpowered, and made Windows Mobile Pocket PC phones look clumsy and awkward, despite the fact that they both supported a variety of features the iPhone didn't, including the ability to edit documents, capture video, send MMS, and so on. Simply adding on features did not enable Microsoft to compete against Apple. The only conclusion that can be drawn from all this is that competing against Apple requires more than just having a feature arsenal. Microsoft's failures in themselves do not necessarily mean that Google's Android will fail in its attempts to float its own smartphone platform. Why Microsoftâs Zune is Still Failing Microsoftâs Zune, Vista, and Windows Mobile 7 Strategy vs the iPhone Will Google Succeed where Microsoft Failed? Microsoft's demonstrated inability to successfully enter consumer markets for MP3 players and smartphones has given observers little faith that the company will somehow turn things around in late 2009 when its next generation of devices are expected to be released. However, prior to that the first fruits of Google's efforts to build its own smartphone operating environment will arrive. Will Google's Android take over Microsoft's crown as the âDOS vendorâ among smartphones? Supporters of Google's Android project point to some parallels between Android for smartphones and Windows on the PC: Android will allow hardware makers to differentiate in ways that can offer features Apple can't (or doesn't want to); it should allow software developers to offer features Apple does not allow on the iPhone; it embraces open, hobbyist experimentation in ways that Apple currently isn't; and it opens the potential for content providers that Apple is not interested in allowing. Openness is Android's key competitive feature. Will all this openness allow Google to unseat the iPhone to become the primary platform developers want to participate in, and subsequently soak up the market for third party hardware makers that Windows Mobile serves? While Google currently has no market share due to the fact that no Android phones have yet shipped, it does have broad vocal support from a variety of the same kinds of hardware manufacturers that supported DOS and Windows and helped to make those platforms successful in the desktop PC market. HTC and Android. The first Android phone is expected to be the HTC Dream; Taiwan's HTC (High Tech Computer) also manufactures Palm's Treo Pro phone as well as many of the most visible Windows Mobile devices. In addition to models produced under its own name, HTC also sells Windows Mobile devices under the Dopod brand, as well as no-name phones branded by providers, such as AT&T, Orange, Sprint, T-Mobile, Verizon Wireless, Vodafone, and others. HTC will also be building the XPERIA X1 Windows Mobile phone for Sony Ericsson. HTC was quick to throw its support behind Android despite its long term alliance with Windows Mobile. Why would it so enthusiastically support an unproven platform from a company that has no experience in consumer hardware platforms? One can only assume that HTC is not happy with the current state of Windows Mobile, and desperately wants another âDOSâ to succeed where Microsoft's has so spectacularly failed. As an Original Design Manufacturer for Palm, HTC watched as Palm adopted Windows Mobile in place of the Palm OS and subsequently fell even deeper into crisis. Palm's only successful phone since has been its Palm OS-based Centro. HTC undoubtedly sees Android as its ticket to becoming the next Dell, but without a similar dependance upon Microsoft. Android for mobile phones is essentially playing the role of Linux for PCs, except that it has the backing of a major company behind it. Can Android Take on the iPhone with Openness as its Feature? As great as this sounds, it's important to consider that Linux on the desktop has made no significant progress in eating into Windows dominance after a decade of trying. Being open, free, flexible, and decentralized hasn't been enough of an advantage to get consumers to migrate from Windows to Linux in any fraction of significance. Similarly, in the music business, Linux-based MP3 players have had no impact on the iPod, despite offering more features, flexibility, support for additional codecs, and so on. In the mobile phone area, Linux enjoys a sizable portion of the smartphone market, but this is almost entirely due to phones sold by Motorola in China, where the advantages of Linux' openness are void. Motorola's Linux phones offer nothing to users in terms of openness or flexibility, and are really no different in terms of features than other appliance 'feature phones' based upon closed operating systems. And again, a key problem with assaulting Apple in a feature war is that neither the iPod nor the iPhone became popular by being âhighly featured.â They both delivered perhaps 80% of the functionality found in all other devices in the market. Rather than trying to match every feature and cater to every niche as Microsoft had with Windows Mobile, Apple's devices did a few things very well at launch, and incrementally developed into full featured devices that still lack some of the more unique features of their competitors. Further, in terms of openness, the demographic that embraces Linux' characteristic freedoms is not the same as the demographic that buys smartphones in quantity and then pays for data service. This is a critical fact to consider because a big part of the iPhone's success stems from the fact that it is being pushed by mobile providers who want to capture the cream of the market willing to pay a premium for data services. The Frankenphone. Combining the fractured aesthetic of HTC's Windows Mobile phone hardware with Android's software, based upon Linux' perpetually unfinished DIY openness and Google's Java-like development platform, will not result in a product similar to the iPhone. Instead, it will look a lot like phones that have already failed in the market. Apple's advantage comes from slick hardware designs with a close attention to detail, combined with software that purposely does less so that it can do what it does better. Even Apple's own conservative attempts to broaden its software capabilities with iPhone 2.0 have resulted in instability problems that can be blamed upon both Apple's early releases of its phone operating system and software from inexperienced third party developers new to the platform. Would the current frustrations with iPhone 2.0 be somehow mitigated by additional openness that also embraced all kinds of variables from different hardware makers with less quality control than Apple, a loose committee of additional cooks working to serve up operating system features targeted at every possible conceived need, and a wider third party software group with fewer constraints on illegal behaviors? The Failure of Open. While it is politically unpopular to criticize the well meaning efforts of open source contributors, the failure of Linux on the desktop, the failure of the vaporware Indrema game console, and the failure of the OpenMoko project to deliver a workable phone within a year of its deadline all underline the serious problems open development faces in the world of consumer oriented devices. Open has simply failed to deliver on its promises in the world of consumer hardware. OpenMoko was supposed to release its first mobile phone to consumers for $250 several months in advance of the iPhone. When the iPhone shipped, the group then announced new plans to get its phone out by the end of 2007. Instead, this spring the group announced new plans to move to an entirely different development platform, and ship its phone mid year for $400 with limited functionality and incomplete software outside of basic GSM phone features. Linux's notable successes, from Motorola's Linux phones to the Tivo DVR to Linksys Routers, have often come without any associated openness or freedom, and were instead delivered simply to provide their manufacturer with a free kernel to build upon. This indicates that while Linux may find its way into an increasing number of smartphones, it will likely not be accompanied by the glorious freedom of an open development environment Google has said it would offer with Android. Apple iPhone vs the FIC Neo1973 OpenMoko Linux Smartphone Can Google Succeed Where Open Has Previously Failed? Despite âopennessâ being Android's strongest competitive feature compared to Apple's iPhone, Google recently revealed that its wide-open development model is intentionally gravitating towards a closed association of top tier partners due to practical considerations. In July, Google accidentally sent out a notice that revealed that it had been seeding private SDK updates to only a subset of its contributors, angering those who believed that Android would be as open as Linux on the desktop or the OpenMoko project. Further, Google has restricted initial development to higher level APIs just as Apple did, further indicating that Google itself realizes that being wildly open to impress a minority of hobbyists will not result in the commercial success of its new platform. That serves to neuter Android's primary advantage over the iPhone. Without delivering on the premise of being wide open, Android is really just a less mature set of Java libraries used to create a specialized binary that runs on a Linux foundation. Unlike Apple's iPhone, Android phones won't have a slick user interface developed by professional artists, nor the iPhone's legacy of mature software development frameworks crafted over the last thirty years, nor the iPhone's tightly integrated hardware with award winning industrial design, nor its marketing power tied into the iPod and Apple's retail stores. Android won't be an open iPhone, it will only be a Windows Mobile phone with a better kernel that runs specialized Java software instead of Win32 or .NET code. Don't expect consumers to be impressed by that. The Biggest Missing Feature. There is one remaining factor that strangles to death any last remaining hope that Android might assassinate the iPhone and assume the crown of the âDOS of smartphones.â That is: Android delivers zero price advantage to consumers. In 1981 and 1991, consumers who wanted Apple computers faced the sticker shock of a somewhat arrogant price tag. Apple sold its computers, as it still does, at the higher end of the market, but there was simply far more range in prices available. In 1981, that meant the Apple II was $2600 and the new Apple III was $3500, even before you added a monitor. On the low end, Commodore sold its far less powerful, but âstill a computerâ Vic-20 for $300, while IBM entered the market with the IBM PC at $3000. Over the next few years, Apple focused on delivering additional sophistication at the same price, releasing the $10,000 Lisa and then the $2,500 Macintosh. IBM continued selling PCs in the same $3,000 to $10,000 range, but other DOS PC vendors began selling machines at prices that ranged as low as $1500. That left Apple with a roughly $1000 price premium over low end PCs. The products weren't really comparable, but consumers only saw the huge price difference. In 1991, Apple was still selling moderate to high-end Macintoshes for $3,800 to $10,000; the crippled Mac LC was $2500, and obsolete-at-birth Mac Classic ranged from $999 to $1500. Windows allowed PC makers to ship a functional $1500 PC and claim a rough approximation to Apple's $2500 entry level system, maintaining that apparent $1000 price premium. Today, pundits are lucky to find a Dell or HP system that is even a couple hundred dollars less than a comparable Mac. However, in the smartphone business, the iPhone 3G is now the same price, if not less, than generic competing phones on the market. Even more significant is the fact that the price of the phone hardware is nearly nothing compared to the cost of the service plan. This fact simply eases any price premium that could cause buyers to flock to a smartphone running a generic operating system over buying the iPhone 3G, regardless of whether it runs Windows Mobile or Android. 1990-1995: Planting Software Seeds Android Partners Have Already Failed. That same pricing principle similarly prevented buyers from considering many of the alternatives to the iPod. While Apple's original iPod models were more expensive than many of the first MP3 players on the market, they were price competitive with models offering similar features. By 2004, it was Apple who was undercutting MP3 competitors on price. Microsoft offered zero price advantage when it began selling the Zune, a major factor in its failure, but Microsoft simply couldn't out-price the iPod; it was already losing money offering the Zune at the same price as the iPod. Apple now has tremendous market power in buying RAM and other components that will prevent any competitors from being able to offer a huge discount over the iPhone's $199 price tag. Even if competitors were to give their phones away, they would only offer a $200 discount to users who would then still need to pay the same mobile fees to use the phone. Android's other partners, including Samsung and LG, have already failed to capture any significant market share in the music player market. Are they going to maintain their position as smartphone makers now that they face similar competition from Apple, its iPod ecosystem, its iTunes Music and Apps Store, Apple's retail store experience, and other factors that are pushing the iPhone? If they can, it is not obvious how partnering with Android will help. Other Problems for Android. Android was announced in early November 2007 and was followed with an early preview SDK within a couple weeks, a month ahead of Apple's initial announcement of the iPhone 2.0 SDK. However, between March and July 2008, Apple delivered nine progressive releases of its SDK, opened its App Store, and sold 60 million apps, raising $30 million to support iPhone software development in just the first month. It has since released three more SDK updates to developers related to iPhone 2.1, which is expected next month. Android just published its first open SDK beta update earlier this week, warning developers that âapplications developed with it may not quite be compatible with devices running the final Android 1.0.â Additionally, Android still has no phones available. By the time the HTC Dream is expected to launch, Apple will have an installed base of around ten million iPhone (and iPod touch) users supporting software development through iTunes. The business model for selling Android apps is no better than that for selling jailbreak iPhone apps: there is no iTunes Apps Store to promote them, so users will have to track them down on their own. Android developers also have no real freedom that jailbreak iPhone developers lack. The only difference is that there are ten million iPhones to sell jailbreak apps to, and currently zero Android phones. If selling a jailbreak iPhone app sounds like more trouble than its worth, imagine trying to sell Android apps to a non-existant audience. Now add the official iPhone App Store into the mix, where publicity, promotion and profits are booming. What platform is going to have the most applications? How many users will flock to a smartphone platform with no apps? The wisdom of releasing a desirable phone and achieving a significant installed base before releasing an SDK makes a lot more sense in retrospect. Additionally, while Apple has a decade of experience in shipping regular updates to Mac OS X and its Xcode developer tools, Google has only shipped a random assortment of web-oriented SDKs (a number of which have been abandoned) as a tangent to its core business of selling advertisements. When the Android SDK 1.0 is finished later this year, developers will not only lack an installed base to sell their apps to, but will also have no high profile market for selling their apps in, and subsequently no financial incentive to develop applications that add value to the Android platform, just like Linux on the PC desktop. Around the same time, possibly within the next month, Apple will be shipping its second major OS release: iPhone 2.1. Apple will also be upgrading its entire user base to the new software so that developers will have a cohesive platform to target. This mirrors the efforts Apple has taken to upgrade its Mac OS X users to the same reference release. Mobile developers will be seeing money pouring in via iTunes while crickets chirp in the Android section of various mobile online stores. Appleâs iPhone Vs. Other Mobile Hardware Makers: 5 Revenue Engines Same Same, But Different: DOS Model Problems. Android developers will also have a series of other problems to manage. Like Windows Mobile, Android is intended to support everything, from BlackBerry-style keypad phones with a small touchscreen to the simple Windows Mobile Smartphone form factor lacking a touch screen to iPhone-like full size touch screens. Also like Windows Mobile, Android phone makers will have the option to leave off Bluetooth, WiFi, GPS location services, graphics hardware acceleration, and so on. Each Android phone will also have unique camera hardware, support for different video and audio codecs, and varied support for other differentiating proprietary services demanded by mobile operators. This will force developers to to make complex decisions regarding the lowest common denominator they choose to support. So while the iPhone will have a cohesive feature set, a managed software environment, and a functional market, Android will be a loose federation of hardware makers selling the same random features found on Windows Mobile today, with a chaotic development environment that lacks any central market for users or developers. And it will be run as an experiment by a company with no experience in consumer hardware or platform development. The Missing Tap. One specific example of the âDOS model problemâ is that Android currently does not support multitouch. It's not touched on in the API, and Google quietly tap dances around its omission. Why no multitouch? Because multitouch screens are expensive, and most OHA hardware members are more interested in making a profit in a competitive phone market rather than impressing consumers as Apple did with the iPhone. Most existing smartphones, even those trying to directly rival the iPhone, use a stylus driven, pressure sensitive tap screen or a simpler, cheaper touch technology that lacks support for sensing multitouch. The iPhone's screen can actually sense up to five fingers at once, but the primary feature multitouch offers on the iPhone is the two fingered tapping and the pinching effects everyone associates with it. Android could certainly support multitouch if there were a demand for it, but that's the point: Google knows that its hardware partners are cheap and unlikely to put out hardware that actually competes with the iPhone. Instead of using expensive technologies that deliver clever yet largely invisible functionality, OHA members, just like PC makers, are far more likely to add flashy, impractical gadgety fluff that's cheap to tack on, such as slide out keyboards, neon tubes, and scratch and sniff stickers. That's how you impress gullible nerds on the cheap. Google itself is blowing smoke and erecting mirrors to distract from the reality that it being a âDOS vendorâ means supporting bargain basement hardware from penny pinching duplicators. Android has been demonstrating some âwowâ features such as a Street Maps app that pans around based on an internal compass in the demonstration phone. The problem is that that kind of thing only makes for a fun demo. Nobody needs to twirl around their phone in the air to see a view of the other side of the street, but everyone who has used an iPhone will wonder why they can't pinch to zoom out. Even worse, most Android phones aren't going to have a compass built into them, so Google is demonstrating features most Android users won't be able to use. That Sounds Like Microsoft… Google's design decisions are beginning to look a lot like Windows Vista; rather than actually working to make laptops boot faster, Microsoft came up with the idea of adding a small screen to the back of Vista laptops so users could check their email without having to wake the system up. But this was a stupid idea for a number of reasons, the most obvious being that most users just want a laptop that boots up quickly. Few laptops got the mini screen, but every user who tries Vista on their laptop will wonder why it doesn't boot up as fast as Mac OS X Leopard. In the same way, Google is advertising features for Android that most users won't ever see in their actual phones while ignoring things people will expect based on their exposure to the iPhone. Android is simply selecting the wrong features. Android will offer the advantages of supporting MMS, recording video, and the list of other features Windows Mobile already supplies. Those features didn't stop Apple from firing past Microsoft in the smartphone arena however, just as the Zune's highly touted WiFi and screen didn't phase iPod buyers. Incidentally, just months after the Zune, Apple had not only demonstrated a larger display but a higher definition multitouch screen, and not only WiFi, but functional WiFi that could be used to browse the web or check email. This suggests that Apple, with its faster release schedule, won't stay behind any of the leading features potentially offered by Android for very long. Android partners, however, will find it as difficult to catch up with Apple's unique features, just as Microsoft has been stymied to keep up with Mac OS X, the iPod, and the iPhone. The underlying reason: both Google and Microosft are tasked with maintaing support for a huge variety of hardware options demanded by all their partners. Apple has the unique circumstances to do only what it needs to do itself. Android in Windows Mobile's Shoes. Like Windows Mobile, Android faces a difficult market. In the US, it competes against the popular BlackBerry in corporate markets and the iPhone among consumers. Worldwide, it competes against entrenched market leader Nokia. The difference is that Google, unlike Microsoft, has no in. Windows Mobile was adopted by Windows-bound IT shops despite its weaknesses. Nobody has any preexisting reason to try an Android phone apart from hobbyists and open software enthusiasts, a demographic that has done little to move Linux on the PC desktop. Google also lacks Microsoft's installed base; it's starting from zero. The smartphone industry initially doubted Apple's chances of making much progress with the iPhone, despite the company having the Mac platform, the iPod, retail stores, platform development experience, marketing savvy, industrial design prowess, and so on. Google doesn't have any of those things. Mobile Providers vs Android. Apple also started with an exclusive partnership with AT&T, a three legged race that demanded effort from both. Google is hoping that hardware makers handle the hardware details and that mobile providers will be excited to sell its Android phones. While hardware makers such as HTC clearly appreciate having found a free alternative to Windows Mobile, it's not obvious why providers would be excited about Android, as it promises an openness that most mobile providers strongly oppose. AT&T took a big risk in getting behind the iPhone, as the phone encouraged users to use email rather than fee-based SMS and MMS, it supported WiFi for data access, and it bypassed AT&T's MEdia Net services to plug into iTunes instead. Verizon refused to parter with Apple and grant it those kinds of concessions. Is AT&T going to take a similar risk to partner with a phone that is not exclusive to it, and is Verizon now going to open its arms to support phones that do not exclusively support BREW, VCast and its other proprietary services? While Android may well eat into Microsoft's Windows Mobile business by stealing away its hardware makers, it seems unlikely that Android will ever serve as more than free alternative to Windows Mobile in a market where Windows Mobile is increasingly irrelevant. Android may have the dubious distinction of swallowing Microsoft's mobile business the same way Microsoft ate up the Palm OS, but even if it accomplishes that goal, Google will likely find itself unsustainably hungry immediately afterward. It will also find itself swimming in a shark tank of hungry rivals, including Nokia's Symbian, RIM's BlackBerry, and Apple's iPhone. Symbian is the final generic platform vying for the opportunity to play DOS in the smartphone market. The next article will examine Nokia's chances in its bid to match Microsoft's PC dominance in the mobile market while setting out in a new venture to copy Android's open software model. Did you like this article? Let me know. Comment here, in the Forum, or email me with your ideas. Like reading RoughlyDrafted? Share articles with your friends, link from your blog, and subscribe to my podcast (oh wait, I have to fix that first). It's also cool to submit my articles to Digg, Reddit, or Slashdot where more people will see them. Consider making a small donation supporting this site. Thanks!
-
What's Next from Apple: New iPods Sept 22, iPhone OS 2.1, iTunes 8.0
Daniel Eran Dilger Kevin Rose has been trying his hand at making broad sweeping generalizations about the next generation of iPods, but sorry, no digg. Most of his predictions are not even original, and those that are are so vague that they're really just worthless. Here's what you can really expect. Rose likes to suggest what's next from Apple, but his guesses only approach reality when they're based on leaks that occur days prior to an announcement. His flat out guesswork tends to be yet far further removed from reality, indicating that he has no special inside track on things at Apple, nor much of an imagination tempered by realistic appraisal. A month before the iPhone was unveiled, Rose predicted it would be available from CDMA providers, have a pull out keyboard, and sport two batteries, one for music and one for the phone. Of course, splitting a battery in half is not really a brilliant solution to prevent music playback from running down your phone, but the simple fact that Rose didn't know about the exclusive deal with Cingular (come on, it was Apple's only mobile partner to date) and the unlikelihood of Apple tacking on an HTC-esque keyboard makes his guesswork easy to dismiss. I had imagineered the iPhone as a web browsing iPod (âbased on Nokiaâs mobile contributions to Safariâ) with SMS messaging features, contacts, calendar, and a camera… six months earlier. And CDMA? I recommended Apple âleave Verizon alone and partner with Cingular, TMobile, and MetroPCS using GSM technology.â The difference between my ideas and those from Rose, apart from mine being six months earlier, is that I presented mine as only reasonable ideas with some rationale behind them; Rose insisted he had special knowledge from reliable sources. Generation 6 iPods An iPhone Worth Talking About The Real iPod touch Deets. Now he's predicting new iPods. The iPod touch is supposed to get âfairly large price drops to distance itself from the $199 iPhone.â Sorry, wrong. The iPhone is only $199 in the minds of consumers. It gets a subsidy from AT&T, which is why you can't just buy one for $199 and walk out the door without signing a phone contract. The iPhone's $2,000 service contract offers plenty of distance between it and the iPod touch. The iPod touch is not possibly going to get cheaper than the iPhone for a couple reasons. First, obviously, it costs nearly as much to make. The lack of a subsidy pretty much balances out its lack of mobile radio components. Second, Apple isn't desperately trying to sell the iPod touch. It exists as a product to sell to users who can't or won't buy an iPhone because they're tied to Verizon or don't want a phone. Rose worries that the iPhone is âcannibalizing sales of the iPod,â but there's nothing more Apple would like to do than to feed every iPod user an iPhone. Sure the bonehead analysts will have another field day complaining about how there's only minor growth among iPod sales while they ignore iPhone numbers, but these guys aren't easy to reach with basic facts. Apple has been giving away the $300 iPod touch to students buying a laptop; that looks like an effort to broaden the iPhone platform. Apple wants college kids playing iPhone games and interested in creating their own iPhone software. Left to their own devices, most kids would buy the old hard drive iPod Classic because they think they need to walk around with their entire torrent library of stolen music. (Get off my lawn!) In any case, we all knew the iPod refresh was coming. I'm pretty sure they're coming on September 22. I'm also pretty sure that the 8GB iPod touch is going away, making the 16GB model the new $199 version. That outrageous price drop, facilitated by today's cheaper Flash RAM, would kill the remaining market for the hard drive-based iPod Classic, converting Apple's entire lineup to Flash RAM. Additionally, it would migrate even more iPod buyers into the installed base of iPhone App Store users and hasten the cannibalization food chain that leads toward the iPhone. The 16GB iPod touch will be sold next to the existing 32GB model, which was just released earlier this year. For that reason, I don't see a larger capacity model being introduced now. I don't see tremendous demand for carrying 64GB of music from people who are also ready to pay for 64GB of Flash. Nano 4: Zune 2007? Rose says the Nano will get a redesign that makes it look like last year's Flash RAM Zune; iLounge already predicted this a month ago, although Rose embellished his version with the idea that âthe actual plastic on the outside will be curved,â presumably like a TV from the 80s. How nostalgic! I miss having a wildly distorted tube picture, almost as much as a scratchable plastic iPod screen. Oh the good ol' days. Will Apple expend significant resources to make the Nano 4 into a widescreen tall/long player and define a new 4GB hardware model to fit into a niche that is only $50 less than the new 16GB $199 iPod touch? How much room for differentiation is there under $200? Seems more likely that Apple will instead only release a cheaper version of the existing 4GB Nano that's closer to $99, leaving room for a $149 8GB Nano in between. That will pull Shuffle buyers up into splurging on a full video Nano. If you want to watch video sideways, you can get an iPod touch for $199. What kind of widescreen cinematic experience can you get with a long/tall Nano/Zune? When I reviewed the Flash Zune, one of the complaints was that half (but only half) of the controls reconfigure when you hold it sideways. Plus, existing iPod Games wouldn't work in the widescreen orientation; both the display and the controls would be messed up. On top of that, regular video playback would be forced to play back wide, and/or look bad because its stretched. Microsoft has no qualms with playing video in an odd aspect radio, but the iPod is made by Apple, which has some aesthetic boundaries that constrain its behavior. Winter 2007 Buyerâs Guide: Microsoft Zune 8 vs iPod Nano iPhone 2.1 Rose says Apple will also release âiPod touch 2.1 software, iPhone to get update very soon after.â We already all knew the iPhone 2.1 update was coming, and that it's going to be significant, and that it is due for release around the same time as the new iPods. Whether the new iPod touch will ship with it in advance of the iPhone would depend on whether iPhone-only features in the release hold it up, but Rose doesn't suggest any special knowledge or rationale behind this claim. iPhone 2.1 is supposed to usher in new GPS features and the push Notification system, but the real demand for downloading it will be that it fixes a major problem that currently causes third party iPhone apps to crash on launch and randomly when running. Apple needs to get this out quick before it blows the reputation of iPhone software stability in the minds of users. That's reason to believe that iPhone 2.1 might ship even before the new iPods, rather than the other way around. Because software developed using the iPhone 2.1 SDK won't run on iPhone 2.0.x, expect everyone to need to update their software to download a new generation of 2.1-only apps. This will be free for iPhone users, but might incur a nominal fee for iPod touch users due to accounting rules. Myths of Snow Leopard 3: Mac Sidelined for iPhone Ten Big New Features in Mac OS X Snow Leopard iTunes 8.0 Rose says iTunes 8.0 âit's a big update with new features,â but doesn't say what they are. He also says it will be âa real point upgradeâ deserving the 8.0 name. However, there is little rhyme or reason to Apple's iTunes version numbering, and no real correlation between the amount features introduced and the version number increment. iTunes 2.0 added iPod support after ten months of iTunes 1.0, but iTunes 3.0 only added minor features the next year. It was replaced by iTunes 4.0 a year later, which added the Music Store and AAC support. Two years later, iTunes 5 introduced some cosmetic changes and was immediately replaced with iTunes 6.0 only a month later, without any major new features. Another year later, iTunes 7.0 arrived with a new look, video game support, and Coverflow. It has since seen loads of new features, from support for Apple TV to the iPhone to new iPods and new movie rentals, all of which were only numbered as minor updates. We've had iTunes 7.x for two years now, so iTunes 8.0 is not really ballsy prediction at this point. Of course, Apple is just as likely to skip ahead and release iTunes X. And if iTunes X isn't ready, we can might even get iTunes 7.8 and 7.9 over the next couple years. Oh my sides. With the likelihood of entirely new iPod touch or Nano models being quite low (after all, the Zune isn't going to get a refresh until late next year, and Apple isn't facing any tough competition at the moment), Apple's iPod announcement might end up more about a new iTunes than the iPod. Rose doesn't make any iTunes 8.0 feature predictions, instead jumping ahead to suggest that Apple is working to make sure Mac OS X 10.5.6 will provide support for Sony's BluRay, the competition to iTunes that nobody cares about. Hmm. Steve Jobs has so little regard for optical discs that he basically shunned iDVD last year when showing off iLife 08, but now he's going to resurrect BluRay and excite customers by including it on the company's laptops, where any resolution advantage it offers over DVD would be nearly invisible? Oh ho ho my sides. iTunes Unlimited? The rumor mill is talking about subscription music in the next iTunes. Steve Jobs has opposed subscription music since iTunes got started. He worked for years to convince the labels to let go of the dream of billing users to essentially listen to the radio. Subscription music has always revolved around outrageous DRM that requires the (historically Microsoft PlaysForSure) player to sync up and check in every month or lose its music. I've written up lots of reasons why subscription music was an awful idea that wouldn't fly. I doubt Apple will actually float it as rumored (âiTunes Unlimitedâ for $129 sounds awful). However, enough has changed in the last two years to reconsider how subscription music could be delivered. For starters, the iPhone and iPod touch are now wireless, so they can both stream and verify exploding media DRM. Apple's iTunes, modern iPods, Apple TV, and the iPhone also now already handle exploding DRM for movie rentals, which blew over last year without any complaint, although it doesn't look like iTunes' movie rentals have had a massive impact on the world due to their relatively high price point. Offering movie rentals appeared to be a requisite concession leading up to convincing the movie studios to agree to movie sales in iTunes. Apple could sell access to subscription music directly from the iPhone and iPod touch that worked similar to movie rentals, and the labels might even allow users to freely copy rental tracks between computers linked to the same iTunes account. Such an arrangement hasn't found mainstream popularity elsewhere, but nobody else had been able to sell music prior to iTunes either. While the rumors suggest there could be a discount for MobileMe users, it would be a lot smarter to make it part of MobileMe instead. That would limit subscribers to Apple's loyal base, easing in the system rather than exposing a brand new subscription service to ten million handheld users and 150 million iTunes users and all but promising another meltdown. At least by making it part of MobileMe, Apple could add lots of subscribers and upgrade existing subscribers to a $99 âunlimited musicâ additional fee. Keep in mind that all this is highly speculative. I doubt âunlimited iTunesâ will fly, as the idea was not leaked but rather simply invented. How Apple Could Deliver Workable iTunes Rentals The Online Music and Movie Rental Myth Rise of the iTunes Killers Myth As Long As We're Speculating… If Apple does convert its entire iPod line to Flash players, it would make sense to incorporate a new audio codec setting that maximized the amount of songs you could copy into an 8GB player. For years, Apple's major selling point on the iPod what that it offered massive hard drive storage capacity. Now it's migrating to Flash, which is more expensive but considerably more shock resistant and suitable for a handheld computer device like the iPod touch. Working to cram more music into tighter spaces would allow Apple to make the iPod touch and iPhone more competitive against a hard drive player. AAC is already optimized for low-bitrate playback. Apple also needs to add remote functionality for controlling Apple TV to iTunes, just as you can already do via the free iPhone app. And how about direct streaming of content between iTunes, Apple TV, and the iPhone, such as for movie rentals. Currently, to get a rented movie from an iPhone to Apple TV you have to do two syncs involving a middleman iTunes PC. iTunes also needs to expand on the options for syncing media to the iPod and iPhone. In addition to syncing specific playlists, it should be able to automatically sync over a smart âParty Shuffleâ mix of music that fills a specific proportion of the device, such as 50% music, 10% podcasts, and then the specific movies, TV, and audio books the user selects. Then shuffle out the listened to tracks and add new music every time it's synced. Allow users to hide songs from iTunes just as you can hide photos from your iPhoto album to simplify the view without deleting anything. Add Time Machine support so you can go back to see earlier play counts and browse your media library as it appeared in the past. Add integrated support for viewing PDFs and other QuickView document types, so you could use iTunes as a metadata-rich document browser with search and playlist features. Or give Preview an iTunes metadata document database interface. More Music Deals. Add other corporate sponsors to the Starbucks deal, so you can discover their playing music and buy tunes over their WiFi link. And isn't it about time Apple and AT&T got together and hammered out that plan to open iPhones to AT&T's hotspots? I'd debit a 99 cent WiFi access fee from my iTunes account if it were necessary. What's the point of setting up $8 per hour WiFi services for the zero people who use them? And on that tangent, how about rolling out my Ubiquitous WiFi idea for allowing other mobile users to borrow your AirPort's WiFi signal? I'd also like to see Apple get AT&T to allow users to place calls over their WiFi link as a concession for not having a functional 3G network in place yet. I also think AT&T should sell or rent AirPort base stations to its millions of broadband users, with all of them open to WiFi sharing so that iPhone users could place a freaking call and access the web at faster than EDGE speeds between now and whenever AT&T actually gets 3G rolled out. Apple also really needs to deliver some sort of central media server, possibly tacked onto Apple TV. Just add a USB hard drive and have it serve up the contents as a Bonjour-discoverable iTunes library to your local network. This would allows users to dump all the media off their laptop. And then allow WiFi sync to optionally copy fresh media to the iPhone from the central media server library. There's plenty that could be tacked onto iTunes, but the biggest new thing in the iPod announcement actually might be something entirely different than last year's iPods for cheaper and a new rev to iTunes. I'll spill that in the next article. Ten Big Predictions for Apple in 2008 Did you like this article? Let me know. Comment here, in the Forum, or email me with your ideas. Like reading RoughlyDrafted? Share articles with your friends, link from your blog, and subscribe to my podcast (oh wait, I have to fix that first). It's also cool to submit my articles to Digg, Reddit, or Slashdot where more people will see them. Consider making a small donation supporting this site. Thanks!
-
Apple is looking for an Exchange QA staffer for iPhone
Filed under: iPhoneEven if iPhones are further into the enterprise market than some might think (or desire), the lack of native non-IMAP support for Exchange accounts on the device has given some users and their IT departments pause. While there are some solid third-party options coming along (Visto and SyncML among others), only an Apple-blessed solution is going to satisfy in the end. Is there progress on the home front? Chadwick sent along a link via ModMyiPhone.com to an Apple job posting for a QA engineer: The iPhone Quality team is looking for a motivated, highly-technical Exchange test/sync engineer with excellent problem solving and communication skills. You will join a dynamic team responsible for qualifying the latest iPhone products. Your focus will be testing Exchange and Outlook functionality with Apple's innovative new phone. The successful candidate will complete both documented and adhoc testing to ensure high quality releases. Hiring a QA engineer implies that the Exchange connector code under development is getting ready for testing and release. Could an Exchange hookup for the iPhone be coming in time for Macworld Expo? Dee-lightful. Thanks, Chadwick.Read | Permalink | Email this | Comments
-
â Let the Tea Leaf Reading Begin
The best thing about being an Apple observer is that even when the company does make a long-awaited announcement, it inevitably leads to new questions regarding what exactly they mean. Apple punditry is the Kremlinology of the tech world. So it is with this week’s announcement from Steve Jobs1 that, yes, “We want native third party applications on the iPhone, and we plan to have an SDK in developersâ hands in February.” We now know two new things: (1) that there will be “native third party applications on the iPhone”; and (2) that the SDK is scheduled for February. That leaves a long list of questions. Whither Widgets? For one: What exactly is a “native third party application”? The obvious answer is the sort of UIKit-based Cocoa-ish applications that underground iPhone hackers have been creating over the last two months — the exact sort of native apps that Apple has itself already written for the iPhone and iPod Touch. For all we know at this point, though, it could be something more like Dashboard widgets — but I think that’s unlikely. Jobs wrote: > With our revolutionary multi-touch interface, powerful > hardware and advanced software architecture, we believe we > have created the best mobile platform ever for developers. JavaScript, HTML, and CSS are cool in that they’re widely-used, widely-known coding standards — but they’re not a good way to create user experiences that take full advantage of the iPhone, and would be pretty hard for Apple to pass off as an SDK for “native apps”. Third party developers want access to the same dog food Apple’s own iPhone engineers are eating. Plus, there’s the issue of performance. Iconfactory developer Craig Hockenberry, who has been tinkering with the unofficial iPhone developer tools to create an iPhone-native version of Twitterrific, wrote a splendid weblog entry titled “Benchmarking in Your Pants” regarding the lackluster performance of JavaScript code running in MobileSafari compared to compiled Objective-C code running in a native iPhone app. Function calls, for example, were 226 times slower in JavaScript. (Hockenberry also benchmarked JavaScript running on the iPhone compared to the same code running in Safari on an Intel-based iMac; the code ran about 80 times faster on the iMac.) Back in January at the iPhone’s introduction in the Macworld Expo keynote, Jobs described some of the apps on the iPhone, including Weather and Stocks, as “widgets”. My somewhat-informed understanding is that Apple’s original plan was for the iPhone to ship with its major apps written in Cocoa and with a handful of smaller apps written as Dashboard-style HTML/CSS/JavaScript widgets — but that this plan was scuttled for performance reasons, and the Weather and Stocks widgets2 were rewritten as UIKit Objective-C apps sometime this spring.3 My guess is that they ran into what Hockenberry documented: JavaScript on the current iPhone just isn’t fast enough to provide an iPhone-caliber user experience. So my money is that the iPhone SDK that Apple plans to release this winter is the real thing — Cocoa-style UIKit apps written in Objective-C. Security? Jobs wrote: It will take until February to release an SDK because weâre trying to do two diametrically opposed things at onceâprovide an advanced and open platform to developers while at the same time protect iPhone users from viruses, malware, privacy attacks, etc. This is no easy task. Some claim that viruses and malware are not a problem on mobile phonesâthis is simply not true. There have been serious viruses on other mobile phones already, including some that silently spread from phone to phone over the cell network. As our phones become more powerful, these malicious programs will become more dangerous. And since the iPhone is the most advanced phone ever, it will be a highly visible target. External security — the threat of vulnerabilities that would allow malfeasants to compromise a victim’s iPhone — is a serious matter. There have already been several published exploits against the iPhone, including an as-of-this-writing open vulnerability in TIFF-processing code in the current iPhone OS. So clearly there is some merit to Jobs’s stated security concerns. As it stands in the current iPhone OS, all processes run as the root user; in broad layman’s terms, any process has access to everything else on the phone. So when a buffer overflow can be exploited to allow remote code execution, that code can do anything. To allow third-party iPhone apps to run today would be to trust those third-party developers not to write code with any security flaws. What the iPhone needs before Apple will allow third-party apps to run is some sort of sandbox, a way to prevent application processes from being able to access things they shouldn’t be allowed to access. But iPhone Cocoa apps are no more inherently susceptible to buffer overflow vulnerabilities than Mac Cocoa apps. And the hysteria over the iPhone’s current “everything runs as root” situation is overblown.4 Applications on your Mac don’t run as the root; they run under your user account. But all of your data — your email, your address book, your documents, everything your apps can read or write without administrator authentication — is vulnerable to any sort of hypothetical buffer overflow exploit on the Mac, and would be on the iPhone, too, even if iPhone apps didn’t all run as root. Sure, root privileges allow an exploit to do anything, but the most important thing on your system is your personal data, and an exploit doesn’t need root privileges to access that. I’m thinking Apple is more concerned about internal security — about having third-party apps limited to a sandbox so that user-installed code has no access to things like, say, the phone network modem’s firmware (the component that you need to diddle with to create SIM unlocks). That’s the key difference between the iPhone and the Mac, security-wise. Which Third-Party Developers? Mac OS X is pretty much completely open to development; even the developer tools are free, and anyone is free to write whatever software they want for the Mac. It seems unlikely that iPhone OS X development is going to be like that. One possibility is that the iPhone SDK will only be available to developers with ADC Select ($499) or Premiere ($3,499) accounts. (Premier and Select ADC members are the only ones with access to pre-release Mac OS X seeds, for example.) If that’s the case, it’s not going to be popular with hobbyist developers, but most professional Mac developers already have paid ADC memberships, and, let’s face it, we all know most iPhone apps are going to be written by Mac developers. Interviewed via email, Craig Hockenberry told me, “If there’s a simple way to get third party apps on the iPhone, you keep 90 percent of the developers happy and jailbreak/unlock has much less momentum. Sure, there will still be people that want to ‘buck the system’ but they’ll be in the minority rather than the majority.” The most intriguing part of Jobs’s announcement was this section, regarding security: Some companies are already taking action. Nokia, for example, is not allowing any applications to be loaded onto some of their newest phones unless they have a digital signature that can be traced back to a known developer. While this makes such a phone less than âtotally open,â? we believe it is a step in the right direction. We are working on an advanced system which will offer developers broad access to natively program the iPhoneâs amazing software platform while at the same time protecting users from malicious programs. It’s hard not to interpret the scare quotes around “totally open” as a reference to Nokia’s recent “Open to Anything” ad campaign — sort of a you guys aren’t completely open either call-out. This seems like a pretty clear indication that Apple is working on a similar signing system for iPhone apps. Restricting development to paid ADC members would instantly allow Apple to associate app signatures “back to a known developer”. Here’s more information from Nokia on the signing program Jobs mentioned; here’s similar information on the Symbian site. Which Apps? Another question is whether Apple is going to allow participating (trusted-by-Apple) developers to write whatever apps they want, signing the apps themselves, or if apps will need to be approved case-by-case by Apple before being signed. Mac OS X Leopard includes a new “application signing” feature, described by Apple thusly: A digital signature on an application verifies its identity and ensures its integrity. All applications shipped with Leopard are signed by Apple, and third-party software developers can also sign their applications. That same page describes a “sandboxing” feature that seems applicable to the iPhone, too: Sandboxing prevents hackers from hijacking applications to run their own code by making sure applications only do what theyâre intended to do. It restricts an applicationâs file access, network access, and ability to launch other applications.” The prototypical example of a potentially popular app that Apple might refuse to approve would be a VOIP app like, say, Skype, in that it would undermine the need for the phone network, which in turn undermines Apple’s revenue sharing with the iPhone’s exclusive network partners. Or, say, instant messaging, the omission of which from the current iPhone is seen by many as a concession to the fact that heavy SMS users pay handsomely for extra monthly messages. (Personally, I suspect iChat for iPhone simply didn’t make the cut for 1.0 but is planned for a future update.) “Nokia’s model is to run as trusted/untrusted,” said Hockenberry. “Trusted apps get to access more than untrusted ones. This model could be extended to allow different levels of access based upon whatever Apple wants (as owner of the root certificate.) Basic access for Wi-Fi, extended access for EDGE, hardware access for deep pockets, etc.” That makes sense, and strikes me as a likely course for Apple. Development There’s a question, then, of how developers will write the apps in the first place. If iPhones only run third-party apps that have been approved by Apple, how do you develop an application in the first place before it’s been approved? Steven Frank — who, as co-founder of Panic and an unrepentant gadget hound, may well be the single most interested person in the world in a supported iPhone SDK — described to me via email the development process for the Danger Hiptop/Sidekick: “The Hiptop/Sidekick platform has a Java SDK that abstracts away all the low-level hardware stuff so you can’t touch it, while still providing everything you need to write an application.  You test and debug in an emulator/virtual machine that can simulate edge conditions like loss of cellular network availability and so on.  When you’re almost done, and ready to try on real hardware, you apply for a ‘developer key’, which is a small certificate that you install on the phone that enables you to run third-party apps that didn’t come from the on-device for-purchase catalog.  To get the developer key, you have to prove to them you actually have an almost complete app, and aren’t just some kid who wants hot Yung Joc ringtones by submitting a build of your application.  You also have to sign a waiver that says you are no longer eligible for support from your cellular carrier.” The iTunes App Store? Which leaves us with the question of distribution and installation. The obvious route is the same one Apple has taken with iPod games: the iTunes Store. Apple, in this case, would likely get a cut of every sale. From a user’s perspective, it’d be easy and obvious: shop and pay for apps in iTunes, and iTunes takes care of installing the software, and, perhaps, synching data. This is similar to the Danger model — where apps must be approved, and can be sold only through the official channel. Limiting, to be sure, but as Frank put it, “The process [of developing for Danger] is somewhat tedious, but still an order of magnitude better than not allowing third-party applications, period.” Frank also pointed out the most glaring downside of Danger’s pay-to-play development model: “One drawback to this approach from the user’s perspective is that there is basically no free third-party software. Everything costs at least a couple bucks.” The announcement appeared on Apple’s Hot News web page, but with no permalink, so it’s likely to disappear from Apple’s web site in a week or two as newer items appear. I’ve saved a plain text copy here for posterity. ↩ I wonder if the Calculator app was originally a widget, too. UI-wise, it’d certainly be a cinch, because just like with the iPhone’s Weather and Stocks apps, it more or less looks and acts exactly like the corresponding widget in Mac OS X. So my theory is that when Apple made the decision to rewrite the iPhone widgets as native iPhone Cocoa apps, they used the widgets as the specs for the apps. “Make a native app that looks and acts exactly like this widget,” more or less. One thing that makes me think this is that the iPhone Calculator app doesn’t make any sounds when you press the buttons. Pure JavaScript/HTML widgets can’t make sounds when you click or tap buttons. I find typing on the iPhone keyboard to be much more satisfying with the sound on; with the sound off, because the keys are virtual, there’s no sensory feedback at all. The Calculator app would feel more real if it simply made the same button-clicking noises as the iPhone keyboard. ↩ That this change was — I believe — made rather late in the game might explain why vestigial references to “widgets” remained in the shipping iPhone 1.0 software. (It could also mean, of course, that Apple plans to re-expose this feature at some point in the future.) ↩ It certainly is a curious question why all iPhone apps run as root. I don’t know the answer. But I’ll bet there’s an interesting engineering trade-off involved somewhere. If you think the reason is laziness or ignorance on the part of the iPhone OS X engineers, you’re an idiot. ↩
-
Why Dan Frommer and Scott Moritz Are Wrong on iPhone Sales
Daniel Eran DilgerSilicon Alley Insider's Dan Frommer says Apple's announcement of reaching its million mark goal in iPhone sales three weeks early is actually bad news for Apple and is convolutedly "below plan." He also says the announcement only props up the speculative conjecture by Scott Moritz of the Street that Apple's iPhones sales are somehow woefully below expectations. They're wrong, here's why.The PremiseFrommer wrote that Apple isn't selling iPhones as fast as planned and is set to only sell around half of its 2008 goal.His premise revolves around the idea that if Apple were selling iPhones at "a constant rate," a million phones in 74 days would be five million per year. However, because it sold over a quarter of those in the opening day and a half at the end of June, Frommer calculates that sales of the remainder in the 72 days since the first of July mean that Apple is only hitting a "3.6 million annual run rate."By the end of 2008, that would only result in 5.8 million units instead of the ten million goal Apple. [Silicon Alley Insider: Apple's iPhone: 1 Million Is Below Plan]Strike One: The Run Rate Myth.The most obvious problem with that idea is the fact that devices don't sell at a constant ârun rate." Apple's iPhone sales took off at launch much faster than the original iPod due to the fact that a swell of early adopters were ready to buy it after being convinced over six months of anticipation. At the same time, many potential buyers held off on plans to buy the iPhone until they could read reviews and get a real sense of how it worked. Many were also locked into contracts with Verizon or Sprint. With only six months of advanced notice, it will still be a few more months before the majority of buyers who want an iPhone even get the chance to buy one without having to pay outrageous fees to cancel their existing mobile contract. iPhone sales are also now taking on the network effect of the iPod, as early adopters show their friends. All these factors have difficult to estimate impacts upon sales that make trying to figure a static ârun rateâ? a very simplistic and pointless exercise.However, there is another factor that simply blows the entire idea of a static ârun rateâ? out of the water. Last November, I predicted that sales of the Zune would bomb that winter because Microsoft had failed to critically examine Apple's historical sales patterns. Sure enough, the Zune was thrown against the rocks by Apple's riptide. Frommer's idea ignores that same reality by imagining that iPhone sales will schlep along at a linear pace. Had Frommer tried to calculate an "annual run rate" for the iPod based on a portion of third quarter sales at any point over the last half decade, he would never have been close to accurate. Thatâs because Appleâs iPod sales roughly triple every winter quarter.In 2002, it sold nearly as many iPods in its winter quarter as it did the first three quarters combined: 219,000In 2003, it actually sold more iPods in its winter quarter than in the first three combined: 733,000In 2004, it again sold more iPods in its winter quarter than in the first three: 4,580,000In 2005, it sold more than 4 million units every quarter, but still sold nearly three times as many in the winter: 14,480,000.In 2006, it sold more than 8 million units every quarter, and then sold over 21 million in the winter quarter.In 2007, it has maintained quarterly sales between 10.5 and 9.8 million per quarter.[Strike 3: Why Zune will Bomb this Winter]Strike Two: The Have it Both Ways Myth.One particularly annoying bit of analysts' talk about Apple's expectations is that they can't seem to decide if Apple's projections are bad because they are conservative lowballs, or if they are bad for being overly enthusiastic figures the company won't be able to reach. They often try to describe them as both, loading contempt on both sides of the scale. This makes them look very foolish. Do they think we have no memory, or are they just changing their stories back and forth in sheer desperation?Frommer tried to argue both sides at once in the same article. Recall that Apple only ever gave two iPhone sales goals: one million by the end of the first quarter of sales, and ten million by the end of 2008. In his piece, Frommer suggests Apple will only be able to sell 5.8 million iPhones by the end of 2008, based on that fallacious "run rate." That would be just over half of Apple's ten million goal. However, he then says that Apple's immediate short term goal was an unimpressive low ball, no doubt because Apple reached it three weeks early.Apple's stated goals must be a greatly frustrating logical conundrum for Frommer, because even at a ârun rate" of one million in a quarter, Apple could only ever hope to sell six million iPhones by the end of 2008, another five quarters later. No wonder he's faced with trying to say that the immediate goal was too low and the longer term one is too high! Frommer needs to stop trying to pound round facts into square holes just so they can be stacked up like bricks the way he would like them to be.Strike Three: The Market Bearing Price Myth.While Frommer and Moritz are enamored with the idea that iPhone prices could only be cut if sales were in crisis, a variety of obvious market realities don't support that simpleton idea. Between now and the end of 2008, Apple has just two holiday seasons. If it wants to dramatically exploit its historical potential for selling roughly three times as many gadgets during the winter season, it makes sense to trade off unit pricing for volume sales, even if it could perhaps sell fewer at a higher price and make more short term profits doing so.Such a strategy isn't unique. Microsoft and Sony currently lose money on their new game consoles in desperate bids to establish their gaming and HD video playing platforms. Even so, this year they both cut prices again to accelerate volume demand. Nintendo purposely aimed low to capture volume sales using a more attractive price point. Given high demand for the Wii and extremely constrained availability, Nintendo "should" seemingly raise its console price and profiteer. It hasn't. While prices are clearly linked to demand, it is a common fallacy to think that the "right price" is always the highest the market will bear. Jobs' 99 cent pricing in the iTunes store is clearly not the top price consumers will pay for downloads. Music labels are fuming that other licensees such as Verizon will collect $2.50 or more for portions of a song sold as a ringtone. Jobs wants media prices low to induce volume sales and attract buyers to the legitimate market for music and movie downloads. Labels and studios want "market pricing," in part so they can jack up the price of popular music to exploit consumers, and in part so they can exploit artists by threatening to release their work at lower tiered prices and signal to the market that their careers are over.[Universal vs Apple in the iTunes Store Contracts][Nintendo Wii vs Microsoft Xbox 360 and Sony PS3]This All Happened Before.Dial back the clock twenty years, and you'll discover that Steve Jobs also fought with Apple CEO John Sculley over the price of the original Macintosh. The desire to use an expensive but pioneering amount of RAM and a futuristic new processor had inflated the price of the Mac, but the design team was still able to deliver it at a fairly attractive price point of $1,995. Scully determined that the Mac would still sell at $2495, delivering high profits to fund splashy advertising. Nothing on the market was really similar to the Mac apart from Apple's $9,995 Lisa. VisiOn for the PC similarly cost nearly $10,000 and did far less. Sculley thought that the market would bear anything Apple might charge. Andy Hertzfeld recalled on Folklore.org that in October 1983, "Steve Jobs strode into the software area one evening, looking angry. 'You're not going to like this,' he told us, 'but Sculley is insisting that we charge $2495 for the Mac instead of $1995, and use the extra money for a bigger marketing budget. He figures that the early adopters will buy it no matter what the price. He also wants more of a cushion to protect Apple II sales. But don't worry, I'm not going to let him get away with it!'"Jobs fought Sculley over the price increase, but Sculley prevailed. Sure enough, Macs did sell well out of the gate to early adopters at the higher price, but sales then began to stall. While Jobs couldn't cut the price for the original Mac to induce wider adoption in the mid 80s, he could choose to cut the price of the iPhone early and use interest in the iPod Touch to ramp users toward the iPhone. That price cut will dramatically boost sales this winter, just as iPod price cuts and feature refreshes do every year.Apple will earn less profit on individual hardware sales of the iPhone, and may even earn slightly less money overall this quarter than it might have selling the iPhone at $599. However, a $399 iPhone will dramatically boost the company's sustainable subscriber revenues and devastatingly cut into stationary rivals like Palm and the Windows Mobile licensees, giving them little opportunity retool and strike back with copycat products.  [Price Fight - Folklore.org][Office Wars 3 - How Microsoft Got Its Office Monopoly]Strike Four: The Myth of Unlimited Availability.Another problem with idea that iPhone sales were in crisis--and that a price cut is a conspiracy to hide the truth--is that Apple sold out of iPhones in many of its retail stores throughout the first three weeks on sale.Carl Howe of Blackfriar's Communications tracked iPhone availability every day through July, and then animated the results in a movie that depicts just how constrained iPhone inventories in Apple's retail stores were. So not only did Apple meet its 94 day goal 20 days early, but it did so despite having no or few iPhones to sell in many of its stores during the first 21 days. Price isn't just related to demand, but also to supply.That also demonstrates the fallacy of Scott Moritz' assertion that Apple secretly planned to sell a million iPhones in a day and a half, and was sorely disappointed after failing to do so. How could Apple have planned on selling a million units in one day when it didn't even have a million units on the shelves of its stores during the first month? Remember, Moritz wasn't saying Apple had a delivery problem in getting enough units to stores as Nintendo is experiencing with its constrained supplies of the Wii. Instead, he tried to suggest that interest in the iPhone was far below Apple's estimates, and buyers were leaving it on the shelf like Windows Vista. The result, he claimed, was that "rivals were rejoicing."The only real rejoicing by rivals was that Moritz was volunteering to repeat the talking points handed to him by Verizon shill Roger Entner of IAG Research. Just hours before Apple announced it had sold a million units, Moritz tried to get some traction out of the idea that Apple had dropped the price in desperation to find another half million or so customers over the next three weeks. Apple isn't the typical tech company being run by visionless bean counters. It it were, it would have continued selling $600 iPhones at least through the end of September and then announced that it had sold its million. Apple had to push out new iPods in early September and fit the iPhone into the price range because next month it will be rolling out Leopard and a series of new software updates. Apple feeds the press in small, consistent, and regular feedings so reporters know what to write. If Apple were a big stupid company such as, say HP, it would parade out a mix of dozens of consumer and business products all together in one big event, and nobody would ever hear about any of it. HP did.[Why a million iPhones in 74 days is better than you think- Blackfriars][HP's marketing this week: fashionable but ineffective - Blackfriars][Unraveling Anti-Apple Panic: the iPhone Launch Success] [More on Scott Moritz and the Jim Cramer Misinformation Engine]Strike Five: It's Too Late to Deny the iPhone.The most comical part of Frommersâ analysis is that heâs trying to stuff a cat back into a bag and explain that there was never really any cat, long after everyone in the room heard the purr and pet the thing. Sorry, but the windows of opportunity to doubt the iPhone have long since closed.Real Windows Enthusiasts were aware of the need to deny the iPhone well before its release. They all chimed in with reasons why the iPhone wouldn't work, wouldn't offer what consumers want, and wouldn't sell well, all hoping that their non-stop misinformation campaigns would act as a self-fulfilling prophesy. They failed miserably.John Dvorak began his smear campaign immediately, appearing on CNBC to say that the iPhone was "trending against what people are really liking in phones nowadays, which are those little keypads.â? He explained, âThe BlackJack, the Samsung, the BlackBerry obviously pushes this kind of thing. The Palm, all of these. I guess some of these stocks went down on the Apple announcement, thinking that Apple could do no wrong. But I think Apple can do wrong, and I think this is it." Reader Jim Barrow sent in a link to a MarketWatch article from March, where Dvorak scribed a rambling diatribe entitled "Apple should pull the plug on the iPhone." He offered no factual basis for worrying that the iPhone might not work out apart from the offhanded comment that "there is no likelihood that Apple can be successful in a business this competitive," words which echoed Dvorak's 1984 observation that "the Macintosh uses an experimental pointing device called a 'mouse.' There is no evidence that people want to use these things."In April, Dvorak inflamed his 'pull the plug' rhetoric further in a TWiT podcast, where he reported to an audience of hundreds of thousands that the iPhone only delivered "40 minutes of talk time" and "the interface fouls up constantly.â? Dvorak said that his inside information on the iPhone came from a "guy at Cingular whoâs testing the product," adding, "heâs telling me confidentially and I shouldnât be telling anybody."[John Dvorak: How Wrong Can One Guy Be?][Readers Write: Don't Write About John Dvorak Anymore]It'll Be the Death of You.Dvorak was joined by Rob Enderle, who called the iPhone âdamnedâ? and ânot a very good phoneâ? at every opportunity in the months before its launch, despite not really knowing anything about it, or even ever offering any rational criticism. Instead, Enderle appealed to fantasy fears of sexual assault, murder, and the violent death of children, all of which he suggested might somehow be related to the iPhone. Unaware that a password protected iPhone--or even a unauthorized unit without a configured service plan--can still be used to make emergency phone calls, Enderle wrote about, "an emergency situation where, say, a woman was being raped and couldnât call for help because she didnât remember her iPhone password." As I understand, with a Windows Mobile phone, even if the unit crashed while trying to place the call, at least the victim could use it like a brick as a blunt weapon. Enderle also feared that being unable to take out the battery would somehow making recharging it impossible, resulting an a scenario where one might end up on âthe wrong side of townâ? with a dead iPhone and be murdered because of it. Being on the wrong side of town was apparently the source of most murders prior to the arrival of the cell phone, which somehow made it safe to be in bad neighborhoods. For those who unfazed by the prospect of one's own own grizzly death in relation to the iPhone, Enderle appealed to his readers to please think of the children, particularly the potential for their brutal decapitation in an iPhone-related collision. "If you are buying this phone for a child or another member of your family," Enderle warned, "please emphasize that entering data on this phone while driving is dangerous." In contrast, operating the slide out keyboards of an HTC brick phone, or using both hands to thumb type on a BlackBerry may or may not save your children as they drive off an embankment, but at least you'll know they didn't die at the hands of Apple's "damned" iPhone.[SCO, Linux, and Microsoft in the History of OS: 1970s][Mac OS X vs Linux: Third Party Software and Security]Pure Concentrated Evil with a Multitouch Screen.Brian Lam of Gizmodo published an impassioned plea to boycott the iPhone shortly before its launch, due to the fact that Cingular had purchased the AT&T name, a brand Gizmodo's writer correlated with "monopoly tactics" in the late 70s. Gizmodo hasn't ever called for the boycotting of Verizon Wireless, which is well known for its anti-consumer tactics and which shares just as much blood with the old AT&T as its Baby Bell sibling Cingular, nor has it ever urged the boycott Microsoft products due to "monopoly tactics." Gizmodo also failed to boyco