How Open will the iPhone Get?

Daniel Eran DilgerThere is obvious interest in iPhone development, and users of the device have good reason to demand a vibrant software ecosystem growing up around it. There are a lot of applications Apple doesn’t have the time or inclination to deliver, but which would greatly increase the value of the phone and subsequently expand sales. Apple needs third party help.At the same time, I have taken it upon myself to act as the tiny minority voice in explaining why I think Apple isn’t...

Daniel Eran DilgerThere is obvious interest in iPhone development, and users of the device have good reason to demand a vibrant software ecosystem growing up around it. There are a lot of applications Apple doesn’t have the time or inclination to deliver, but which would greatly increase the value of the phone and subsequently expand sales. Apple needs third party help.At the same time, I have taken it upon myself to act as the tiny minority voice in explaining why I think Apple isn’t simply being foolish and shortsighted in the way that it is rolling out its iPhone software platform. Back in January, I explained why Apple might face resistance from third party developers, and why it might be best suited following a managed platform strategy in the model of video games, where Apple would developing its own apps and work with developers to co-publish, without setting up a wide open development platform like the Mac or Windows. [Inside the iPhone: Third Party Software]I also defended against the market-speak droids that came out in a vengeance against Apple’s so called “closed platform? by highlighting the absurdity of ABI’s claim that not running third party software made the iPhone “not a smartphone,? pointing out that the overwhelming majority of today’s third party mobile software either:solves problems in Windows Mobile that shouldn’t exist.fills voids left by Windows Mobile that Microsoft should have covered.exists without reason as frivolous garbage-ware.is overpriced trash.or will work on the iPhone already.[More Absurd iPhone Myths: Third Party Software Panic]With Journalists Like These, Who Needs to Report a Factual Story?In May, I went to Apple’s shareholder meeting (just barely; they use metal detectors for security and I have a metal plate in my arm from a motorcycle accident), and used the opportunity to ask Steve Jobs about iPhone development In front of all those rich stockholder and media types.“While Apple's closed platform policy may make sense for consumers,? I asked, “does Apple recognize the needs of large, institutional buyers who are excited about the prospect of applying low cost, handheld computers with their own custom development??Jobs went on record to answer that Apple was working to balance the needs of software security and deployment with demands for custom development on the iPhone. The “real? press, including Ellen Lee in the San Francisco Chronicle and Troy Wolverton of the San Jose Mercury News, failed to ask any interesting questions or even note the interesting answers. Instead, Lee published a diatribe about how Jobs was “feisty? and “fired back? at anyone who dare ask any questions. Lee also described an unhappy shareholder contingent based entirely upon--as reader David Barnes noted--conversations with two union leaders with clear political goals. She may as well have invented that story from her desk and saved herself a trip.Wolverton turned in a tepid report in May, but then tried to retell Lee’s story in August, in an incendiary article that spun the meeting’s vote--three months later--as a hotbed of shareholder outrage and discontent. Wolverton still hasn’t got back to me as promised to explain away his documented record of half-truths and negative spin on all things Apple. What a coward![Answers from Steve Jobs at Apple's Shareholder Meeting][RoughlyDrafted Forums - Answers from Steve Jobs at Apple's Shareholder Meeting][Troy Wolverton Documents Faux Apple Shareholder Outrage]An iPhone SDK at WWDC?Prior to WWDC in June, I explained why I didn’t think Apple would release a software development kit for it, and that it would likely orient apps around the web as Dashboard-like widgets instead. I outlined reasons why, in addition to pointing out that being “closed? did not necessarily mean being a completely locked down black box, and that Apple’s viewpoint was subject to change as the surrounding circumstances did. [Mobile Disruption: Apple's iPhone and Third Party Software][An iPhone SDK? Predictions for WWDC 2007!]An Open iPhone Software Plan.Days before the iPhone’s release, I pointed out that Apple had already gone on record about its plans for the iPhone back in an April earnings report:CFO Peter Oppenheimer stated, “We believe the iPhone is a revolutionary device that is years ahead of the competition. At Macworld, we demonstrated a number of the iPhone's breakthrough features, including its pioneering multi-touch display and user interface, visual voicemail, desktop class e-mail and web browsing, and of course, the best iPod ever. “We plan to build on this incredible foundation by continuing to develop new software features as well as entirely new applications and incorporate them into the iPhone. Since iPhone customers will likely be our best advocates for the product, we want to get them many of these new features and applications at no additional charge as they become available.“[Apple's Secret iPhone Application Business Model]Since then, I’ve pointed out the same thing: the iPhone isn’t likely to become a Mac-like open platform anytime soon, but its really not accurate to call it a closed platform either. Two recent articles presented more details on why, integrating in the historical events of the Office Wars.[Six Reasons Why Apple May Never Open the iPhone][How Closed Is the iPhone?]Reasons for Wanting an Open iPhone SDK.Reader Ken Tozier responded with three main reasons he thinks Apple should open up the iPhone to developers. He wrote:“A supported SDK would eliminate the negative ‘hacker’ stigma for third party applications. Since Apple never partners with anyone but large corporations, under the closed model, the little guy will never get a chance to legitimately write applications for the iPhone. Without this legitimacy, only a miniscule proportion of iPhone users will ever take the risk on hacked applications. The average user will just be too scared off by the label ‘hacked.’
“A supported SDK would bring a large percentage of developers, who want to create iPhone/iPod-Touch apps under Apple's control. It's just easier and faster to use Apple's Cocoa classes than plod through open source SVN trees trying to  stitch together disparate code fragments into your own ‘big idea.’
“Small developers are the ones who will be writing the most creative iPhone apps. Fleshing in the iPhone universe with myriad stars, that are just too small for Apple to bother with. Bar code readers based on the camera. Foreign language flash cards, Road trip license plate games for kids where, when they see a new license plate, they could press a button for info on that state. Lava lamps, virtual fish tanks. Carpenter's levels. Nail finders. The possibilities are endless and Apple will never do any of them.“The iPhone already contains a large chunk of ARM adapted Cocoa classes with the exact same method prototypes that have been in use for years in OS X. Apple isn't going to change classes like NSDictionaries, NSStrings, NSURLs etc for the simple reason that it's battle tested, ‘just works’ and changing these would break all their stuff too.“So, that just leaves a handful of high level iPhone specific classes. For example, I'd be a happy camper if, in addition to file read/write, Apple gave us the following iPhone hardware accessor classes:NSBasebandServiceNSBasebandClient
NSBluetoothServiceNSBluetoothClient
NSWiFiServiceNSWiFiClient
NSMultiTouchClientNSAccelerometerClient“With NSBasebandService and NSWiFiService, it would be possible to create a wireless modem application where your laptop talks to the phone in WiFi-ese and the phone talks to another phone on the other side of the world through the baseband. Teleconferencing from a camp site.“With NSMultiTouchClient, you could use the raw coordinate (and pressure?) data however you wanted. Keys on a virtual instrument, pads on a virtual drum kit, whatever.“With NSAccelerometerClient you could create really cool multi-player games and physics demonstrations for the classroom.“Apple needs to do this. I can't put an accurate percentage on it, but my gut feeling is that third party apps could increase iPhone sales by 10 to 15 percent. Maybe even more if someone comes up with something revolutionary.?The Hacker Stigma.Tozier raised some good points. However, regarding the hacker stigma, what great or useful applications do people not use because of such a stigma? Mac the Ripper, Handbrake, and torrent apps and sites are wildly popular, even though they are known to be "grey area" and require thwarting of laws and jurisdictions just to host them. People might be afraid of putting unknown third party software on their mobile, but they should be. If Apple rubber stamped its approval on all third party software to remove this stigma, it would only confer all rage related to glitches, battery loss, spyware, and other problems directly upon Apple. Why would Apple want to take responsibility for a bunch of hobbyist apps when it faces regular petty lawsuits over "whether it adequately informed users that batteries might wear out" and other frivolousness?Frozen Cocoa: Tastes Great But Doesn't Flow.The hackers are already working to use Apple's Cocoa classes. There is no alternative system on the iPhone to use. Just as on the Mac desktop, many apps are existing Free and Open Source Software wrapped in nice Cocoa interfaces. That's what iPhone apps would largely be as well. But for Apple to offer official support for this, it would have to freeze its Cocoa frameworks and make them public.Apple already maintains private frameworks in Mac OS X; developers can't really use these, not because Apple wants to reserve them for itself, but because they are in flux. Apple commonly develops a framework privately, then after testing it in production and refining it, opens them up for developers to use in the next release of Mac OS X. If developers were allowed to build against the closed versions, their work would break as Apple made improvements. It's the same on the iPhone. If Apple opened up its internals as a public API, it would then be hamstrung to make any changes.We already know that Apple plans to make major changes to a number of things, particularly Notes and Calendar in relation to Leopard. If Apple allowed developers to go out and build a "Notes+" they would be angry after Apple released its own plans related to Notes, and "outraged Mac users" would be paraded around offering their opinion that Apple shouldn't step on developers shoes and should pay third parties before offering a similar solution to the same problem. Think of Watson and Konfabulator.An Expanding iPhone Software Ecosystem of Small Developers.At the same time however, Tozier raises salient points about the breadth and depth of software that Apple will never provide solutions to. I have an iPhone. I want to install cool things on it. I can imagine things that would be incredibly useful and powerful and fun. I'm surprised Apple hasn't made any allowance to even package up "local web apps" that developers could distribute that could do things without a network connection. It would be great if Apple could deliver a sandbox environment that would skirt around all the problems I raised and deliver a vibrant software ecosphere for the OS X devices.I can also think of a dozen other things It would also be great if Apple could tackle. Unfortunately, market realities mean that the company's abilities are constrained and it has to focus on the most valuable opportunities. As the company builds the iPhone platform, I think it will make sense to progressively allow increased access to third parties. Steps Toward Open.I think "local web apps" would be an extremely important first step, along with simpler Dashboard-like widgets similar to the iPhone’s Maps, Weather, and Stocks. Put them on a separate set of pages behind "Dashboard" or something. Very little risk.A second step would be to allow access to the cooler stuff via the web, so local web apps could access sensors and Bluetooth and other things. This begins to raise security risks and liability risks. The first apps are going to be used to copy around songs and pop up ads; there is too much money in "not paying for content" and "pushing messages at people." Look at Windows: open ubiquitous platform, satiated with software piracy and viral adware.I agree that the idyllic paradise is flowing with the milk and honey of third party software, but there are real threats to defend against as well. Which is why I brought up Mac OS licensing. Who would have guessed that software licensing would cost Apple more money that it made? Good ideas are sometimes really just ideas.But ideas are so much fun to speculate about. Let’s play Reverse Bingo for iPhone Software, by trying to correctly guess which icons will fill up the iPhone’s home page. I have a few ideas, but there’s still time to suggest your own.What do you think? I really like to hear from readers. Comment 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! Submit to Reddit or Slashdot, or consider making a small donation supporting this site. Thanks!
  • 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!

  • Six Reasons Why Apple May Never Open the iPhone

    Daniel Eran DilgerThe history of the Office Wars provides interesting context for Apple’s software strategy with the iPhone today. While third party software development offers all kinds of tantalizing potential for the new mobile, there are a half dozen reasons why Apple may not ever deliver the iPhone fully open to third party development, following the model of gaming consoles.Office Wars 1 - Claris and the Origins of Apple’s iWork Office Wars 2 - Microsoft’s Outrageous Office ProfitsOffice Wars 3 - How Microsoft Got Its Office MonopolySoftware Lessons For the iPhone: 1997 - 2007.When Steve Jobs gained the opportunity to retake control of Apple in 1997, he immediately set out to build and assemble a software business for the Mac platform. Apple restarted serious development of QuickTime, much to the chagrin of Microsoft, which had targeted its sights on quickly destroying it to make way for monopolistic expansion of its Windows Media. [Microsoft's Plot to Kill QuickTime][How Microsoft Pushed QuickTime's Final Cut][Why Apple Failed][How CPR Saved Apple][Why Apple Bounced Back]In addition to repurposing NEXTSTEP as Mac OS X and buying and building a series of professional and consumer software suites, the new Apple also developed the iPod platform. The iPod used intuitive software to differentiate Apple’s hardware, launching the computer maker into a new market for sophisticated, data-driven consumer devices. Microsoft’s own efforts in consumer electronics have flopped miserably with the failures of its Handheld PC, Pocket PC, UMPC, Windows Mobile, Media2Go, Mira, SPOT, and Personal Media Center initiatives, among many others.[Apple’s NeXT Server Offensive on Microsoft][The Spectacular Failure of WinCE and Windows Mobile][Windows XP Media Center Edition vs Apple TV]Microsoft Outgunned in Software by a Hardware Maker.Microsoft was late to realize the software threat posed by the new Apple. Five major revisions and over thirty free updates to Mac OS X have ran circles around Microsoft’s capacity to deliver one desktop operating system software update and a couple service packs since 2001.[Leopard, Vista and the iPhone OS X Architecture]Apple also introduced three generations of iWork as an expanding productivity suite during the four year hibernation period Microsoft left since its last version of Office for Mac. Apple delivered support for Microsoft’s own proprietary OOXML file format on the Mac even before Microsoft itself could. At $79, iWork will eviscerate sales of the $400 Office for Mac, which has until now been a cash cow lazily ruminating for years between releases.This year, Apple also targeted and destroyed Microsoft’s fledgeling efforts to repurpose WinCE as a smartphone platform, seemingly overnight. That has given Apple a significant new platform in the iPhone, soon to be joined by the new iPod Touch. [What’s New in iWork 08][Apple's Secret iPhone Application Business Model][Curious Stuff About the New iPods]Six Reasons the iPhone Will Stay Closed.Will Apple give third party developers the keys to its new vehicle and allow them to drive off with the value it has created? It hasn’t yet, and there are a number of reasons to think that Apple won’t. Note that I am not expressing an opinion that the iPhone should be left closed, but rather simply presenting why I think it is unlikely Apple will ever open it up in the same way the Mac is open to any and all development.First, the company has lined up a suitable outlet for third party expansion via the standards based web platform available within Safari. That’s not enough to do everything developers want to do--it has serious constraints for creating games, for example--but it offers a good enough alternative to serve more than 80% of most developers’ needs.

[Mobile Disruption: Apple's iPhone and Third Party Software]
[iPhone Gremlins: Crashing, Security, and Network Collapse!]
Second, the company has developed and begun production testing of online software sales through iTunes, currently limited to 5G iPod games. This mechanism appears too sophisticated to simply be designed for a half dozen $5 games. Apple is quite obviously going to distribute other software through iTunes for the iPhone. If it were going to be open, there would be no need for such a secure software distribution system.

[Apple's New Dual Processor Game Console]
[Hacking iPod Games: How Apple's DRM Works]
Third, historical perspective suggests that once a solid platform has been established, a vendor can sell software as fast as it can deliver it without even trying very hard. Apple’s Claris, Microsoft’s Windows, and the game consoles from Sony and Nintendo all provide examples of this. The iPod’s success suggests Apple can establish a viable mobile platform without the need for software partners. It can handle software transactions as fast as it can sell iTunes songs. That’s big.

[Office Wars 1 - Claris and the Origins of Apple’s iWork] 
[Office Wars 2 - Microsoft’s Outrageous Office Profits]
[Office Wars 3 - How Microsoft Got Its Office Monopoly]
[Nintendo Wii vs Microsoft Xbox 360, Sony PlayStation 3]
Fourth, depending upon large third party developers has caused Apple--and Steve Jobs--some severe headaches. Microsoft's late 80s betrayal of the Macintosh led to Apple’s enslavement to Office, and induced CEO John Sculley to sign away broad intellectual property rights to Microsoft, which Microsoft then immediately used as a weapon against Apple.

In the mid 90s, Microsoft led Adobe, Macromedia and other large companies to abandon the Mac platform. In the late 90s, those same companies refused to support Apple’s new Rhapsody plans following the company’s acquisition of NeXT, forcing Apple to spend half a decade retooling the Mac OS, primarily so those developers could sell their existing apps to Mac users without much effort, even while they were earning fantastic software profits and delivering minimal innovation.

In other words, Apple’s technology game plan was delayed for a half decade so that Microsoft could sell its $400 copies of Office and Adobe could sell suites of its $500 and up creative applications, all while Apple did all the work in adapting its $99 operating system to run their Classic Mac OS code with minimal effort. 

Prior to returning to Apple, Jobs experienced his own betrayal and abandonment at the hands of partners--including IBM, HP, Digital, Data General, and Sun--related to NeXT and OpenStep. 

In all of these cases, the third parties were simply acting in their own best interests. With the iPhone, Apple will act in its own best interests. It will carve out a phenomenally powerful software platform for itself.

[Why OS X is on the iPhone, but not the PC: The History of NeXT]
[Office Wars 3 - How Microsoft Got Its Office Monopoly]
[Cocoa and the Death of Yellow Box and Rhapsody]
Fifth, open Application Programming Interfaces involve complex management and maintenance. This is not a problem unique to Apple; it exists for Microsoft and every other company that offers an API for developers to build upon. An API is an interfacing boundary between the software supplied by a vendor and the software supplied by third parties. 

Ideally, an API allows third parties to do everything they need very cleanly. That allows the vendor to make changes on their side of the API curtain without causing any compatibility problems for software on the other side. In reality, nearly every change and update has significant impacts for third party developers. The more complex and low level of an API being exposed, the more difficult it is to manage significant changes without introducing problems for third party partners. 

Apple has worked to develop objective APIs that are stable and resilient to internal changes, but if developers are unsatisfied with the level of performance or portability provided, they will work around the API boundary, almost guaranteeing that any significant changes made on Apple’s side will break their applications in the future. 

Microsoft has often accommodated such “bad programming? by expanding APIs and creating new ones, and lugging around a legacy of old APIs to retain broad compatibility with existing applications. The result is that it is very difficult for Microsoft to actually innovate, or to offer OS level enhancements that upgrade existing applications. 

This is particularly a problem for Windows Vista, which is hamstrung between the problem of providing entirely new hardware driver APIs on one hand while also maintaining a boatload of crufty legacy APIs on the other. It is absolutely the worst of both worlds. 

[Five Windows Flaws]
[Leopard vs Vista 5: Development Challenges]
Sixth, as is the case with software APIs, closed hardware platforms offer a vendor open flexibility for future expansion, portability, and upgrades. 

With the Xbox, Microsoft didn’t provide a wide open set of APIs for developers, only a subset for building very similar types of games. This closed API allowed Microsoft to move the console from Intel to PowerPC hardware in the Xbox 360 without extreme problems, something the company was unable to maintain earlier when it tried to deliver Windows NT for various hardware platforms in the late 90s. 

Apple has already benefitted from the flexibility of a closed hardware platform on the iPod. Had Apple allowed developers to write applications for the iPod, it would have to string along support for those old applications across every new generation of the iPod. Having to do that would complicate Apple’s own efforts to deliver new iPods. 

Additionally, customers would be upset with Apple’s iPod if the apps they downloaded crashed, installed spyware, or caused performance problems. While a rogue Mac app isn’t likely to drain a laptop battery down dead, power management is far more critical on handheld mobile devices like the 11 mm thick iPhone. 

Given that many consumers are already flummoxed by the reality that batteries wear out after a few years, imagine their rage at finding out that Apple allowed them to install a some worthless Tamagotchi pet that destroyed their battery early. 

Similar problems plague Palm OS and Windows Mobile devices. In particular, Microsoft’s attempts to provide a “one size fits all? solution and broadly license it to hardware developers results in API constraints that limit supported screen size resolutions, break compatibility with existing versions of applications, and severely limit the power management performance of those devices and their ability to deliver acceptable battery life. 

If there were any meaningful installed base of Windows Mobile phones, it would also be plagued with spyware and viruses, just as Windows is on the desktop. 

[Inside the iPhone: UI, Stability, and Software]
[Device Problems In Search of a Solution]
[David Sessions Tries to Milk iPhone Battery Panic in Slate]A Safe API Boundary for Third Party Development.The simple solution to all these issues is to not offer a custom, wide open API at all, and instead leave third party developers to build applications that make use of open web standards. Nothing new to learn, no barriers to adoption, no proprietary development tools to maintain, no pleading with developers to support a new platform that remains unproven in the marketplace, and no third party crisis to manage when the hardware and software are significantly upgraded.No API, no problem! Hackers can discover how to install tools and handy mini-apps, but Apple’s next software update or hardware revision won't have to figure out how to maintain compatibility with those hacks. That allows the hackers to hack without holding things back. Meanwhile, Apple can reserve the right to offer highly integrated applications of its own that take full advantage of the underlying system without revealing or sharing its intellectual property secrets with third parties that may choose to use those secrets against it--just as Microsoft did to Apple with Windows in the late 80s, or as Sony did to Nintendo with the original PlayStation just a few years afterward.[Mobile Disruption: Apple's iPhone and Third Party Software]Closed Development Involving Third Parties is Not Open.Incidentally, this is the same closed model that resulted in great success for Microsoft and Sony after they betrayed and then supplanted their former partners. Microsoft set up the illusion of an open, developer-friendly platform with Windows, but then used its home field advantage to plot out the assassinations of any and all of the potential rivals it didn’t want to compete against: WordPerfect, Lotus, Ashton-Tate, Borland, Netscape, Sun, and today’s targets such as Google and Symantec.The unsurprising result was that Windows users ended up using Microsoft’s Word, Excel, Access, Fox Pro, language tools, web browser, media software, desktop search, anti-virus, spyware management, etc ad nauseam. With Windows users completely enslaved to Microsoft’s own applications, it was easy to erect significant barriers to prevent the emergence of any new competitive applications from rivals. Clearly, Windows is only an “open platform? in areas where it suits Microsoft. Further, Microsoft’s idea of who a “competitor? is can change. For example, Windows desktop search wasn’t a rival feature for Microsoft to kill until it decided it wanted Google’s business.[Office Wars 3 - How Microsoft Got Its Office Monopoly]Windows Enthusiasts’ Slavery to a Vicious Master. Whether Microsoft’s closed Windows platform is a bad thing is a matter of debate; Windows Enthusiasts celebrate their enslavement. It is my opinion that Microsoft’s closed Windows platform isn’t bad simply because it is closed, but rather because Microsoft’s insatiable greed is holding back innovation that would otherwise flourish. One example is Microsoft’s Internet Explorer browser, which rapidly advanced until Microsoft destroyed Netscape. After that, it went into maintenance mode hibernation and didn’t budge until Firefox began to threaten Microsoft’s position years later. That’s anti-consumer; Microsoft won’t do anything for its enslaved users until a would-be savior threatens to set them free. Microsoft isn’t bad because it is closed; it is bad because it is disgustingly greedy. Windows Enthusiasts need to stop deluding themselves into thinking that they live in a free world of an open platform. They are slaves, and their master is not only vicious, but also incompetent and has no taste. [Safari on Windows? Apple and the Origins of the Web][Apple in the Web Browser Wars: Netscape vs Internet Explorer][The Web Browser Renaissance: Firefox and Safari]Closed Without Pretense.At the same time, it is possible to voluntarily join a closed platform and benefit from its advantages. Nintendo carved out a closed video gaming empire that required third party developers to pay it licensing fees in order to develop any games to sell for its system. Nintendo’s closed business model worked better than Atari’s with the 2600, which had earlier allowed third party games developers to glut the market with bad games, resulting in the video game crash of 1983. Consumers were left thinking that home video games were done to death and would never recover.Sega, Sony, and Microsoft’s Xbox group have all similarly managed closed gaming platforms to deliver high quality expectations, even subsidizing game consoles to establish user interest. The only differences for Apple’s closed iPhone may be that:Apple’s iPhone hardware sells at a sustainable profit without a desperate subsidy, removing risk and allowing for regular feature upgrades. 
Apple is likely to use software downloads as a way to integrate the iPhone into Mac hardware sales and its online services, rather than simply trying to make a killing selling $50 to $75 game software titles as the console makers do.[Mac OS X vs Linux: Third Party Software and Security]Software as a Great Differentiator.By offering free or low cost software in the model of $5 iPod games, Apple will be able to use its closed platform to deliver software designed to:attract more iPhone and iPod Touch hardware buyers.earn iPhone mobile service revenue fees.earn commissions from WiFi iTunes sales and related deals. direct new iPhone users to iTunes and Apple TV.draw attention to the Mac, which will offer iPhone integrated features Windows does not. Microsoft does some of the same things with Windows Mobile, which ties into the company’s Windows Server products--including Exchange Server--and is also deeply integrated with the desktop sync services of Windows and its Office applications. The problem for Microsoft is that it does not sell phones or make money on service revenues as Apple does. Microsoft charges expensive client access and software licensing fees, but still can’t make a sustainable profit on its Windows Mobile business. It’s also stuck with lame vendors such as HTC, which make poorly integrated hardware that is embarrassing to use. Microsoft could make its own phone, but like the Zune it would alienate its existing hardware partners; further, the Zune disaster indicated that hardware sales isn’t a core competency of the company anyway. [Phone Wars: iPhone vs TyTN, Treo, Pearl, E62, P990, Q][iPhone Sales vs Zune, Palm, RIM, Symbian, Windows Mobile]Selling Hardware with Software vs Selling Software Licenses.Using software to sell hardware fits in with Apple’s past and present use of free or low cost software to differentiate the Mac. In the distant past, that included HyperCard and QuickTime; today it includes the shareware-priced but highly regarded iLife and iWork apps. The full version of Mac OS X costs $129, while Microsoft’s Ultimate Windows Vista is an absurd $400, the same price as an iPhone!Apple’s strategy of using low cost, high quality software to differentiate its hardware plays well against the fact that consumers simply don’t want to pay for software, while they think nothing of paying big money for desirable hardware. Nobody would pay much for an iPod “OS? or a software music player, but millions of people have paid hundreds of dollars for an iPod.That principle has worked in Microsoft’s favor in the past, as it hides the cost of Windows by invisibly bundling it into PC sales. However, its recent fantasy that consumers will widely upgrade their PCs to more expensive versions of Vista indicates Microsoft is highly delusional. Pro-Microsoft wags can chart out their predictions of “impressive Vista adoption? based entirely upon OEM bundled copies, but consumers don’t want it, and no significant number of people are going to pay big money to upgrade to the $400 Vista Ultimatum. [Windows 95 and Vista: Why 2007 Won't Be Like 1995]The Commodity Future of PC Software.What will happen instead is an increasing commoditization of the consumer PC and its software, driven towards standards by an industry that demands interoperability. Microsoft couldn’t hold back the web with its proprietary MSN a decade ago, and companies that once pushed Windows are now behind Linux, including Novell and IBM. PC OEMs are also rethinking their unilateral relationship with Microsoft as they struggle to survive in the shadow of Microsoft’s vast profits. Rather than paying $400 for a PC with a $50 OEM copy of Windows running IE and Outlook, nagging you to verify your software as Genuine and to upgrade to the $400 version of Vista and to hand your credit card number to the dancing paperclip recommending a subscription to Windows Live OneCare terrorism protection, the $250 PC of the near future will come with a standards based web browser and email client. It will be called an iPhone, and it won’t run Microsoft Office.What do you think? I really like to hear from readers. Comment 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! Submit to Reddit or Slashdot, or consider making a small donation supporting this site. Thanks!

  • Office Wars 3 - How Microsoft Got Its Office Monopoly

    Daniel Eran DilgerOffice Wars 1 - Claris and the Origins of Apple’s iWork Office Wars 2 - Microsoft’s Outrageous Office ProfitsOffice Wars 3 - How Microsoft Got Its Office MonopolyMicrosoft’s Office monopoly gives the company more revenues and delivers nearly as much profit as its Windows software. How did it gain such a powerful position in productivity applications? The history of Office is rooted in decisions Apple made in the 80s with the Lisa and Macintosh, and also has an interesting correlation to Apple’s iPhone strategy today.The Origins of Office.While Microsoft has overwhelming power in desktop productivity applications today, it entered the market late. In the early 80s, Microsoft principally sold language software and struggled to license copies of AT&T’s Unix under the name Xenix. In 1981, Microsoft teamed up with IBM to license a copycat version of CP/M as the DOS for IBM’s new PC. Microsoft didn’t really get started in applications until Steve Jobs approached the company that same year with a proposal to develop for Apple’s new Macintosh.Entrusted with prototype Mac hardware and inside access to Apple’s development tools, Microsoft made an agreement with Apple in 1981 not to ship any mouse-based products of its own until a year after Apple introduced the Mac. In exchange, Apple promised to give Microsoft a rare opportunity to enter the competitive desktop applications market using its entirely new Mac platform as a launching pad.[SCO, Linux, and Microsoft in the History of OS: 1970s][SCO, Linux, and Microsoft in the History of OS: 1980s]Software Sells Systems!Prior to the Mac, Apple had released the Lisa as its first graphical desktop computer. Since developing new graphical apps for the Lisa was very different and required special training, Apple delivered its own complete productivity suite for the Lisa. It planned to open up the Lisa platform to third party development at some point after the initial launch, but the immediate focus had been to deliver a unique set of applications to demonstrate the power of Lisa’s new graphical interface.Recalling the software focus of the Lisa development team, reader Jim Hoyt emailed me several months ago in response to “Why Apple Bounced Back,? an article crediting Apple’s recent internal software development efforts with a large role in the company’s turnaround over the last decade. Hoyt wrote, “In 1979, John Couch, the soon-to-be head of the Lisa project, was in charge of all software at Apple Computer. He commissioned this poster: Software Sells Systems.? I’ve been meaning to publish the otherwise long since lost to history poster, so here it is, belatedly. Thanks Jim![Why Apple Bounced Back]Apple Delivers Lisa Suite Seven Years Ahead of Microsoft Office.The poster’s premise was obvious: the Lisa wasn’t going to sell itself; it needed practical software applications to usher in the future of the graphical desktop. Apple developed an entire suite of seven productivity applications that shipped with the Lisa system in 1983, including word processing, spreadsheet, database, drawing, graphing, project management, and terminal emulation programs. It was seven years later before Microsoft would first package its Word, Excel, and PowerPoint applications together as Office 1.0 in 1990. In his February 1983 review of the Lisa for Byte magazine, Gregg Williams concluded: “As you can tell, I am very impressed with the Lisa. I also admire Apple for deciding to make the system without being unduly influenced by cost or marketing constraints. The Lisa couldn’t have been developed without such a deep commitment, and no other company I can think of could afford such a project or would be interested in doing it this way (the Lisa project reportedly cost over $50 million and used more than 200 person-years of effort!). In terms of the actual, as opposed to symbolic, effect it will have on both the microcomputer and the larger-computer market, the Lisa system is the most important development in computers in the last five years, easily outplacing IBM’s introduction of the Personal Computer in August, 1981.?A year later, Lisa ended up being replaced by the much less expensive Macintosh, which delivered much of the Lisa’s functionality at a quarter of the price. However, the Mac did not include the Lisa’s expensive megabyte of RAM, its hard drive, or its productivity application suite. The Mac only shipped with a word processor and painting tools.Why Apple didn’t port its Lisa applications to the Macintosh is a confounding riddle, because it had more than a half decade of opportunity to do so. The main reason for this was a paranoid fear of alienating outside developers, along with jitters related to IBM’s rapid poaching of the desktop computing world after the arrival of its PC in 1981.[“The Lisa Computer System? Reprinted from Byte, issue 2/1983] [The Lisa, Apple's First GUI-Based Computer System - VAW][How Apple Keyboards Lost a Logo and Windows PCs Gained One]Apple’s Lisa vs the Third Party Mac Platform: 1980 - 1984.Competition inside Apple between the Lisa development group and the Macintosh team led to a different software strategy for the Mac. Since the smaller Mac group didn’t have the resources to develop a full suite of applications in advance of its launch, it planned to leverage third party development in the same way as the Apple II had.Sales of Apple II computers had exploded in 1979 with the release of Dan Bricklin’s VisiCalc spreadsheet software. That success was a large reason why IBM decided to get involved in the microcomputer business with the PC in the first place. It wasn’t until 1984 that Apple began making lots of money selling AppleWorks, its word processing, spreadsheet, and database package for the Apple II. It continued to sell the software with only limited updates well into the early 90s.Apple management failed to see the potential for delivering its own suite of Mac applications as it had on the Lisa, and as it very profitably would later do for the Apple II. Instead, it became increasingly enamored with the idea of partnering with third party software developers and delegating away the work--and the profits--of creating its own Mac software. Motivated by fears of inhibiting a third party software industry like the one that had grown up around the IBM PC, Apple intentionally stifled its own internal software development efforts and later spun them off into the Siberian gulag of Claris. That move would prove to be a devastatingly expensive mistake that would nearly destroy Apple over the next decade.Incidentally, three of the most important products Apple would release during that decade of decline were software products: the profitable AppleWorks for the Apple II in 1984.the free 1987 HyperCard for the Mac.the free 1991 QuickTime for the Mac.[HyperCard: Apple and the Origins of the Web][1990-1995: Planting Software Seeds][QuickTime: The Secret Weapon Inside iTunes]A Fearsome Future VisiOn for the PC: 1981 - 1983.Another contributing reason for Apple’s rush to embrace third party developers on the Macintosh may have been related to the fear of VisiCorp’s new mouse-driven VisiOn graphical desktop environment. VisiOn originally appeared on the Apple III in November of 1981, but the complete commercial failure of that new machine after the delivery of IBM’s PC prompted VisiCorp to announce moving its support to the PC in 1982, with a promised release target of mid-1983. Apple was still scrambling to release the Lisa and the Mac, both of which had slipped repeatedly.While clumsy, slow, and expensive--the base VisiOn software and a mouse cost $790, each application cost between $250 and $400, and it required a $5000 hard drive upgrade on top of a $2000 PC--VisiOn was backed by the legendary VisiCorp, the company that had helped launch the Apple II to fame with VisiCalc. VisiOn also tapped into IBM’s “up is down? PC, which despite its high price and low level of performance and innovation, had cut deeply into Apple’s business expansion plans, almost entirely due to IBM’s reputation and its monopoly position in business computing. After witnessing its first big failure with the Apple III, and then seeing a tepid response to the $9,995 Lisa in 1983, Apple was no doubt very concerned about IBM’s PC being converted into an ugly frankenstein Mac knockoff with that $7,500 VisiOn upgrade bolted on, cheered on by a press giddy at the prospect of being bamboozled by IBM’s overpriced and under delivering PC.The only way to compete with the threat of such a graphical system for the PC would be to deliver the new Macintosh as quickly as possible at a much lower cost with lots of applications from a variety of third party developers. Fortunately for Apple, VisiOn also slipped several months and wasn't delivered until the end of 1983. Right up until it completely fizzled, the press hailed VisiOn as a promising competitor to Apple’s Lisa and the forthcoming Macintosh.By 1983, VisiCorp had fallen apart; its star development manager Mitch Kapor had left to found Lotus Development. Kapor’s new spreadsheet product, Lotus 1-2-3 for the DOS PC, destroyed the remains of VisiCorp and its VisiOn.[VisiCorp Visi On - Toasty Tech][1980-1985: 8-bit Platforms]Frying Pan to the Fire: Apple Runs to the Arms of Microsoft: 1981.Finding developers willing to commit to investing in Apple’s next new platform was difficult after the failure of the Apple III and the wildly successful launch of the PC. Apple later found that its developer relations would suffer at the release of the “no other software needed? Lisa. For the Mac, Apple decided to copy the PC model by directing the majority of its efforts into courting third party developers and downplaying its own software releases, which were only intended to serve as basic placeholders. Even so, many PC developers planned to take a ‘wait and see’ approach to supporting the Macintosh.Hoping to prime an early and explosive business success for the Macintosh in the same way VisiCalc had launched sales of the Apple II, Steve Jobs made plans with Microsoft to deliver a graphical Mac interface for its struggling Multiplan--a VisiCalc spreadsheet clone--and a new Chart application.Microsoft had also secretly begun another Mac app initially called MultiTool Word, based on the Bravo word processor developed by Xerox PARC’s Charles Simonyi and Richard Brodie; Microsoft hired both in 1981. The company didn’t tell Apple about its new word processor project because the Mac team had already started developing a word processor for the Mac called MacWrite.[A Rich Neighbor Named Xerox - Folklore.org][An Office User Interface Blog - Microsoft’s Jensen Harris]Apple’s Problematic Partnership with Microsoft: 1981 - 1985Next to IBM, Apple was among the first companies to realize that getting into a business partnership with Microsoft was a really bad idea. Throughout 1983, Microsoft employees began intense discussions with Apple about how the Mac system software worked internally, involving issues unrelated to desktop application development. The reasons for this became obvious when Microsoft made a surprise pre-announcement at the Comdex trade show in November 1983 of a clone of Apple’s Mac environment for the PC called Windows, along with the release of a text-based Word for DOS using a mouse. Apple had previously worried about VisiCalc’s independent VisiOn appearing for the PC, but now its own partner had taken its internally developed graphical desktop work to deliver a competing product on IBM’s platform. Microsoft had discovered a loophole that allowed it to ignore its exclusive agreement with Apple because the contract had tied the year-long waiting period to the Mac’s planned ship date in 1982; that contract date wasn’t updated as the project slipped into 1984.It turned out that Word for DOS wasn’t very popular, since DOS PC users didn’t see much benefit from only using a mouse with a single application. It also turned out that Microsoft couldn’t deliver on its promise to ship Windows 1.0 by early 1984; it wasn’t actually available until 1985, and even then was a complete joke of a product and fully unusable. However, the problems Apple would suffer for trusting Microsoft were only just getting started. Windows 1.0 wasn’t much to look at, but it did offer an advancement beyond the neanderthal text interface of Word for DOS. Apple also had reason to worry when it found Microsoft was directly collaborating with IBM in 1985 to deliver a new DOS replacement called OS/2. [1990-1995: The Race to Deliver The Next New Platform][Mac Office, $150 Million, and the Story Nobody Covered]Apple Grows Dependent upon Third Party Software: 1985 - 1990.Apple’s partnership with Microsoft continued to worsen. Microsoft finally shipped its spreadsheet for the Mac in 1985, but threatened to also release it for the PC as well, prompting Apple CEO John Sculley to sign away rights to a variety of Mac system software details to Microsoft in 1985 in exchange for exclusive Mac development of the graphical Multiplan for two years. Microsoft’s Multiplan and Chart applications for the Macintosh were among the strongest software features Apple touted in its 1984 advertising. (Click to view full size).A very young Bill Gates appeared next to Mitch Kapor of Lotus Development in Apple’s Mac ads to observe, “To create a new standard takes somethings that’s not just a little bit different. It takes something that captures people's imaginations. Macintosh meets that standard.? Were he not trying to sell Windows Mobile today, he might say the same of the iPhone!Sculley had been arrogantly dismissive of Bill Gates’ July 1985 suggestion that Apple work quickly to broadly license its Mac technology to Northern Telecom, Motorola, and AT&T. Instead, Apple sought to retain control of the unique Mac desktop as a way to sell its hardware.At the same time, Apple grew increasingly reliant upon Microsoft to deliver updates to its applications for the Mac, and worried about threatening any of its third party Mac developers with its own internal application software efforts.However, in 1984 Apple had released AppleWorks for the Apple II. That program rapidly became the top selling software title of any computer platform, despite Apple’s minimal efforts to market it. It was nearly an embarrassment for Apple, which wanted to push the graphical new Macintosh, not a text-based 8-bit program. By 1987, Apple had spun off its own apps--including AppleWorks, MacWrite, MacDraw, and MacPaint--into the Claris subsidiary. Claris went on to profitably develop and acquire a suite of Mac productivity apps, but operated at an arms’ length distance from Apple. By 1990, Sculley realized the vast profit potential in application software. Apple had two solid platforms: the Apple II and the Mac. The company’s minimal efforts to market any software for them was clearly a huge mistake. Sculley subsequently decided to retain Claris as part of Apple rather than spinning it off, but that late decision shattered the subsidiary because its employees and managers had been given the expectation that a Claris IPO would make them rich. Many left in disgust.[Office Wars 1 - Claris and the Origins of Apple’s iWork]Microsoft Becomes an Applications Company: 1985 - 1989.At the same time, Microsoft’s graphical Multiplan for the Mac--which ended up being combined with the Chart app and renamed as Excel in 1985--became a huge seller for Microsoft. In contrast, the textual DOS version--which retained the Multiplan name--couldn’t compete with the top selling Lotus 1-2-3 on the PC side.Two years later in 1987, Microsoft’s deal with Sculley expired and the company released Excel 2.0 for the PC, along with Windows 2.0, which copied more of the Mac desktop, including the basic ability to display overlapping windows. No OEMs shipped Windows 2.0 on their PCs, but anyone buying the new Excel got a copy of Windows and a taste of the graphical Mac environment, albeit with Microsoft’s garish colors and its horrific MDI-style interface.Apple Sues to Stop Graphical Copycats, But Only On the PC: 1985 - 1988.While a number of companies delivered graphical environments in the pattern of VisiOn for various computer systems of the time, Apple was only threatened by those that promised to deliver the Mac look on the PC.For example, Apple ignored Berkeley Systems’ mouse-based, windowing GEOS environment, offered initially for the Commodore 64 and later Apple’s own Apple II systems.However, when CP/M maker Digital Research introduced its GEM/1 for the DOS PC, Apple sued and won an injunction that forced the company to remove certain features Apple had originally developed for the Mac, the most obvious of which was its use of graphics regions to draw sophisticated overlapping windows. At the same time, GEM/1 was also being sold for the 1985 Atari ST, but Apple completely ignored that product, enabling Atari to deliver a system so similar to the Mac it was commonly called the Jackintosh, after Atari CEO Jack Trammell. Apple also ignored overlapping windows in the 1985 Commodore Amiga, and a similar graphical desktop in the 1987 RISC OS developed by Acorn Computers. Apple was certainly aware of the British Acorn’s RISC OS, as the two companies had partnered to form ARM in order to develop a new generation of RISC based processors powering Acorn’s RISC PC and later, the Newton. Those same ARM processors now power iPods, the iPhone, and the vast majority of all mobile devices. [Origins: Why the iPhone is ARM, and isn't Symbian]However, Apple went ballistic upon the release of Microsoft’s Windows 2.0 in 1987. One reason was that Microsoft was pointedly using the product as a way to move its Mac applications to IBM’s PC, a move Apple correctly feared would quickly erode the unique value of the Macintosh. Additionally, Microsoft was also describing Windows as the basis of a new interface for IBM’s promised OS/2. Apple was livid that the trusted partner it had launched into the applications business would immediately sell it out and migrate those same applications to directly benefit its main hardware competitor. Despite the fairly insignificant sales of Windows 2.0, Sculley’s Apple sued Microsoft in 1988 over the use of Mac software details it had taken from Apple in its 1985 agreement. It also sued HP over a Windows 2.0 add on pack called NewWave, which supplied additional Mac-like features to the PC. Meanwhile, sales of Excel on the PC gradually began to grow and Microsoft worked increasingly hard to replace its Mac partner and then destroy it, using Windows as a tool to port its Mac applications to the PC instead. [Apple's Billion Dollar Patent Bluster: Patent vs. Copyright]Apple Loses Jobs, Opportunities: 1986 - 1988.In 1986--as Apple’s panic over Microsoft moving its Mac apps to the IBM PC was just getting started--Steve Jobs’ plans to rapidly move the Macintosh into the business and server arena were getting shot down by the more conservative minded Sculley. Apple’s board feared that increased investment in the Macintosh might spread the company too thin.[Steve Jobs and 20 Years of Apple Servers]Jobs subsequently left Apple in frustration to form NeXT, Inc, and develop his own ideas for business oriented workstations. Sculley replaced him with Jean Luis Gassée, who shared Sculley’s vision for dabbling in impractical technology ventures like the Newton and keeping Mac models configured for high end markets.Apple continued to make outstanding profits from increasing sales of the Mac and continued sales of the Apple II, but the company had made a grave mistake in ignoring and avoiding the software business. Even worse, it was now dependent upon a rival company to maintain key software titles for the Mac.Apple was also losing key engineering talent to Jobs’ NeXT, which by 1988 was delivering the first release of what Apple itself should have been working on: its next generation of hardware and software. [Newton Lessons for Apple's New Platform][Why OS X is on the iPhone, but not the PC: The History of NeXT]Sculley’s Apple Bungles Office Applications.While Sculley’s Apple fought Microsoft’s Windows in the courts, it did little to effectively compete in the marketplace, either with the Mac as a platform or in the applications arena to take on what would become the Microsoft Office suite in 1990. To deliver Office, Microsoft simply paired Word and Excel with PowerPoint, a Mac presentation application Microsoft acquired in 1987. Had Apple simply ported its Lisa applications to the Mac, it would have had a head start of several years to develop and refine its own applications suite, and could have maintained them as unique to the Mac without giving away its crown jewels to Microsoft in 1985. After ten years of trying, even Microsoft could eventually deliver a good enough copy of the Mac with Windows 95 in late 1995. After that, Microsoft pulled the plug on Office development for the Mac and didn’t release another update until 1998.[Office Wars 1 - Claris and the Origins of Apple’s iWork]Apple’s Squandered Opportunity in Software Sales.The bizarre thing was that Apple was making money selling AppleWorks on autopilot, and continued to do so from 1984 into the early 1990s. Additionally, the new ClarisWorks for the Mac easily captured the top spot in Mac software sales from Microsoft’s Works within its debut year in 1991. Even so, Apple did little to capitalize upon the discovery that software would indeed sell systems, just as Couch had foreseen back in 1979. Apple had a printing press for creating money, but simply left it idling while Microsoft delivered low innovation software titles and raked in millions of dollars in Mac software revenues. Sculley’s Apple essentially sat back and granted Microsoft full opportunity to clean out its entire business model without a fight, hoping that the law would rush in to correct the inequities at some point in the near future. Instead, the court deliberated for a tech eternity until 1994, and then threw out Sculley’s “look and feel? lawsuit, largely on the basis that Sculley had earlier granted Microsoft limited rights to Mac ideas back in 1985 in his desperate bid to keep Microsoft as a Mac developer. The bitter irony was that between 1985 and 1995, Microsoft needed the Mac at least as much as Apple needed Microsoft. Even in 1997, Steve Jobs could get Microsoft to agree to a half decade of continued development of Office for the Mac by simply adding Internet Explorer to the Mac desktop. Jobs turned down the hardball demand that Apple kill QuickTime, and even got a public relations coup out of the deal by having Microsoft announce a $150 million investment in Apple.Sculley’s penny wise, pound foolish conservative greed destroyed Apple and directly transferred the vast potential wealth of value Apple had originated at great expense for its 1983 Lisa graphical office suite to Microsoft, which subsequently ran with it and deserted the company. [Mac Office, $150 Million, and the Story Nobody Covered][Apple’s NeXT Server Offensive on Microsoft]Microsoft Betrays IBM and Uses Office Against OS/2.Apple wasn’t the only partner Microsoft exploited, turned on, and then tried to drive out of business. The earliest and most obvious example was IBM, which had launched Microsoft into significance as a reseller of DOS. Microsoft betrayed IBM in the development of OS/2, first by pulling out of the operating system partnership, then by canceling Office for OS/2 after shipping an initial version for it in 1992. IBM later bought up Lotus and worked to compete against Microsoft’s growing influence with Office. Microsoft responded by using its new monopoly positions to punish IBM in various moves documented in the Microsoft monopoly trial. That story follows in Office Wars 4. Using the Office Monopoly Against NeXT.Jobs carried lessons learned from watching the implosion of Apple under Sculley to NeXT. His initial goal for NeXT was to build a software platform. However, nobody was shipping hardware up to the task of running an advanced operating system, so NeXT began following the business model of Apple, selling new hardware with advanced software.While Jobs had found it challenging to find software partners for the Mac at Apple, the task was even more difficult at NeXT, which Apple had forced into the ultra high end of the workstation market using a non-compete agreement. NeXTSTEP pioneered advanced rapid development frameworks to make it easier for third parties to deliver software for the new system. When Jobs discovered that Lotus was working to deliver a new spreadsheet paradigm for OS/2, he gave the Lotus team a NeXT system and got involved in refining the software to show off the features of his new platform. In contrast, Microsoft used the productivity applications monopoly it had been handed by Apple to impede adoption of NeXT. When asked about writing software for NeXTSTEP, Microsoft’s Bill Gates famously fumed, “Develop for it? I'll piss on it.? Gates also announced plans to immediately deliver his own advanced operating system with object oriented development frameworks called Cairo, which turned out to be a vaporware lie Microsoft repeated from 1991 until NeXT was acquired by Apple in 1997.[1990-1995: Microsoft's Yellow Road to Cairo]Microsoft’s Murderous Partnerships.Microsoft helped to ensure that neither NeXT nor OS/2 could acquire a broad enough computing platform to drive a self-sustaining software business. Apple was able to maintain a struggling niche platform on the Mac, but fears of stepping on third party developers’ toes actively prevented the company from actually building on that potential until the late 90s. Ironically, Microsoft did just that, by developing its solo PC platform with Windows and then using it to destroy third party developers it viewed as competitors. By tying its Windows and Office products together, Microsoft could strangle its own former partners--the top developers of MS-DOS applications--including WordPerfect, Lotus’ 1-2-3, database and developer products from Ashton-Tate and Borland, and really every major developer on the PC that in any way challenged Microsoft.Microsoft’s coldly calculated murder of every rival DOS application developer and later many of its Windows developers, from Novell to IBM and Sun to Netscape, is an oddly public fact treated as a taboo secret by Windows Enthusiasts, who avoid all mention of it as they talk about how Apple “can’t work with partners? in the rich, supportive way Microsoft supposedly has. Any competition between Apple and third party developers--even with shareware programs--is paraded through the insufferable blogs of ZDNet and the pages of IDG’s InfoWorld/PCWorld/Computerworld and described as unconscionable conduct. This is from writers who all witnessed first hand Microsoft’s massacres of any and all “partners? the company decided no longer suited its fancy. Have these wags all been brainwashed, or are they just lying for money? As a side note, the Office Wars and Microsoft’s monopoly position in applications provide interesting insight into how Apple is deploying its iPhone software strategy, which the next article will examine.What do you think? I really like to hear from readers. Comment 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! Submit to Reddit or Slashdot, or consider making a small donation supporting this site. Thanks!

  • August 2007 Zoon Awards for Technical Ignorance and Incompetence

    Daniel Eran DilgerIn an effort to recognize the spectacular efforts of individuals and organizations promoting the regression of human achievement in the field of technology, a series of nominations await your vote to determine the recipients of August 2007 Zoon Awards.Meet the Zoons.Segregated by color, the various Zoons highlight the world's absolute worst in small minded ignorance, paid to say propagandism, and blind devotion to products without merit.The Pink Zoon is awarded for a spectacular effort in fear-based propagation of uncertainty and doubt, or efforts to infect headlines with false information with the primary goal of preventing innovation, competition, and the emergence of new ideas, or simply to make a quick profit.
The White Zoon is awarded for the blinding glare of a shiny blank brain, particularly when such ignorance is presented with authoritarian emphasis by an individual or news source operating well outside its abilities. This award may also be assigned to a company or organization in recognition of epic failure.
The Brown Zoon is awarded for squirting extraordinary amounts of intentionally noxious misinformation, whether dredged from an impacted recollection of twenty years ago, sucked from the trusty bucket of canned responses, or simply invented as needed to create an intolerable outburst of stink.These should not be considered as first, second and third placements, as each tie for an equal standing in the Zoon Hall of Shame. It is also possible to award multiple parties for the same award, either as shared participants or, in the case of an unclear majority vote, tied nominations.Meet the Zoon Nominees.As one might imagine, determining the most fitting recipient might be difficult given the wide range of potential candidates standing in line. Here's a brief background on the nominations for August.Troy Wolverton, San Jose Mercury News.A writer for the Street and most recently, the San Jose Mercury News, Wolverton always manages to dig up an unattractive headline for any news related to Apple. A series of articles documented his negative spin and inaccurate reporting, particularly when the subject related to Apple.Wolverton promised me and other readers that he would answer the questions related about his shoddy journalism record, then cowardly ran away. He also wrote emails to RDM readers assuring them that he was only ever honest and unbiased, and that RoughlyDrafted should be read with great suspicion.[10 FAS: 8 - San Jose Mercury News’ False Apple Scandal][Troy Wolverton Documents Faux Apple Shareholder Outrage]Wolverton is nominated for a White and Brown Zoon.Neil Cavuto, Fox News.While actually based on reports from the end of July, I wrote about Cavuto in August, qualifying his nomination for arrogantly complaining about how Apple purportedly over promised iPhone shipments it then failed to deliver. In reality, Apple didn't indicate any sales goals for its first weekend. Cavuto also confused AT&T authorization numbers with Apple's sales figures. Fox News subsequently corrected his comments to suggest that he hadn't made the error, but still failed cover up the core problem that Cavuto's entire rant been a specious bit of ignorant rambling delivered--rather hypocritically--with far too much arrogance than the subject required.Cavuto is nominated for a Pink and White Zoon.[10 FAS: 9 - Troy Wolverton, Neil Cavuto, and the Apple Stock Scandal]Jim Cramer, Scott Moritz and Brett Arends, the Street.After documenting how he would spin false information to manipulate the market as a hedge fund manager, Cramer praised his apprentice Moritz for publishing a string of articles dredging up or simply inventing false information about the iPhone with the intent to knock value from Apple and suggest that Apple's phone was not competitive, not selling as expected, and that Apple's deal with AT&T was an unprecedented deal earning unconscionable profits. Arends is thrown in for good measure after delivering similar work directly from the mouths of Street-savvy Verizon shill, Roger Entner of IAG Research.Cramer, Moritz, and Arends are nominated for a White and Brown Zoon.[More on Scott Moritz and the Jim Cramer Street Misinformation Engine][The Street's Flaccid Campaign Against the iPhone][Unraveling Anti-Apple Panic: the iPhone Launch Success]George Ou, ZDNet, CNET.Nominated in August primarily for his article misrepresenting typography technology and falsely portraying Mac OS X as incompetent in the area of text rendering, Ou deserves extra reason to earn your Zoon vote for failing to admit that he falsified his report, and instead attacking those who pointed out his error.[Tech: Zoon for George Ou]After posting the article detailing why he was wrong and establishing a pattern of his consistently inaccurate and tilted writing, someone who appeared to be Ou emailed me to say:“If you're gonna do a hit piece, at least do it accurately... I'm not going to get uptight about a little man like you chewing on my feet and I'm not even going to bother cursing at you for writing a blatant hit piece on me. It's not worth my time.?Assuming that the author was unlikely to actually be Ou, I did a search on the email and found an online comment from the same address mentioning being a former ballet dancer. To determine if the author was Ou or just simply a joker trying to get a response, I wrote back, “Hi George, What was inaccurate in my article? Are you really a ballet dancer??Ou tu?In reply, Ou wrote, “I was a professional Ballet dancer up till 2000 and I still try to perform now and then,? but didn’t note anything that was incorrect in the article. When I asked for the correction again, I got two emails, one insisting that, “The 'FreeBSD community' is essentially Sam Leffler. Sam pretty much wrote all that wireless code. Sam is an employee (contractor) of Atheros. Atheros is involved in that FreeBSD code.?The second said, “You don't even understand the fact that the same Atheros ‘team’ led by Sam Leffler that wrote Apple's wireless drivers is the same team that wrote the open source MadWiFi drivers for Linux and FreeBSD. The same wireless drivers Apple said there was no problem on had to be patched three times a month later. And here you are slandering me because I defended two researchers against a billion dollar corporation.“When you smear my photograph and slap a "SHILL" on top of it, that is slanderous and insulting. You're accusing me of taking payola which is a crime and only a ‘little man’ would slander someone like that. It's one thing to disagree with me or not like a certain piece I wrote, but smearing someone's photo with accusations of shill is nothing but the act of a coward. Unprofessional? There's nothing unprofessional about calling trash like you little and I'd say that to your face.?Pearls Thrown.How could a professional writer fail to understand his subject matter, fail to grasp basic logic, and then be so arrogant about it on top? I wrote, “George, I don't have to prove that people from FreeBSD did not contribute to Apple's driver. I never stated that, and it has no relevance to statements I made. You had to prove that Atheros did not deliver the driver, and that it came directly from FreeBSD without Atheros' involvement. That was the question, and your misunderstanding of the architecture of Mac OS X helped you to confuse the situation.“The truth is that Atheros contracted with an expert to port some of the FreeBSD code for use in its driver for Mac OS X, which only shares significant similarities with FreeBSD in its userland environment. Atheros had to deliver unique work for Apple to offer a working driver for Mac OS X, and paid a contractor to complete that work.“You maintained that Atheros simply wasn't involved at all, and that Mac OS X's driver just came from the FreeBSD repository. That was wrong. Your explanation of why this was the case was also wrong. It is clear you still do not understand the situation entirely. That's why you shouldn't be writing about it as if you are an expert, simply because someone told you something that sounded believable off the record. You don't understand the issues involved, but operate under the assumption that everything you think up as a plausible idea is also the truth. It isn't.“Slander, as noted in my article, is spoken. Libel is written. Just FYI. Also, a shill doesn't necessarily need to be paid, so calling you a shill isn't ‘accusing you of payola.’ Also, payola really only is illegal in broadcasting. There are plenty of people who are paid to say things, and nobody is arresting them. The company you work for largely serves advertisers; that isn't illegal, or all of CNET would be shipped off to jail.“There is nothing cowardly about pointing out that you are a shill and then documenting your attempts to spread misinformation in efforts to make Vista look good and Apple look bad. There is something very cowardly about fuming that you've been outed, and rather than apologizing and correcting your error, and then maintaining that you're simply better that others so your misinformation campaigns don't matter.“I don't have a little man complex, so repeating that doesn't really bother me. It does make it clear that you have some size issues in addition to your general lack of professionalism and technical incompetence.?To which Ou elegantly replied, “Go find yourself a bathhouse in the city where you belong. You have no business writing.? Using the same address, Ou responded to several other online sites defending himself and ignoring the errors of his article. How does Ou have a job? Ou is nominated for a Pink, White, and Brown Zoon, and his winning will also earn a Zoon for ZDNet and its CNET parent.Windows Genuine Advantage, Microsoft.After choosing a delightfully ironic name for its software DRM system, Microsoft then bungled its validation system for users worldwide. The hundreds of millions of PCs running Windows XP and Windows Vista phone home to Microsoft at regular intervals, but the company set up the system with a single point of failure. An inevitable failure prevented the company from maintaining resilience to downtime--something the company highly touts as an Enterprise feature of Windows Server--but it also highlighted the problem of validating software in general using a system that assumes guilt when there is any question in reaching the validation server. Windows users who tried to verify their genuine software had software features remotely turned off because of the WGA problems.[Tech: WGA the Dog]WGA is nominated for a White Zoon.Oliver Rist, InfoWorld, IDG.Suggested by reader Robert de Bie, Rist yesterday wrote an article titled “Does Mac OS X suck? Apple's desktop platform has impressive technical chops, but it falls short from a business perspective.?Never mind the sophisticated and professional headline, the real question is, did Rist back up his headline, or simply cower in a bed of second hand fear, uncertainty and doubt? No need to guess, really; this is InfoWorld, a rag primarily useful for its ads. No competent IT manager wastes much time reading the ramblings of such stuffshirt columnists.Rist brings up the idea that Mac OS X is really just Unix with some frosting, making it easy to coo about, but not really ready for real business. Unfortunately, Rist offers no basis for anything that he says. In fact, his headline and (forgone) conclusion don't even match what he writes in between. Under the subject of networking, Rist says, “OS X has an excellent networking client, both wired and wireless — due in large part to FreeBSD rather than anything coming out of Cupertino.? But wait, does FreeBSD write the Mac’s Apple File Protocol? Does it maintain Samba for Windows networking? Wrong on both counts. By spouting the dittohead myth that Mac OS X is just FreeBSD with an Apple logo, Rist has already established that he knows nothing about the subject he's pretending to be an expert in. He then says nothing else about networking, granting that Mac OS X has no real issues.Security Absurdity. On the subject of security, he says “It's a pretty secure system. Yes, ever since OS X has become more popular, attacks and breaches on the platform have become more numerous. And, yes, those numbers are high enough that if I were managing a portfolio of MacBooks I'd be installing anti-virus on them.? Rist linked his comment to another IDG article reporting on a Mac OS X worm threatened by the anonymous "InfoSec Sellout," which turned out to be a fraud. That's the extent of the acceleration in Mac OS X “attacks and breeches,? a crank call? There are yet no viruses for Mac OS X, and all the malware that exists is proof of concept ideas hatched in a lab. Strike two for Rist in trying to write about security issues. Even so, he concedes, “once the personal firewall is up and the AV installed, I'd fully expect to see far, far fewer security-related problems from my Mac clients than my Windows clients.?[10 FAS: 10 - Apple’s Mac and iPhone Security Crisis.]Many Words, Little Point.On the subject of reliability, Rist beats up Artie MacStrawman for insisting that Mac OS X apps never crash. He then provides some recollected figures for estimating how many times he has noticed a Mac app crash compared to Vista crashes. He passes by saying, “Apple's probably less crash-prone overall.?On the subject of software compatibility, Rist says Apple “treats third-party developers like the proverbial redheaded stepchild, which results in significantly fewer third-party software options for Apple users than Windows users,? then follows up with the genius, “When it comes to mission-critical, vertical-type business software, Windows clients far outnumber Apple clients. If they didn't, Macs would be populating a much larger number of corporate desktops.?How does this guy get work writing? By the end of page one, Rist had said nothing at all. On page two, Rist really gets going. He starts off referring to "Apple jihaders," as if he has a fundamentalist shock radio show rather than a column designed to inform IT managers. Rist says people don't want to retrain employees to use Macs, and then suggests that retraining users for the significantly different Vista would not be an issue. He gives the Mac a “grudging? pass again and moves to hardware. [Paul Thurrott's Merciless Attack on Artie MacStrawman]Mac OS X’s Hardware Features.He says that Gateway has more USB ports and a finger print scanner in the same form factor for less cost, without outlining his comments with any factual basis. He then complains that his MacBook suffered a hard drive failure after four months. “That's a pretty short time frame for serious hardware failure,? Rist wrote. It's odd that hardware issues are being outlined in an article about “why Mac OS X sucks,? but someone writing to an audience of experienced IT users should be aware that computing hardware--particularly hard drives--is most likely to fail in its first few months. Past that break in period, most hard drives typically have a relatively stable three year life span, after which problems become statistically more likely to occur. It's called the bathtub lifespan curve, because like the contour of a tub, it starts high, then drops low for a long stretch, then begins to rise again. Clearly, Rist doesn't know what he's talking about at all, even when complaining about consumer Mac hardware in the context of Mac OS X as a business operating system.Dude, You’re Being a Shill.After "passing" all of his categories, Rist then fails Mac OS X in “business orientation.? There are good and justified reasons for faulting Apple in the IT arena, but Rist doesn't mention a single one. Instead, he prattles on about Apple's consumer ads, and how they portray the typical Mac user with a “SOHO, I'm-cooler-than-you, coffee house image.? For all the dittoheads who like to repeat this idea, I'd like to remind you all that Dell's memorable mascot was a smirky pothead who couldn't finish sentences beyond, “Dude, you're gettin’ a Dell! (excited thumbs up).? That had no impact on Dell's Enterprise sales, because serious enterprise users don't make their decisions based on watching prime time TV and deciding whether they like the advertisements targeted at families. So please shut up about the Justin Long and John Hodgman Get a Mac ads. Enterprise Worthy Dell Pothead Vs. the Too Good for You Coffee Drinking Mac.Highly Unqualified.Rist is a “senior senior contributing editor? at InfoWorld. With this sort of incompetence and ignorance, it makes one wonder what kind of single celled organisms must pass for junior editors at IDC and its various ComputerWorld, PC World, and InfoWorld properties.While writing “a column devoted to running Microsoft technologies in medium and large enterprise environments,? Rist only notes experience in running a small Microsoft-oriented software business and writing for rags like Computer Shopper. That qualifies him as a Microsoft shill, but not as a columnist offering advice about ‘medium and large enterprise’ IT environments.Rist is nominated for Pink, White and Brown Zoons.Microsoft’s Pseudo-Philanthropy in New Orleans.Bob Emery notes that Microsoft is offering free software for hurricane-hit businesses in the devastated New Orleans area. However, in order to qualify, users have to sign up for a three year plan, of which Microsoft only covers the first year. A local paper noted “For the typical small business of 50 employees and 25 personal computers licensing Microsoft Windows Vista and the Office 2007 suite of programs, the free year can result in savings of as much as $12,050.?Of course, what that really means is that recovering small businesses will actually have to shell out $24,100 just for software licenses, in addition to buying computers capable of running Vista. One might think that a company earning $50 billion in revenues might be able to offer more than an advertisement to struggling businesses, particularly since software costs Microsoft nothing to deliver.[Microsoft gives free software to hurricane-hit businesses - New Orleans CityBusiness]Votes toward Microsoft's headline friendly, fake philanthropy will help the company earn its White Zoon for its WGA fiasco.Vote in the Forum and add your comments.Official awardees: Pink : George Ou, ZDNet, CNETWhite : Windows Genuine Advantage, MicrosoftBrown : George Ou, ZDNet, CNETWhat do you think? I really like to hear from readers. Comment 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! Submit to Reddit or Slashdot, or consider making a small donation supporting this site. Thanks!

  • Leopard and the History and Future of Mac OS X on PowerPC

    Daniel Eran DilgerHow long will Apple continue to support existing models of Macs in the latest version of Mac OS X? Previous versions of Apple’s OS have drawn the line for officially supported Macs based on practical considerations, rather than just being arbitrary or artificial. Here's what the past suggests for Mac OS X Leopard and the version that comes after it.The Post-Copland Crisis.Apple carried along official support for the 1986 Mac Plus through Mac System 7.5.5 in 1996. That established an expectation for Mac users that any new Mac System Software would be able to run across a decade long generation of old hardware. Further, Apple had only begun officially selling System 7 as a retail product a few years earlier; many Mac users continued to think of the Mac operating system as something that was available for free, as it had been in the past. That unreasonable support expectation combined with the sense of entitlement held by Mac users had helped to complicate Apple’s mid-90s failure to deliver Copland as a successor to System 7 between 1993 and 1995, and would continue to dog the company in its plans to provide a significant system software update after Copland was mothballed. Faced with the task of maintaining full backward compatibility for both existing applications and a wide range of hardware--but without any assurance that a significant number of Mac users would actually pay for the upgrade--it’s no wonder why Apple was stuck at System 7 for over a decade (Mac OS 8 and Mac OS 9 were only retoolings of the System 7 operating system released in 1991), and why plans to completely overhaul System 7 with Copland and Gershwin failed.If Apple had the luxury of operating outside of a real market economy and could simply rely on guaranteed future sales at high retail prices, it could have plowed along for twice as long and eventually released something, as Microsoft did a decade later with Windows Vista. As Windows Enthusiasts like to point out, Vista will eventually get deployed no matter how bad it is. [The Secrets of Pink, Taligent and Copland][Has Leopard Fallen into a Copland-Vista Conundrum?][SCO, Linux, and Microsoft in the History of OS: 1990s]Spindler’s Complications.By 1990, Apple CEO John Sculley had recognized that Apple needed to set a reasonable minimum hardware threshold for its operating system releases and to figure out a way to get Mac users to fund the expensive operating system development the company was doing. At that time, both Microsoft and IBM were charging PC users around $100 for retail copies of Windows or OS/2, neither of which were even really usable.Figuring out how to actually accomplish those goals never got done at Apple. Instead, Sculley’s successor Michael Spindler attempted to imitate Sony by releasing ranges of Mac hardware under a variety of vaguely Latin sounding names--Quadra, Centris, and Performa--and a series of confusing, nondescript model numbers. Starting in early 1994, Apple also underwent a complex transition from its original 680x0 Macs to PowerPC hardware. Since much of the original Mac software was written in assembly language, the transition relied on emulation of the existing Mac System Software, which further complicated efforts to deliver significant new features without breaking existing software or prematurely cutting off support for existing machines. Non-PowerPC Macs continued to be sold into 1996.Spindler’s Apple also began plans to license the Mac software to other hardware makers in late 1994, including APS, Bandai, DayStar, Motorola, Pioneer, Power Computing, Radius, and UMAX. That effort skimmed off the cream of Apple’s profitability and handed it to the cloners, leaving Apple to service the low end of the market at Sears with its Performas while also funding the development of nearly profitless Mac System Software to support an increasingly wide range of hardware. [Why Apple Failed]Simplifying the Mac Hardware Lineup Around the G3.When Steve Jobs returned to Apple in 1997, the company's product line was all over the place, although efforts were already underway to simplify things. Apple had only