When Microsoft launched SharePoint 2010 over a year ago, they promoted an improved mobile experience. This new mobile experience promised better connectivity through devices like phones. However, is it any better and can any organization realistically use what’s provided out of the box? The answer, for most firms, is no.
Much like the rest of SharePoint however, the mobile components of SharePoint 2010 can provide a foundation. This foundation comes in varying forms. Organizations hoping to connect their mobile workforce to content and/or functionality in SharePoint will want to understand what is and is not mobile in 2010.
What is Mobile?
Since then, mobile devices have come a long way. The advent of better smartphones and far better pure-tablet devices create loads of enhanced “mobile” possibilities. In very real terms, mobile in the year 2011 still means creating a unique experience. However, this experience is largely through specialized HTML interfaces (for less well-endowed smartphones like Blackberry) or an application (e.g. through iTunes App, Droid and/or the Zune store for the Windows Phone 7 devices).
These experiences aren’t simply watered down versions of their larger, PC-formatted cousins, but tools that provide the “heart” of the application in an easy-to-consume mobile package.
What Does SharePoint Provide?
Microsoft delivered a pretty radically improved SharePoint platform in 2010. Unfortunately, a vastly improved mobile experience wasn’t front and center. Instead, Microsoft gave us a slightly improved version of their watered-down HTML-based interface layered with more platform capabilities.
This mobile interface is enabled largely by default and is as easy as browsing to your SharePoint site using your mobile phone. What you get is a document and list-centric view of your site. The mobile site provides basic access to list items and documents, but little else. In fact, it doesn't even allow for any real interaction with those items or files, save viewing them. Microsoft has published some good guidance on what you can expect.
Even at a time when iPhone sales were skyrocketing, Droid devices were taking off and Windows Phone and BlackBerrys were well established, Microsoft did little to capitalize on their capabilities. In fact, given the explosion of the new tablets from Apple, Samsung and Motorola, Microsoft clearly missed a grand opportunity to further embed SharePoint in the information worker psyche.
Controlling the Default Experience
Even though the default mobile experience isn’t much to talk about, to Microsoft’s credit, they do provide mechanisms for controlling/improving the experience a bit. This control starts with the “compact.browser” file (located in App_Browsers directory of your SharePoint’s IIS directory). This file determines what device browser agents are considered “mobile.” If the browser agent is listed, SharePoint will automatically redirect to the mobile URL (http://[YOUR_SITE]/m or http://[YOUR_SITE]/?mobile=1). If not, you are directed to the standard interface (or the one you’ve created). You can find a list of “out of the box” supported browsers listed in the Technet blog article listed previously.
The magic, though, isn’t the automatic redirection, but rather the various files that present this experience. For example, the file “mbllists.aspx” is the default page for viewing lists. It’s constructed using a collection of various mobile templates and uses the browser capabilities file to determine how to render for specific devices.
For the more technically inclined, you can also manipulate the default mobile page. Microsoft provides guidance on how to accomplish updating the basic interfaces on MSDN. The changes are largely limited to the master page and theme. However, for those seeking only to stick their toe in the pool of mobile experiences, this is a good start.
- SharePoint is Already Legacy
- Are You Too Old to Work in Tech? IT's Midlife Crisis
- What to Do When Yammer Adoption Stalls
- Web Content is Obsolete
- Faking Big Data #strataconf
- Salesforce Shares Its Marketing Vision #DF14
- Is Your Information Architecture Ready for SharePoint 2013?