Escolar Documentos
Profissional Documentos
Cultura Documentos
Mobile Web
Technology Options
1. INTRODUCTION
The mobile phone is evolving. Conversations regarding the mobile Web are getting increasingly louder.
And Sapient’s clients want to know: What is the right mobile strategy for this new, ever-changing landscape?
As capabilities and options widen, the choices can seem confusing. This paper responds to clients’ questions
and will explain some of the best platforms that are available for browser-based experiences on the mobile Web.
Parity. In many cases, the client wants parity with the wired
Web. That is, they want to offer the same services on the
mobile device as they do on the Web.
Enhanced experience. The iPhone has raised the bar and
really changed the consumer expectation of the mobile
2.1 Why mobile? Why now? experience. The on-the-go experience is often enhanced
Wired and mobile browser standards are converging, when compared to that of the wired Web and, in many cases,
thereby reducing the fragmentation we’ve seen in the cannot be accomplished without the added capabilities of
past. This is due in part to the evolution of HTML5 and the mobile device.
smartphones, and their efficiency in task-oriented design.
Device features like Geolocation (where a developer can No impact on IT. The mobile Web solution needs to
find a user’s location and customize the experience), minimize any impact on existing IT teams.
device recognition, and camera integration are starting
to be exposed right within the browser. That indicates a With the client in mind, we’ve developed what we’re calling
trend toward richer experiences on the browser as HTML5 “mobile architecture guiding principles” to ensure that
continues to expand, and as device manufacturers give us these demands are met.
the ability to build better virtual experiences.
4. SAPIENT’S GUIDING PRINCIPLES specifically rendered for the requested device. The wired
Our mobile Web research centered on a number of mobile Web site serves as an input for this platform. Some have
architecture guiding principles to help tackle the options. proprietary device databases and claim to have thousands
Six principles stood out as the focus. of devices there with hundreds of attributes, so that they
can quickly decide what the capabilities of the target device
Target experiences. WebKit, a layout engine, is a great are and adapt the content to that target device.
example, and it’ll be explained more later. Choosing to
target high-end WebKit-based devices becomes a unifying 5.2 Mobile Portals.
factor for the majority of traffic on the mobile Web. Mobile portal are products that are used to create a
mobile site that is distinct and separate from the wired
Maximize reuse. Again, by reusing Web processes and Web experience. Unlike the previous option, these
assets, such as design, code, and deployment, we avoid platforms offer a slew of widgets and layouts with the
duplication of the business investment. option to customize to the requirements that can be
delivered to a broad range of target devices. Most use a
Personalize campaigns. The goal is to create unique device independent proprietary language for source code.
experiences for clients around ecommerce and multi- Developing on these platforms is akin to developing on
channel commerce. traditional Web portal platforms plus the use to the device
independent markup language. And like the Content
Decouple the Web and mobile. Design and development Adaption Platforms, Mobile Portals have their own
teams should be separate in order to eliminate database based on device type and browser features.
dependencies while integrated just enough to maximize re-
use and consistency. 5.3 Custom WebKit Centric Solution.
A WebKit is a layout engine designed to allow Web
Allow integration. Multi-channel integration is a key browsers to render Web pages. A custom WebKit-focused
experience, and online transactions should span the Web implementation would uses markup and language
and mobile. For example, if a product is added to a cart technology such as HTML5, JavaScript, and CSS. Rather
on the phone, the consumer should be able to finish that than target all browsers, this implementation would
transaction on the Web. concentrate on the more prevalent device classes, such as
the iPhone, the Android, Blackberry 6.0+, and WebOS. The
Manage traffic. Segment and manage traffic on a device unifying theme here is that the browsers on these devices
basis. Clients should be able to take the traffic coming in are all based on the Webkit layout engine.
from an iPhone and direct it to an optimized experience.
Additionally, the user should have the option to switch to 6. MOBILE WEB SOLUTIONS
the full Web experience if they so choose. Now it’s time to break these solution types down even
further. Let’s talk about four real options for those searching
5. TECHNOLOGY OPTIONS for browser-based mobile Web options.
Now, let’s focus on the three broad solution types for
developing the mobile Web. Content Adaption Platforms 6.1 UsableNet: A Content Adaptation Platform
and Mobile Portals have balanced the tradeoff between UsableNet’s pitch is straightforward: Give them six weeks
coverage and enhanced experience. They address most and your mobile Web site will be ready.
client demands and most of the driving principles addressed
above. Conversely, the custom WebKit is more specialized UsableNet provides all the technological services necessary
and is designed specifically for higher-end smartphones. to translate a Web site to the mobile Web, without involving
the client beyond selecting suitable content for the mobile
5.1 Content Adaption Platforms. product. Because no training or infrastructure is needed,
Content Adaption Platforms use existing Web pages as a companies that employ strong in-house Web design and
source and adapt them into a mobile experience that is a mature ecommerce framework will find UsableNet to
be a perfect fit, because they can delegate the mobile mobile device. The platform also uses XHTML-based
specialization to UsableNet, and remove the need for in- coding and auto-categorizes unknown devices.
house mobile Web programming. Unfortunately, InfoGin uses .Net-based implementation,
which requires a C#, .Net, and Visual Studio experience
Very often, UsableNet’s clients are from the hospitality and environment. It’s weaker on actual customer
industry where functional aspects such as checking in, implementations, and cannot build custom IGML (InfoGin
booking a flight, or booking a hotel room have a higher Markup Language) components. As far as HTML5, CSS3,
priority over the mobile experience. Consider UsableNet for and advanced mobile features, there’s not much available.
quick projects that need an overnight turnaround. And, if
your user base contains a wide variety of devices, from basic 6.3 Volantis: A Mobile Portal
phones to the most advanced smartphones, UsableNet Volantis employs a combination of transcoding, SiteBuilder,
may be advantageous for the implementation. and custom coding. They have a proven record of thin-client
solutions for a wide variety of customers.
But proceed with caution if your requirements are heavy Volantis has modified its product lines and strategy
on user experience or forward-looking features such as significantly during the past few years, transforming itself
Geolocation or device recognition. The platform seems into a vendor primarily supplying its vast device library
to be closed, though UsableNet claims to provide an SDK and transformation engine. This narrow market focus
(software development kit) for premier clients. Additionally, has enabled Volantis to build a significant lead over other
HTML5 and CSS3 features are completely driven by client vendors of device library functions,
requirements, and device recognition is the responsibility of
the client as well. Some sites seem to lack thorough mobile Volantis uses a language called XDIME (XML Device
rendering; some phones just aborted it, which resulted in Independent Mark-up Extensions), which is based on the
lost information such as images. W3C’s DIAL (Device Independent Authoring Language),
an XHTML 2.0 standard. The foundation of the platform is
6.2 InfoGin: A Content Adaptation Platform robust, but has yet to embrace the changes in HTML5.
InfoGin has been in business since 2000 and employs about
80 people. They use software solutions that are deployed Volantis has a good number of interface components
within individual data centers to create adapted documented on its site including auto-complete. It also
mobile sites. uses a custom CSS wrapper (-mcs) that tries to map the
most appropriate CSS properties. Additionally, an XML
InfoGin focuses on a mobile Web adaptation server — Pipeline can consume XML feeds from CMS databases. If
the Intelligent Mobile Platform (IMP). This platform provides your objective is to code once and run anywhere, Volantis’
a visual design studio that offers content editing and multiple solutions can help fill the gap. The platform’s
development tools to create new or existing Web content. standard compliance is impressive and features such as
markup optimization are handy.
InfoGin administers content and functionality adaptation,
as well as developer tools among others. In our analysis, But, if your objective is to leverage the latest features,
InfoGin’s product offering had more unique features for Volantis may fall short. And the narrow market focus
custom implementation, such as content overlay, and has left Volantis relatively unprepared to answer the
the automatic content adaptation platform. If working requirements of rich-client architectures. Also, the custom
with InfoGin, consider having a prototype built up that CSS and theme options are completely dependent on
demonstrates at least one objective of the experience; their parser. And Volantis shows persistent and significant
this development should result in a better chance of a confusion over standards and technologies in presentation
successful outcome. (e.g., HTML5 and CSS3 were confused with Bondi and JIL
widget frameworks).
Favorable features include the ability to adapt CSS and
JavaScript. Additionally, InfoGin has a desktop level 6.4 NetBiscuits: A Mobile Portal
emulator that captures screenshots for Flash and AJAX NetBiscuits is a complete content adaptation platform
responses and then sends back HTML content for the
But NetBiscuits is not without its share of problems. For If you require compatibility across most devices over
instance, the proprietary markup language cannot be higher-end mobility features, one of the Content Adaption
compiled, there is no advanced HTML5/CSS3 components Platforms or mobile portals provided can probably be
featured, and code quality is poor when using tables. leveraged.
Also, NetBiscuits work well for a basic implementation,
but will not actively support any customization. So, if your On the other hand, with emerging WebKit devices, the
site requires simple implementation and isn’t heavy on mobile browser landscape has moved beyond compatibility
experience, consider NetBiscuits. into mobility. We’re really able to leverage features that are
only available on specific device families.
6.5 Custom WebKit focused implementation By taking a closer look into the platforms that exclusively
And, just quickly, remember that we also have the Custom serve the browser-based mobile Web experience, you’re
WebKit platform option, a solution that deals almost now be better prepared to advise clients on the quickly-
primarily with smartphones. evolving mobile solution space.
Gartner — Magic Quadrant for Mobile Consumer Application Platforms (3 December 2009, Michael J. King, William Clark, Nick Jones, ID :
G00171503)
UsableNet — www.usablenet.com
InfoGin — www.infogin.com
Volantis — www.volantis.com
NetBiscuits — www.netbiscuits.com
WebKit — www.webkit.org