To iPhone or not to iPhone, that is the Question

[drscott]

Paul's getting his new phone today, so I need to decide what to do with mine. The iPhone's really attractive, but a few faults keep me undecided: no Bluetooth stereo headphone protocol, no cut-and-paste, slow data network. The first two will probably get fixed with software updates, but the network hardware won't, and it's rumored the new model with much faster network hardware will appear in April '09.

I don't mind paying Steve $100/year for being on the leading edge, but $400/year is too much.

So I'll look through the alternatives, and consider keeping my old phone until next year's iPhone 2.0.

Comments

[excessor.livejournal.com]

It was long ago, wayyyy before I knew him.

[pulsecub.livejournal.com]

Back when they used those Apple Card Stacks (I forget what they were called...)? :)

[dr-scott.livejournal.com]

Not THAT long ago, more like '87-'91, and it doesn't mean much -- meant I used their toolset and did some programming. What Paul means is that I don't approve of the extreme "no buttons" approach that means some of the commonest things you'd want to do with a phone require looking at the screen and several gestures to accomplish, instead of a button push. Elegance is nice, but not when it sacrifices too much usability.

I'm still making up my mind, and part of me wants to not care about the near-term obsolescence of the network hardware to get the easy integration. But better to forget about it for six months...

[pulsecub.livejournal.com]

Well, here's one thing to factor into your equation (since you like those so much ): You have a month, I think, to try it out and return it if you don't like it. There's nothing like living with a device for a while to see if it fits into your life before making the commitment for the long haul.