RIM is working on rich attachments, just like Apple's working on push, but if you had to choose a device based on present features (and that's how it works), you'd have to decide whether you want the first fragment of your e-mail message instantly or it's worth a potential 15-minute wait to read a rich attachment. I can come up with a nearly endless list of trade-offs.
Another excellent give and take example is found in the browser: Apple wins hands down for readability and controls, but iPhone lacks, and likely will always lack, Java and Flash. On the other hand, no mobile device can touch iPhone for AJAX content. iPhone was made for AJAX, and the Safari browser evolves faster than others.
Who comes out on top? It likely depends on whether you're dependent on existing Java MIDP software. If you have the option of fresh development, the iPhone SDK might have an answer, or it might not. I can't say, because the iPhone SDK is under complete non-disclosure. I was quoted in the public portion of the Worldwide Developer Conference keynote, so I'll stretch my neck out and tell you that there isn't a better mobile development platform, toolset, or documentation set than iPhone's. It's foolish of Apple to keep people from writing about it.
[For more on the shortcomings of Apple's iPhone developers program, read "Apple's iPhone contracts leave developers speechless."]
Stay tuned
I'll continue to work with my iPhone 3G and report on my experiences in my Enterprise Mac blog. But for now, I'll say that the iPhone 3G is probably the best $199 smartphone on the market. It shines in rich documents,
over-the-air sync, direct connectivity with Exchange Server, and AJAX applications. iPhone's trump card is usability. You
can drop an iPhone on the desk of a person who's never seen one before, and they'll be working it within the hour. The typing
takes getting used to, but it is leagues better in iPhone 2.0 than on the original iPhone. Most of all, you can actually read
the thing. Text and graphics are as clear as on any desktop, and Apple always fills the screen.
I suppose I'd be remiss if I failed to mention that an iPhone is also an iPod. AT&T may not want you to hit iTunes with the iPhone 3G, but podcasts, video clips, and PowerPoint decks are within easy reach. But I wouldn't advise downloading such files over the air if you're not on a business rate plan. AT&T will charge consumers with per-kilobyte overages or flip them into metered data plans if they exceed unspecified transfer limits. Surprise! Business customers are more likely to get a call from their rep if volume becomes a problem.
If you have existing mobile applications that rely on Java, Flash, or .Net, or if you have server-side applications that use BlackBerry Enterprise Server, iPhone's not for you. There's no way to get from any of these to iPhone. Whatever custom mobile solution you have now would have to be reconceived as AJAX or iPhone-native software, or as a client/server solution with an AJAX front end.
But if you're not constrained by your currently deployed mobile software, give the iPhone 3G a trial run. I was pleasantly surprised to find that, on the whole, the iPhone 3G clears the bar for professional and enterprise use, and in some ways, sets a higher one.
Tom Yager is chief technologist of the InfoWorld Test Center. He also writes InfoWorld's Ahead of the Curve and Enterprise Mac blogs.
Talkback
E-mail
Printer Friendly
Reprints



