The mobile views are not a solution, so many customers turn to custom design, but I would rather a responsive design be built into SharePoint.
Thank you for the suggestion! In the past several months, we have released a series of new interfaces for SharePoint Online, all of which are responsive (e.g, modern list, modern document library, modern team site home page, new site connect page, and modern site page, etc.). We also released mobile apps across iOS, Android, and UWP platforms. Hope these help you better work on mobile and on the go. Let us know if you have any new feedback/followups.
26 commentsComments are closed
Greg Burns commented
The mobile view of a site fails in two ways:
1. The mobile view exists on a separate URL, which the user might be required to type in (and on a mobile phone, connecting/logging in to a SharePoint site is already unpleasant).
2. It represents content containers only: documents, list items, etc. While this may be convenient for some, that is not the entire point of a SharePoint site. A site is more than a file share, it's a functional interface to services and information. Users need to see things like timelines, newsfeeds, navigation and layout.
You may argue that site owners who want to deliver a site like that should use Publishing features to create a responsive portal. But that is not an option for the casual user. Branding SharePoint like that involves a steep learning curve.
A collaboration portal is meant to be simple. But "simple" doesn't just mean "give me my files". We want it to be "Simple" AND "Responsive", so no matter what type of device my users have, they will never feel frustrated or lost.
Suggestions: tagging zones and divs for screen width ranges, to determine what is hidden, stacked or resized; collapsing quick launch to hamburger menu; automatic creation of renditions of images after upload (e.g. resized for different resolutions).
And maybe choose a well-known framework like Bootstrap, instead of creating a custom SharePoint one.
Bill Ayers commented
Yes, an increasingly important use case for customizing master pages is to make them responsive to support mobile. But customizing master page, particularly on O365, has drawbacks (per PnP guidance). So ideally MS would invest in making the OOB pages responsive, perhaps using something like Bootstrap as a starting point.
This is especially important with recent guidance putting custom master pages at the bottom of the options list for branding. Yet, they are the only way to get your fingers in the pot deep enough to do responsive design.
If you deliver only one improvement to On-Prem in vNext, please let this be it...Mobile views as they exist today are not the answer for mobile team sites...
Work in progess is something that needs improvement.