88 comments

[ 3.1 ms ] story [ 142 ms ] thread
(comment deleted)
On one hand, I don't like the glorification of overwork and burning people out for the sake of maybe making a great product: "You're going to have to give up nights and weekends probably for a couple years as we make this product."

On the other hand, they did make the iPhone, so I guess this is a lesson to project managers and executives that death marches do occasionally pay off.

It seems a lot of influential software projects were death marches. I just finished a book about Windows NT which almost drove its developers to the breaking point. Mac development was the same.

However, I believe most death march projects don't end as something influential.

What's the book?
Probably "Showstopper!" by G. Zachary. I remember really liking it.
Showstopper is indeed a really fun read. IIRC the reason it was a death march project was because microsoft needed a unix competitor yesterday because everyone knew unix was going to take over the desktop and DOS/Windows was doomed.
Yup. Great read. Just right for a weekend
In the end iPhone added billions to the company and shareholders, but interesting if all these engineers who spent nights and weekends to make that happen got an extra pay for that. Not much about that in the article, just the praise for extra work. If I remember correctly from iCon book, the was period when engineers on Steve's jobs team where paid less than in other teams in Apple. This would really suck working weekend and creating multibillion dollar product, but getting regular salary as the rest of the folks in the company.
Any idea if this division of Apple employees are eligible for stock options? If so, those may have ended up being one form of a payoff.
I think the real question to ask is "Could they have been just as successful without doing a death march?"

Obviously it's hard to know the answer to that, but I suspect it's yes.

Apple did a great job engineering the iPhone. They really killed it, no doubt. That being said, I think that Apple was the only company that could have invented the iPhone in the mid-2000s, because of their high degree of vertical integration. They were the only company that had a completely proprietary computer system for which they developed the hardware and software. Also, I think that the basic interface for the iPhone was fairly inevitable. Cell phones were becoming little computers and giving them little keyboards was a problem, because there wasn't enough space. If you figure that little keyboards were a dead end, then about the only remaining option was to use a touch screen. Other companies could have started working on the touch screen, but they didn't have an operating system. I believe Apple was in a unique position to create the iPhone.
Handspring could have left the keyboard off the Treo, their earlier PDAs were much closer in style to the iPhone.
Other phone vendors also felt tantalizingly close, but they were all busy optimizing their local maxima without making that final "finger-controlled" breakthrough.

I remember using a Sony Ericsson Symbian UIQ phone in 2006 (the M600i IIRC, Jobs was rumored use an earlier phone in the same OS series, the P800), where they had put the action buttons at the bottom of the screen at a finger-friendly size. I remember often quickly using my fingers to do common tasks, but it was a resistive screen and they still used scroll bars and tiny checkboxes. In hindsight it shouldn't have been that difficult to make the leap to finger-first, but it was Apple who did it.

it was Apple who did it

I think you mean LG: https://en.wikipedia.org/wiki/LG_Prada

Apple made the first successful one. Which seems to be their knack, after all.

Pretty sure Prada didn't have a proximity sensor or multitouch.
Of course it didn't have multitouch; Apple had bought the patent beforehand.
And that is perhaps the one thing everyone glosses over.

Multitouch was being developed by a startup that Apple gobbled up.

The M600i was my all time favourite phone, only to be surpassed by the Nokia N9. That rocker QWERTY keyboard was god-damned fantastic.
> I think that the basic interface for the iPhone was fairly inevitable

I hear that a lot, and I'm not convinced.

I think people needed to have a strong motivation to get used to software keyboards. I think most companies implementing one would have screwed it up (see: RIM).

So you'd need a compelling use case and compelling software to force that sea change. I find it plausible that, absent Apple's existence, we'd be using clunky GUIs on desktop computers and even clunkier GUIs with physical keyboards on smartphones.

I also think it required a manufacturer to completely sell out to the concept. If there are 5 similar phones by the same company, only one of which has a software-only keyboard, you won't get sales, development, and engineering support you need to drive a successful change.

Much like laptops still being shipped with floppy drives and VGA ports years after those technologies were effectively dead.

Laptops ship with VGA ports because the business world is full of conference rooms where the projector only has a VGA cable.
And if PC manufacturers forced the issue they'd sell more dongles and/or drag businesses into the 21st century.
Yeah, I'm not convinced either.

Android was still getting built with a Blackberry-style physical keyboard at that point.

It feels like if it wasn't for a few researchers in the interaction lab we wouldn't have gotten software keyboards for a while.

I think that the basic interface for the iPhone was fairly inevitable.

We could have had a long detour through Blackberry-like devices with keyboards. But comprehensive smartphones in some form were to be expected as the electronics got cheap enough.

I find it plausible that, absent Apple's existence, we'd be using clunky GUIs on desktop computers

Without Apple, we probably would have had something like lower-priced Sun or Apollo workstations on the desktop. For most of the 1980s and 1990s, people at well-funded companies did have Sun workstations on the desktop. With, though, crappy GUIs. XWindows is from that era. It would never have occurred to Sun to hire Susan Kare.

Sun didn't have the volume to support software companies. Interleaf had something better than Microsoft Word by 1983, before the Mac had even shipped. But their business model was to bundle a few Sun workstations and a laser printer with the software, for about $60K. Software for Sun machines tended to cost a few thousand dollars per seat.

Just because the hardware would improve doesn't mean the UI would improve.

Digital cameras have killer hardware, but they still have the same crappy menu systems they had when they were first introduced in the 90's.

You absolutely need extremely rare talent to produce original & creative ideas like what was used in the iPhone, and the digital camera makers have absolutely none of that talent.

Yes, the world would continue to use clunky desktop-oriented WindowsCE/Blackberry/Treo phones today without Apple. They really were original and unique to the industry in how they completely changed its course.

Also, never take advice from Phil Schiller.

I'm not necessarily disagreeing with you, but what in your opinion makes the menu systems in digital cameras so crappy?

I have an older Canon digital SLR, and while the rear LCD isn't as big, bright, or high res as newer cameras, and it lacks touch support, I generally find the menu system pretty nice. It's fairly information dense and has dedicated buttons for a whole host of features so that you don't have to go digging through a bunch of hamburger menus.

Digital cameras already have a great interface for most users. It's single button click.

The menus and dials are for expert users who don't want a more simplified interface because it's more efficient for them to learn the dense interface that novices find confusing.

None of that disagrees with my point, I don't think.

>>I think most companies implementing one would have screwed it up (see: RIM).

Little keyboards were a dead end (I think I remember reading contemporaneous articles noting the fundamental problem of "little keyboard -> little screen" and the little screen being just too small. The real issue wasn't the little keyboard per se, it was the little screen). I think Apple had the advantage in creating software keyboards, because they had the ability to tightly coordinate the hardware and software development. They also the capital to take the risk.

I suppose RIM also did hardware and software, but their software was less sophisticated than Apple's.

>>I find it plausible that, absent Apple's existence, we'd be using clunky GUIs on desktop computers and even clunkier GUIs with physical keyboards on smartphones.

Wasn't that sort of my point? My point was that only Apple was positioned to do the iPhone in the mid-2000s.

Given the difficulty of entering the mobile handset market, and the inertia of most players, I'm just not sure we would have broken out of the rut.

I think the player who might have made the leap was Google, who was experimenting with touchscreen devices, but they aren't the boldest company when it comes to hardware.

>>Given the difficulty of entering the mobile handset market, and the inertia of most players, I'm just not sure we would have broken out of the rut.

I think we might agree on that?

I guess my main thesis rests on the idea that an iPhone is more like a tiny computer than it's like a circa-2007 cell phone. It was easier for Apple to make a tiny Mac with phone capabilities than it would have been for a handset manufacturer to retrofit PC-like functionality onto their handsets. Apple was already the master of the Mac ecosystem, which they could leverage however​ they wanted. Handset manufacturers would have had to acquire a computer platform or partner with a computer company (which, I guess, is the story of Android).

It's also at least arguable that Apple earned (past successes, devoted following, etc.) something of a license to break with existing patterns. Even if the new patterns/techs weren't quite baked yet and people weren't fully ready for them.

This applied to dropping the hardware keyboard on the iPhone.

It also applied to something like the lack of printing on the original iPad. This was a big critique that a lot of people had when the iPad first came out. Now, even though there are printing options, most people don't really care any longer.

> If you figure that little keyboards were a dead end, then about the only remaining option was to use a touch screen.

Actually, the Palm Pilot from the 2000's was an alternative to both - sort of a touch screen, but used a stylus and its own script for writing characters.

This makes no sense at all.

All the cell phone companies had their own proprietary OS.

Android was getting built at literally the same time.

> All the cell phone companies had their own proprietary OS.

Symbian was used by dozens of manufacturers and came in different flavors. S60 for standard smartphones, S80/90 for communicators, UIQ for touchscreens.

Windows Mobile was also widely used and had an edition for phones using a touchscreen and one without them.

Hundreds of millions were sold before the iPhone even came out.

And the S90 UI would continue on into Maemo.

And i swear i could finger type on the 770 before iPhone showed up, even though it was a resistive screen.

> I think that the basic interface for the iPhone was fairly inevitable

Yeah, in 2000 I assumed that phones would end up like that, because keys took too much space for something that fits in your pocket. I was an enthusiastic fan of Windows Mobile when it came out, and I've been on iOS since the first iPod Touch.

You’re going to have to give up nights and weekends probably for a couple years as we make this product.

The excerpt doesn't give a strong rationale for why people had to give up nights and weekends.

It wasn't to protect apple from bankrupcy, because thanks to the ipod and imac apple was already a profitable business.

It wasn't because phones were a threat to the ipod, because carriers had the phone market locked up so tight that you couldn't do a decent mp3 player on a phone. The ROKR was ample evidence for that.

It wasn't because competitors were on the horizon, because all phones at the time were terrible, and would have remained so without the iphone.

As far as I can tell from the article, the pressure cooker was created deliberately, by having competing teams and top-down imposed deadlines, but it still doesn't explain why it was necessary to do things like that. Was it all due to Steve's personality? If that's the case, how is modern-day apple? Is the autonomous car project still this crazy pressure cooker, or can people go home over the weekend to spend time with their families?

Apple needed to fulfill its deal with Cingular in a timely matter:

http://archive.wired.com/gadgets/wireless/magazine/16-02/ff_...

"And what would AT&T think? After a year and a half of secret meetings, Jobs had finally negotiated terms with the wireless division of the telecom giant (Cingular at the time) to be the iPhone's carrier. In return for five years of exclusivity, roughly 10 percent of iPhone sales in AT&T stores, and a thin slice of Apple's iTunes revenue, AT&T had granted Jobs unprecedented power. He had cajoled AT&T into spending millions of dollars and thousands of man-hours to create a new feature, so-called visual voicemail, and to reinvent the time-consuming in-store sign-up process. He'd also wrangled a unique revenue-sharing arrangement, garnering roughly $10 a month from every iPhone customer's AT&T bill. On top of all that, Apple retained complete control over the design, manufacturing, and marketing of the iPhone. Jobs had done the unthinkable: squeezed a good deal out of one of the largest players in the entrenched wireless industry. Now, the least he could do was meet his deadlines."

That, and the hardware relevancy, seem like plausible reasons: but why limit yourself to only the rock-star engineers willing to work in secret and for extreme hours? It doesn't seem like they had competency, competitive, or budget constraints that would have prevented them from using more engineers, more openness, or, again, more engineers on the project.
Great products are made by small teams. Adding a large amount of people to a small team does not guarantee that the product will ship faster - many times, the opposite is true.
There was a pretty fixed window in which the hardware was going to be relevant, and an enormous amount of work to be done to get a useful product out in that window.

It's also worth being ... cautious about this account. Many of the competing / complementary perspectives aren't represented, often because they are still working there.

Fixed how?

First, it wasn't about the hardware. Other companies (Nokia, HTC, Samsung, Motorola) were doing competitive hardware.

It was all about the software and Apple was so far ahead of everyone else, that if they took 1 year more to ship, they would still be far ahead of everyone else.

As history shows, the only credible competition was from Microsoft and Android. RIM/Nokia/Samsung/HTC/Motorola (all significant players) couldn't replicate iOS no matter how much time they would take.

First iPhone was released on June 2007 (https://en.wikipedia.org/wiki/IPhone)

Windows Phone was released on Nov 2010, 3 years later (https://en.wikipedia.org/wiki/Windows_Phone).

First Android was released on September 2008 (https://en.wikipedia.org/wiki/Android_version_history) and took a long time to achieve design quality parity with iOS.

Apple had plenty lead time.

"It was all about the software and Apple was so far ahead of everyone else, that if they took 1 year more to ship, they would still be far ahead of everyone else."

How did they know that for certain?

Easy, they can just travel forward in time to now and have the benefit of hindsight.
Not only that. The android which was going to happen before the iphone was a very different beast. It was closer in spirit to WinCE and BB than to iOS. WP7 also happened only because of the android and iphone competition. I think it's reasonable to say that smartphone OS's would have remained terrible for a long time without the iphone leading the way.
I feel like some people romanticize working long hours and weekends as some sort of 'elite workhard' class, even though they could have done the same work during normal working hours.
I think some of these people also get into work late, like somewhere between 10:30am and 12pm (if not later, maybe?).

If you can afford to sleep in that late most likely you don't mind covering that time at night instead.

Likely, but I've worked with a lot of people who will do that and also turn around and give you shit for leaving at 5.
I know someone who worked on the original iPhone. He was a quiet, Midwestern guy, and didn't like being yelled at by Jobs. He stayed until the product shipped, then quit Apple.
The ironic thing is that everyone at Apple benefited greatly from iPhone success (stratospheric rise of stack price made everyone's stock options worth a lot).

A good strategy would be to be an Apple employee working on a project that receives less scrutiny and pressure and stay for a few years after iPhone launch, to get most of the benefit of the rising stock price without the crappy work environment.

You can't guarantee that someone else will not come out with something in the mean time. There is quite clearly a time limit to which this would have been amazing.

And even at the time, many people ridiculed the iphone.

>You’re going to have to give up nights and weekends probably for a couple years as we make this product.

The right response is always "Ok boss, but you're gonna have to give up 30% more money to my salary".

(comment deleted)
"The iPhone ruined more than a few marriages". That would really never be worth it to me. But maybe it depends on your marriage.
More likely that quote is a Fallacy of Single Cause.

https://en.wikipedia.org/wiki/Fallacy_of_the_single_cause

No, "the iPhone" in this sentence is representing the iPhone development program and its high-stress, night- and weekend-consuming, burnout-inducing, multi-year schedule. That - and the resulting changes in behavior - can absolutely be sufficient cause of a wrecked marriage.

Some fallacies are universal: "If A then B, therefore because not A, not B" is an example. But that one seems extremely contextual. It denies that "If A then B" is possible.

I'm willing to be the iPhone (the actual device) might actually have had part in many more broken marriages than the development process itself. Mind you, not saying the iPhone caused the broken marriages, but it has become the preferred medium of communication for a substantial part of the population.

I wonder how many of the unmasked Ashley Madison users were iPhone users :P

I disagree with this. Marriages fail for a lot of reasons - the iPhone project may be similar to a military deployment - except nonmilitary spouses/families are unlikely to be prepared for that kind of stress.
But they maximised shareholder value! /s
It's strange to remember that no-one had ever seen 'swipe to scroll' before the iPhone unveil in 2007. It's so fundamental to everything now. Before, touchscreens had little scrollbars with up down arrows. Nuts.
Pretty sure Windows had this in their tablet PC stuff, thought it was more "flick" to scroll. I remember sitting around the house, browsing using the touch system and thinking it was pretty nifty, and this was before the iPhone was released.
Correct, you could swipe to scroll on Microsoft's tablets, or UMPC's as they used to call them.
Apple made people oblivious to everything that came before the iPhone.
Prior to the iPhone most touch screens were resistive and you had to use a stylus and press hard on the display, capacitive touch screen made all the difference.
Nah, by the time iPhone came out, many devices used soft resistive screens that one could easily use with fingers.

I often thumb typed on a Nokia N800 for example.

Thing about resistive screens though is that it has much better precision. Thus one could operate checkboxes and scrollbars that were downright tiny.

And speaking of scrollbars, i kinda miss them. I wonder how many times i have tried to scroll or pan and something makes the capacitive sensor think i instead pressed some element. Having distinct scrollbars avoid the ambiguity of input.

I think you might have some rose colored glasses on. Resistive screens suck. Even modern ones are less accurate than the original iPhone with respect to touch. They can be good if you have a narrow tip stylus, but otherwise they have always seemed borderline unusable to me. I always end up using my fingernail because touch recognition is so poor.

And anyway, to whatever extent you can type on a tiny keyboard or select a tiny checkbox with your finger, it comes down to software, because your fingertip isn't precise even if the screen is.

Scroll bars also suck for touch devices because they have to be so absurdly wide to be usable.

It kind of dampens the image of Jobs as visionary leader.

For a long time he was against making a phone, other executives had to convince him that Apple should make the phone, even doing risky things like running "secret" projects exploring possible technologies for the phone.

Job's talent seems to be more of a taskmaster: once he decided that phone needs to be done, he was able to organize people to do it, even if it meant great personal sacrifices.

Yeah but it's good that Jobs who has a kind of god-like status these days could be a complete f*ing idiot (which would be his own words) by being against things like the iPod for Windows.
True. It does dampen it.

But the whole "our CEO is a genius, the gift of the gods", is a standard trick in branding luxury products. Actually, one of the more interesting stories behind the iPhone would be of the marketing behind it. But i'll guess we'll never hear it, because there's always new stuff to sell.

> Job's talent seems to be more of a taskmaster: once he decided that phone needs to be done, he was able to organize people to do it, even if it meant great personal sacrifices.

He was also a fantastic editor. He was very good at saying "no" to things whether it was because they were just bad ideas, weren't fully done yet, were missing something important, where especially when some stuff that other people thought was important wasn't and needed to be removed.

Now we know he didn't always get it right, he could be swayed by personal emotions such as when he wanted to keep the iPod off Windows.

But clearly he got it right a number of times where it really mattered.

Jobs greatest skill was the ability to change his mind when the data proved him wrong. Lots of leaders will deny new info that contradicts their goals, or take far to long to actually take action when the truth was staring them in the face. Jobs could switch on a dime.

He was against a phone for good reasons, then when his employees solved those problems he became its greatest advocate, to the point of threatening to fire Schiller if he didn't get on the iPhone train.

So great to read personal stories about many of the insanely hard-working & talented engineers who made the iphone and ipod. Their stories sadly are often lost or left out.
Check out "Showstopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft" by G. Zachary. The book was recommended in a thread above. The book is about Dave Cutler and other DEC engineers joining Microsoft to build Windows NT (originally "OS/2 NT").
Have to plug Soul of a New Machine as well. It's more about hardware than software--Data General's Eagle (MV/8000) minicomputer in the early 80s. I'm somewhat biased as I was the product manager for many of DG's systems over a fairly long period (starting about 5 years later) but it's still one of the best books about product development ever written.
Great excerpt. Except, it ignores the fact that there were smartphones, touchscreens, app stores, MP3's on phones way before the iPhone.

It's a very American point of view, since Nokia never made a lot of progress with their smartphones in the US, like Blackberry did, and their phones were strickly email and business.

I had a touchscreen phone that could hold hours of video or hundreds of songs, send instant messages, browse the web, get apps, use WiFi... In 2004. In 2005 you could alreday get GPS, more versatile hardware and better accessories.

The iPhone did a huge cultural change, and pushed UI and apps into the future. But pretending that it was the first one to make icons like phones today use or that it created the first computer-phone like the excerpt says - is nonsense.

It was the first MODERN smartphone phone, in that it defined everything that came after. The ford Model-T wasn't the first car, but in many ways it defined what we're all used to (controls changed though) and was a breakthrough product that sold WAY better than what was available before.

The iPhone with such a large shift from the things that existed before that even though they had many of the features in different forms, it's a bit hard to look at them and say "that's the same thing as a smartphone" instead of "that's a really fancy feature phone" or "that's a PDA with a radio stuck on it".

touchscreen as in stylus or touchscreen as in finger?
No you didn't. If it required a stylus they blew it.
It's like full Pol Pot year zero:

> The software engineers saw P2 not as a chance to build a phone, but as an opportunity to use a phone-shaped device as a Trojan horse for a much more complex kind of mobile computer.

Do they mean... a PDA? Apple's execution and OS is amazing but the idea they invented mobile computing is insane. Palm created that market, then Windows Mobile did, then Apple did, then Android did.

The percentage of the population with a PDA was effectively zero before the iPhone created the market. People carrying Moto Qs were a geeky elite. Apple made this mainstream.

RIM was closest but even they missed the real market with their focus on email and physical keyboards.