Friday, July 31, 2008 -- 10 a.m. -- on my couch
It's been a while since I've done one of these.
I received an e-mail from caller John the other day and he had a very thought-provoking look at why he doesn't think we've seen copy and paste yet.
Yes. Yet.
Here's what John wrote
I have been reading your blog since before 1.0 came out, and like you, I have wondered why copy and paste isn't in the iPhone's OS. I think I have figured out why.
The president of our agency loves his iPhone but he desperately wants an app to edit his Word docs. I kept promising that there will be an app to do that. None has come yet. It occurred to me that with 2.0 allowing us to read Pages docs that Apple is probably working on iPages. Of course, they want to be first to get that one out.
Revelation: The best way that Apple could stunt any doc editing app would be to keep copy / paste out of the OS. I predict with copy/paste we will see that editor - from Apple.
That's an interesting thought. iPages. Or iWork Mobile perhaps?
Caller Chris was the first person to mention an iPhone version of iWork several months ago ... he wasn't talking specifically about cut and paste at the time, but he was right in that it makes total sense for Apple to release this app and it makes total sense based on what caller John is saying here.
The fact that the iPhone can now read iWork documents is very important. It could read Word files but not iWork files, which seems a bit backwards.
Interestingly, there are plenty of "smart" phones out there that only allow for read access on office documents -- and other Windows Mobile devices that allow read and edit.
I remember when I purchased my T-Mobile MDA about 2 years ago that one of the things that drove me to decide on that phone was the ability to edit office docs. I actually used to write things in Word on the train when my commute was a little longer than it was now. It wasn't great, but I could do it and that meant a lot.
I shopped around. I looked at the Motorola Q and it was a nice looking device, but it was read only. In the end, I wasn't happy with that.
When I found out the iPhone was read only, I wasn't too happy ... but it wasn't going to stop me from buying an iPhone.
Then, I read Chris's idea and I thought .. yep .. that's an awesome idea. It makes sense.
And now when I read John's idea, it makes total sense.
And I'll tell you what ... if mobile iWork landed in the App Store tomorrow, I'd pay $50 for it ... that is, if it worked as well as I think it should. However, as an owner of iWork, I think I should pay less, but we'll save that for another post.
So, callers, what do you think of what John had to say? You think it makes sense? Let me and John and everyone know in the comments.
Thanks for taking the time to send this to me, John. And if any of you out there have any insight like John's, please send it my way. You could be featured in an upcoming edition of caller's corner.
Thanks for calling.


























