Your Web site may be optimized for the desktop experience and may need help translating to mobile use. Mobile applications require different, more compact navigational aids, and content must fit into a smaller footprint. Mobile Web sites need "click to call" options to take advantage of cellular technology, a robust search, flexible menus, and quick access to content. Tables and figures may need to be adjusted to avoid unnecessary "pinching" and scrolling.
The following topics help you develop Mobile Web pages for Ektron.
Ektron separates content from presentation so that content developers can concentrate on composition. A mobile device template, because of the smaller footprint, may have a single column to eliminate horizontal scrolling, pinching and zooming. Instead of creating different content, you decide what is optimal for each device by creating different templates. You may need to replace objects (such as a rotating banner or those with large download times) with mobile-equivalent objects.
Mobile device templates differ from desktop ones in several ways.
In addition, some content considerations are needed.
Ektron can detect specific characteristics of a mobile device, such as the differences between the Android Droid X and Droid 2. These characteristics help you determine how to render the user experience. For example, one device may support Flash technology and another may not.
To determine which mobile devices to add to your device configurations, review your Analytics reporting to see which mobile devices are browsing your site. To see the Browser and OS report:
The example shows that Android and iPhone mobile devices have browsed pages. Create templates and device configurations to improve the experience of these visitors.
Follow these steps to set up a mobile template. If additional details are needed, a link is provided at the end of the step.
<add key="ek_EnableDeviceDetection" value="true">
account.pb.smartphone.aspx
.Now, if a mobile device user accesses a page which uses that template, the mobile-enhanced template displays the content.
Create a device configuration to accommodate a variety of mobile devices by grouping characteristics, such as display size. You can group devices for standard presentation and add refinements for specific devices. For example, a device configuration may consist of a Smart Phones group (Android, BlackBerry, iPhone, etc.) and a Tablets group (iPad, RIM, etc.).
Within Ektron, you can group devices by model or operating system. Grouping by model gives you more control over specifications, but it's quicker to group by operating system. You may want to first group by operating system, then only define models that do not work properly under an operating system configuration.
IMPORTANT: Because a device may be covered by several configurations, use the Reorder button to determine the order in which devices are checked. See Also: Reordering Device Configurations
Each mobile device's definition includes an operating system. To reduce effort, you can create configurations by choosing one or more operating systems. When you do, each device using that OS is automatically included in the list. For example, you create a device configuration for all Android phones.
While defining a mobile device, you decide if the configuration applies to handheld devices, tablets, or both device types. You also specify a resolution (width and height). So, if two devices share an operating system but have different resolutions, create a separate configuration for each one.
Prerequisites:
To add a device configuration by selecting an operating system:
When adding individual devices to a configuration, group devices that share characteristics, such as Flash support and screen resolution. Since you will assign the configuration to a mobile template, make sure that all devices support the template's functionality.
NOTE: You cannot edit the Generic and Generic Mobile configurations.
You can determine the first acceptable configuration that a device will use. To accomplish this, change the order of the device configurations.
For example, you configured an iPad in the AppleDevices and the TabletDevices configurations. However, because AppleDevices is set for a small resolution, you want an iPad to use the TableDevices configuration (which has a larger screen). Reorder the devices so that TableDevices appears above AppleDevices.
You can view your Ektron content in any mobile device template. This will help ensure that the content fits properly within the screen resolution.
Prerequisite: Access to your Web server's file system
The Wireless Universal Resource File (WURFL) is an XML configuration file with information about many mobile devices. It is maintained by the open-source community. For more information, see http://wurfl.sourceforge.net/.
The following disclaimer is found on the WURFL.sourceforge.net
site:
IMPORTANT: There is no guarantee of any kind that any of the info in the WURFL is correct. All the information has been gathered by collecting reports from users and developers around the globe.
This section contains these topics.
The WURFL file is located in [siteroot]\app_data\wurfl.xml.gz
.
WARNING! This file is part of Ektron's install and upgrade process. Changes to this file are overwritten during upgrades.
To open wurfl.xml.gz
, use a file extractor that opens gzip files, such as 7zip. After extracting, use any program that opens a standard XML file to open wurfl.xml
.
http://sourceforge.net/projects/wurfl/files/WURFL/
wurfl-latest.xml.gz
.wurfl-latest.xml.gz
to wurfl.xml.gz
.[siteroot]\app_data\
.To add a device that is not in the WURFL file:
devicetest.aspx
.devicetest.aspx.cs
.Response.Write(Request.UserAgent.ToString());
It may look like this:Mozilla/5.0 (iPad; CPU OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A5288d Safari/7534.48.3
wurfl.xml
file for the user agent. See Also: Locating and Opening the WURFL Filewurfl.xml
, do nothing.wurfl.xml
, create a patch file and add the device to it. See Also: Creating a WURFL Patch File Use a WURFL patch file to add a mobile device not included in the standard WURFL file.
NOTE: For more information, see http://wurfl.sourceforge.net/patchfile.php and http://db.scientiamobile.com/static/top.htm.
Prerequisite: You completed the steps in Adding a New Device to the WURFL File
web.config
file.<wurflLocation path="c:\inetpub\wwwroot\your web site\App_Data\wurfl.xml.gz" />
<patches />
<patches>
tag and the following line, as shown.<patches>
<add path="c:\inetpub\wwwroot\your web site\App_Data\wurfl_patch.xml" />
</patches>
Replace your web site with the path to your Web site.
web.config
file, verify that ek_EnableDeviceDetection
is set to true.wurfl.patch.xml
file.your-web-site\App_Data
folder.wurfl.patch.xml
.<wurfl_patch> <devices> <device id="apple_ipad_ver1_sub50" user_agent="Mozilla/5.0 (iPad; CPU OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A5288d Safari/7534.48.3" fall_back="apple_ipad_ver1_sub42"> </device> <device id="apple_iphone_ver5_0" user_agent="Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_2 like Mac OS X; en_us) AppleWebKit/534.46 (KHTML, like Gecko)" fall_back="apple_iphone_ver4_2"> </device> </devices> </wurfl_patch>
The following list explains the <device>
element's parameters.
- id—Enter an ID that is unique among all WURFL files on your server. In other words, you cannot use an ID that exists in
WURFL.XML
.- user_agent—Enter the user agent information from Step 1e of Adding a New Device to the WURFL File.
- fall_back—Enter a device ID that is similar to the one your are defining and exists in the
WURFL.XML
file. This value tells the patch file the type of device being identified. In the example above, the iPad iOS 5 points to iPad iOS 4.
You can set up Smart Form configurations to recognize a user's device and, based on that information, display appropriate content. For example, if a user is not using a Smart Phone, show a complex display with rich graphics. If a user is using a Smart Phone, create a simpler presentation of the same fields without graphics. To learn about this capability, see Inserting a Conditional Section.
You can also designate some or all of an HTML form's postback message to be conditional upon a user's device. So, for example, the postback message for Smart Phone users can be much shorter than the message for users who are not using a mobile device. To learn more about this, see Specifying Conditional Text in the Postback Message.
Mobile browsing makes the geographic location of a site visitor very important information. For example, if a mobile visitor is accessing your site, you can show nearby stores and special promotions. Creating the mobile experience in Ektron takes 2 steps.
Ektron content can have MapLatitude and MapLongitude metadata. This metadata is automatically added when you publish content with a street and city address in the MapAddress field. To learn more about this, see Setting Content Found on a Map.
The following image shows the MapLatitude and MapLongitude metadata.
Because of the size of a mobile device, you may decide to rearrange the content list, map image, and search components provided by the Map server control. To do this, change the standard map EkML file. See Controlling Output with Ektron Markup Language and the sample file [siteroot]/workarea/template/map/map.ekml
.
To complete this step, place the Map Server control on a mobile device template. See Map Server Control Properties and Separating Content from Presentation for more information.
After finishing the previous steps, you can browse to the template that contains the map on a mobile device. If your Smart Phone has GPS capability, it shows your location at the center of the map. For all other mobile devices, the center of the map is the Latitude and Longitude coordinates set on the Map Server Control.
Content locations appear as map pins, and the content list is sorted by distance from the current location (with GPS) or map center.
See also these Web pages.