If I remember correctly, Nokia had good tech for smart phones, but no vision or courage to drive the market in that direction. It was not a well-managed company.
If I remember correctly, Nokia had good tech for smart phones, but no vision or courage to drive the market in that direction. It was not a well-managed company.
Apple was unique: they were willing to bet the company on a single form factor, they had a small but loyal and vocal fan base, and they had their own retail stores to give people the opportunity to experience the phone.
Anyone else would have made it just one of a half dozen phones and it would have languished in a dusty corner of one of the crappy operator stores where no one knew how to use it or had any reason to push it.
Their phone was the full modern smartphone years before the iphone. They're the ones who met with Larry Page and got him to make a mobile version of Google.com.
Jobs met with handspring back when apple was focused on the mac PC. Jobs stood up at the whiteboard and drew a mac with all the aspects of a person's life around it. Handspring's CEO or CTO stood up and drew a handspring phone and all the same photos, music, www, etc around it. "Except you'll carry this with you everywhere you go." It was at that moment jobs realized he needed to build a phone and what it needed to look like.
Thing is, while handspring got there ~5 years before jobs did, they didn't have anything to leverage. They were a small startup and completely at the mercy of the telco carriers with their existing cellular subscribers, who then proceeded to force changes to the interface and apps. Handspring actually had to risk it all on their vision of what a phone should be.
Jobs had a healthy apple with a healthy mac computer lineup and billions in the bank. When apple went to the telcos all jobs had to do was ask "do you want access to our millions of ipod users?" and he got his way. Handed the concept and executed with essentially zero risk.
That's actually not true, all of the telcos rejected the pitch except AT&T. There was considerable risk in it from their perspective, because Apple wanted total control over the user experience: no carrier logos on the handset, no carrier logos in the operating system, no preinstalled carrier software.
Edit: for context, carriers wanted control of revenue and obviously fought against net neutrality. At the time, they made big money with SMS and other services.
Yeah, android was busy developing a platform, and they even had some vision (unusual for that industry) because of the Danger team. Yet they were shocked by the iPhone and basically restarted — luckily before having demoed anything publicly.
Then Steven Elop left Microsoft to become Nokia CEO; decided to move everything to Windows Phone; publicly pointed out everything was on fire; crashed the stock price by 85%; sold Nokia to Microsoft at a massive discount; and then finally rejoined Microsoft. If it wasn’t an act of corporate sabotage designed to obtain Microsoft an established phone vendor subsidiary at a fraction of its cost, then it’s hard to see how he could have done a better job on purpose.
It’s always weird to hear. He blamed Nokia’s inability to come up with a decent mobile OS and get behind it.
Horace Dediu has written a lot about both Apple and Nokia. I recall him saying Nokia did some things really well. I think they were caught totally flat footed, and the Symbian debacle did them in
The iPhone came out when Windows XP was the default PC experience for most of the world, why would anyone need anything like iPhoneOS on a damn phone? Talk about overkill.
Just finished reading The Innovator's Dilemma. Phenomenal read.
- “Crossing the Chasm” in the end this book is really just a single drawing, but the text explains the problem: why early traction not only doesn’t imply future growth, but if misunderstood, can kill any future growth. Also very important for investors and people at big companies.
- I really like the underrated “Mastering the Dynamics of Innovation” by Utterback. It’s kind of a complement to the other two, full of amazing market hacks to get a new product established.
For example, 120 years ago, electric companies would put on demo sessions for the public, so the gas companies would send people with metal bars in their sleeves to short out the electrical systems (in a cloud of sparks of course!). So Edison (IIRC) got the clever idea to run the electric wiring through the gas conduit, both “for safety” and to take the gas out of service.
We often don’t understand what the true characteristics and affordances of a new technology are — and neither do the customers. That’s what this book is about.
I got into a rut in terms of just doing programming and reading technical content about a year ago. So, I started reading from a list of books mentioned in various HN posts.
As I slowly make my way through the list, I feel both like an idiot for not having read these books earlier, and at the same time thoroughly happy that there are such beautiful concepts out there to learn that's not just programming or systems design.
Hadn't heard about the Utterback one! Seems like it would be right up my alley.