T-Mobile has announced that the new flagship Android device will come with Sherpa, an app which personalizes the device to the end user. Here is a short slide show on the myTouch. This is the first baby step for a service provider in truly differentiating themselves using Android.
Android has several advantages which have so far not been sufficiently leveraged. It has Exchange support, as well as POP/IMAP; it has great web-based sync to Google calendars (which also easily syncs with Exchange) and contacts; and open source makes it easier in some ways to develop against than most other platforms. So what could be done to take better advantage of these traits?
Pulling all of these together suggests carriers should focus on enabling the social address book through encouraging third party providers to tackle carrier-suggested roadmaps for messaging, calendaring, and contacts management.
T-Mobile has taken the first steps by using a 3rd party to launch Sherpa. But personalization cannot take place within an app to be meaningful.
What Sherpa should become is not personalization within an app. The app should merely be a mechanism to ensure customers are opting in to allow personalization and by installing it Sherpa should embed itself within contacts, calendar, maps, and messaging.
For example if you frequently sms your friend then his contact details should show "text" first; conversely if you only ever call someone their contact detail should show a phone icon and offer one-touch dialing as the first option. People who are near you in place, time, and online status should be surfaced before people who are offline, not near you, etc.
Google's new "what's here" feature for maps should also show how many other mobile users are at a location and should filter/rank content based on user preferences and the supposition that the user is mobile.
T-Mobile should infuse Sherpa with this type of network-derived data to seed preferences with what other devices are doing, where they are doing it, and when they are doing it. None of this requires personally identifiable data. But your phone should know if it should ring or vibrate based on where you are. It should know where other people like you are--and are not--and where they are going. And all of this should be presented within the call log, contacts, and home page. Not within an app.
There is so much which could be done to make Android phones the device of the social graph. But doing so does not mean adding pile of features and UIs on top of the device. It means stripping out extra layers and steps to make the core actions of the phone smarter and more dynamic.