WALL and WURFL

Hi,

 In this section we'll see what's purpose of WURFL (Wireless Universal Resource FiLe) and the WALL (Wireless Abstraction Library) tag library and how far it's efficient as a cloud service (SAAS device detection). 

WURFL:

WURFL (Wireless Universal Resource FiLe) is a community effort focused on mobile device detection. WURFL is a set of proprietary application programming interfaces (APIs) and an XML configuration file which contains information about device capabilities and features for a variety of mobile devices. Until version 2.2, WURFL was released under an "open source / public domain" license. Prior to version 2.2, device information was contributed by developers around the world and the WURFL was updated frequently, reflecting new wireless devices coming on the market. WURFL is a repository of wireless device capabilities. The goal of the WURFL project is to describe the capabilities of common wireless devices around the planet and provide a simple API to programmatically query the capability repository.

WALL:

WALL (Wireless Abstraction Library ) is a JSP tag library that lets a developer author mobile pages similar to plain HTML, while delivering WML, C-HTML and XHTML Mobile Profile to the device from which the HTTP request originates, depending on the actual capabilities of the device itself. Device capabilities are queried dynamically using the WURFL API. A WALL port to PHP (called WALL4PHP) is also available.

Problem of device fragmentation

The desktop web-channel, which is primarily divided up between a handful of browsers, relies on HTML as its markup, and content written as HTML can be expected to be visible to most users of a web-based channel via one of the standard browsers (Internet Explorer, Mozilla Firefox, Safari, Opera, and so on). Software updates for desktop browsers are frequently made and widely distributed.

Unlike the desktop web-channel, there is a tremendous amount of fragmentation in the mobile device-channel. Markup can be WML, HTML, HDML, XHTML Mobile Profile, etc. In addition, unlike a standard desktop web-channel, a wireless-device channel will vary on screen size, ability to support client side scripting, ability to support various image formats, and even color. Because the markup is generally sent directly to the phone, there is no opportunity for a central server to "fix" or adapt to browser limitations or defects. Software updates for mobile browsers are rare.

Solution approaches

There have been several approaches to this problem, including developing very primitive content and hoping it works on a variety of devices, limiting support to a small subset of devices or bypassing the browser solution altogether and developing a Java ME or BREW client application.

WURFL solves this by allowing development of content pages using abstractions of page elements (buttons, links and textboxes for example). At run time, these are converted to the appropriate, specific markup types for each device. In addition, the developer can specify other content decisions be made at runtime based on device specific capabilities and features (which are all in the WURFL). The WURFL contains over 500 capabilities for each device, that are broken up into 30 groups. A complete listing of available capabilities is available from the WURFL documentation page. There is an online WURFL test site called Tera-WURFL Explorer that allows one to look up the capabilities of devices based on their user agents and browse through the devices in the current WURFL file.

WURFL Cloud

In March 2012, ScientiaMobile has announced the launch of the WURFL Cloud . While the WURFL Cloud is a paid service, a free offer is made available to hobbyists and micro-companies for use on mobile sites with limited traffic. With the popularity of mobile devices, content providers need to identify those devices and their capabilities. Developers can retrieve a list of device capabilities by accessing a Device Description Repository (DDR). WURFL, a popular open-source DDR, has addressed the problem for over 10 years. ScientiaMobile, founded by the WURFL team, offers a DDR solution which addresses the most disparate needs, from large enterprise installation with strict performance and reliability requirements, to regular companies who need a simple inexpensive solution, to non-profit organizations who do not have a budget for a commercial DDR.

The ScientiaMobile WURFL Cloud offering presents a variety of plans for customers, ranging from small hobbyist sites to large enterprise installations. Customers can query the WURFL device detection repository in real time to get the latest device data.

Device detection can be set up in minutes by any averagely skilled programmer in one of the supported platforms.

Standalone solutions offer companies blazingly fast device detection solutions installed and accessed locally on your own environment.

•  Install locally on your host
•  Periodic updates
•  Use without AGPL restrictions
•  APIs
•  Full source code

WURFL cloud service provides a continually updated DDR without the hassle of installation at a fraction of the cost. The WURFL Cloud Service is a highly-available installation of the WURFL Device Database which allows companies to query updated WURFL mobile device information in real time. Regular APIs require that developers or system administrators periodically download and deploy a newer wurfl.xml file, to enrich the DDR with the device profiles of recently-released devices.

•  Continually updated
•  High availability
•  Managed Service
•  Ease of use
•  Monthly rates

Who can use the WURFL Cloud?

WURFL Cloud is open to companies of all sizes, though no OEM clients or software as a service companies (SaaS) can use the WURFL Cloud client to serve their customers. Right now PHP 5.1+, Java 1.5+ and ASP.NET 4.0 are officially supported. ScientiaMobile has developed, but not yet officially released, a Ruby, Python and ASP.NET 2.0 version of the Cloud Clients. In addition to this, at least one premium customer has been allowed to 'speak JSON' to the Cloud directly. Developers can contact ScientiaMobile and request access to pre-release versions of those clients.

  

How users sign up for the WURFL Cloud?

See Getting Started guide.

MEAP and MCAP

Hi,

 Gartner (a leading market research firm) coined the terms MEAP (Mobile Enterprise Application Platform) and MCAP (Mobile Consumer Application Platforms)

What is the difference between MCAP and MEAP?

A mobile consumer application platform is a framework that allows mobile application developers to build, manage, test and deploy mobile apps for end consumer engagement. MCAP delivers rich contextual, delightful user experiences to maximize the reach of their services. A Mobile Consumer Application Platform (MCAP), provides a set of tools and mechanisms that allow companies to create, run and manage multiple mobile applications from a single solution stack. The MCAP consists of a development environment, an integration layer and a management component that together support the secure channeling of relevant data and back-end services to the hands of consumers on a variety of mobile environments.

MCAP Providers: 

• Worklight (Worklight’s open approach allows developers to choose between four development methodologies, namely HTML5, hybrid-web, hybrid-mixed and native)
• Sencha 
• IDC's Mobile Consumer Application Platforms CIS analyzes the development, distribution, and usage of consumer mobile apps and sets that against the competitive evolution of the major app platforms, HTML5, and the dynamics between native and browser-based apps. Mobile app developers are central to the strategies of every player in the mobile ecosystem and create new ways to interact with retailers, content, the mobile Internet, and other users. A key component of this CIS is quarterly mobile application developer sentiment surveys, measuring app developer perceptions and priorities around competing mobile OSs, HTML5, smartphone and media tablets, APIs, social networking, and next-gen mobile app opportunities like augmented reality, interactive retail, and the connected home.
  Markets and Subjects Analyzed

  ---

  
  
• Consumer mobile application developer attitudes toward the major mobile ecosystems including Apple's iOS, Google's Android, HTML5, Nokia's Symbian, RIM's BlackBerry OS, Microsoft's Windows Phone 7, and HP-Palm's webOS
• Competitive dynamics and performance of the major consumer mobile app platforms and ecosystems above
• Performance metrics, evolution, and competitive outlook for mobile app storefronts including Apple's App Store, Google's Android Market (Google Play), RIM's App World, Nokia's Ovi Store, MSFT's Marketplace for Mobile, and HP-Palm's App Catalog
• Evolution and the role of social networking in mobile including Facebook, Google+, Twitter, LinkedIn, and Foursquare

 

Examples of Mobile Consumer Applications

A mobile enterprise application platform (MEAP) is a comprehensive suite of products and services that enable development of mobile applications. MEAP is used by large enterprises for deploying mobile applications for their work force. They are more focused on satisfying internal functional requirements and systems.

Examples of Mobile Enterprise Applications

Below some of the points covered-up related to MEAP approach

Purpose: 

MEAPs address the difficulties of developing mobile software by managing the diversity of devices, networks and user groups at the time of deployment and throughout the mobile solution’s lifecycle. Unlike standalone apps, a MEAP provides a comprehensive, long-term approach to deploying mobility. Cross-platform considerations are one big driver behind using MEAPs. For example, a company can use a MEAP to develop the mobile application once and deploy it to a variety of mobile devices (including smart phones, tablets, notebooks and ruggedized handhelds) with no changes to the underlying business logic.

Rule of three:

The Rule of Three refers to a concept developed by analyst firm Gartner, whereby companies are encouraged to consider the MEAP approach to mobility when they need their mobile solutions to:

1. Support three or more mobile applications
2. Support three or more mobile operating systems (OS)
3. Integrate with at least three back-end data sources

According to Gartner, using a common mobility platform, like a MEAP, brings considerable savings and strategic advantages in this situation.

A MEAP solution is generally composed of two parts: a mobile middleware server and a mobile client application. A middleware server is the solution component that handles all system integration, security, communications, scalability, cross-platform support, etc. No data is stored in the middleware server – it just manages data from the back-end system to the mobile device and back. Most MEAPs also come with a mobile configuration/development toolset that allows companies to create and adjust the mobile solutions. Mobile apps can be deployed as "thick" applications -- or native apps that are installed on the device - or rendered in the device's browser using technologies such as HTML5 (something that's often called the "thin" approach). Whether a "thick" or "thin" application is deployed depends on application complexity, device support, requirements for user experience, and the need for app availability in the absence of network coverage.

Features and capabilities

• MEAPs can support more than one type of mobile device and operating system without having to maintain separate sets of code.

• MEAP typically contains a mobile middleware server where integration connectivity, security, app management are supported.

• Writing a custom app extension is very easy with most MEAP solutions because they use 4GL techniques that do not require writing code. This toolset comes in the shape of plug-in for an industry standard IDE, such as Eclipse.

• Integrate with multiple server data sources for leverage SOA services from backend systems.

• Leverage development skill and tools you already know and expertise you already have. More details are in the Mobile application development section.

• Centrally manage mobile applications. The management of the actual devices that is more tailored for B2E scenario and it is typically done with the MDM

• Enhance existing business platforms by making them accessible to users anywhere, at any time.

According to TechNavio's analysts, “the Global Mobile Enterprise Application Platform market will reach $1.6 billion in 2014.”
According to Gartner's 2011 MEAP Magic Quadrant report, the following vendors are the industry-leading MEAP providers:

• Antenna Software
• Kony Solutions
• Pyxis Mobile
• RhoMobile
• Sybase Unwired Platform
• Syclo 
• To form Mobile eco system is across chipset vendors, handset OEM's, Device OS Platform, Enterprise System providers, MEAP (Mobile Enterprise Application Platform) & MCAP (Mobile Consumer Application Platform), and MDM (Mobile Device Management). Alliances include SAP-SUP, Antenna, Google, Kony, Mobile Iron, Zenprise, Eggplant and others name are available into the market.