8 ms·
None of the handset makers back then were in a position to come up with a workstation class OS, with desktop class application development frameworks and highly
by simonh 7y ago
None of the handset makers back then were in a position to come up with a workstation class OS, with desktop class application development frameworks and highly tuned power management and commercial level software development tool chains. They just didn’t have software groups anywhere close to able to deliver something like that. Their software was at best based on embedded variants of Linux with very bare bones dev environments and frameworks. They just didn’t have anything close to the required level and breadth of dev experience and capability.
Furthermore when the iPhone came out almost nobody in either the phone or the Tech industry in general appreciated what Apple had done and why it mattered. I must have read a handful of posts a month like yours back then trivialising the issue as just having to ‘come up with something’. Desktop OS systems like OSX and Windows at the time aren’t something you can just come up with. It’s this sort of thinking that doomed desktop Linux to the margins for decades, and without the Google Android team’s immediately realising what had happened and what they needed to do about it, handset Linux could very easily have ended up a footnote like desktop Linux. Nobody else in the industry seems to have had that insight back then.
What I think would have happened is Microsoft would have eventually got their act together and brought out a credible Windows Mobile and licensed it to the handset makers. Other than Google they are the only software company with the resources in talent and technical depth capable of it. Without Android to light a second fire under them it might have taken longer than it actually did, but they did do this in the actual timeline and without Android to compete with their strategy would have worked.
- mehrdada 7y ago> Nobody else in the industry seems to have had that insight back then Helps to have someone on Apple board, you know
- jannes 7y agoThat's a good point. I had forgotten that Eric Schmidt was a director on the board of Apple between 2006 and 2009 while being the CEO of Google. Apparently they had Eric Schmidt step out of the room whenever they talked about Apple phones. https://www.cnet.com/news/i-resigned-from-apple-board-for-the-right-reasons-says-googles-eric-schmidt/ https://www.cnet.com/news/i-resigned-from-apple-board-for-th...
- mehrdada 7y agoPerhaps years later he stepped out. Not at the beginning though I assume. iPhone announcement day was a lovefest between Steve and Eric.
- addicted 7y agoGoogle also had early access to the iPhone because it was one of the few (the only?) non Apple companies to release Ana app on the iPhone on day 1 (Maps was powered by and created by Google initially if I remember correctly).
- jannes 7y agoThere was a native YouTube app on day 1 as well (The one with the old TV icon). However, I believe it was developed by Apple.
- 2muchcoffeeman 7y agoI really miss that app. Youtube. No ads. It was great.
- agloeregrets 7y agoNot only that, it was Pre-Google YouTube.
- jsjohnst 7y agoGoogle bought YouTube in November 2006[1], months before Apple announced the iPhone. [1] https://en.m.wikipedia.org/wiki/YouTube https://en.m.wikipedia.org/wiki/YouTube
- jsjohnst 7y agoIt was built entirely by Apple.
- leoc 7y agoWhich probably all helps to explain why SJ was so stung by Android and willing to start lobbing patent suits around.
- simonh 7y agoThe first iteration of the Google Maps app was actually written by Apple engineers, and just used Google APIs to access their mapping data. Google took over development later when the iPhone dev kits became available to third parties.
- agloeregrets 7y agoAnd if you can’t have someone on Apple’s board, it helps to have the inventor of the iPod. (Palm’s WebOS)
- fsloth 7y ago" yours back then trivialising the issue as just having to ‘come up with something’." Sorry, I was not trying to trivialize the complexity of the issue. Rather, I was trying to slyly refer to the other competetive handsets already on the market back then. The question was if Android had not happened, would Apple rule the mobile ecosystem completely. I don't think so. Rather, capital chose Android as the most viable alternative. There were viable alternatives back then such as Meego which had the combined expertise of Nokia and Intel behind it. It was the market and business that sealed Apple/Android duopoly, not the lack of viable alternative tech stacks.
- dijit 7y agoBe mindful about windows phone too, it is very revisionist to call it failed; it had all the hallmarks of a successful product except it didn't have developer attention so it died.
- fsloth 7y agoYes, Windows as well. Enumerating all the pre-IPhone incumbents with a credible shot in an alternative history universe would be a long list.
- Nursie 7y ago> it is very revisionist to call it failed How so? It never achieved much market share AFAICT, despite being marketed heavily everywhere from slashdot to the tv. It had to be relaunched each revision as the platforms were incompatible, it was always way behind on features and playing catch-up... and eventually MS ditched it entirely. Sure, absent android it could have had a shot. But I wouldn't call the platform a success.
- dijit 7y agoWe're talking about a hypothetical situation where android doesn't exist. Microsoft phone OS 7 (the one that was adapted to the Nokia phones originally designed for MeeGo) was very polished and quite pleasant to use. I think it would have succeeded. I say this through a clenched jaw though because I had just started working at Nokia during the time of the acquisition and was quite enthusiastic about MeeGo.
- tracker1 7y agoPalm's WebOS was decent and MS already had some admittedly mediocre devices.
- leoc 7y agoAnd as xorcist said https://news.ycombinator.com/item?id=22287837 https://news.ycombinator.com/item?id=22287837 it seems likely that Nokia really had finally figured it out with Meego (though I've never touched the thing myself). It was fairly inevitable that a decent #2 smartphone OS would be along sooner or later as soon as iOS had provided the competitive impetus and the blindingly obvious model to crib from. OTOH it's also quite clear why Google would not have wanted to gamble on waiting around for somone else to get their act together, especially since it already happened to own the guts of an okay smartphone platform. Not only would a viable #2 have taken an uncertain amount of time to emerge, it could have turned out to be someone quite unfriendly to Google: it would very likely have been MS, after all. And after all (viz. __ka https://news.ycombinator.com/item?id=22287118 https://news.ycombinator.com/item?id=22287118 ) what other platform owner was ever going to be friendlier to Google search than Google itself? And let's be frank, by the mid-2000s it wasn't really that bloody hard, from a purely technical point of view, to ship a decent mobile OS running on an adequate hardware platform. It seems pretty clear that in almost all cases, what was most sorely missing was someone with both the power and the taste to make an overall assessment of UX and say "no, this is shit, come back with something acceptable"; maybe to even make a few hirings or acquisitions if necessary to get someone competent on the problem. But this is one facet of one of the most remarkable and slightly strange things in the history of tech. Even by not too long into the '90s it was easy, for anyone with eyes to see, to look at a Macintosh on one side and a VCR blinking 00:00 on the other and see what the future of device UI was. But companies with massive resources and their very future at stake, including firms of impressive competence like Sony and Nokia, couldn't get there. Up to the early iPhone age it seems that the list of companies which could do good work in software-heavy/"smart" UI was roughly: 1) Apple 2) Microsoft, but only when Apple first provided them a detailed model to crib from. Not something to sneer at too much, because others couldn't do it even then 3) Some Mac/PC ISVs who could do good work, but purely in software and only inside the lines of the existing Windows/Mac platforms. (OFC by this time MS itself was effectively a Mac ISV with notions.) 4) Some device or HW startups who flailed around commercially (Danger, NeXT, Be, the set-top-box group at Sun which begat Java http://www.blinkenlights.com/classiccmp/javaorigin.html http://www.blinkenlights.com/classiccmp/javaorigin.html ...) See also the iPod, Apple's Digital Hub strategy (Jobs' hope that consumers would buy Macs in order to make their consumer-electronics devices usable), Sony's catastrophic missed opportunity to turn PlayStation into an app and Web-browser platform https://news.ycombinator.com/item?id=22288538 https://news.ycombinator.com/item?id=22288538 , and the fear other companies felt towards MS even after Apple had been first to a hit smartphone.
- jacobush 7y agoiPhone wasn’t even supposed to have an app store.
- type0 7y agoiPhone wasn’t even supposed to be jailbreaken either.
- johnbellone 7y agoIt originally didn’t even have custom apps but web shortcuts.
- xorcist 7y ago> with desktop class application development frameworks It was for this very reason Nokia bought Qt. They very much had a desktop class dev story going, and also some pretty solid mobile device cred. People seem to forget the Greenphone, which was sold as a development platform but you could actually buy it and it was a proper phone with the full dev stack, more than a year before the iPhone was shown publicly. Nokia absolutely had what was required to stay relevant. Without the hostile takeover, things might have turned out different.
- skriticos2 7y agoNokia had a problem long before that. They were trying to play on too many playgrounds. They had S60 and Symbian as their workhorse OSs and then were dabbling in various custom Linux stacks (I had an N800 back than, GTK+ based - could skin it like a tricorder - fun times). Then they acquired Qt (Trolltech) and instead of building a UI on the Widgets tech stack they wanted to re-invent the wheel with QML - which is how the Qt framework became this weird two GUI frameworks in one that don't really mesh to this day. Granted, Google was also just throwing stuff at the wall and seeing what stuck, but at least they are a tech company with multiple revenue streams - while Nokia wasn't either of those - so without a laser focus they were doomed from the get go. And they did not have it.
- pjc50 7y agoThe irony was that there were already versions of Windows Mobile kicking around. Compaq iPAQ, for example. It ran Windows CE and required a stylus. To me, it seems that Apple managed to do to the phone what they'd already done to MP3 players. They weren't the first, and they didn't win the price/features war, but they had uniquely better UX on the device. The key differentiating features seem to me to have been: - toughened glass screen - stylus-free interaction due to use of capacitative screen - multitouch - real web browser (not WAP) - (US) escaping the control of carriers; nobody remembers the "iTunes phone" the ROKR. Also indirectly killing carrier's attempts to do nickel-and-dime billing and therefore turning internet into a bulk commodity: https://en.wikipedia.org/wiki/300-page_iPhone_bill https://en.wikipedia.org/wiki/300-page_iPhone_bill - the marketing achievement of being a fashion device not a tech device (Tesla are explicitly copying this, to their advantage) (again, I'm not claiming that they were the first to do any of these, but they did all of them well together)
- rjsw 7y agoWindows CE had a real web browser, the only feature I remember that was missing was support for PNG images.
- jl6 7y ago> stylus-free interaction due to use of capacitative screen > multitouch IMHO these two were the key standout killer features that made the iPhone a qualitatively different and better experience than every handset that had come before.
- pjc50 7y agoI'm still expecting someone to well-actually us and point out an obscure device that did both first, but to me these were the spectacular features. Resistive touchscreen + stylus was and is awful (qv the other thread about how you hold a pen, like a ballpoint a stylus on resistive requires pressure and can be hard on the grip. It's also extremely loseable)
- jsjohnst 7y ago
- ori_b 7y ago> None of the handset makers back then were in a position to come up with a workstation class OS, with desktop class application development frameworks and highly tuned power management and commercial level software development tool chains. Did you ever use early Android? It was impressively bad.
- simonh 7y agoYes and you're right, it took the Android team years to catch up, but they started a massive course correction effort basically the day the iPhone was announced. Google realised how much of a threat the iPhone was and threw everything they had at getting Android up to speed. My point is the incumbent phone handset companies didn't have those sorts of resources in skilled development teams with system level experience and support services available to throw at anything. Microsoft left it for years, believing they could still compete using their single tasking Windows CE kernel based platform. That's why Windows 8 with a true pre-emptive multitasking NT based kernel, able to run background services and run on multiple cores wasn't ready until 2012. By then Android had already had it's act together for a few years and it was too late for MS.
- pjmlp 7y agoIn what concerns NDK tooling they still have quite a bit to catch up with Windows, but that is what we have.
- greedo 7y ago>I must have read a handful of posts a month like yours back then trivialising the issue as just having to ‘come up with something’.< I remember ESR going on and on about how Apple was doomed any day now. He lost site of how the direction the world was going, wishing instead it went where he wanted it to end up.