Anyone who has been reading these pages knows that I am keen on the fusion of the Web, PC, and mobile. Not only have I been elaborating on what makes a great mobile product, but I have been trying to understand the dynamics of Mobile Living in the Web world.
I’ve mentioned a bunch of Web companies that get mobile, companies that understand how to create neat mobile products, products well integrated into the Mobile Lifestyle. What I haven’t done is list Web companies who I think need an infusion of mobility into their products. I don’t mean that these companies don’t get it, but from what I have seen, they either have nothing, or have a long way to go to create compelling mobile products and services.
Some Web companies that could use an infusion of mobility (in no particular order):
Six Apart – TypePad, LiveJournal, Comet; Yahoo! – Flickr, Search, Yahoo!mail; Google – GMail, Search, Dodgeball, GMaps; Blogbridge; Socialmarks; Broadband Mechanics; Wikipedia; Social Text – SocialText.Net, SocialText.Org; AskJeeves – Bloglines; Apple – iTunes, iPhoto, .mac; 37signals – Basecamp, Backpack, Ta-da lists; eBay – Skype; Writely; Amazon; del.icio.us; Feedster; Technorati; qoop; dropcash; Barfrog
This list is by no means complete, but includes a subset of companies I have been observing and like. To be fair, some of these companies have already created connections to the mobile world or already on the right track. Also, some of these are actually companies connected to the Mobile Living space, but could go further than, say, just SMS or basic browsing.
But, here is my question for all Web companies:
What is your strategy to integrate your Web product with the Mobile Lifestyle?
Please leave a comment or send me a private email on your thoughts about this. Here are some related questions to help you formulate an answer.
– How important is integrating your Web-based product to the mobile world?
– How does mobility extend your business model?
– Would you hire a full-time person or team to do the integration for you?
– Would you hire an external team of consultants to either guide you or do the integration for you?
– Would you partner with a company to add mobility to your offering?
– Who do you turn to to understand how integrating your product to the mobile world will impact your business?
Feel free to add or comment on this list of companies or what kind of questions you’d like to ask. You can also participate with your mobile phone: visit http://winksite.com/cschick/mobile (bookmark it!) with your phone or click on the ‘Powered by WINKsite’ graphic on the upper right of this page to open it up in your browser.
A few disclaimers and comments: Of course, the goal here is to get a feel for what Web companies are doing in the mobile space and thus make some business suggestions. I will collect info for the next month or two and try to summarize at some point. All responses mailed directly to me are confidential and will not be repeated without permission. Also, don’t get all excited thinking this is directly related to Nokia (my employer). It’s not. But, what I learn here might spill over there, so let me know if you’ve withheld something because of my employer. And, my personal email address is on my about page.
Charlie, I’ve had this conversation with a prominent member of your list above. Would be happy to share the feedback with you. Give me a call.
And of course, some in that list have very visible initiatives into mobile. There is an opportunity here which isn’t so much about integrating mobile into these solutions, but rather, a mobile solution that integrates some of the services above. The frustration is facing the obstacles of mobile network access and handset variablity.
For example, some operators allow use of RTSP for streaming video and some prevent it. In the U.S., Sprint, Cingular and T-mobile do not block RTSP, but Verizon Wireless does. So anyone could create a video to stream to phones using tools like Apple’s Quick Time (covert to .3gp or .mp4) and Darwin Streaming Server (DSS) and make that stream available. There is great variability in screen size and on board codecs which make the quality and reliability of delivery a challenge. Also, if they happen to be on a carrier that restricts access to RTSP, they won’t be able to view the stream.
My first MP3 phone was a Samsung offered by Sprint in 2000. I’ve been stuck in the pattern of copying from PC to phone since then, and the iPod opportunity was created by mobile operators who didn’t see the opportunity back then and still don’t quite grasp their role for web services and rich media. On the present path, WiMAX or MVNOs are positioned to serve pent up demand for mobile web services as the iPod did for mobile music.
The topic of how mobile lifestyle transforms products and/or services brings to mind many thoughts.
The obstacles of mobile network access and handset variablity only exist as barriers if your app is contingent on carrier distribution/integration and the very latest handsets. Useful mobile lifestyle services do not necessarily require any of the above.
It’s easy to get sucked into the hype that rich media alone somehow brings about a more useful mobile experience. For me an effective mobile lifestyle strategy has less to do with whizbang features and entertainment content (although i want that stuff myself) and more to do with apps that follow, assist, react to or support the daily routines (Is “social rituals” the better thought?) of people without requiring the user to be aware of the technology or lack thereof. Rich media can enhance that experience which is fine, but again…it’s not a requirement.
Last year, Adam Greenfield had (IMHO) an inspring article titled, “All watched over by machines of loving grace: Some ethical guidelines for user experience in ubiquitous-computing settings”. (http://www.boxesandarrows.com/archives/all_watched_over_by_machines_of_loving_grace_some_ethical_guidelines_for_user_experience_in_ubiquitouscomputing_settings_1.php)
One quote from that work should be kept in mind when thinking “lifestyle” – “If ubicomp applications are rushed to market and allowed to appear as have so many technological artifacts in the last thirty years, then they will present those users with a truly unprecedented level of badness.”
Adam goes on to provide some general principles for us to observe, as designers and developers for ubiquitous systems.
Principle 0, is, of course, first, do no harm.
Principle 1. Default to harmlessness. Ubiquitous systems must default to a mode that ensures their users’ (physical, psychic and financial) safety.
Principle 2. Be self-disclosing. Ubiquitous systems must contain provisions for immediate and transparent querying of their ownership, use, capabilities, etc., such that human beings encountering them are empowered to make informed decisions regarding exposure to same.
Principle 3. Be conservative of face. Ubiquitous systems are always already social systems, and must contain provisions such that wherever possible they not unnecessarily embarrass, humiliate, or shame their users.
Principle 4. Be conservative of time. Ubiquitous systems must not introduce undue complications into ordinary operations.
Principle 5. Be deniable. Ubiquitous systems must offer users the ability to opt out, always and at any point.
Re: “There is an opportunity here which isn’t so much about integrating mobile into these solutions, but rather, a mobile solution that integrates some of the services above.”
I agree MoJo. Mobile access to specific services is only part of the story. Part of the opportunity can be found in helping people discover, organize, personalize, and glue together these and other fragmented services and content (i.e. features, functionality, friends, fotos, fun, feeds and favorites). Mobility 2.0 is all about “power to the person”.
I agree to you and even I feel the need. And yeah, as ‘mobile jones’ says – its ‘mobile net access’, handset variability.
But there is also another fundamental problem. Its the UI and the screen. There is a need for ‘re-design’. Either in form of a j2ME or brew application and more simply WAP or WML app. On a mobile browser – all cell phones behave differently => becomes a problem to deal.
The approach would be to give I think limited functions to use. Focus should be on simplicity i.e less functions which would be needed when the user is mobile.
Do mail me – if you get any thoughts on this from ‘mobile jones’