• The UI must follow a fast learning curve. The users should be able to easily understand how the app works. If the UI of the app is not user friendly, the users will start creating distance with the app resulting in decreased user engagement.
• The app UI must allow user to learn using the app quickly rather than making them search for or explore learning. The easier is for the users to learn using the app, the more will be the user engagement.
• Consistency is another important aspect of the UI for a Kinect app. As the users become acquainted using the app, they would predict some elements of the app and the designers need to make sure that the elements are in place so that the user is able to find them easily. In other words, it can be said that the design elements should synchronize with the human learning behavior.

Ribbon is a great new feature introduced by SharePoint 2010. It provides great user experience for users with elevated privileges, like contributors and site owners. However, for users with lease privilege, such as visitors and anonymous users, it seems like a big waste of page real estate. Because for those users, all ribbon provides are navigation breadcrumb and welcome control (user name with a drop down list on top-right corner).

So I have been asked to figure out a way to remove or hide the ribbon area from user with lease privilege, and here is how:

1. Open your SharePoint master page



<div id="signinlink"><a href="/_layouts/authenticate.aspx">User Login</a></div>

<Sharepoint:SPSecurityTrimmedControl runat="server" Permissions="ManageLists">
  Put Your Control Here ... such as ...
  <div id="s4-ribbonrow" class="s4-pr s4-ribbonrowhidetitle">
  ..........
  </div>

<style>
#signinlink{display:none;}
</style>
</SharePoint:SPSecurityTrimmedControl>

2. Save and publish master page


OR



<div class="signinlink">
<a href="/_layouts/authenticate.aspx">User Login</a>
<a href="/_layouts/signout.aspx" class="signout">Sign Out</a>

</div>

    <asp:LoginView runat="server">
    <AnonymousTemplate>
        <style type="text/css">
            #s4-ribbonrow { display: none; }
        </style>
    </AnonymousTemplate>
    <LoggedInTemplate>
    <style type="text/css">
            .signinlink { display: none; }
            .signout { display: block; }
      </style>
    </LoggedInTemplate>
</asp:LoginView>


Class in style.CSS
.signinlink
{
color:#093762 !important;
font:12px Arial;
font-weight:bold;
text-decoration:none;
padding-top:20px;
}
.signout
{
color:#093762 !important;
font:12px Arial;
font-weight:bold;
text-decoration:none;
display:none;
}

Find this file, look in your IIS directory for your SharePoint site and look for the App_Browsers folder. Mine file was located at:

C:\inetpub\wwwroot\wss\VirtualDirectories\portal.contoso.com80\App_Browsers\compat.browse
 

Option 1 - Modify the compat.broswer file

<capability name="isMobileDevice" value="true" />
 
for each device in the file located at your Web Application system file location e.g.
C:\inetpub\wwwroot\wss\VirtualDirectories\nbsp80\App_Browsers\compat.browse.
To:

<capability name="isMobileDevice" value="false" />

For each device in the file. I actually tried this and did a find replace on all.

Option 2 - Modify the web.config file

For this fix in the web.config file. Simply add this block in the 'configuration/system.web' child elements:

<browserCaps>
<result type="System.Web.Mobile.MobileCapabilities, System.Web.Mobile, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
<filter>isMobileDevice=false</filter>
</browserCaps>