Device-aware applications

From Sense/Net Wiki
Jump to: navigation, search
  •  
  •  
  •  
  •  
  • 80%
  • 6.0.5
  • Enterprise
  • Community
  • Planned

Overview

Device aware application - iPad Login

The Smart Application Model is a feature of Sense/Net for defining frontend templates to display and manipulate data in the Content Repository. It enables portal builders to create a unique look and feel for content while also saving time. Beyond that, device-aware applications can be created for customizing the user interface for specific devices, e.g. tablets, mobile phones or even different internet browsers.

Details

In the past we accessed internet sites only from a desktop browser. Nowadays there many different browsers and devices that can access the web and may need a different user experience. There is a possibility that you want to display the same data in a different form on different devices. For example the 'desktop' version of a workspace main page may display a lots of lists, recent content and user links, while the same workspace entry point should display information in a much more compact way on a mobile or tablet screen. When the same URL (e.g. http://www.example.com/workspaces) is visited, it can present a different user experience depending on the device.

Sense/Net provides an efficient way to handle this task by introducing Devices. Using our application model you can define custom applications that will display content on specific devices.

Device-specific applications

Device-aware applications are similar to any other application on the portal - in most cases they are Smart Pages. The only difference is that they reside under the customized application and have a different name - the same name as the device they are built for.

For example if there is a Browse application for the Task Content Type somewhere in the Content Repository, you can build a custom page for tasks for the iPad if you create a page with the following path:


  • .../Workspaces/(apps)/Task/Browse/iPad


Note that the Browse content above can be a regular application page but it is possible to create a simple Folder for only holding the iPad application.

When a user navigates to a Task content under the Workspaces section from an iPad, he/she will be presented the custom iPad page instead of the common Browse page. If you want to define an Edit page for the Task type to display on the iPad, you should place it under an Edit application and name it as iPad.

Examples

See the following, simple content tree:

  • MySite
    • (apps)
      • GenericContent
        • Browse
      • Task
        • Browse
    • Workspaces
      • (apps)
        • Task
          • Browse
            • iPad
      • MyProjectWorkspace
        • Tasks
          • Task1 (type: Task)
      • MySalesWorkspace
        • (apps)
          • GenericContent
            • Browse
        • Tasks (type: Task)
          • Task2


Let's have a look at some requests that may arrive, and how the system handles them. We do not specify an Action in these requests, which means that the default action will be used, which is Browse.

  1. Found (apps) folder under Workspaces
  2. Browse application found under the type folder Task
  3. The user agent states the request is sent from a desktop browser.
  4. Application used: /MySite/Workspaces/(apps)/Task/Browse
  1. Found (apps) folder under Workspaces
  2. Browse application found under the type folder Task
  3. The user agent states the request is sent from an iPad.
  4. Application used: /MySite/Workspaces/(apps)/Task/Browse/iPad
  1. Found (apps) folder under MySalesWorkspace
  2. Browse application found under the type folder GenericContent
  3. The user agent states the request is sent from an iPad, but there is no custom iPad application here.
  4. Application used: /MySite/Workspaces/MySalesWorkspace/(apps)/GenericContent/Browse

Please note that in the 3rd example above the portal will serve the request using a more general application (defined for the GenericContent content type) because it is defined on a deeper level than the iPad application for the Task type on the Workspaces level.


Related pages