Ars iPhone Review

It's funny. I just read Ars Technica's exhaustive-as-usual iPhone review, and in the conclusion they write:

It's clear to us that the iPhone wasn't meant, at the outset anyway, as a smartphone for smartphone people (who typically end up being business people). Instead, the iPhone was meant as a smartphone for everyone else: average people who, until now, had no reason or motivation to get a BlackBerry or something similar that may have been more difficult to use and had way too many features for the average phone user.

Why is this funny? Because the Ars crew and I completely disagree when it comes to the things we love and hate most about the iPhone. Particularly Safari — it's their "home run," but my least favorite part. This discrepancy is primarily a matter of perspective. I am a typical, non-smartphone using cell phone user. Or at least that's where I'm coming from. I'm used to surfing the web on a computer and using a phone as a phone and contact device. So everything that improves upon the telephone experience is a boon for me, but I never surfed on my phone anyway, and compared to my computer the iPhone just can't stack up. Smartphone users, on the other hand, have been frustrated by this crippled, mobile version of the web on their phones for years, so the iPhone's version of the web is a huge boon for them.

What's amazing, though, is that in the end we both come out fairly pleased with the device on the whole. Ars gives it an 8 out of 10. I'd give it a 9. But overall there is enough good about the iPhone to please both the cell phone crowd and the smartphone crowd. Now that's what I call balance!

If you really want a thorough review, I highly recommend the one at Ars.

My iPhone

I bought one on opening day. I hadn't intended to, but sometimes the hype gets the better of even me. Well, hype and a burning hatred for my then-service provider, Sprint. So I bought one on opening day, over a full week ago. And I can honestly say I haven't been happier with a purchase since I bought my first Powerbook. In fact, this puppy basically is my new laptop. But it fits right in my pocket.

(A side note: A few days ago I got a bill from Sprint. Not for the early cancellation fee like I expected, but a bill for service that I'd paid several days earlier on a phone number no longer under their purview. This will not be the first time they've tried to charge me for a phone that's no longer in service. When I first moved to New York, it took me three months to cancel my previous phone. Their service has gone steadily downhill ever since. Sprint, this is why people hate you and will spend hundreds of dollars to switch to another service. Assholes!)

A lot has been said about the iPhone thus far. And I pretty much agree with most of it: the iPhone, with the exception of a few forgivable oversights, is a revolutionary, market-changing, life-altering device, and easily the best cell phone ever.

This sort of praise has been near-universal among iPhone owners. And for good reason. The iPhone is all those things. But it's the little things that people love and hate about the iPhone that vary from person to person. So I wanted to add my two cents, my voice to the chorus as it were. And I wanted to see if I could do it all (or most of it) on the iPhone itself. So, for a week I've been taking notes on the iPhone on the iPhone. And I'm typing this entire article on my trusty iPhone, between meetings and lunches, totally on-the-go style and shit, using the Mail application.

So far so good.

Google Maps
What probably surprised me most was how endlessly useful and well-integrated the Google Maps feature is. My first day with the phone I had dinner plans. I knew the name of the restaurant, but no one could tell me the address. Did I fret? Did I worry? Did I complain? Heck no! I just Googled it. On my cell phone! But not only was I able to easily retrieve the address, I also got the phone number and URL for the restaurant's site, and this information was easily added to my contacts for later easy retrieval — calling, browsing, want have you. Now I find myself looking up every place I ever call for take-out and adding it to my contacts because it's so damn easy and downright fun. Nearly everything about the iPhone works as easily and seamlessly. It's one of the true joys of owning this phone.

Camera
The next surprise for me was how good the photos look. The camera on the iPhone may not have many (ANY!) features, and the images may not hold up to a dedicated digital camera, but it comes a lot closer than any phone I've ever had.


Camera Sample 1: The Park
(click image for larger view)

Color and contrast look quite nice under normal lighting conditions. I've actually managed to get some really nice shots — shots that on my other phones would've looked like total crap.


Camera Sample 2: Some Dog
(click image for larger view)

And of course those shots can easily be assigned to contacts or wallpaper with the press of a few virtual buttons.


Camera Sample 3: Flower
(click image for larger view)


Optimizing Photos for iPhone:
Apparently, photos from my old phone are not good enough for the iPhone

(click image for larger view)

Contacts and Syncing
And speaking of contacts, all my contact information transfers seamlessly between my Mac's Address Book and my phone now. Windows users may be used to this, but it's another first for me. Synching my phone and my Mac now is not only doable but fairly easy and trouble-free. My only complaint is that, while Address Book syncs are two-way and multi-computer aware, most of the other sync functions hinge on the typical iPod paradigm, in which one computer is the master to which the iPod syncs. This is unfortunate — I have a bunch of computers I'd love to sync up — but not terribly surprising. And as long as the contacts can sync with multiple machines I can live with it.






Some Sync Conflict Dialogs
(click image for larger view)

Oh, one other complaint: locating a contact is a fairly straightforward affair — go to your contacts and scroll the list. Not bad. But I have hundreds of contacts, and this glut of contacts cries out for a search function. Apple's Address Book application has search capabilities. The iPhone's version of Safari has it too — start typing a URL and Safari makes appropriate suggestions based on history and bookmarks. Indeed, my previous phone — a Samsung A900 — even had this capability. It was just dog slow and a total pain. I was really hoping Apple would improve upon this functionality. Instead they chose to leave it out. Not a deal-breaker, but a bit disappointing. I do find myself wanting this feature on a regular basis.

While we're at it, do the same for the Calendar application.

Mail, Folders, Drafts
Mail syncing is not what it sounds like either. That is, account settings get synched but not the mail itself. In fact, the mail client is a stripped down version that (with my IMAP server, anyway) only shows top-level folders — Inbox, Sent, Drafts and Trash. No subfolders are visible. No rules are applied. No spam is filtered. Nevertheless, it's handy as hell to have constant access to my latest mail, and to anything I might be working on — like this article, for instance. In fact, the more I think about it, I'd rather save the organizing for my computer, so this is totally fine, and probably a good thing in the end. Typing in Mail, as throughout the iPhone interface does take some getting used to, but I'm already pretty proficient with two fingers after only a week. The only weird thing in Mail is that saving drafts requires a press of the "Cancel" button, after which you are prompted to save the draft. There is no "Save" button. (Though there does appear to be an auto-save, which I just learned after my first Mail crash — yikes!) I find this behavior very unintuitive and more than a little scary.

Notes
Another pleasant surprise has been the Notes application. I'm a big note-taker, and I find myself using it constantly. It couldn't be much more bare-bones — or much uglier — but I use it all the time. And again, typing is generally quick and trouble-free.

Safari
Having real web access has proven pretty damn handy as well, though without WiFi it's kind of painful. In fact, surfing the web is probably the least satisfying thing about using the iPhone. For one, Safari crashes on me with a fair degree of regularity. (And by the way, the other apps almost never do.)


Crash Log Dialog: The Logs are in:
/Library/Logs/CrashReporter/MobileDevice/iPhoneName/Baseband
(click image for larger view)

And, though it's a fairly full-featured browser (I for one am glad there's no Flash most of the time), pages not designed for the phone can still be difficult to read. The New York Times, for instance, which sometimes uses a fairly wide column for articles, almost must be read in horizontal mode. Fortunately — brilliantly — the iPhone provides just such a feature. But surfing the web is just generally not the rich media experience I was hoping for. It has been useful for cheking our network and the status of certain servers. And it will be great for when I want to read sites that consist mainly of text. But really, who has time to read these days anyway?

Battery
I've also been quite happy with the battery life of this phone. I haven't actually talked on it for any length of time (that will require a call to Mom), but I use it for notes, mail, Google and checking the weather all freaking day (I can't keep my hands off the damn thing) and my battery seems to consistently last a full two days, though barely. My old phone would die in the middle of any call over a couple hours and needed to be recharged nightly. 'Course my old phone couldn't check mail, weather, Google or take notes either — at least not without jumping through some major hoops and incurring some major charges. I guess when I think about it, one of my favorite things about this phone is that it's not my old phone. Doing anything on that phone was a chore. Most everything on the iPhone is either dead easy or downright fun. Who'd've ever thought you'd hear a cell phone described as "fun?"

But I digress.

The Phone
The phone part of iPhone is fine. Nothing to really write home about, but fine. The nice thing about using iPhone as a phone is, of course, the interface. There is no talk button. When receiving a call, as everywhere else on the iPhone, you're presented with a list of contextual options — "Answer" or "Decline" if you're using other features of the device. I actually wasn't sure how to answer my first call. The phone was locked, so I unlocked it and then panicked a little. "Now what?" Turned out, I had already answered by the simple act of unlocking the phone. Nice!

Sound quality, as reported elsewhere, is clear but a bit quiet, especially given that I live in a big, noisy city. It's much better with the earbuds, but I'm not usually in a position to use them, especially when I'm out and about. I do hope they fix this with a firmware or software update. I have a feeling they will. Still, sound is clearer with less background interference than my previous phone. So overall I'm pretty pleased with the phone portion of my iPhone.

Improvements
The iPhone is by no means perfect, of course. Though I'm about as happy with a version 1 device as I think humanly possible, there are just a few things I would love to see improved. Everyone has their priorities. My list goes something like this:

  • Contact and event searching
    Like I said earlier, this would be really nice if implemented well.
  • Better backspace placement
    I am always hitting the backspace button inadvertantly (though I am getting better).
  • Cut/copy/paste
    This a given, and probably the number one complaint about the iPhone. If Apple could provide this with a software update, everyone would be pleased as punch, I'm sure.
  • Disk access
    I was pretty bummed that I can't use this iPod/iPhone as a hard drive. It's the one thing even my old phone can do. Give me access to that 8 gigs, please. (There is now iPhone Drive, though I'd rather not have to pay to access my own hard drive, thank you very little.)
  • Volume increase
    It would really be nice if we could turn the iPhone up a bit for calls. Plenty of volume for the iPod, though.

That's about it. I'm really a pretty happy camper.

Final Thoughts
All kinds of new, mind-altering experiences have come my way since getting this phone. For one, people actually talk to me at parties now. The iPhone is actually so cool it spills over onto me. It has a surplus of cool. Cool to spare. And for the first time ever, though I've never been an iPod person, I've actually put on headphones and used the iPod functions of this phone (I may now be hooked like the rest of the world). I'm not sure why I tried it, really. I guess I just like the thing that much. It's just so damn touchable!

But the most telling event happened the other day while I was using my computer, actually. I was looking at a web page and wanted to scroll down. And for just the briefest of moments it was all I could do to keep from using my finger.

This is big, folks. Really big.

This article written on my iPhone
(but edited on my computer)

External Network Unification Part 5: Almost There

It's been quite some time since I've been able to post anything of any substance. This has a lot to do with the fact that I've been super busy relocating our department and participating in the gut renovation of our lab. This has been an immensely stressful process, but in the end I find that I've learned so much from it, I simply can't complain. I'm coming out a far better SysAdmin than I was going in. And that's a remarkably valuable thing to both me and my employers.

But moving and planning the physical aspects of the new lab has only been a portion of what I've been working on. This renovation has been the perfect opportunity to rebuild our network infrastructure, and part of said rebuilding has resulted in the near completion of our authentication unification project. At this point we've gone from eight different authentication servers — that is, anytime we created a new user, we had to do so on eight different systems — all the way on down to two. Which means that now, anytime we create a new user, we do so on two machines.

Our goal is to get it down to one, hopefully before the Fall semester begins. Our mail server is proving to be the most difficult machine to get working with LDAP authentication, mainly because it authenticates mail users through the wonders of some weird combination of authd, Courier and PAM, and we've yet to crack the magical code that gets these all working in tandem via LDAP. Aside from Mail, though, everything is done. So I thought I'd take a bit of my hard-earned vacation and loosely describe to you how it's all working.

Before I start I'd like to just acknowledge all the help I've had from my fellow SysAdmins in the department. I had a huge amount of assistance on the *NIX server side of things, as well as with network infrastructure and even some last-minute PHP finagling without which this project would have taken significantly longer. In fact, all I really had to do was build the authentication servers and clearly articulate what I wanted. I'm extremely grateful to everyone who helped out.

The little bit of network infrastructure I mentioned is our DMZ. We now have a proper — and more importantly, properly secured — DMZ on which to place an authentication server. I won't go into too much detail here, but suffice to say, having a secure DMZ gives us all kinds of options for authentication between internal and external networks, and makes me feel a whole lot better about using Mac OS X Server as our authentication system for both networks.

Yes, we are using Mac OS X Server to authenticate our entire network. The reason is because Mac OS X Server is the most mature and usable implementation of LDAP for user authentication available on the market today. Is it perfect? No. Is it completely secure? Probably not. Is there anything that even comes remotely close to being able to handle the complexities of user management and database redundancy across platforms with such remarkable ease-of-use? Nope. Nothing. We tried building our own custom LDAP server, which would have been excruciating, and would have taken forever. We tried Red Hat's Directory Server, which looks like it will eventually turn into something to match Mac OS X Server, but which just wasn't yet up to snuff. Nothing matched Mac OS X Server, which did everything we wanted it to, right out of the box and with a minimum of fuss. In fact, once the user database is built, building a Mac OS X master or replica authentication server is a complete and total breeze. At the time of our building and testing it was really the only practical option.

So, here in a nutshell, is what we have:

Internal Network
All authentication originates from the internal network. Passwords can only be changed from the internal network at this time, which is by design. Systems on the internal network include:

  • Master Authentication Server
    Hosts authentication for... Well... Everything, really. This is essentially the same server we used all last year for all our internal authentication needs for Mac, Linux and Windows workstations. It's now being used to push authentication to the external network as well.
  • Internal Replica Authentication Server
    This provides replication of the Master. Should the master fail, the Replica is intended to pick up services (though this doesn't always work perfectly).
  • File Servers
    We have two file servers on the internal network — a Mac and a Linux box — both of which authenticate directly against the Master.
  • Workstations
    We have about 30 Mac, Windows and Linux machines all authenticating to the Master.

DMZ
The DMZ sits between the Big Bad Internet (BBI) and the internal network. It has its own firewall that is fairly strict about what can get in from the BBI. All DMZ authentication originates from the internal network, but is provided by a single server which sits on the DMZ. Systems on the DMZ include:

  • External Authentication Server
    This server is also a replica of our Master, but it's not intended as a failsafe. Rather, it provides authentication services to the entire DMZ. It gets its user database, of course, from the Master. But for other systems to bind to an LDAP server, its role must either be "Master" or "Replica." Setting the role to "Connected to a Directory Server" won't work. In addition to sitting on our DMZ, which is properly firewalled against the harsh realities of the Big Bad Internet (BBI), this system also makes use of its own strict local firewall for an extra added layer of security. Also, all replication communication between Replica (DMZ) and Master (Internal) is encrypted.
  • Data Server
    In addition to unifying authentication, we've also consolidated data storage and access wherever possible. In the past, for instance, movies streamed from the Quicktime Server were stored on that machine's local drive. Web sites were stored on our web server. So, building a web site that used Quicktime Streaming required users to log into two separate machines — the Web Server and the Quicktime Streaming Server. Now we're storing all user-generated content on a separate, dedicated machine — our Data Server — and sharing that machine out to the various servers via NFS. Centralizing this data store means users have only to log on to one server for anything they ever want to do. And also that only that server needs to authenticate users. And yes, that server authenticates them via LDAP on our External Authentication Server. All neat and tidy. Internal and external home account data is still segregated, however — users still have separate internal and external data storage. Though, if we could figure out how to do it securely, this could change.
  • Quicktime Streaming Server
    This machine also uses its own local firewall. It gets its user database from our External Authentication Server over secure channels using the "Connected to a Directory System" as its role currently. Ultimately, however, because of the Data Server, this machine will not need to authenticate users. We are leaving the ability open temporarily to accommodate legacy users.
  • Drupal CMS
    Our new Community site is built on the Drupal engine. We're using the LDAP module to authenticate to the External Authentication Server. Drupal's LDAP module is simple and easy to set up, as is the Drupal system as a whole. So far we're very happy with it.
  • Computer Reservations System
    This is a custom web app built long ago by a former student. We've (and by "we" I mean my colleague) basically hacked the PHP code to authenticatevia LDAP rather than MySQL.
  • Mail Server
    Currently not authenticating to the External Authentication Server. We're working on this and hope to have it working by the beginning of the school year.

The Future
Yes, there's more we want to do. It's always amazing how, once you've completed something, you immediately start seeing ways to make it better.

  • More Redundancy
    Ultimately, in addition to the Replica, I would also like to automate a clone of the Master's boot drive to an external firewire drive as sort of an ultimate safety. Should anything ever go wrong with the Master, I simply plug the firewire clone into virtually any Mac system on the internal network and I'm back on my feet. It might also be wise to have some sort of failsafe for external authentication as well.
  • More Security
    while our setup is fairly secure right now, there are a few areas I'd like to beef up even more when I get a chance. In particular, our CMS connection is not as secure as I'd like it to be. And ultimately I'd like to harden every machine on the DMZ to the best of my ability.
  • More Unification
    Anything else we can unify — and at this point that's mostly internal and external data — I'm open to considering. It's going to be really interesting for me to look critically at what we've done so far and find the flaws and refine the system. But I'll constantly be looking at ways to simplify our current setup even further without compromising security. The easier our network is to use, the more useful it becomes. We've come a long way, but I'm sure we can find even better ways to do things.
  • More Services
    Now that we have an infrastructure in place for user creation, we can add services freely to our network without the worry of creating users for said services. New services need only the ability to authenticate via LDAP. We're already planning an equipment checkout system, and possibly some calendaring systems.

So, I've just finalized the master authentication server. It's done. Built. Finished. Kaput. The rest of our servers are still in various states of finality, and we have until September to lock them down. But right now, unified authentication is, for all intents and purposes (and with the exception of mail), working. And we couldn't be happier. The ultimate test will be, of course, letting users loose on this new infrastructure. I'm betting they'll like it almost as much as we do. At least the ones who know the old system. New users will be none the wiser. Ain't that always the way?

*Sigh*

Magic iPhone

Just got done watching the iPhone Activation Video — 'cause with the announcement of the very reasonable service plans I've pretty much decided I'm getting one of these puppies — and I noticed a bit of an error in the video. The demonstration iPhone in the video is apparently an 8 GB model and starts off with 7.27 GB of storage.


iPhone: 8 GB Model
(click image for larger view)

But by the end of the video its capacity has increased tenfold!


iPhone: 75 GB Model
(click image for larger view)

Well, that cinches it. If the iPhone's capacity magically grows as you add data, it's surely the most wondrous device ever, and certainly worth having.

I'll take three!

Finally!

I still have no time to post, but I did want to squeeze in a quickie regarding yesterday's WWDC news (or lack thereof).

Needless to say, count me among the underwhelmed. A usual, we were all expecting big things, but this seemed like WWDC 2006 reheated. Leopard looks nice, but hardly revolutionary. We've been waiting two years. We want revolutionary. We want the iPhone on the Desktop.
I guess there's always next year.
Oh yeah, and Safari on Windows? Great. If you're a Windows user. Or a Safari user. Unfortunately, Safari lost me a while back, and it's going to take a lot of catch-up for it to get back to the top spot in my browser list. Still, I will say, I'm typing this in the Safari 3 Beta, which I didn't used to be able to do on Blogger. At least not properly. There are still some things that don't quite work right, but it's much better than it was. And overall I'd say I'm favorably impressed with this version.
But for me the happiest moment was seeing Apple's new home page. They've finally ditched the 10+ year old pinstripe and Chiclet tab bar for something a bit more modern and refined.

Finally!


Apple's New Tab Bar: Much Better
(click image for larger view)

UPDATE:
As a couple readers have pointed out, looks like the Apple redesign is for the U.S. site only at this point. I never realized I had such an international readership.