Slashdot Mirror
The Story of the Original iPhone's Development
jds91md writes "Today's NY Times delivers a great story of the development of the iPhone by Apple. It focuses on the events during the leadup to Steve Jobs taking the stage with shockingly buggy prototypes and pulling off the show that is now history. 'Only about a hundred iPhones even existed, all of them of varying quality. Some had noticeable gaps between the screen and the plastic edge; others had scuff marks on the screen. And the software that ran the phone was full of bugs. The iPhone could play a section of a song or a video, but it couldn’t play an entire clip reliably without crashing. It worked fine if you sent an e-mail and then surfed the Web. If you did those things in reverse, however, it might not. Hours of trial and error had helped the iPhone team develop what engineers called “the golden path,” a specific set of tasks, performed in a specific way and order, that made the phone look as if it worked.' One of the big problems was the phone's connectivity. The man in charge of the iPhone's radios, Andy Grignon, had to deal with Jobs's anger when rehearsals didn't go well. Grignon said, 'Very rarely did I see him become completely unglued — it happened, but mostly he just looked at you and very directly said in a very loud and stern voice, "You are [expletive] up my company," or, "If we fail, it will be because of you." He was just very intense. And you would always feel an inch tall.'"
The whole story is a great testament to engineers, in that (a) it's incredible they could have made the demo work that well, and (b) Apple actually shipped the thing described in that story just six months later - and it was basically pretty functional and solid.
Even for you Apple Haters out there that have zero interest in reading something like this - well anyone who is an engineer should read it, and if you can't bring yourself to do that at least read the very last paragraph which is fun for everyone.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I don't know why this surprises anyone. EVERYTHING I have ever designed had to be demoed before it was ready, sometimes a year or more before it was ready. Usually we could arrange to have the actual engineers (me or someone on my team) do the demo, and we always tred to practice to insure we could demo only things that worked. When the boss had to do the demo we always had extensive rehearsals, and emphasized that he must perform the steps exactly as we practiced or bad things would likely happen. On some projects hardware was so late we had to build simulators and hide them under the table so the software would have something to control/monitor. I believe this sort of demo is very common in any sort of R&D environment including big name companies demoing new products/technologies for the first time. Every demo of an early prototype will crash or show unexpected behavior at some point during the demo, the key to the impression it makes is how well the demonstrator handles the issue - getting mad in a public demo is never a good idea. Usually you just tell someone else to file a bug report, and move on - explaining that there is, of course, still some polishing to do; or use it as an opportunity to explain the way you work with customers to resolve such issues - leaving the impression that you engineered the failure in order to fit that topic in to the presentation. My ex boss was a master of that technique. Even in my current job where my products are for internal use I am frequently asked for demos before products are ready, the difference being I don't have to offer smooth explanations when things go wrong, usually I just have to offer an estimate of when it might be done.
Ford didn't invent the car either, but the Model T was certainly innovative and redefined the automotive industry. The same can be said for the iPhone.
Not my experience. Are you just typing in the garbage you're paid to type in?
Yes, they are.
Social Media Marketing companies like Burson Marsteller, Waggener Edstrom and others have teams posting FUD and moderating in all tech sites on behalf of Apple, Microsoift, Facebook etc.
And you're right:
"Contrary to what you’ve heard, Android is almost impenetrable to malware
Until now, Google hasn’t talked about malware on Android because it did not have the data or analytic platform to back its security claims. But that changed dramatically today when Google’s Android Security chief Adrian Ludwig reported data showing that less than an estimated 0.001% of app installations on Android are able to evade the system’s multi-layered defenses and cause harm to users. Android, built on an open innovation model, has quietly resisted the locked down, total control model spawned by decades of Windows malware. "
http://qz.com/131436/contrary-to-what-youve-heard-android-is-almost-impenetrable-to-malware/
Of course, Slashdot doen't consider this news bcause it's sponsors haven't paid it to.
Neither does it mean "popularizing".
Palm, Nokia, RIM, and Microsoft didn't just invent these technologies, they brought them to market and had very successful products with them.
No. They produced entirely different devices and were (more or less) successful with those. The innovation in the original iPhone wasn't in any of the underlying technologies -- those had all been there before. The innovation of the iPhone was in the overall design, the vertical integration of the touch screen with the new "physical" touch UI and the sensors, the unified co-design of hardware and software and applications and later the app store model and so on. All those things constitute innovations in themselves -- and they have since totally disrupted and recreated the entire smartphone market.