App Development in a Mobile World: A CIO Handbook A High-Level Look at Mobile Strategy, App Development Deployment and More...?

SAP Mobile Applications

Table of Contents

3 Introduction

4 SECTION 1: Guiding Mobile Initiatives

Directing Results-driven Mobile Initiatives

Creating a Mobile Strategy

Reaching Customers with Business to Con-sumer (B2C) apps

Engaging your Work-force with Business to Employee (B2E) apps

8 SECTION 2: Developing Mobile Apps

Mobile App Architec-tures

Aligning the Architec-ture to the Use Case

Matching App Functions to Device Forms

Building Secure Apps with Authentication

The Mobile Developer Toolbox: Frameworks and Developer Environ-ments

App Enhancements with SDKs

Adding Value with Data Integration

The Case for Using OData for Data Integra-tion

15 SECTION 3: Deploy and Manage Mobile Apps

The Mobile Platform Advantage

Proof Point for Platform-based Mobile Strategy

Deployment Scenarios: On-Premise vs. Cloud

Checklist for Mobile App Platform that Supports B2C, B2B, and B2E Apps

20 SECTION 4: Achieve Best Practices

App Development Methods – Moving From Concept to Launch

Managing the App Lifecycle

Save Time and Money

Setup a Mobility Center of Excellence.

22 SECTION 5: Finding SAP Resources

How Can SAP Support My Mobile Initiatives?

See How SAP Custom-ers Run Their Business-es Better With Mobile

Learn More with SAP Mobile Resources

3App Development in a Mobile World

Introduction

To help explain some of the topics you will need to be aware of, and to separate the must-haves from the nice-to-haves, SAP has developed the App Development in a Mobile World: A CIO Handbook - a reference guide for applying a mobile strategy in the context of application architectures, best practices and resources available to help you.

This eBook is divided into five sections:

• Directing Result-Driven Mobile Initiatives: Mobile strategy, use cases, and factors to consider • Developing Mobile Apps: How to choose the right architecture for your use case, tools you can use • Deploying and Managing Mobile Apps: Platform-based approach vs. point solutions • Best Practices: How to save time and money, and get the most from your mobile strategy • Finding SAP Resources: Assets to help in your planning

As you research options for every part of your mobile lifecycle and build out the material to support your decisions, we hope you find this eBook to be a helpful reference.

As a senior stakeholder driving mobile initiatives in your organization, you may be lost in a sea of technologies and claims from vendors promising rapid delivery of applications to your employees, customers and partners.

Native

Mobile Web

Hyb

rid

HTML5 Feature Phone Smartphone

Kiosk

SMS

Tethered

Sync MCAP MEAP M

DM

Tablet

iOS

WebOS

Windows Mobile

Android

BlackBerryOS Symbian

MeeGo

App

s

Gradient

Security

Scalability

On Premise

Cloud

Open Standards Future-proof

Integration

APIs BYOD CS

S

JavaScript

UX

Connectivity

Authentication

Augmented Reality NFC

mPayments M2M

Swipe

Transition

Ani

mat

ion

Gesture Accelerometer GPS

LBS

Session Management

M2M

mBanking

RDC

MM

S

Enterprise App Store SDK

GeoLocation

JavaScript

App Cache

Local Storage Local Storage

Kiosk

Syn

c R

elia

bilit

y

LUA

Device Management

mMoney

4 App Development in a Mobile World

SECTION 1: Guiding Mobile Initiatives

DIRECTING RESULTS-DRIVEN MOBILE INITIATIVES

Mobile apps have moved from nice-to-have additions to must-have business tools as consumers and employees turn from laptops and desktops to their smartphones and tablets. Marketing, sales, retail, HR, business development, and other lines of business want mobile apps that give them anywhere, anytime access to business data. Consumers expect apps designed around their favorite brand-name products and services.

This demand, coupled with the fact that most organizations don’t have dedicated resources that can focus on addressing

the mobile needs means near-certain failure for most mobile projects. If mobile projects are slow to launch, difficult to support, or racking up unexpected costs, this guide will have suggestions for moving your mobile plans onto a more successful path.

This guide outlines key concepts and methodologies for app development that will speed your mobile initiatives. You will find guidance for creating a strategy, insight into different app architectures, development methodologies, deploy-ment options, and more. If you’re a CIO new to mobile or your mobile projects are slow to launch, difficult to support, or racking up unexpected costs, this guide will have suggestions for moving your mobile plans onto a more successful track.

CREATING A MOBILE STRATEGY

Mobile is introducing sweeping changes throughout your workplace. Bringing your organization into the mobile age demands a mobility center of excellence led by a chief mobile officer. This execu-tive leads mobile initiatives, and most importantly bridges the gap between business and technology, providing the direction for mobility throughout the organization.

The first order of business for the chief mobile officer is creating a mobile strategy that details the following eight items:

Mobile Vision Document the mobile vision (beyond devices and features) and align it with business strategy. Avoid misperceptions by incorporating input from stakeholders (users, lines of business leaders, and IT) to discover the business drivers, benefits, and expectations of mobile in your organization.

Innovation Identify mobile potential through user-centric methods (Design Thinking) to illustrate how mobile will bring innovation to the organization. For more information on Design Thinking, please review the white paper and video.

Use Cases Establish a two-year plan that describes use cases, prioritization (value/need versus feasibility/effort), standard plus specialized apps, and initial quick wins that deliver high value.

Implementation Select a build, buy, rent, or combination approach based on existing infrastructure, skills, development, projects, and operations.

Architecture and Technology

Specify the app architectures that best support your mobile apps while ensuring standardization and flexibility. Evaluate a platform concept that considers the back-end systems and future needs (scalability, reusability, user growth, new functionality). Establish guidelines for OS, devices, and functionality (features, sensors, offline, and more).

5App Development in a Mobile World

The following can be used as a starting outline for the mobile strategy document:

• Vision and mission • Use cases and business processes

impacted • Business value and benefits • Architecture and technology • Risk and security • Governance and organization • Skills and transformation • Consolidated roadmap

If you are just getting started on your mobile strategy or have an initial strate-gy and are starting on detailed planning, SAP has service offerings to help out.

REACHING CUSTOMERS WITH BUSINESS TO CONSUMER (B2C) APPS

Mobile B2C - “Business to Consumer” or “Business to Customer” applications exploded onto the scene with the release of the original iPhone and Apple App Store in 2007.

SECTION 1: Guiding Mobile Initiatives

Today’s consumer smartphone rarely suffers from neglect. According to a recent Harris poll1 nearly 60% of users won’t go an hour without checking their smartphone; 74% of 18–34 year-olds use them before going to bed or immediately upon waking up. You can take advantage of this always-on behavior to expand your business’ reach.

An important point to consider is that even if your target audience has adopted the always-on usage mode, you will need to deliver value to them in your app so that they will incorporate it into their daily habit pattern. The following are a few key use cases that popular apps incorporate:

• Provide useful information about your products or services to drive sales2

• Enable easy access to current transaction status and order history to promote additional purchases

• Make your mobile customer an “insider” to deals and promotions

• Create a sense of “community” by providing access to read and create reviews of products and services – a major step to increasing brand affinity

With such huge potential, there was a time where many businesses rushed to be in the App Store without investing a lot of time in fine tuning the user experi-ence. Many pundits refer to those not-too-distant-past days as the (consumer) “app bubble”. While consumer smart-phone use continues to increase, the level of sophistication and expectations of users has risen too. A key metric to consider is the “app abandonment” rate. A recent study3 shows that while 79% of consumers will try an app a second time after it fails to impress, the rate drops to 16% for trying the app a third time. Here are a few examples for “hooking” your customers the first time:

• Consider banking applications that allow users to make a deposit simply by taking a picture of a check

• Many retailers today support quickly arranging in store pickup of items ordered from a mobile phone to save shipping costs and provide immediate gratification

• The common thread is to look for opportunities for the user to do things that would otherwise be time consuming or difficult

Risk and SecurityIdentify and assess general risk factors and for specific use cases, include awareness and compliance considerations.

Team Building Identify mobile team and list skills and experience required (development, operations, administration), note specific skill gaps, and draft a skill development roadmap.

TransformationDefine a communication framework to share mobile news and advancements throughout the organization.

1 https://www.lookout.com/resources/reports/mobile-mindset; That’s sixty percent of users of all ages that check phone once per hour. That statistic is roughly ten

percent higher for 18–34 year-olds.2 Wave Collapse, 2012. “93% of people who use apps in stores have bought something at a physical location in the last week (compared to 84% for non-app users). 3 Digital Trends, Joshua Pramis, Mar 13, 2013.

6 App Development in a Mobile World

SECTION 1: Guiding Mobile Initiatives

Understand the Consumer Device Landscape

As of Q1 2013, Android devices made up 49% of the new sales the U.S., iOS was 44%, Windows Phone was 6%, and other vendors including BlackBerry made up the rest. You will almost certainly need to plan to deploy your application into multiple App Stores.

Consumers Demand an Application Designed for Their Device

Modern “pro-sumers” have high expecta-tions of the look and feel of an applica-tion. Each device operating system today has a well-defined and distinct look:

• Ensure your application completely conforms to the device vendor’s user experience style guidelines

• Exploit features unique to each device OS – examples of this include packaging key features of your application as an Android Widget, leveraging the iOS Passbook to store coupons or loyalty cards, or even enabling device-level content search

• Your choice of mobile platform can significantly affect your success on these points

• Test to ensure your mobile platform functions at scale, and that it provides capabilities to debug operational issues without compromising security

Leverage Existing Mobile-Enabled Pathways

Although creating your own B2C mobile application provides the most direct pathway from you to your customer, don’t overlook these opportunities:

• Social media marketing is closely coupled to mobility through systems like Facebook, Twitter, Pinterest and YouTube. Create and cultivate a presence through these sites that will promote your products and brand

• Almost all modern mobile phones provide free apps capable of scanning coded magazine ads, signs or billboards. Embedded QR-Codes can rapidly provide contact information, street addresses, or even direct a potential customer to a targeted web campaign

FIGURE 1 AN EXAMPLE QR-CODE (TRY IT WITH YOUR PHONE)

ENGAGING YOUR WORKFORCE WITH BUSINESS TO EMPLOYEE (B2E) APPS

Mobilizing applications for your enter-prise increases your business’ efficiency and reliability. That, in turn, can reduce costs and lead to a competitive advantage.

Mobile Business to Enterprise (B2E) computing has been around in one form or another for well over thirty years (including luggable, or laptop solutions). Early pioneers in this technology quickly recognized the challenge in matching the primitive device operating systems of the day with sophisticated enterprise data-base systems. From that problem, early leaders such Sybase, Syclo, and SAP all independently created the first of what would become know as Mobile Enter-prise Access Platforms, or MEAPs.

These first MEAPs included developmenttools to inspect and map enterprise dataobjects into something that would fit onrelatively small mobile devices. MEAPsalso included their own User Interfaceframeworks to improve on the relativelyprimitive device OS UIs. MEAPs typically include the runtime Mobile Server infra-structure to securely manage devices, enterprise authentication, cache and transport data, and log transactions, as well as other critical operational services.

7App Development in a Mobile World

SECTION 1: Guiding Mobile Initiatives

These use cases rise to the top of the stack because of the gains possible with mobile apps. For Field Service, a common metric to measure efficiency is “wrench time” - which is literally the amount of time a field worker will actual-ly be performing work. The cross-indus-try average for wrench-time is on the order of 2.5 hours per day, with the rest of the time taken up with transit time

If we fast forward to today, mobile operating systems, device hardware, and mobile development tools are much more capable. At the data center, or even in the Cloud, Service Oriented Architecture (SOA) has emerged as an approach to exposing data with-in the enterprise.

Today, the top use cases for mobile include:

• Requests and approvals • Sales force automation • Field service • Document management • Order/inventory management

The following chart shows to relative percentages based on a recent SAP survey on a subset of our customers.

(driving and finding the job site), sorting through the pile to find the correct work order, after troubleshooting – finding (or leaving to get) the right parts – and post-work documentation. It is clear that even a small increase in efficiency (as small as 15 minutes per worker per day) could have a huge impact on overall efficiency. At SAP, our customers see an average of a 45 minutes per day increase in

wrench-time. For a company with a 500-person field work force, this trans-lates into an extra 7,500 hours per month of productivity.

24%$

22%$

18%$

9%$

17%$

5%$5%$

Mobile'Use'Cases'

Workflow$Apps$ CRM$$ Work$Orders$

Order/Inventory$Mgmt$ Consolidated$Docs$+$Media$ AnalyGcs$

Retail$ExecuGon$

24%$

22%$

18%$

9%$

17%$

5%$5%$

Mobile'Use'Cases'

Workflow$Apps$ CRM$$ Work$Orders$

Order/Inventory$Mgmt$ Consolidated$Docs$+$Media$ AnalyGcs$

Retail$ExecuGon$

24%$

22%$

18%$

9%$

17%$

5%$5%$

Mobile'Use'Cases'

Workflow$Apps$ CRM$$ Work$Orders$

Order/Inventory$Mgmt$ Consolidated$Docs$+$Media$ AnalyGcs$

Retail$ExecuGon$

24%$

22%$

18%$

9%$

17%$

5%$5%$

Mobile'Use'Cases'

Workflow$Apps$ CRM$$ Work$Orders$

Order/Inventory$Mgmt$ Consolidated$Docs$+$Media$ AnalyGcs$

Retail$ExecuGon$

24%$

22%$

18%$

9%$

17%$

5%$5%$

Mobile'Use'Cases'

Workflow$Apps$ CRM$$ Work$Orders$

Order/Inventory$Mgmt$ Consolidated$Docs$+$Media$ AnalyGcs$

Retail$ExecuGon$

8 App Development in a Mobile World

SECTION 2: Developing Mobile Apps

MOBILE APP ARCHITECTURES

Businesses, especially consumer-brand companies, need to cast a wide net and build or buy mobile apps that run on smartphones and tablets, the mobile web, and SMS. Mobile apps range from simple to complex, and many of the features and functions depend on the underlying architecture. Your organiza-tion will have apps developed on these five architectures: native, mobile Web, hybrid, Metadata driven (MDD), and SMS.

Having apps with different underlying architectures ensures that you meet the broad spectrum of business and user needs. One architecture will rarely suit all of an organization’s apps. Instead, as your mobile needs evolve, your apps will be built on the architectures that best support the use cases and provide an exceptional user experience. An app’s architecture will depend on the require-ments for the application, your use cases, user base, internal skills available, timeline, budget, and more.

Native Apps – Delivering the Richest Experience, Always at the Leading Edge

It seems illogical, but mobile technology vendors, and even industry analysts, vary in how they define what qualifies as a Native mobile application. From our perspective, there are three straightfor-ward tests that qualify an application as Native:

• The application is developed directly in the device OS’s preferred IDE or IDE plugins. For example, Xcode for iOS,

ADT Plugins for Android, Microsoft Visual Studio for Windows Phone, and so on

• The vendor-preferred language is employed to code the application: Objective-C or C++ for iOS, Java for Android, C# or VB.Net for Windows Phone, etc

• The User Interface is developed using the OS’s UI Framework and Operating System APIs

Why Is This Definition of Native Important to You?

By employing these truly native environ-ments and tooling, your development teams can deliver the richest user expe-rience possible on each device, and also have direct access each device OS-specific features and hardware. Your team also has access to these features sooner, since they can take OS SDK updates directly from the device vendor as soon as they are available. Finally, your team is also easier to staff: an iOS or Android developer is productive in this model almost immediately.

A key idea behind native development is to deliver the optimal user experience or to get the most efficient and direct access to device hardware. We recognize there is a competing need to deliver application functionality across different device vendors – we’ll tackle that in just a moment.

SAP adheres to this definition of native application development.

SAP adds value by supplying native Client SDKs that add rich security, services and data modeling, as well as caching and offline operation capabilities to native development.

Hybrid Apps – Delivering the Widest Reach from a Single Source Code Base or “Write once, run many”, “Write once, run everywhere” Has Evolved

Desktop development has basically been a monoculture for years. Microsoft Windows® has dominated, especially in business. Not so for mobility: The explo-sion of consumer device brands and operating systems had the benefit of reducing hardware prices, but at the same time presented a challenge to every mobile developer: how can costs be contained where in cases where one needs the same application on many different device types?

Some technology vendors addressed this issue by creating cross-platform frameworks and proprietary tooling to allow for a “write once” model. Such platforms would function by embedding an open source language such as Python, Ruby, Perl, or Lua within the mobile application. This language runtime would be combined with a proprietary UI Framework to create the application user interface. In a strong sense, these were the first “application containers” – although experts rarely called them that.

9App Development in a Mobile World

SECTION 2: Developing Mobile Apps

Parallel to this, HTML standards evolved rapidly. Advances included better Java-Script support for dynamic web sites, and much more advanced styling via Cascading Style Sheets (CSS). Well-styled and highly functional UI Frame-works such as jQuery, Sencha, and Dojo emerged. Crucially, device OS vendors have invested time to highly optimize HTML5 and JavaScript performance on their respective hardware.

Mobile Web (HTML5) Apps are Web-based apps optimized to the screen resolution and capabilities of mobile browsers. The apps are frequently imple-mented with some combination of serv-er-side logic and on-device logic, and UI controls implemented in HTML5, Java-Script, and CSS delivered by the web server. This class of applications runs in the mobile browser, and as a result has very limited access to device resources (for example, camera). One clear benefit of Mobile Web apps is that it is possible to deliver a greatly improved user experi-ence (navigation, size of text, and so on.) over a standard web interface, when users visit your website from a mobile device.

So, What’s Different about HTML5 Apps and Hybrid Containers?

The result of improvements in HTML and JavaScript was the emergence of the HTML5 Application Container, or Hybrid Container. A Hybrid Container wraps the device’s optimized native web browser into a true native app. The actual applica-tion is coded using HTML5, CSS3, and JavaScript. The container includes APIs allowing the application greater access

to device capabilities than a plain web application. Different Containers are crafted for iOS, Android, Windows Phone, and so on. Combine these containers with a HTML5 UI Framework and the net result is a well-performing application that runs on multiple platforms from a common code base.

The difference between a Hybrid Container and older “write once” approaches is important: older imple-mentations were a combination of a language foreign to the device and a proprietary UI framework. The older approach required specialized skills and training for an effective team. Moreover, the foreign nature of the language and UI framework often led to performance and experience issues within the app. The end result being a “lowest common denominator” set of capabilities shared across the target platforms. In contrast, a Hybrid Container leverages the highly optimized device-specific web view and – by exposing a HTML5/CSS3/JavaS-cript framework – expert developer resources are easier to find and re-use.

Apache Cordova is the most popular mobile Hybrid Container today, and is the open-source version of Adobe’s PhoneGap product. SAP has embraced Cordova as the basis of its Hybrid Container technology. The SAP product team has gone through an extensive effort to extend the capabilities of the Cordova container, adding capabil-ities of the SAP Mobile Platform without narrowing the flexibility that developers demand of modern open software.

Metadata Driven (MDD) Apps – Single Code Base, Rich, Preconfigured Apps

A metadata-driven application model (MDD) uses a dynamic, discovery-orient-ed development environment to rapidly create, test and distribute mobile appli-cations to a pre-built application “player”. The Metadata is a runtime description of the data object, transactions, and synchronization definitions required to drive the application.

Rather than being compiled into native code, each MDD application is stored in a form optimized for runtime performance, and is packaged to facilitate seamless updates of the application in the produc-tion mobile user community.

SAP delivers a Metadata Driven Applica-tion architecture through its (formerly Syclo) Agentry 4GL development, tests, and platform runtime products.

SAP also leads with a family of prebuilt Agentry-based Field Service and Mobile Asset Management solution applica-tions. These solutions are widely used today in industries such as, Utilities, Oil & Gas, Government, Life Sciences, and Manufacturing. These solutions have been preconfigured to connect to SAP ERP and CRM systems, and these same applications can be used as starting points for creating custom tailored solu-tions with extended functionality, or interactions with other data sources. It is important to note that as with all SAP mobile solutions, back-end connectivity is not limited to SAP systems. In fact, there are over 500 deployments of MDD apps accessing non-SAP back-ends.

10 App Development in a Mobile World

SECTION 2: Developing Mobile Apps

SMS – A Lightweight App for Any Device

An SMS app is quite different from the other types of mobile apps. It requires no client-side app, as it relies on information exchanged through two-way messaging and sophisticated back-end capabilities that automate the exchange. The infor-mation exchange can be server- or client-initiated. Once initiated, the server auto-matically responds with offers, questions, information, a coupon, coupon codes, or something else to the user. These apps are very effective in emerging markets where smartphone penetration is still relatively low. They are

also applicable in mature markets and for certain demographics that regard text messaging as a more convenient communication mode. An example use case would be sending SMS messages to confirm a credit card or debit card trans-action where the user has the ability to confirm or contest the charge immediately.

App Development in General

Mobile app development is interesting in that 80 percent of the development work for many apps is the same. The remain-

ing 20 percent is customization work that separates the apps for specific use cases and audiences. A mobile app plat-form speeds the development process by enabling that larger portion of must-have app capabilities, such as authenti-cation, encryption, push notifications, offline data caching, and more, across all apps.

Without a mobile platform, your develop-ers will have to build and test these func-tions themselves as they create their apps. That’s a lot of work.

The following table is a quick recap on the various application architectures:

Types of Architectures

Native Apps Mobile Web Apps Hybrid Apps Metadata Driven (MDD) Apps

Developer skill-set needed

Device-specific design and programming talent required, Objective-C for iOS, Java for Android and BlackBerry, C# for Windows

Web developers with HTML5, JavaScript, and CSS knowledge

Web developers with HTML5, JavaScript, and CSS knowledge

Experience with MDD tool

Work effort ***** *** ** *

Cross-platform support

None Yes, through third-party framework or custom code

Yes, through third-party framework or custom code

Yes

Performance Fast Variable Variable–especially for data-intensive apps

Fast

Automatic updates No Yes No Yes

Distribution model through app store

Yes No Yes Yes

(***** is most difficult; * is least difficult)

11App Development in a Mobile World

SECTION 2: Developing Mobile Apps

ALIGNING THE ARCHITECTURE TO THE USE CASE

Consider a NativeApp When:

• A completely unique and compelling user experience is central to the app’s success

• Time-to-market with the latest hardware and device OS features or high performance is critical to success

• You will only release the app on one device type

Choose a Hybrid App When:

• You plan to run your app on multiple device operating systems

• Overall user experience is important, but a degree of flexibility in the look and feel is acceptable

• You have an existing HTML5 or JavaScript development resources available to pull into your mobile project team

Opt for Metadata Driven App When:

• You need to create business apps such as field service, inspection, asset management, or CRM and want to leverage a working app

Explore your mobile app options, read the following two white papers: Building Enterprise-Grade HTML5 Mobile Apps and Hybrid Mobile Apps - More Function-ality At Lower Cost.

MATCHING APP FUNCTIONS TO DEVICE FORMS

Choosing the mobile device your apps run on is just as important as selecting the best architecture for your app. Android, BlackBerry, iOS, and Windows smartphones and tablets present unique development environments and user experiences, and people interact with tablets and smartphones quite differently.

Android and iOS devices are early market leaders that have benefited from mass consumer appeal. Windows devic-es will become more prevalent during the next few years, and they may win strong business support, as many expect them to plug and play more easily into existing back-end environments. You will need to develop apps for all these operating systems and devices, and you will want to align the apps’ functions and features to how people interact with each type of mobile device.

Users pick up their smartphones, for example, often and for short time peri-ods throughout the day. Tablet usage occurs less frequently, but people spend more time on the larger devices. These tendencies make the smartphone more appropriate for apps that demand less time, such as order or vacation leave approvals. Apps with forms to fill in, on the other hand, are better suited for tablets.

Find additional insight on the impact of mobile in the enterprise and beyond in the Enterprise For Dummies eBook. Visit the blog and download the eBook from there.

BUILDING SECURE APPS WITH AUTHENTICATION

Mobile security leans heavily on tradi-tional security practices. User authenti-cation, for example, is a long-standing best practice for maintaining control over your enterprise data. For mobile business apps, authentication is a requirement. Consumer apps will also need user logins, and the user creden-tials will be cached in the server (unlike enterprise apps). Your industry, govern-ment regulations, data collected, and many other factors will impact the app’s security requirements.

No one wants to login to use an app, but some form of authentication is a necessi-ty. You can streamline the authentication process by using single sign-on (SSO), which allows the sharing of logon infor-mation across apps. Users will be authenticated automatically as they move from one app to another, ensuring a positive user experience. The time to define security and authentication requirements is early in the develop-ment, as it’s more cost-effective to build authentication in the app initially and avoid future re-work.

The client authentication process normally begins with the mobile app creating a session by sending an HTTP (S) request to the server. Usually the server is protected behind a firewall and the request is routed through a reverse proxy or relay server, which detects the un-authenticated request and challenges (using any of the authen-tication methods described below). After the challenge, the client may already

12 App Development in a Mobile World

SECTION 2: Developing Mobile Apps

have network credentials configured, or perhaps there is a callback to prompt for credentials.

Basic authentication is the minimal scheme of authenticating a user with username and password. Apps must be able to validate a user’s credentials against multiple directories, such as LDAP, Active Directory, and others. Using this form of authentication is generally not recommended, since it does not support SSO, and requires the consum-ing application to provide secure storage for the login credentials and handle initial and expired passwords. Another caveat of basic authentication is that applica-tions built by different development teams will not be able to share credentials.

Single Sign-On SSO offers an array of benefits. Perhaps the most significant is that a user only needs to remember a single set of credentials, regardless of the UI, to gain access to multiple apps and network services. SSO also means that all authentication-related informa-tion is centralized on a single security service provider, which helps enterprise administrators enforce a consistent authentication policy throughout the identity management process. There are two forms of SSO authentication:

• SSO using certificates: X.509 client certificates are widely accepted and supported as the standard for certificate based authentication. In this method, a digital certificate with the user’s public key is sent to the server, which then validates the certificate

and allows login. X.509 client certificates usually require a public key infrastructure (PKI) to handle the certificate distribution (this should be provided by your MDM solution). With this approach, the mobile platform server establishes an HTTPS connection to a backend with client certificate forwarding in the HTTP header

• SSO using logon tickets auth-enticates the user through an external provider, creating a login session. This session is forwarded with the user ID to an agent running inside the back-end system. The session is re-validated, and a logon ticket is issued for future transactions

Identity and access management leverage the user management and authorization credentials stored in exist-ing back-end systems. Mobile apps re-use the credentials already set for enterprise systems, avoiding the need to maintain a separate configuration for mobile user authorizations and manage-ment. This authentication prevents secu-rity breaches of enterprise systems by requiring existing user credentials such ID numbers, VPN info, level of employ-ment, and other information that identi-fies the user’s level of access.

THE MOBILE DEVELOPER TOOLBOX: FRAMEWORKS AND DEVELOPER ENVIRONMENTS

Desktop development has basically been a monoculture for years. Not so for mobility. The explosion of consumer device brands and operating systems presents a challenge to every mobile developer: How can costs be contained while still building the same app for many device types?

An early solution was cross-platform frameworks and proprietary tooling that allowed a “write once” model. Open source languages were embedded within the mobile app and combined with a proprietary UI framework to create the application user interface.

Parallel to this, HTML standards evolved rapidly. Advances included better Java-Script support for dynamic Web sites and more advanced styling via cascading style sheets. Well-styled and highly func-tional UI frameworks such as jQuery, Sencha, and Dojo emerged. During the same time, device OS vendors optimized HTML5 and JavaScript performance on their respective hardware.

These advances are especially important for hybrid apps that use an HTML5 appli-cation container or hybrid container. The app is coded using HTML5, CSS3, and JavaScript. The container includes appli-cation programming interfaces (APIs) that give the app greater access to

13App Development in a Mobile World

SECTION 2: Developing Mobile Apps

device capabilities than a plain Web app. When the container is combined with a HTML5 UI framework, the apps deliver exceptional performance and run on multiple platforms from a common code base.

The developer can leverage the UI frame-work to make the app more valuable by

adding services, such as coupons, payments, geo-location, SMS services, push, synchronization, offline support, and others.

These popular IDEs and frameworks help your developers create rich, sophisticat-ed native or hybrid apps:

Platform Tools

iOS Xcode, Dashcode (web)

Android Eclipse, Android Studio

Windows 8, Windows Phone 8 Visual Studio, Visual Studio Express

BlackBerry • Legacy BlackBerry: Eclipse • BlackBerry 10: Cascades, Momentics IDE

HYBRID DEVELOPMENT TOOLS

Primary Hybrid App Container Toolkits

Hybrid Apps and Mobile Web App Tools

Other Toolkits Frequently Used

• Apache Cordova • SAP Mobile Platform Kapsel plug-ins

(for Cordova) • Adobe PhoneGap • Appcelerator Titanium • Sencha Touch Container (Cordova

fork) • Developer skill set needed

• jQuery Mobile • Sencha Touch • Dojo

• WBackbone • Bootstrap • Angular

14 App Development in a Mobile World

SECTION 2: Developing Mobile Apps

APP ENHANCEMENTS WITH SDKS

Third-party Software Development Kits (SDKs) make a good app great by enabling features and functions that are difficult to develop internally. The follow-ing SDKs have proven track records and greatly improve the user experience.

Augmented reality: Metaio and Vuforia are frameworks that allow an app to present contextual information, augmenting what the user can see using either location, image, or pattern detection.

Immersion: Developers can add an immersive experience by adding a panorama or 3D element to the app. Apps developed with krpano have a 360-degrees panorama, coupled with live video feeds (from onsite cameras) that gives the user a real-time overview of a given field of view and the ability to interact with it dynamically. Unity3d immerses users in a full 3D environment and lets them interact with different points of view.

Communication: Developers can enhance the communication experience with SDKs such as OpenTok, which enables a live video chat functionality within the app. Bump supports data exchanges between phones across platforms.

These SDKs, and others, provide much of the consumer-grade functionality and rich user experience that end-users want in their apps for both work or personal use.

ADDING VALUE WITH DATA INTEGRATION

Mobile apps become more valuable when they access data stored in back-end systems. Proprietary interfaces and XML-based Web services expose this data for the apps, but neither is very mobile friendly.

When planning data integration, you must determine what data should be exposed to clients. Finding the right balance is tricky. Exposing more data than is needed degrades the UI perfor-mance and battery; when not enough data is available, the app is less useful to the user.

A host of interfaces, such as Web servic-es, JDBS, REST, and OData, are available to connect the back-end system and mobile app. As mobile app development matures, OData is expected to become the leading protocol for connecting apps to the data in back-end systems.

THE CASE FOR USING ODATA FOR DATA INTEGRATION

Web Services architectures have evolved rapidly in the recent past. Early web Service Oriented Architectures (SOA) were based on SOAP. More recently, RESTful web services gained acceptance as a lighter-weight approach: REST has the reputation of being more easily consumed by mobile and dynamic web applications. Today, OData is an emerg-ing web services standard. It was origi-nally proposed by Microsoft and has been embraced by industry leaders, including SAP.

OData defines an access layer atop a REST protocol and adds the following key capabilities to conventional REST services:

• Defines a formal query language to dynamically select the best data set for a given task

• Supplies integrated metadata descriptions of the data structures it exposes

• Supports dynamic combining of related objects in a single result set

• Supports paging for larger result sets • Allows for server-side searching of

data content without constructing complex queries

• Returns results in the developer’s choice of XML or JSON data formats

• Works with well-known mobile protocols including REST, HTTP, and HTTP-based security/authentication protocols

The key strengths of OData lie in its dynamic nature. Data exposed via OData can be optimized directly by the applica-tion developer without requiring back-end services modifications. This saves on development time and cost by reducing the back-and-forth interactions between application and server development teams. An OData services approach also cuts testing costs by reducing the need for hand-crafted server code.

Visit OData.org for the latest news and updates on OData.

15App Development in a Mobile World

SECTION 3: Deploy and Manage Mobile Apps

POINT SOLUTIONS VS. PLATFORM SOLUTIONS

Every future decision you make about your mobile strategy will be affected by your decision to invest in point solutions or a mobile app platform. This decision will affect your organization’s ability to develop, manage, and secure both apps and devices. At first glance, point solu-tions seem like a good fit for enterprise mobility. No doubt they are a low-cost entry to developing mobile apps, but the

costs start adding up quickly as mobility expands throughout the organization.

Point solution development for even a basic app will lead to long-term costs:

• 3 to 4 engineers for 3 months for a single authentication method

• 2 to 3 engineers for 2 months for basic, online data access

• 3 engineers for 12 months for ongoing maintenance

16 App Development in a Mobile World

SECTION 3: Deploy and Manage Mobile Apps

Additionally, point solutions typically fail due to other shortcomings:

• Data security (HTTPS secures data during transmission, but securing data at rest is difficult)

• Network access required (offline modes and synchronization are difficult)

• No cross-platform push notifications or lifecycle management

• Different teams (sometimes a mix of internal and external) and technologies prevent code re-use

If you are going to compare point solu-tions and mobile app development plat-forms side by side, read the following five-part blog: When A Good Mobility Idea Becomes A Management Night-mare. Part 1 | Part 2 | Part 3 | Part 4 | Part 5

THE MOBILE PLATFORM ADVANTAGE

There’s power in a platform-based approach that benefits IT, developers, and users. A mobile app’s success rests on the user experience, and a mobile platform helps ensure an amazing user experience by providing the components to run uninterrupted at all times.

Like an iceberg, many of the tasks asso-ciated with a successful mobile app deployment lie hidden from view.

!  Authentication !  Business application integration !  Security – devices, data, content !  Offline access and synchronization !  Multi-platform support !  Administration !  Application versioning and lifecycle management !  Push notifications !  Proxy !  Reporting and analytics

Mobile Platform value-add 20%

80%

17App Development in a Mobile World

SECTION 3: Deploy and Manage Mobile Apps

Here is a representative sample of the capabilities for administration and appli-cations you will need to deploy a mobile application:

Key Administrative Capabilities:

• Client device and application registration

• Enterprise authentication and identity provider integration

• Operational usage logging and transaction tracing

• Application versioning/application update management

• Cross-platform push notification services

• System usage reporting and analytics • Mobile services clustering/horizontal

scalability/failover

Key Client Capabilities:

• Client business object data modeling. • Data synchronization services –

between the client and enterprise back-end

• Offline data caching • Offline data change queuing • Encryption of data over the air (“data

in motion”) • Encryption of device data (“data at

rest”) • Multi-platform application and user

interface frameworks (enabling a “Write once” development approach)

The point is, these are capabilities that mobile operating system SDKs and web services APIs won’t provide out of the box. Without a mobile platform, your developers will have to build and test these functions themselves as they create your first application. That’s a lot of work. At the point you create your second application, your team will need to refactor this original code to adapt it to the different needs of the new app. In many ways, that’s even harder work.

A good mobile platform will provide these functions out of the box, ideally in a way that exposes these capabilities that is reusable across a range of B2E application types – from true native applications that can display rich 3D graphics and custom hardware to “Write Once” Hybrid applications that run across a range of devices from the same source code base.

When app development teams have these capabilities available they can focus on delivering a superior user expe-rience rather than spending extensive time on low-level coding. IT also gains significant advantages from a mobile app platform as it helps them maintain corporate security and gain visibility into all mobile solutions. Furthermore, devel-opers save time because they can add the most popular and recently released features into the mobile apps using their current skill sets.

Value for Developer

• Flexible framework supports broad set of development skill sets

• SDK and tools support ensures developers are fast and productive

• Reusable services and frameworks keep apps consistent and extensible

• Support for industry-standard protocols and open-source technology

Value for IT Admin

• Single platform for all mobile apps that scales linearly

• Centralized management minimizes efforts needed to monitor and manage

• Industry standards ensure security assurance and control

• App platform and app management enables end-to-end mobile lifecycle management

Value for the End User

• Centralized, governed development supports consistent app experience

• Self-service portal enables user empowerment

• Cross-platform support ensures user choice and BYOD programs

• New apps and capabilities are easily found and discovered in enterprise app store

Learn why there’s more Power in the Platform.

18 App Development in a Mobile World

SECTION 3: Deploy and Manage Mobile Apps

PROOF POINT FOR PLATFORM-BASED MOBILE STRATEGY

A real-world cost comparison within one company clearly shows the budgetary impact of a platform-based approach. In

this example, a large global company developed 40 business apps. The U.S. division relied on multiple best-of-breed tools and custom development. The Canadian division developed the same mobile apps using the SAP Mobile Plat-form. The results speak for themselves.

U.S. Company: Point Solution Approach Canadian Company: SAP Mobile Platform

Team size: 40 EngineersSchedule: 18 months

Costs: 20 Eng @ $1,000/day 20 Eng @ $600/day

Total Development cost: $11.5 million

Of the development cost, $1.7 million was allocated to design work

Team size: 10 EngineersSchedule: 4 months

Costs: Re-used U.S. Design $1.7m 5 Eng @ $1,000/day $0.4m 5 Eng @ $600/day $0.2m

Total Development cost: $2.3 million

Using a platform approach and SAP tools, the Canadian team saved $9m (80%) and delivered more than 12 months faster!

19App Development in a Mobile World

SECTION 3: Deploy and Manage Mobile Apps

DEPLOYMENT SCENARIOS: ON-PREMISE VS. CLOUD

Many organizations are looking at cloud-based services before on-premise solu-tions to reduce costs. A cloud-based mobile app platform helps enterprises deploy mobile apps quickly and at a reduced cost. An on-premise platform is appropriate when many apps are being deployed or when the apps and mobile devices are accessing large datasets. Having the system of record and the mobile platform in the same location reduces communication latency times and ensures better app performance.

What’s best for your organization, just as in what app architectures to choose, will depend on the number of mobile apps you have, the types of mobile apps you support, internal resources, and time constraints.

On-Premise Is Best When:

• Experienced datacenter and IT staff is available

• Plans are underway for long-term support of mobile apps and devices

• Six or more mobile apps (or variants on multiple platforms) will be launched in the next 12 to 18 months

• Your mobile apps require rich data sets and robust features

The Cloud Makes Sense When:

• IT resources are limited • Your mobile strategy is to start small

with fewer than six apps, and launch quickly with minimal costs

• Fast time to market requirements do not allow for infrastructure build out

• Strategy is to test the mobile waters before investing in large-scale capacity

For more information, check out these two white papers covering test results for cloud performance and scalability and cloud security.

CHECKLIST FOR MOBILE APP PLAT-FORM THAT SUPPORTS B2C, B2B, AND B2E APPS

Mobile apps typically fall into these cate-gories: business to consumer (B2C), business to enterprise (B2E), and busi-ness to business (B2B). The characteris-tics of these types of apps and the end users’ expectations are significantly different. In the short term, you may only develop and support one type of app, but long term you will have mobile apps from all groups.

As the number and types of apps increases, a mobile application platform ensures a level of consistency and order. You will be able to meet the goals from your mobile strategy for:

Scalability: Your organization will adapt easily to:

• New mobile devices introduced to the marketplace

• Requests for more mobile apps with sophisticated features

• Larger, more diverse user bases

Security: Your apps will provide:

• Streamlined authentication for both enterprise and consumer user

• Enterprise-level authentication that prevents security breaches of business systems

• Consumer-level authentication that protects privacy

User experience: Your users will experience:

• User-friendly, consumer-like interfaces • Exceptional online and offline

performance • Increased productivity with broad

access to business back-end systems

When comparing platform options as part of vendor selection due diligence, the key features to consider are:

• Support for multiple authentication methods (SSO, certificates, username/password, identify management, and more)

• Ability to integrate with back-end databases and systems from multiple vendors

• Security for data (in motion and at rest)

• Support for offline use with data synchronization

• Application on-boarding, provisioning, versioning, and lifecycle management.

• Cross-platform push notifications • Administration functions including

reporting and analytics • Multi-platform support

20 App Development in a Mobile World

SECTION 4: Achieve Best Practices

APP DEVELOPMENT METHODS: MOVING FROM CONCEPT TO LAUNCH

The design process for mobile apps is significantly different from the familiar client-server business app. Design teams are applying new collaborative approach-es, such as design thinking and agile development, to create apps for today’s dynamic, consumer-driven mobile world. Before your organization develops its first mobile app, consider adopting these forward-thinking techniques that were used to develop many of the most successful mobile apps available.

Agile development is based on iterative development cycles that release apps in shorter time frames (sprints) with feature sets that will be enhanced in future releases. Enterprises applying agile development:

• Launch basic functioning apps in a relatively short timeframe

• Continually improve the app by incorporating insights uncovered during development

• Release frequent updates and new features regularly that enhance the apps

Design thinking encourages out-of-the-box thinking and cross-team collabora-tion. Businesses are adopting the prac-tice to create user-centric products and services. By solving a design issue through a user lens, software designers build apps that are much more appealing and useful to end users.

When using design thinking, developers create an app in multiple stages. Design thinking proponents use different labels for the stages, but generally speaking they are:

• Understand and define the problem • Observe users • Generate ideas (ideate) • Prototype/experiment • Test, implement, improve

Both agile development and design thinking spur creativity and originality. Developers can pour the innovations that result from these methodologies into highly functional, user-friendly apps.

21App Development in a Mobile World

Other very important parts of mobile design process are User Experience and User Interface Design. The current Mobile OS’ have set the bar very high for how things should look & feel. With the consumerisation of IT through mobile, the prosumers in the enterprise will expect apps that have the same amaz-ing, beautiful and compelling UX/UI that consumer level apps have. Hence setting the mobile design bar higher in the enterprise than ever before.

MANAGING THE APP LIFECYCLE

Businesses have never witnessed a life-cycle like the mobile app. These apps have more frequent updates, must accommodate multiple device types, and support different access rights for

SETUP A MOBILITY CENTER OF EXCELLENCE

Mobile technology is one of the fastest changing fields today. The need to stay current on mobile device capabilities, operating system capabilities and

SECTION 4: Achieve Best Practices

internal users. Those are the major differences and even more make manag-ing mobile apps labor intensive.

A mobile app platform centralizes the development, management, and all steps from launch to end of life across all mobile apps. Businesses can easily oversee:

• One development effort using familiar development tools to create an app for all devices

• Consistent apps that have the same deep device level controls, access to back-end data, security controls, and premium performance

• App launches and updates that are preconfigured based on group policies related to device type or job role

changes, and select the right tools and approaches for a a given business case, supports the creation of a dedicated group of mobile experts.

Many companies have opted to staff a “chief mobile officer” role and/or create a mobile center of excellence (COE)

• “Zero touch” app deployments and automated app updates that minimize worker disruption and reduce tech assistance

• Pain-free deployments through enterprise app stores

• Exceptional, consumer-grade, user experiences

SAVE TIME AND MONEY

Every development project can be controlled using three levers: cost, schedule, and functionality. Organiza-tions attempt to set these levers to achieve the best results based on their unique situation. To streamline your mobile app projects, consider these options to reduce costs or decrease time to market.

group to manage the technical complexi-ties on behalf of the business. For a detailed discussion on how to create a COE, and develop its charter, read: “Best Practices for a Mobility Center of Excellence.”

Reduce costs and time Pre-built apps Look for apps that can be rebranded and modified for internal processes

Reduce costs and time Deployment options Consider a cloud-based deployment to speed time to market, avoid capital budget constraints, or adapt to unknown adoption rates

Reduce TCO Integrated enterprise mobile management

Push out new versions quickly with minimal resources required

Reduce TCO Integrated reporting Provide sophisticated reports of usage information, adoption rates, performance stats, and more, in seconds

Reduce TCO Traceability Troubleshoot and fix problems quickly before they cause widespread issues

22 App Development in a Mobile World

SECTION 5: Finding SAP Resources

HOW CAN SAP SUPPORT MY MOBILE INITIATIVES?

Both analysts and customers alike acknowledge SAP as leader in mobile. SAP is the only vendor to be named a Leader in both of Gartner’s Mobile Magic Quadrants, and achieve an “‘Excellent’ Score for Product Viability in Gartner’s Critical Capabilities for Mobile Applica-tion Development Platforms.” Download the reports for more information:

• 2013 Gartner Mobile Application Development Platform Magic Quadrant

• 2013 Gartner Mobile Device Management Magic Quadrant

• 2013 Gartner Mobile Application Development Platform Critical Capabilities

If you are ready to go all-in with mobile, the SAP portfolio delivers what you need. Here’s how to do it:

Enterprise Mobility Management: Deploy SAP Afaria for Mobile Device Management, app management, telco spend management, app distribution and on-boarding, and deployed app feedback.

Manage mobile content: Roll out SAP Mobile Documents (cloud or on-prem-ise) to enable secure and flexible access to and collaboration to business content.

Pre-built, customizable apps: Purchase apps from SAP Store for instant mobilization.

SAP Mobile Platform: Deploy pre-built and custom B2E, B2B, and B2C apps running on top of SAP Mobile Platform for enterprise-grade security, back-end agnostic deployments. Build native, hybrid, MDD, and SMS apps, with SAP toolkits or your choice of development environments.

Consulting and Rapid Deployment Services: Fill skillset gaps with experts from SAP and SAP partners that can take you from mobile strategy develop-ment through app development, system deployment, and on-going lifecycle management.

Enhanced capabilities: Roll out apps that will astonish your customers, employees, and partners. Feature 3D visualization, augmented reality, loca-tion-based services, exceptional perfor-mance, and integration with SAP HANA. Watch this short video showcasing apps built by our Mobile Innovation Center using SAP Mobile Platform.

SAP HANA Cloud Platform: SAP Plat-form as a Service (PaaS) offering powered by SAP HANA.

Managed services: Deploy mobile solu-tions in the cloud for fast deployments that don’t drain IT resources with a service provided by SAP Partners.

23App Development in a Mobile World

SECTION 5: Finding SAP Resources

See How SAP Customers Run Their Businesses Better with Mobile

Vodafone: A Trailblazer in Mobility with SAP

Sysco Improves Processes with SAP for Wholesale Distribution

Abantia: Calculating the Value of a Mobile Investment

Standard Bank of South Africa is Bringing Banking to the Unbanked

Creating a Mobility Strategy for Real-time Service Information

24 App Development in a Mobile World

SECTION 5: Finding SAP Resources

LEARN MORE WITH SAP MOBILE RESOURCES

There are many resources available online. Here are the main ones to investigate when getting ready to deploy your mobile solution:

Resource Description

www.sap.com/mobile The main SAP Mobile website. From here, you can explore all SAP Mobile solutions

www.sap.com/mobileplatform

SAP Mobile Platform site on sap.com

SAP Mobile Platform Developer Center

SAP Community Network Site for getting started with the SAP Mobile Platform. Sign up for a free 30 day trial, or free developer license for the platform hosted on Amazon Web Services

SAP Mobile Academy Free video tutorial site on how to sign up for the free trial, free trial and free developer license, and step-by-step guides for building native and hybrid apps on multiple device platforms

SAP Mobile Secure The most comprehensive mobile management and security portfolio. Embraces mobile device diversity and provides IT with the confidence that corporate information is safe. SAP Mobile Secure solutions enable enterprises to secure devices, apps, content, and services, optimizing the mobile experience for users of today’s most popular mobile devices

SAP Afaria Free Trial SAP Afaria is an industry-leading Enterprise Mobility solution to manage and secure large-scale deployments of mobile devices. The software simplifies the complexity of mobility whether workers are using BYOD or corporate-owned smartphones or tablets for both cloud and on-premise deployments.

SAP Mobile Documents SAP Mobile Documents delivers a mobile content management solution designed for enterprise deployments where collaboration, security, and control of business content are critical

SAP App Protection by Mocana

The Mocana app wrapping solution helps customers address advanced mobile security requirements and quickly deploy secure mobile apps, especially in highly-regulated industries like financial services, retail, and government. It gives SAP advanced security features and FIPS 140-2 certified encryption for apps

Tangoe (Partner Development Agreement)

SAP partner Tangoe offers a Telecom Expense Management (TEM) solution that helps the mobile enterprise contain mobile costs through a number of different products focused on Mobile Telecom Expense Management

SAP Mobile Strategy Services

SAP offers a pre-defined service for customers just starting with planning or adopting Enterprise Mobility, as well as detailed planning for Enterprise Mobility

Talk to an SAP representative: +1-866-727-1489

Contact SAP

www.sap.com/contactsap

(13/10) ©2013 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.