You are on page 1of 36

2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T

1
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
D Z O N E R E S E A R C H P R E S E N T S
2 01 4 GUI DE TO
MOBILE
DEVELOPMENT
TOOLS, STRATEGIES, AND INSIGHTS FOR
ACCELERATING MOBILE DEVELOPMENT
BROUGHT TO YOU I N PART NERS HI P WI T H
2
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
WELCOME
Dear Reader,
This is the third guide we've produced in the DZone
Research series this year and we've been excited by
your response to the rst two. It is clear that many of
you are anxious for resources to help create high-
quality products and services, and your feedback
thus far has been immensely helpful in shaping the
direction of these guides.
For this guide, we heard from over 1,000 of
you and learned a ton about the ways you are
developing for mobile. With your insights, we
were able to put together a strong portrait of the
mobile development landscape and unveil many
perspectives. As you read this guide, we hope that
you will discover some new things that will help
accelerate your development, from best-practices to
new tools.
As always, thanks to everybody who played a part
in the creation of this guide, including those of
you who took the time to complete our survey, the
experts who shared their knowledge, the vendors
who helped us understand their products, as well as
our research partners.
Enjoy the guide and happy developing!
Jayashree Gopalakrishnan
Director of Research
research@dzone.com
TABLE OF CONTENTS
SUMMARY & KEY TAKEAWAYS
KEY RESEARCH FINDINGS
THE MOBILE LANDSCAPE: CROSS-PLATFORM
PROBLEMS AND SOLUTIONS BY ALEC NOLLER
THE STATE OF NATIVE VS. WEB VS. HYBRID
BY MITCH PRONSCHINSKE
BACK-END INTEGRATION: A MAJOR HEADACHE
FOR ENTERPRISE MOBILITY
BY SUHAS ULIYAR
GAME OF PHONES INFOGRAPHIC
MOBILE UX: REFINING PERCEIVED
PERFORMANCE BY ANDREW TRICE
THE STEP-BY-STEP MOBILE
DEVELOPMENT CHECKLIST
SOLUTIONS DIRECTORY
GLOSSARY
CREDITS
DZONE RESEARCH
JAYASHREE GOPALAKRISHNAN
DIRECTOR OF RESEARCH
MITCH PRONSCHINSKE
SENIOR RESEARCH ANALYST,
AUTHOR
MATT WERNER
MARKET RESEARCHER
ALEC NOLLER
CONTENT CURATOR, AUTHOR
BENJAMIN BALL
RESEARCH ANALYST
Special thanks to our topic experts Alex
Curylo, Pieter De Rycke, Raymond Camden,
Max Katz, Jose Roy Javelosa, and our trusted
DZone Most Valuable Bloggers for all their
help and feedback in making this guide.
DZONE CORPORATE
RICK ROSS
CEO
MATT SCHMIDT
PRESIDENT & CTO
BRANDON NOKES
VP, OPERATIONS
ALEX CRAFTS
SENIOR ACCOUNT MANAGER
HERNNI CERQUEIRA
LEAD SOFTWARE ENGINEER
KELLET ATKINSON
DIRECTOR OF MARKETING
ASHLEY SLATE
GRAPHIC DESIGNER
CHRIS SMITH
MARKETING ASSOCIATE
4
10
18
24
25
35
3
6
14
22
DZone Research Guides are published by DZone, 150 Preston Executive, Cary, NC 27513.
All contents 2014 DZone. All rights reserved.
REUSEPERMISSIONS AND REPRINTS:
Email research@dzone.comPhone +1 (919) 678-0300. Fax +1 (919) 443-1110.
PRINTED IN USA.
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
3
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
SUMMARY & KEY TAKEAWAYS
Entering todays mobile space requires signicant decisions about the development technology you want to use. Will your apps
be native, web-based, or will you choose from a variety of cross-platform tools to make something in between? If you develop
native apps, will you build for both Android and iOS? These decisions are often made without adequate knowledge of industry
trends and relevant data. The DZone 2014 Guide to Mobile Development gives readers a full picture of the various approaches to
mobile development, enabling them to overcome its biggest obstacles. Exploring the data and content in this guide and on its
companion site dzone.com/research/mobile will help you understand:
The challenges of cross-platform mobile development and strategies for overcoming them
The strengths and weaknesses of native, hybrid, and web-based approaches to mobile development
Mobile development trends and preferences from a survey of more than 1,000 mobile professionals
Feature comparisons between various Mobile Application Development Platforms (MADPs)
Strategies for mobile user experience design and enterprise integration
KEY TAKEAWAYS
A Web or Hybrid App is Becoming the Preferred Enterprise App
As enterprises start to build more B2E apps, they are likely to turn to web and hybrid apps, or use
MADPs that generate native apps from a common codebase. Our mobile development survey found
that the organizations building web and hybrid apps are making more enterprise apps than the overall
pool of respondents. The organizations that are exclusively focused on enterprise apps are also using
web technologies 15% more than Java, which is the second most common language for that group.
The lower cost of maintaining a single codebase is driving a surge of web and hybrid apps in the
enterprise world.
Many Developers are Turning to Cross-Platform Tools
Cross-platform tools are being used by 41% of the mobile developers surveyed, and it is the
most popular tooling group among a long list of common mobile utilities. This nding is further
emphasized by the two most common pain points among the mobile developers surveyed: testing
efciently on multiple devices (53%) and building native apps for multiple platforms (50%). MADPs
are certainly not the only answer to these challenges, but the platforms compared in our solutions
directory are worth investigating.
The Majority of Mobile Customers are Still External
Among the mobile developers surveyed, 60% said they are developing for
consumers and 54% are developing for businesses outside their own. This
indicates that customer experience should be the key concern for todays
mobile developers, and that performance must feel native. The enterprise
app space is growing, but only 30% of respondents said their organization is
developing them.
Commissioned Apps and Marketing Through Apps are Primary
Revenue Sources
Most companies are making money by building commissioned apps or by
marketing products through a mobile app. The expected revenue source for
mobile apps is correlated to the size of the organization. The most common
target revenue source for organizations larger than 99 employees is revenue from
marketing and brand awareness for another product, while organizations under
100 employees cite commissioned apps as their most common revenue generator.
4
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
KEY RESEARCH FI NDI NGS
DZone surveyed over 1,000 IT professionals with some involvement in mobile technology for the 2014 Guide to
Mobile Development, providing key information on mobile monetization, tool usage, production levels, and
platform prioritization. The largest demographic segments are developers (39%) and development team
leads (29%). 53% of respondents come from small organizations (under 100 employees) and 47% come
from large organizations (100 or more employees). The majority of respondents are headquartered in the
US (36%) or Europe (36%).
MORE MOBILE HOBBYISTS AND EMPLOYEES THAN FREELANCERS
Over half (51%) of those surveyed work in an organization that develops mobile apps and 48% of all
respondents have participated in their organizations mobile eforts. Outsourcing is relatively unpopular,
with only 14% saying their organization outsources mobile development eforts. 37% of respondents
have developed mobile apps as a freelancer, showing that fewer developers choose to strike out on
their own when building mobile apps. However, 56% have built mobile applications as hobby projects,
and 30% of the overall respondents dont expect any return on investment from their apps.
ANDROID AND WEB SKILLS MORE COMMON THAN IOS SKILLS
Android has the largest percentage of organizations and individual respondents
targeting the platform with 84%. iOS is a close second with 70%. 56% of
respondents say they are developing for web or hybrid, and Windows Phone
has a strong showing with 24%. When respondents were asked which platforms
they personally have helped build applications for, Android has a larger lead
with 71% and web/hybrid takes second place with 50%. 47% of the respondents
have built iOS apps and 17% have built Windows Phone apps. Android has a
large set of developers in this survey most likely because its platform language,
Java, is already ubiquitous in the software industry. Web skills, along with Java
skills, are much more common than Objective-C skills, which are not often
used outside of iOS development. One of the more interesting statistics is that,
among large organizations, 14% more organizations are targeting iOS compared
to small organizations.
THE LEADERS ARE BUSINESS AND UTILITY APPS
The top ve types of apps that respondents and their organizations are working on include Productivity, Finance, and Business (63%), Tools and
Utilities (39%), Social Networking and Communications (20%), Travel, Maps, and Navigation (17%), and News, Media, and Weather (16%). For
hobbyists, Tools and Utilities is the most common type (55%), and for freelancers, its between Productivity, Finance, and Business (53%) and Tools
and Utilities (46%). Hobbyists are also much more interested in developing games (27%) or entertainment apps (16%) than other developers.
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
5
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
CROSS-PLATFORM DEVELOPMENT AND TESTING ARE THE BIGGEST PAIN POINTS
The most common mobile development pain points for respondents centered
around multi-platform development and testing. Testing efciently on many
diferent hardware sets and screen sizes is the biggest pain point for respondents
(53%), while building native apps for multiple platforms (50%) is a close second.
The third most common pain point is a lack of skilled mobile developers (40%).
Respondents from large organizations were 10% more likely than those from
small organizations to experience pain points around integrating with existing
in-house apps, lack of skilled mobile developers, and security.
COMMON TIMELINE FOR MOBILE APP DEVELOPMENT IS 1-3 MONTHS
App development time can vary widely based on a host of factors, but nding out how
much time it generally takes organizations and individuals to develop apps is useful for
discovering industry opinions about how long an app should take to complete or how large
a project should be. The top three answers for organizations were 12 weeks (14%), 8 weeks
(13%), and 4 weeks (10%). For individuals working by themselves, their timetables gravitate
toward 4 weeks (15%) with 12 and 8 weeks (both 12%) close behind. As for the number
of apps completed per year, the chart to the left shows statistics for the number of apps
organizations are churning out.
CROSS-PLATFORM TOOLS ARE USED BY NEARLY HALF OF MOBILE DEVS
41% of respondents say they or their organizations are using cross-platform tools such as
Apache Cordova/PhoneGap. This is the most popular type of mobile tool, with IaaS/PaaS as
the second most crucial development utility at 20% usage. For programming languages, Java
is very popular in this group of enterprise developers (73%), but web languages appear to be
the most common skillset (80%). Objective-C for iOS is third with 45%, and C#, the language
of Windows Phone, is fourth with 25%. The mobile usage percentages for the rest of the
programming languages can be seen in the chart to the right.
COMMISSIONED APPS AND PRODUCT MARKETING ARE THE MOBILE BREADWINNERS
Commissioned apps (37%) are the number one overall source of expected mobile app
monetization. Marketing and brand awareness for another product (26%) and app store
purchases (25%) are the other two major sources. For small organizations, commissioned apps (43%) are still the most common expected
revenue source, but app store purchases are in second place (31%) and product marketing is in third (21%). This is probably due to the small
amount of employees needed to build an app-based business or a mobile development-for-hire shop. For large organizations, marketing for
another product is the most common expected revenue source (32%). Commissioned apps are second (28%) and app store purchases are
third (18%). Many larger organizations come with larger products, so often their focus is on moving leads through a sales pipeline toward more
valuable, non-mobile product purchases.
WHAT ARE YOUR ORGANIZATIONS PAIN POINTS
FOR MOBILE APPLICATION DEVELOPMENT?
1 TESTING ON MULTIPLE DEVICES
2 BUILDING NATIVE APPS FOR MULTIPLE
PLATFORMS
3 LACK OF SKILLED MOBILE DEVELOPERS
6
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
Mobile development has become a ubiquitous part of
the software industry, and most developers understand
the central dilemma organizations face when building
a mobile app: cross-platform development. What
options exist for deploying an app to multiple platforms
simultaneously? What are the strengths and weaknesses
of each platform?
The backbone of mobile development is the native application,
but there are a growing number of alternatives: web apps provide
a browser-based solution, hybrid apps leverage web development
skills in a native package, and code translators apply one platforms
native development skillset to the codebase of another. However,
the diferences can be subtle, and every option carries its own set of
drawbacks.
NATIVE DEVELOPMENT
Native applications are built from the ground up for a specic
platform and tailored to t it. The precise, platform-centered
nature of native development means that these apps have no
limits in terms of access to APIs and device features, performance
optimization, and platform-specic best practices for user interface
design. Ideally, every mobile app would be built this way: to suit its
exact purpose while utilizing all of the available resources.
NATIVE APPLICATION DEVELOPMENT
ANDROID IOS WINDOWS PHONE
Language: Java
PrimaryIDE: Eclipseor
AndroidStudio
Language: Objective-C
PrimaryIDE: XCode
Language: C#
PrimaryIDE: Visual Studio
One of the major benets of native mobile development is the
availability of resources. For example, developers targeting
Android have the Android Software Development Kit (SDK) at
their disposal, which includes a suite of tools to streamline the
development process: the SDK Manager condenses updates and
tool installations into a single menu, the AVD Manager provides
access to the Android Emulator and other virtual devices, and the
Dalvik Debug Monitor Server (DDMS) is a powerful debugging tool,
just to name a few. iOS and Windows Phone developers have similar
toolsets available in their SDKs, covering everything from the UI
and device feature tools of Cocoa Touch in the iOS SDK to the real
world testing conditions of the Simulation Dashboard for Windows
Phone 8. These toolsets make native SDKs invaluable and thorough
resources.
Unfortunately, the native SDKs are all robust toolsets that a native
developer has to learn for each platform. To develop native apps
from scratch (rather than through an intermediate tool), developers
must be skilled with the required language, IDE, and development
tools for each targeted platform, and if developers with diverse
skillsets are not available, additional developers must be hired. This
can be a serious problem, given the increasing push to develop on
multiple platforms. For example, according to DZones 2014 Mobile
Developer Survey, 62% of respondents targeted both Android
and iOS. The economic constraints of native development are a
major factor in the growing popularity of web apps, hybrid apps,
code translators, and Mobile Application Development Platforms
(MADPs), which allow developers to reach multiple platforms with
just one tooling ecosystem.
WEB APPS
The skillset for building a basic mobile web app is more common
than that of native development. Essentially, mobile web apps are
just regular websites optimized to look good and function well on
mobile devices, and they can provide a quality app-like experience
if the developer is very skilled in web technologies. Widely
understood front-end web development languages such as HTML,
CSS, and JavaScript provide the logic behind a web app, and there
are plenty of tools and libraries out there to help web developers
direct their skills toward mobile devices. jQuery Mobile and Sencha
Touch are two examples of mobile web frameworks that provide UI
components and logic for sliders, swipes, and other touch-activated
controls that are common to native mobile applications.
The community around open source web technologies is another
key diference between native and web development. Web
technologies like Node.js and AngularJS are some of the most
popular projects in the open source community according to
GitHub statistics [1]. This suggests that the community support and
knowledge base around web technologies is broader than native
technologies.
In addition to being a more common skill set, mobile web
development can also solve a fundamental issue with native
application development. Aside from possible browser compatibility
issues, web apps present a near-universal cross-platform option.
Most APIs and hardware features will not be accessible by web
apps, and because they are not discrete applications in the same
way that native apps are, web apps cannot be distributed through
common means, such as Apples App Store and Googles Android
Marketplace. Web apps may be a particularly exible option, but
they lack a presence on fundamental mobile distribution channels.
HYBRID APPS
Many of the drawbacks for web apps are alleviated by another
cross-platform option built on the same core web development
skillset: the hybrid app. Like web apps, hybrid apps require web
development skills, but unlike web apps, they include some native
features to allow greater exibility. It gets the name hybrid
because it is built with web languages and technologies at its core.
THE MOBILE LANDSCAPE:
CROSS-PLATFORM PROBLEMS AND SOLUTIONS
BY ALEC NOLLER
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
7
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
With the help of a native packaging tool, it can be deployed just
like a native app and access more native device capabilities (device
APIs) than a pure web application.
A hybrid app is created by rst coding the application to run in
the devices native webview, which is basically a stripped-down
version of the browser. For iOS this view is called UIWebView, while
on Android its called WebView. This view can present the HTML
and JavaScript les in a full-screen format, and pure web apps can
achieve this full-screen view as well. WebKit is the most commonly
targeted browser rendering engine because it is used on iOS,
Android, and Blackberry.
Where a web app really starts to become a hybrid app is when
the app is placed inside of a native wrapper, which packages the
hybrid app as a discrete application and makes it viable for app
store distribution. In addition to the native wrapper, a native bridge
allows the app to communicate with device APIs, such as alarm
settings, accelerometers, and cameras. The native bridge is an
abstraction layer that exposes the device APIs to the hybrid app as
a JavaScript API. This is one feature that clearly separates hybrid
and pure web apps, because web apps are unable to pass through
the security structures between the browser and native device
APIs. Access to many of the hardware features on mobile devices
makes hybrid apps feel more like native apps than web apps from
the user perspective.
MADPS AND CODE TRANSLATORS
Some tools can go even further in terms of taking a single
codebase and deploying it on multiple mobile platforms. MADPs
are development tools, sometimes including a mobile middleware
server, that build hybrid or native apps for each platform using
one codebase. Some MADPs, such as Appcelerators Titanium and
Trigger.io, can take advantage of native elements where native
is necessary or higher performing. UI widgets may be native,
for instance, while a more exible JavaScript API condenses the
universal parts of mobile development and maximizes code reuse.
As more native elements are introduced, some of the drawbacks of
native development reappear, such as the costly need for multiple
skillsets. MADPs are most useful in scenarios where an application
needs to work with many back-end data sources, many other mobile
apps, or many operating systems [3].
A less comprehensive but more straightforward solution is to use
code translators when building native apps for multiple operating
systems. These tools take native code and translate it into another
platforms native code, or translate native code into a neutral low-
level alternative, such as bytecode. One example is Googles J2ObjC,
which translates Java classes into their Objective-C equivalents,
alleviating a lot the initial development of an iOS version of the
app. Although its much more than a code translator, a product
called Xamarin does something similar by allowing developers
working with C# and .NET in Visual Studio to produce a native
ARM executable. They can then take advantage of ahead-of-time
(AOT) or just-in-time (JIT) compilation to run their apps on iOS and
Android in addition to Windows Phone [3].
As is the case with hybrid apps, the UI presents a problem.
Because UI development cannot be translated between platforms,
code translators still require signicant knowledge of the
native platform to write the UI. In other words, code translators
can provide substantial benets in terms of cutting down
development time, but theyre not necessarily a write once, run
anywhere solution.
NO SILVER BULLETS
Between native apps, web apps, hybrid apps, and the growing
number of MADPs, there are a lot of options for mobile
development. Its important to note that there is no one solution
that does everything. Some sacrice afordability and accessibility
for pure native performance, UI for easy cross-platform deployment,
or ease of development for native authenticity. Even the simplest
tools come with some degree of a learning curve. If a method with
no trade-ofs existed, the industry would adopt it en masse, and you
would know about it.
Because there are trade-ofs, developers and decision-makers will
have to recognize their needs, and the needs of their users, in order
to determine the best way to approach mobile development.
[1] https://github.com/search?o=desc&q=stars%3a%3E1&s=forks&type=Repositories
[2] http://trigger.io/cross-platform-application-development-blog/wp-content/uploads/2012/05/
slide03-v5.png
[3] http://www.kony.com/resources/glossary/mobile-application-development-platform-madp-0
Ideally, every mobile app would be built this
way: to suit its exact purpose while utilizing all
of the available resources.
W R I T T E N B Y
Alec Noller
Alec Noller is the Senior Content Curator and leader of
the Mobile Zone at DZone. When he's not creating and
curating content for DZone, he spends his time writing
and developing Java and Android applications.
Inspired by Trigger.io [2]
Close the App Gap. Create powerful
data-driven mobile & web apps with
minimal coding.
ANYTIME, ANYWHERE
ACCESS.
Quickly build and deploy apps on any cloud or device with
Progress

Pacic

, Platform-as-a-Service (PaaS). Jumpstart


your mobile or web app development, connect and leverage
data, and deploy your app using the web, cloud, or hybrid
environments all from a single development code.
Visit www.progress.com/dzonemobile
and take a trial today.
2014 Progress Software Corporation and/or its subsidiaries or a liates. All rights reserved.
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
9
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
There is a critical need to deliver apps that
are optimized for web and mobile devices.
As a result, many developers are living by
the motto of web is not enough when
developing enterprise applications. When
developing applications that span web and
mobile, you should think about designing
apps specically for each device, how youll
connect and integrate backend data, and
how youll deploy and manage the apps.
CONSIDERATIONS WHEN DEVELOPING
CROSS-PLATFORM APPS
Do you standardize on a single platform or
use diferent approaches for each device?
One way to avoid this question is to choose
a solution that allows you to build and
deploy apps on any environment, using a
single development approach. To deliver
apps fast and save crucial development
resources, you need to build device-specic
apps without writing device-specic code.
BENEFITS OF USING A SINGLE PLATFORM
While organizations are turning to
Platform-as-a-Service (PaaS) to assemble,
deploy, and manage applications they
need to carefully consider support for
mobile. It is important to select a PaaS that
provides a rich mobile experience without
custom code and also ofers support for
both private and public cloud deployment.
Without these capabilities, you wont reach
your goal of quickly building, deploying,
and managing compelling apps.
DRIVEN BY DATA
What good is an application without data?
With a simple, fast connection to cloud
and on-premise data, you can develop and
deploy modern, high-performance business
applications regardless of source whether
youre using RDBMS, SaaS apps, big data
stores, or others. You need standards-based
data connectivity built into your PaaS
solution so that you can go from data to
application at lightning speed.

Create powerful data-driven mobile and
web apps with minimal coding. Visit www.
progress.com/dzonemobile and take a trial
today.
FUTURE PROOFING APPLICATION DEVELOPMENT
CREATE POWERFUL DATA-
DRIVEN MOBILE AND WEB
APPS WITH MINIMAL CODING.
Close the App Gap. Create powerful
data-driven mobile & web apps with
minimal coding.
ANYTIME, ANYWHERE
ACCESS.
Quickly build and deploy apps on any cloud or device with
Progress

Pacic

, Platform-as-a-Service (PaaS). Jumpstart


your mobile or web app development, connect and leverage
data, and deploy your app using the web, cloud, or hybrid
environments all from a single development code.
Visit www.progress.com/dzonemobile
and take a trial today.
2014 Progress Software Corporation and/or its subsidiaries or a liates. All rights reserved.
Additional informationinthe vendor prole sectionof the guide
WRI TTEN BY
Mark Troester
Senior Director of Pacic
Product Management
and Solution Marketing,
Progress
TARGETS
STRENGTHS
CUSTOMER SUCCESS STORY
NOTABLE CUSTOMERS
DESCRIPTION
FREE TRIAL 30-day free trial
USES
Enterprise Apps (for internal use)
TWITTER @progresssw PHONE 1-800-477-6473
Easily meet the web and mobility requirements of your users
Easily assemble, manage, and deploy web and mobile apps:
powerful applications at low cost.
Leverage multiple data sources with Progress data integration for
web and mobile apps
Deliver powerful native apps without writing device specic code
Rich PaaS support for all your web/mobile or mobile-only apps
Progress Pacic Platform-as-a-Service (PaaS) can
be used to build business apps fast, with simple
point-and-click wizards and drag-and-drop features.
With Pacic you can also connect your app in real
time to a variety of SaaS, relational, NoSQL, big data,
social, CRM, and ERP sources. Using Progress Pacic
you can develop, deploy, and manage apps for iPhone,
Android, web, or cloud. You can manage multi-tenant
apps from the browser in the environment of your
choice: public, private, or on-premise.
Brixxs is already making an impact with Progress Rollbase, part of Progress Pacic, by helping registered taxi companies in the
Netherlands to quickly comply with new regulations and improve the quality of their services in large cities. by using Progress
Pacic, Brixxs has developed and updated applications that have allowed taxi companies to comply with strict new regulations
introduced by the Dutch government, within just 3 days of them coming into effect. Progress Pacic made this possible by
allowing Brixxs to rapidly build their apps using an intuitive, easy-to-use web interface.
moTwin
Brixxs
Good Done Great
Carego International
Explore Analytics
FreshERP
Progress Pacic BY PROGRESS SOFTWARE
Rapidly develop & deploy business apps using the mobile, data integration, self-service, and collaboration
capabilities of Progress Pacic.
FULL PROFILE LINK
dzone.com/r/ xsYW
Additional informationinthe vendor prole sectionof the guide
CATEGORY
MADP



Web
Hybrid
Native
TAGS -JAVASCRIPT- -MOBILE
MIDDLEWARE- -USAGE ANALYTICS-
-PERFORMANCE ANALYTICS--
-REST + SOAP-
10
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
A continuing question in mobile development is whether its
more benecial to build applications that are written directly for
a native platform or to build applications on web languages and
technologies. When tools like PhoneGap emerged, a third hybrid
option became available that could use native code in conjunction
with web languages to gain a set of attributes that no native or web
apps have. Today, there are also Mobile Application Development
Platforms (MADPs) that can generate largely native apps from a
single original codebase, which does not have to be written in web
languages.
MADPs are compared on a tool-by-tool basis on DZones mobile
research portal (http://dzone.com/research/mobile). For native,
hybrid, and web applications, this article will serve as a comparison
between the three mobile app types. In addition to the comparison
information, youll also get a snapshot of the industry use cases and
current trends around native, web, and hybrid apps.
COST
Native apps often cost more to develop and distribute because of
the distinct language and tooling ecosystems, which require more
investment in developer skills if you need to develop for more than
one platform. However, cost is dependent on many other factors
as well, so native apps wont be the most expensive option in every
case. Building an excellent mobile web app also requires a high
degree of developer expertise, so no matter which type of app you
build, quality will always be expensive.
TESTABILITY
Mature and predictable native platforms with proven tools tend to
make testing easier than the frameworks that create hybrid apps
using JavaScript-to-native communication. Web app testing can
also be a struggle if the developer isnt skilled and knowledgeable
about the JavaScript ecosystem. Native app testing becomes
increasingly difcult if you maintain multiple codebases and
support a large number of devices.
CODE REUSABILITY/PORTABILITY
Perhaps the biggest weakness of native apps is their lack of
portability to other platforms. The appeal of web apps is that you
can have one codebase and run it on any major mobile platform.
The appeal of hybrid apps is similar, because you are able to reuse a
large amount of code for each platform. However, web apps arent
100% portable. Newer web standards arent always supported by
the browsers on every device, so even web developers have to
worry about compatibility issues [1]. It should also be noted that
native app webviews are not the same as device browsers, and
therefore have their own fragmentation issues.
DEVICE ACCESS
Although web apps can access some basic mobile device APIs, like
the GPS for geolocation apps, they still have very limited hardware
access. They dont have support for Digital Rights Management
(DRM), which is needed for many multimedia services, they cant
harness background processing, and they cant use secure storage
outside of applications. There are some new standards currently
being drafted by the W3C that will give web apps a few more
capabilities for accessing device APIs, but for the next few years,
hybrid apps and native apps will provide signicantly more access
to device APIs. Hybrid app frameworks have made a lot of progress
getting access to most of the low level features, like the gyroscope
and accelerometer.
UI CONSISTENCY
Mobile web UI frameworks help web and hybrid apps build native-
looking UI components, but diferences still remain. The frameworks
also have to stay up to date with major platform design updates
like iOS 7. In iOS, a web or hybrid UI is especially apparent, because
when UIWebView is used, the bitmap compositing does not happen
in the hardware like it would for a native app. Subtle features
like the bouncing efect at the bottom of a page on iOS cant be
completely recreated in JavaScript. Thats why the developers who
built forecast.io (a web app that rivals native UX) recommend that
NATIVE HYBRID WEB
COST
Commonlythehighest of thethreechoices if
developingfor multipleplatforms
Similar topurewebcosts, but extraskills are
requiredfor hybridtools
Lowest cost duetosinglecodebaseandcommon
skillset
CODE REUSABILITY/
PORTABILITY
Codefor oneplatformonlyworks for that
platform
Most hybridtools will enableportabilityof a
singlecodebasetothemajor mobileplatforms
Browser compatibilityandperformancearethe
onlyconcerns
DEVICE ACCESS PlatformSDKenables access toall deviceAPIs
ManydeviceAPIs closedtowebapps canbe
accessed, dependingonthetool
OnlyafewdeviceAPIs likegeolocationcanbe
accessed, but thenumber is growing
UI CONSISTENCY
Platformcomes withfamiliar, original UI
components
UI frameworks canachieveafairlynativelook UI frameworks canachieveafairlynativelook
DISTRIBUTION
Appstores providemarketingbenets, but also
haverequirements andrestrictions
Appstores providemarketingbenets, but also
haverequirements andrestrictions
Norestrictions tolaunch, but therearenoapp
storebenets
PERFORMANCE
Nativecodehas direct access toplatform
functionality, resultinginbetter performance
For complexapps, theabstractionlayers often
prevent native-likeperformance
Performanceis basedonbrowser andnetwork
connection
MONETIZATION
Moremonetizationopportunities, but stores
takeapercentage
Moremonetizationopportunities, but stores
takeapercentage
Nostorecommissions or setupcosts, but there
arefewmonetizationmethods
THE STATE OF NATIVE VS. WEB VS. HYBRID
BY MITCH PRONSCHINSKE
NATIVE VS. WEB VS. HYBRID: 7 FACTORS OF COMPARISON
CON PRO NEUTRAL
KEY
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
11
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
you build an original UI for web apps, rather than trying to recreate
the native UI and having your app look wrong to users [2].
SEO
This may not be the fairest criterion for native applications, but if you
want the textual and semantic content of your app to be found and
ranked by search engines, your app has to have a web component. A
web component is required because apps are closed environments,
and search engines cannot access that information.
DISTRIBUTION
With app stores, native and hybrid apps are able to harness marketing
tools such as rankings and featured placement all in a well-maintained
system. Web apps, by contrast, dont have to fulll any app store
requirements, and they are accessible through any compatible
browser. The disadvantages for native and hybrid apps are the
app store requirements and content restrictions. For web apps, the
downsides are that you dont get the marketing benets of an app
store. Web apps also have to be manually bookmarked if the user
wants a shortcut on their homescreen.
PERFORMANCE
Native code will always be the most straightforward path to the
snappiest performance. Hybrid app performance can be strong,
but will sometimes sufer depending on how the tools build code to
interface with the native OS. Web apps can have strong performance
as well, if you have skilled web developers and use modern standards
like appcache. Web and hybrid performance will also improve as
mobile browsers get faster JavaScript engines. Other things that
can help mobile web performance include using WebKits overow
scrolling to create scrolling divs, using tools like FastClick to speed up
hyperlinks, and only animating GPU-accelerated properties [3].
DEPLOYMENT/UPDATES
If app updates arent automatic, they can be a real annoyance to
the user. A huge advantage for web apps is that you can deploy
them like any other desktop website. Hybrid apps can make some
updates through the web without app store approval, but hybrid apps
and native apps still have to jump through the hoops of app store
approval, and they need to download any updates from the app store.
MONETIZATION
For web apps, you can make money through advertisements,
subscriptions, or an app store for web apps, though the vast majority
of app downloads still happen in the native platform stores. Native
and hybrid apps have more options for monetization, including in-app
purchases, platform-native ads, and the app purchase itself. However,
to be in the high-prole native app stores, you need to hand over a
percentage of your app download revenue to the company that owns
the store (usually around 30%). There is also an initial fee to develop
for the platform and deploy on the app store.
NATIVE VS. WEB VS. HYBRID: THE TRENDS
When looking at the trends in the native vs. web vs. hybrid
conversation, it cant be denied that native apps are heavily favored
by consumers. A recent survey by Flurry, a mobile analytics company,
found that mobile users in the US spend 86% of their time using
native or hybrid apps [4]. That number is still 54% even if you lter
out gaming apps. Comparatively, 14% of their time is spent in the
browser using mobile websites. This is a pretty good indication that
an app-like experience, whether its through native or hybrid code, is
the preferred mode of consumer interaction.
If thats not enough evidence, you just need to look at the most
popular mobile apps right now and youll nd that most of them are
native. Facebook and LinkedIn both tried to build hybrid apps for
accessing their websites, but they found that the experience and
performance werent up to their standards, so they built native apps
for all of the major platforms [5]. However, those companies can
certainly aford to have many developers with the skillsets to build on
those platforms.
An area where
web and hybrid
app development
is becoming more
common is in the
enterprise. The need
for business-to-
employee apps (B2E)
is expected to grow
exponentially over the
next few years, and
most companies will
not want to build and
maintain two or more
codebases for every
app. Another option
for these enterprises is
using MADPs, which were described in the introduction. The expected
growth of B2E apps has led some analysts to recommend choosing
hybrid apps or MADPs for large scale internal app development, while
building native apps for external customers with high performance
expectations [6]. Web apps tend to be recommended if the
organization needs to circumvent app stores, build an e-commerce
storefront that is searchable on the web, or create a marketing site
that is also easily searchable and accessible through the web.
The point of this exploration is not to pick a winner, but to know the
strengths and weakness of each application type. The choice between
native, web, or hybrid is dependent on a number of factors, including
business needs, app requirements, developer skill, and development
timelines. All potential types should be explored and evaluated before
implementing a mobile strategy.
[1] http://mobilehtml5.org/
[2] http://blog.forecast.ioitsnotawebappitsanappyouinstallfromtheweb/
[3] https://github.com/ftlabs/fastclick
[4] http://blog.flurry.com/bid/109749/AppsSolidifyLeadershipSixYearsintotheMobileRevolution
[5]https://www.facebook.com/notes/facebookengineering/
underthehoodrebuildingfacebookforios/10151036091753920
[6]http://www.techtimetea.com/trendsenterprisemobility2014/
W R I T T E N B Y
Mitch Pronschinske
Mitch Pronschinske is the Head Analyst for DZone's
Research division. He has been writing, curating, and
editing content for an audience of IT professionals
for over four years. In that time he has learned the
complexity that software producers deal with on a
daily basis, and he strives to make their world easier
to understand and digest.
THE CHOICE BETWEEN NATIVE,
WEB, OR HYBRID IS DEPENDENT
ON A NUMBER OF FACTORS,
INCLUDING BUSINESS
NEEDS, APP REQUIREMENTS,
DEVELOPER SKILL, AND
DEVELOPMENT TIMELINES.
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
13
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
The forces pushing enterprises to mobile
are so well documented and talked about
that they dont really bear repeating.
The business case has been made. The
organization has spoken, and the response
from IT is quite varied.

The early adopters listened to public
examples, like Facebook, and decided that
native was the way they had to go even if
their app bore no resemblance to the public
use case. What they unfortunately ran into
was a big bag of hurt. The fundamentally
splintered approach of hand-coded, cross-
device native mobile app development
crushed many of these projects after the
rst test app.

Others went down the path of trying to
cram a desktop browser app onto a four-
inch screen, often with disastrous results.

These early wounds
developed into scar tissue
that still leaves some IT
shops hesitant to engage.
The many that are pushing
(or being pushed) past that
fear are understandably
cautious and curious:
What are my options?
Which path should I choose (pros and
cons)?
What rst app gives the biggest bang for
my buck?
HOW DO I GET STARTED QUICKLY?
Much has changed since the time of these
rst painful forays, as is always the case
with technology. The state-of-the-art has
advanced to a point where enterprises can
meet the high demands of their customers,
partners, and employees with amazingly rich
UX that weaves data, process, and practice
cohesively inside apps that run beautifully on
any form factor they are used on.

For more information, go to http://bit.ly/m-
dzone
PAINLESS MOVE TO MOBILE
THE STATE-OF-THE-ART FOR MOBILE HAS ADVANCED
TO A POINT WHERE ENTERPRISES CAN MEET HIGH
DEMANDS ... WITH AMAZINGLY RICH UX THAT WEAVES
DATA, PROCESS, AND PRACTICE COHESIVELY.
WRI TTEN BY
Sean Allen
Director of Product
Marketing, OutSystems
TARGETS
STRENGTHS
CUSTOMER SUCCESS STORY
NOTABLE CUSTOMERS
DESCRIPTION
FREE TRIAL Free version for individual
users, no ALM or staging capabilities
USES
Enterprise Apps (for internal use)
TWITTER @outsystems PHONE (404) 719-5100
Create once for all devices utilizing responsive web design
True no lock-in: customers can detach on to industry-standard
application stacks with open Java or C# code; no proprietary
runtime
Can use flexible deployment scenarios from on-premises to
public, private , or hybrid cloud
Allows creation of more complex systems, including those using
large volumes of data and non-trivial workflows
Not just for building single-function apps
OutSystems provides an open, high-productivity
PaaS that allows users to create, deploy, and manage
enterprise mobile and web apps with integration into
existing systems. OutSystems includes Continuous
Delivery facilities to deploy and manage those apps
after release, including lifecycle governance and
integrated UX monitoring.
Liberty Seguros is a leading insurance company and part of the Boston-based Liberty Mutual Group - a global insurer and
sixth largest property and casualty company in the United States. Liberty's vision was to connect every single department
and external partner through an end-to-end solution that placed the customer at the core of operations and analytics. The
single information system would streamline collaboration with external partners such as agents, repair shops, customers, and
more. Liberty is a great example of what long-term use of OutSystems Platform can produce. Fast forward 10 years and Liberty
Connect is a mature collaborative platform with customers at its core. It allows every area of the company, including external
partners, to interact in real time, and that has made it possible for Liberty to completely sustain its business without losing the
ability to offer customer-centric services.
Liberty Insurance
PlayRight
FICO
Bacardi
Warner Brothers
Charles River Laboratories
OutSystems Platform BY OUTSYSTEMS
OutSystems Platform empowers developers to create, deploy, and manage amazing mobile and web applications
more efciently with current skills.
FULL PROFILE LINK
dzone.com/r/ GMRL
Additional informationinthe vendor prole sectionof the guide
CATEGORY
MADP

Web
Hybrid
Native
TAGS -JAVASCRIPT- -JAVA- -IDE-
-VERSION MGMT-- -USAGE ANALYTICS-
REST + SOAP-- -HOSTED-
14
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
A few months back, I was asked to talk about my job
in front of a class of 8th graders during a local school's
career day event. To simplify things, I told the class
that I build mobile applications for companies. I
explained that the apps I create are like the apps that
you nd on the app store, except they are built for
businesses. One of the students raised her hand and
said that she had built an iPhone app in two weeks!
Thats right, 8th graders are now building iPhone apps, and
one of them was asking me what was so tough about my job?
Upon reection, I realized that over the last 15 years of building
mobile apps, we have come a long way from the time when
it used to take developers months or sometimes more than a
year to build one app. You would need highly skilled mobile
application developers for Windows Mobile, Symbian, or
Blackberry, but now even kids can build iOS and Android apps.
There does seem to be an app for everything these days, but
the one area over the last decade that remains a complex
and costly endeavor is integrating the mobile facing client
application with enterprise systems. Integration comes with
challenges that include adherence to IT security policies for
Single Sign-On (SSO), integrating with one or more back-end
applications, complying with data encryption policies, and
other obstacles that still exist after a decade of unprecedented
technological progress.
Today, there are many frameworks and tools that help
mobile client developers build native, web, or hybrid mobile
applications. However, there are fewer tools that make your
life just as easy when integrating the client facing application
with enterprise systems. I wonder what the 8th graders
response would have been if I had asked her to authenticate
her application via SSO and integrate it with an enterprise
application for data?
ENTERPRISE INTEGRATION MAKES MOBILE HARDER
Creating mobile applications continues to create new
challenges for the IT team. Even talented programmers nd
that they might not have the specic expertise required for
exposing back-end services so they can be readily and securely
consumed by mobile applications. Not only is IT struggling
to provide the required skill sets for a mobile world, they
are nding it difcult to meet new expectations for project
timelines.
Additionally, it is rare for customers to say that they need a
mobile app in the next 12 to 18 months. Most customers expect
applications to be delivered in a few days or weeks. Customers
and even development professionals often underestimate how
difcult it is to build, connect, secure, deploy, and manage a
mobile app.
The reason for this is because writing a standalone client
app and posting it to the app store isnt the difcult part.
The difcult part, especially for the enterprise, is making that
application talk efectively to back-end enterprise systems. It is
also about securing the data accessed by the app as it connects
to the back-end systems. To do that, developers must devise
ways to extract critical information from back-end applications
and data repositories, while also delivering output optimized for
mobile devices.
HARD DECISIONS
Mobile development also forces hard decisions about what
features to include from the backend. Mobile is not about
putting wheels on the system of record (SOR) and calling it
mobile. Mobile apps must be designed with context in mind and
with the supporting data source(s) to deliver the context. In
the past, mobile applications were mostly integrated to one on-
premise back-end application. Today, enterprises are beginning
to deploy a distributed application environment with the core
applications remaining on-premise and others being moved to
the cloud (sales, HCM, etc.). In addition, there are other public
cloud services, such as geolocation, payment, social networking,
collaboration, and messaging, that drive additional context for
the user when integrated with mobile applications.
These mashups deliver a nal challenge to IT, which is that
these applications must scale reliably with enterprise-grade
performance. Many enterprises have not faced this challenge
because they have only dealt with the tactical deployment of
one or two mobile apps.
However, as the user volume grows from a predictable B2E
volume to an unpredictable B2C volume, the ability of the
infrastructure to scale and perform at an enterprise-grade
becomes critical to providing an excellent quality of experience
(QoE). A slow response for data from the backend will have
end-users abandoning an application despite the best user
interface, which will cripple the overall user experience.
BACK-END INTEGRATION:
A MAJOR HEADACHE FOR ENTERPRISE MOBILITY
BY SUHAS ULI YAR
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
15
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
SOA AND MOBILE
Wasnt the promise of Service-Oriented Architecture (SOA)
to provide a high-performing and reliable services layer that
integrates the back-end applications and abstracts them from
the consumers of data (i.e. the multichannel clients)? So, why
do you need a mobile enterprise application platform (MEAP)
or Mobile Application Development Platform (MADP) in order
to develop mobile enterprise applications?
The truth is you dont. MEAPs and MADPs came into existence
to solve both the clientside development challenges as well
as the back-end integration challenges. They do this by
providing a consistent way to integrate with back-end systems
and provide additional mobile services such as bidirectional
sync for ofine applications, push notications, application
provisioning, and version control.
SOA vendors were being used primarily for web applications
or application-to-application integration. They were not
focused on solving the mobile integration problems, such
as providing a lightweight protocol for delivering output
optimized for a mobile device. This led to fragmented,
duplicated, and siloed architectures, one for mobile and one for
the rest of the applications.
FULFILLING THE PROMISE OF SOA
The middleware infrastructure designed for web-based
applications can now support mobile clients by exposing
existing services or reshaping existing services as RESTful
APIs, which are the preferred mechanism to integrate services
for mobile applications. Those features, which used to be
unique to MADP vendor platforms (e.g. push messaging, sync,
caching), are now often available as features of the middleware
technology stack.
As data gets distributed
and fragmented,
orchestrating data between
these back-end systems
becomes a requirement.
With user identity
distributed, it becomes
a critical requirement to
have a federated identity
with integration to SSO
that supports diferent
authentication protocols
(such as OAuth 2.0
and SAML) along with
traditional enterprise
user stores (LDAP, AD).
It is critical to have a
middleware architecture
that brings together
an integrated identity
management solution and
an integration architecture
that exposes services
that can be consumed
by multiple channels. In
addition, this infrastructure
must have built-in
reliability, scalability, and
performance that can handle
a growing and potentially
unpredictable volume of
trafc above your existing
web trafc. This is what is
going to make an enterprise
successful in delivering
efective multi-channel
applications.
With the move towards the
cloud, Mobile-Backend-as-
a-Service (MBaaS) provides
a standard approach to deal
with complex server-side
programming. It provides a
set of rich RESTFul interfaces for all the operations required
by the mobile app and abstracts the backend from the mobile
developer. MBaaS comes with built-in mobile-specic SDKs/
APIs and services, custom and third party APIs, containers to
build and orchestrate services, integrated security, analytics,
monitoring, and management. With all these features, client
developers can focus more on front-end applications by using
their choice of mobile client development tools for native,
web, or hybrid apps. This enables developers to simplify
development by integrating with mobile-ready APIs exposed in
the cloud.
The promise of SOA is being fullled, so now what? You might
not need a MEAP or MADP that solves a niche problem. Mobile
is no longer tactical; it is critical to business success. Businesses
are looking for an enterprise-wide mobile-rst strategy for
B2E and B2C applications that leverages and complies with
their back-end infrastructure for security and integration.
Enterprises are looking to reduce cost of ownership and deliver
to their business by reusing common components. They are
always looking for ways to simplify enterprise mobility. After a
decade of mainly front-end innovations, were nally starting to
see solutions that also simplify back-end concerns.
W R I T T E N B Y
Suhas Uliyar
Mr. Suhas Uliyar is a 19-year mobile industry veteran,
known as a strategist and technology evangelist
responsible for designing and developing enterprise
mobile applications, middleware, and tools. Suhas
is responsible for driving Oracle's mobile strategy
and vision. He is a seasoned executive with years of
technical and business management experience in
enterprise software. He has a successful track record
as both an entrepreneur in small start-ups and as
an executive with major industry leaders. Suhas
has held leadership positions with SAP, Motorola
Solutions, Spring Wireless, Dexterra (Antenna
Software), and Micromuse (IBM).
MOBILE DEVELOPMENT
FORCES HARD
DECISIONS ABOUT WHAT
FEATURES TO INCLUDE
FROM THE BACKEND.
MOBILE IS NOT ABOUT
PUTTING WHEELS ON THE
SYSTEM OF RECORD AND
CALLING IT MOBILE.
WASNT THE PROMISE
OF SERVICE-ORIENTED
ARCHITECTURE (SOA) TO
PROVIDE A HIGH-PERFORMING
AND RELIABLE SERVICES
LAYER THAT INTEGRATES THE
BACK-END APPLICATIONS AND
ABSTRACTS THEM FROM THE
CONSUMERS OF DATA (I.E. THE
MULTI-CHANNEL CLIENTS)?
www.bridgeit.mobi
A Different Kind
of Hybrid
HTML5 Development
Access Native Features
Cross-platform Support
No Native Code
No App Store Submissions
No New Tools
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
17
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
Hybrids deliver native features using
web-based development techniques.
Conventional hybrids bundle the web
app into a native app, but BridgeIt
eliminates this requirement and opens new
possibilities.
HTML5: YES, BUT...
Hybrids use HTML5/CSS3/
JavaScript, but are typically
bundled with an embedded
browser into platform-specic
native apps. These apps are
installed through app stores
and run locally on the device.

BridgeIt apps are pure web
apps. The BridgeIt utility
augments the standard mobile
browser with native features
accessible directly from the
web app. Web deployment
eliminates external approvals,
and the BridgeIt utility is automatically
installed when required.
DEVELOPMENT EASE
Bundling conventional hybrids requires
additional tooling and reduces developer
efciency. Furthermore, the capabilities of
embedded browsers have lagged behind
best-in-class mobile
browsers like Safari and
Chrome. Developers
must use only the lowest
common capabilities of
the embedded browsers,
setting aside the
powerful new features of
HTML5/CSS3.

No bundling is required
with BridgeIt, and the
web app leverages
best-in-class browser
capabilities. The BridgeIt
utility augments the standard browser with
native features and is automatically installed
when required.
SIMPLE DISTRIBUTION
Conventional hybrids are native apps
and are typically published to platform-
specic app stores. External approval and
publication processes are onerous and time
consuming, which increases support costs.

As web apps, BridgeIt hybrids leverage
server-based distribution. They are not
subject to app store submission processes or
approvals, and support costs are reduced.
BRIDGEI T: NOT ALL HYBRIDS ARE CREATED EQUAL
WRI TTEN BY
Steve Maryka
CTO, ICEsoft
Technologies
CONVENTIONAL
HYBRIDS BUNDLE
THE WEB APP INTO
A NATIVE APP,
BUT BRIDGEIT
ELIMINATES THIS
REQUIREMENT
AND OPENS NEW
POSSIBILITIES.
TARGETS
STRENGTHS
CUSTOMER SUCCESS STORY
NOTABLE CUSTOMERS
DESCRIPTION
FREE TRIAL Open source version
available
USES
Enterprise Apps (for internal use)
TWITTER @icefaces PHONE (403) 663-3322
Automated device theming enables a single web application to
adopt the look of the native mobile device it is viewed from
Extends the ICEfaces Ajax Push capabilities with Cloud
Push, leveraging native platform push capabilities to deliver
notications even when the application is not active
Extends the ICEfaces framework with a suite of mobile controls
for UI development
ICEmobile is a framework for developing
cross-platform mobile web applications with Java
EE and JSF. ICEmobile supports hybrid application
development with the ICEmobile containers and
integrates with the BridgeIt utility application.
A large parcel delivery company had a legacy application running on Java EE infrastructure, and was accessed by employees
using desktop browsers. Evolving business demands required the functionality be extended to include external users/
customers accessing the application via tablets and smart phones. Development and support costs associated with native
mobile development were unacceptable, and app store publication was undesirable. ICEmobile enabled them to leverage
legacy software investments and easily extend their existing desktop application into the mobile space. ICEmobile's suite
of mobile JSF components simplied the application design, and minimized development and support costs. Additionally,
ICEmobile's push and hybrid capabilities future proofed their product roadmap.
Aetna
FedEx
U.S. Steel
BNSF
Thermo Fisher Scientic
US Government
ICEmobile BY ICESOFT
ICEmobile is an easy and cost-effective way to mobilize Java EE web applications. Go beyond HTML5.
FULL PROFILE LINK
dzone.com/r/ hkyX
Additional informationinthe vendor prole sectionof the guide
CATEGORY
MADP

Web
Hybrid
Native
TAGS -JAVASCRIPT- -JAVA- \
-ON-PREMISE- -MOBILE MIDDLEWARE--
-IDE-
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
21
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
Data is critical to an organization, but
thats not news to anybody. Its not just
a by-product of doing business, it is the
business. Being able to access and digest
that data is a competitive edge. For many
years, it sat behind large CRT monitors and
enterprise grade rewalls. The data stayed
safe and sound in the data center. Laptops
were the rst to challenge the system. VPN
connections arose to answer the outcry and
help keep data safely at home.

Then mobile showed up and knocked on the
door. Mobile devices with their silky smooth
designs and futuristic form factors that let
you access your email, approve workows,
and close a sale.
KEEPING IT SAFE
Building mobile apps is not the same as
developing desktop and web apps. Our
standardized tools buy us little to nothing
when it comes to mobile devices. So the
question becomes, how do I let my data
leave the nest, but make sure that it stays
safe and protected?
THE TRADITIONAL
SERVICES LAYER
Services are the key
to securely unlocking
enterprise data on
mobile devices. We
used to call them web
services but now they
are known as APIs.
One of the difcult
things about services
is that they present
architectural challenges that are not easily
answered until you implement them. While
the services layer is a necessary abstraction,
its also an added level of complexity and
maintenance.
PAAS AND PRE-BUILT CONNECTIVITY
The future of productivity in building
connected mobile apps is not in creating
more services and acquiring
more technical debt. The future
is in leveraging the productivity
features that PaaS ofers, such as
pre-built connectors, to securely
expose enterprise data, thereby
allowing development teams to
concentrate on building world-
class applications.
For more information, please
visit: www.telerik.com/platform
MOBILITY AND LEAVING THE NEST
HOW DO I LET MY
DATA LEAVE THE
NEST, BUT MAKE
SURE THAT IT
STAYS SAFE AND
PROTECTED?
WRI TTEN BY
Burke Holland
Product Manager,
Telerik
TARGETS
STRENGTHS
CUSTOMER SUCCESS STORY
NOTABLE CUSTOMERS
DESCRIPTION
FREE TRIAL 30-day free trial
USES
Consumer Apps
Enterprise Apps (for internal use)
TWITTER @telerik PHONE (888) 365-2779
Includes a comprehensive mobile UI library
Supports all three development approaches: web, hybrid, and
native
Integrates with Apache Cordova
Addresses the entire lifecycle of the project (from design to
deployment)
Modular platform that can be integrated with other tools and
services
Telerik Platform is a cross-platform solution that
includes UI libraries for web, hybrid, and native
development as well as a suite of integrated cloud
services. It addresses the entire lifecycle of the app,
and integrates with any development environment.
With a focus on technology and service, Paylocity is constantly striving to offer the latest tools and solutions to make payroll and
HR processes easier. With the shift to a mobile-focused world, the company recognized the need for a mobile app that would
enable their ESS users to view and make changes to their accounts via any mobile device. With Telerik Platform, Paylocity was
able to create a secure cross-platform mobile app to serve its client-base of over 7000 organizations in less than 6 months.
Paylocity
Verizon
Ernst and Young
Symantec
HP
Microsoft
Telerik Platform BY TELERIK
A modular platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and
native apps.
FULL PROFILE LINK
dzone.com/r/ PLMa
Additional informationinthe vendor prole sectionof the guide
CATEGORY
MADP



Web
Hybrid
Native
TAGS -HOSTED- -MOBILE
MIDDLEWARE- -IDE- -VERSION MGMT--
-USAGE ANALYTICS-
22
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
MOBILE UX REFINING PERCEIVED PERFORMANCE
BY ANDREW TRICE
Performance is critical when you are building apps
for mobile devices. When using a device that is built
for accomplishing tasks quickly and on the go, like a
smartphone, performance is an even bigger concern
than on desktops. Being users ourselves, we all
understand this, but we also understand that users can't
see an app's network timelines or latency scores. The
user's perception of application performance depends
upon aesthetic design, feedback to the user, speed of
information, and much more. All they see is the user
experience you have crafted for them, so even if your
performance metrics are great, your apps can still feel
slow if you don't employ the right techniques in your
code. In many ways, perceived performance is more
important than actual performance. In this article, we're
going to focus on the user's perception of performance.
Lets rst examine two major use cases for mobile apps: accessing
information on the go, and entertainment. If you are accessing
information on the go, there is a good chance you are in a hurry
or youre on a limited-speed connection. You need the app to
give you the information you need as fast as possible. In the
case of entertainment, you just need the app to provide uid
interaction. In this case, performance is part of the entertainment
factor. In both of these cases, the apps performance is not simply
characterized by how fast the app is processing information
behind the scenes. Rather, this extends into the apps design and
system architecture.
INSTANT FEEDBACK
The most immediate factor of an apps performance actually
has nothing to do with raw processing power. User feedback, or
some sort of response to user input, is probably the most critical
factor to having an app that seems to perform well. If you touch a
button, that button should immediately provide feedback to the
user. If you swipe across the screen to drag an object, that object
should follow the users touch immediately.
Most native components will handle user feedback (ie: button
states) for you. However, if you are building a mobile web or
hybrid application, it is extremely important that you build in
some sort of user feedback to inform your users that their input
has been received and you are performing some sort of action.
The button press case is extremely basic, but if you have a user
interface that doesnt acknowledge the user input, then there is
no way for the user to know that the input has been received.
Regardless of whether or not this app is actually slow, the user
will perceive the app as being slow or buggy simply because
there is nothing to let the user know that their input has been
received and that the app is preparing a response.
LOADING ANIMATIONS
After youve tapped a button, does your app let the user know
that something is happening, or does the UI simply lock up until
the next piece of data is ready? If its possible (and in most cases,
it is), you should never lock up the user interface thread while
you are requesting data from a remote source. This is a major red
ag and users will immediately notice when the entire application
locks up and becomes unresponsive.

A better way of handling this would be to request data in a
background thread (so it does not lock up the UI) and present
the user with some sort of visual cue that an action is being
performed. By handling data in a background thread, the app
stays responsive and never feels like its freezing up. If youre
building a hybrid or mobile web app, dont worry; the browsers
XMLHttpRequest wont lock up your webviews UI, so this is less
of an issue.

Rather than just making your user wait until data is available
before changing views, you can change the user perception
and trick them into feeling that the app is faster by providing
some sort of feedback. It could be as simple as a spinner or a
progress bar, however, these have also been known to draw the
users attention to the fact that they are waiting. Alternatively,
you could create a loading view animation that slowly removes
the previous pages data or shows pieces of the new data as it is
loaded. Overall, you want to have some way of entertaining and
distracting the user while they wait. By engaging the user with
animation, you are changing the perceived performance and user
experience of the application, even if the loading time does not
actually change.
FAMILIAR NATIVE PHYSICS AND GESTURES
Buttons and animations are great for any form factor, but the
features that make mobile so convenient and elegant to use
have always been the touch controls. There is a common set of
interface physics and gestures that all popular mobile platforms
share, including momentum scrolling, side swipes, pull-to-refresh,
and multi-touch zooming controls.
Its important for app designers to harness these mobile-specic
controls wherever they can, and they need to be snappy.
Natively built apps dont have too many issues with these built-in
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
23
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
controls, but web and hybrid apps can have issues recreating this
functionality. Luckily, there are tools and CSS controls that can help.
For implementing momentum scrolling, you can use the overow-
scrolling: touch property on the container and then write some
JavaScript that only applies that class if the container is visible. The
JavaScript is necessary because that CSS property disables the
tap-the-top feature of mobile browsers that commonly sends you
back to the top of the page. For implementing gestures like pull-to-
refresh and zooming controls, there are plenty of great JavaScript
libraries that can help, such as Hook.js and Hammer.js.
HARNESS THE GPU
In many cases, youll use animations in your mobile apps, especially
in the loading instances mentioned above, but how do you make
sure those animations are uid and snappy? Obviously, stuttering
or choppy animations can be very problematic. They give the
user the feeling that the app is slow and buggy. This is one of the
major issues that people often complain about with HTML-based
applications. In native applications, this is less of an issue unless
you are doing something extremely complicated. Generally, native
animations are fast and smooth.

In HTML applications there are ways to make the app feel faster and
make animations smoother. Avoiding computationally-expensive
browser reow operations is critical for making uid animations.
Browser reow operations occur when your contents size changes,
or the position of your content changes, causing it to impact the
layout of neighboring DOM elements. If you change width, height,
or top/bottom/left/right styles of a DOM element, this will trigger
browser reow operations.
If you want to animate your content in HTML, you can use CSS
transitions or animations with the transform:translate3d (x,y,z)
style. This style forces rendering of your DOM content on the GPU
and can also be used to move or animate your content without
triggering those expensive browser reow operations. This
technique can be used to achieve solid 50-60 frames per second
animations in mobile web experiences. However, it is also important
to make sure that the DOM elements you are animating dont
exceed the GPU maximum texture size. Otherwise, you could end
up with an annoying icker in your animations, which completely
ruins the user experience.
PREEMPTIVE PERFORMANCE
Another technique that you can use to make your application feel
extremely fast is to preempt user actions before the user performs
them. For example, lets say you capture an image with your app.
You start uploading that image before the user has actually said
theyd like to upload the image. The user then enters a name and
description, and by the time the user hits the upload button the
image is already uploaded. Then, when the user does hit upload,
they will be amazed at how quickly the upload took place. This
is exactly what Instagram does in their app, and it is part of what
set Instagram apart from their competition early on. Preemption
doesnt work in every scenario. You dont want to aggressively load
data that may never be necessary, but it can work extremely well in
the cases where it does t.
ALL DECISIONS MUST CONSIDER UX
In a nutshell, perceived performance is really all about
understanding how the user experiences UI performance, not the
actual performance metrics. You need to consider how the end
user is going to be impacted by every technical and architectural
decision that you make. If there is ever a situation where the user
needs to wait, then give them feedback to let them know that the
app is still working. Request data during an animation sequence,
or play animations while the app is doing something else in the
background. Preempt data loading if you can. If you cant, then
you might want to consider lazy-loading your data. If youre
building a web app, let the GPU handle the UI in any way possible.
Regardless of the interaction, it is critical to develop your apps in a
fashion that tailors the experience to the users delight.transitions
or animations with the transform:translate3d (x,y,z) style. This style
forces rendering of your DOM content on the GPU and can also
be used to move or animate your content without triggering those
expensive browser reow operations. This technique can be used
to achieve solid 5060 frames per second animations in mobile web
experiences. However, it is also important to make sure that the
DOM elements you are animating dont exceed the GPU maximum
texture size. Otherwise, you could end up with an annoying icker in
your animations, which completely ruins the user experience.
W R I T T E N B Y
Andrew Trice
Andrew Trice is a Technical Evangelist with Adobe Systems.
He has more than a decade of experience designing,
implementing, and delivering rich applications for the
web, desktop, and mobile devices. He is an experienced
architect, team leader, accomplished speaker, and
published author, specializing in object-oriented
principles, mobile development, real-time data systems,
GIS, and data visualization.
Another technique that you can use to make your application feel
extremely fast is to preempt user actions before the user performs them.
This is exactly what Instagram does in their app, and it is part of what set
Instagram apart from their competition early on.
24
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
THE STEP-BY-STEP
MOBILE APPLICATION DEVELOPMENT CHECKLIST
GENERAL APP PLANNING
F Write a statement of purpose or elevator pitch for your
application.
F Gather expected user requirements (a survey of potential users
could be helpful).
F Gather business requirements for the application.
F Examine the potential competition for your app (business model,
strengths, weaknesses).
F Determine the IT resources required to support this application.
F Create a list of the core functionality for version 1.0 (Minimum
Viable Product).
F Make a whiteboard drawing of the architecture.
F Decide if your app will be a native, web, or hybrid app (or if you will
build multiple types).
F If your app is native or hybrid, determine the platforms for
distribution.
F Determine if you will build a different app for different form factors
(phone, tablet, TV, etc.).
F Decide on the development sourcing strategy (insourcing,
outsourcing, or co-sourcing).
F Identify the team members and stakeholders for this project along
with their responsibilities.
F Determine who will support the app when it's nished.
F Collaborate with team members to build a structured and
repeatable project calendar.
F Construct a marketing strategy in parallel with app development.
Execute pre-release marketing.
ENTERPRISE APP PLANNING
F Ask employees what they would like to have in a mobile app.
F Identify processes that could be handled more efciently with a
mobile app.
F Identify data that could be monitored more often with a mobile
app.
F Find out which systems mobile workers need to access frequently
(e.g. internal web portals).
F Ensure your enterprise mobile systems have fast data access using
authorized methods.
DESIGN AND DEVELOPMENT
F Harness design and development tools that will make your team
as efcient and effective as possible.
F Compile a list of objects and actions for the application and their
relation to each other.
F Reduce screen elements down to the bare essentials.
F Build wireframes for each screen in the app along with a navigation
map.
F Build a functioning prototype with MVP features.
F Do usability tests on the prototype, covering every item on your
user and business requirements lists.
SECURITY
F Decide if your app will use custom tokens or security standards
(e.g. SAML, OAuth).
F Determine if your app needs SSO for logging into multiple apps.
TESTING
F Prepare an appropriate on-device, real-time testing and debugging
strategy.
F Determine which devices you need to acquire, then integrate them
into the team's testing workflow.
F Have a plan for reacting quickly to issues on untested devices.
F Harness user simulation scripts and load testing tools to test user
and business requirements in high trafc conditions.
F Log and visualize all appropriate data for easy pinpointing of
problematic code.
F Ensure that your app meets the requirements for any target app
stores.
F Conduct private beta testing with all of your employees (not just IT).
F Conduct beta tests with real-world users. Try giving out gift cards at
a coffee shop to recruit testers.
LAUNCH
F Determine a build and deployment process that lets you deploy
updates early and often.
F Complete the tasks necessary for deployment to your target app
stores.
F For non-app store distribution, prepare an app server for wireless
distribution.
F Follow any platform requirements for non-app store distribution.
F Execute your marketing plans for launch.
F Monitor app performance and track new software bugs.
F Collect data on real-world usage and monitor feedback from
customers.
F Continue to improve the app according to a roadmap based on
customer behavior.
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
25
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
In this section of the guide you will nd proles of the most
promising mobile development platforms and frameworks
to help you develop mobile apps more efciently.
To view an extended prole of any product, you can use
the short-code link found at the bottom of each prole, or
simply go to dzone.com/research/mobile and enter in the
shortcode at the end of the link.
THE SOLUTIONS DIRECTORY
Get easy access to full product profiles with this URL
MADP
TAGS -JAVASCRIPT- -JAVA- -OBJECTIVE-C- -C#-- -MOBILE MIDDLEWARE-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @phonegap
FREE TRIAL Opensourcesolution
Allows developers to remotely build apps in the
cloud using PhoneGap Build
Can instantly update apps without recompiling
Features an App Store for building apps
without installing separate SDKs
Hundreds of plugins are available for accessing
native device APIs
Cordova/Phonegap
Android
iOS
Windows Phone
BlackBerry
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
PhoneGap lets you create native apps using HTML, CSS, and
JavaScript for iOS, Android, Windows Phone, and more.
Adobe Phonegap BY ADOBE
FULL PROFILE LINK
dzone.com/r/ vQ6x

Web
Hybrid
Native
TAGS -JAVASCRIPT- -ON-PREMISE- -HOSTED- -MOBILE MIDDLEWARE-- -IDE-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @alphaSWcorp
FREE TRIAL 30-dayfreetrial
Focus on front-end to back-end and
prototype-to-production development for
online and offline enterprise applications
Uses a single code base across all platforms,
and integrates with several existing databases
and web services
Offers a coding-optional approach to improve
developer productivity
Responsive application design for both mobile
and desktop
Cordova/Phonegap
Enterprise Apps (for
internal use)
STRENGTHS
Alpha Anywhere is a prototype-to-production environment to
develop and deploy enterprise-level, cross-platform mobile and
web business apps.
Alpha Anywhere BY ALPHA SOFTWARE
FULL PROFILE LINK
dzone.com/r/ xkYW

Web
Hybrid
Native
TAGS -JAVASCRIPT- -MOBILE MIDDLEWARE- -REST + SOAP- -IDE-- -OAUTH2-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @appcelerator
FREE TRIAL Opensourcesolution
Create rich native iOS, Android, hybrid,
and mobile web apps from a single
JavaScript-based SDK
Integrates with other Appcelerator tools such
as Studio, Alloy, and Cloud Services to simplify
the development process
Efcient code modules to reduce development
time by allowing users to write less code
Built to create apps that scale with business
needs
Android
iOS
Windows Phone
Blackberry
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
Build, test, package, and publish mobile apps using JavaScript
and a single code base, without managing multiple toolkits or
languages.
Appcelerator Titanium BY APPCELERATOR
FULL PROFILE LINK
dzone.com/r/ ysX9

Web
Hybrid
Native
26
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
MADP
TAGS -JAVASCRIPT- -HOSTED- -ON-PREMISE- -MOBILE MIDDLEWARE-- -IDE-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @apperyio
FREE TRIAL Full-featuredfreeversion
Visual, drag-and-drop UI builder for creating
HTML5, jQuery Mobile, and PhoneGap apps
Integrated backend services (database, push,
server code)
Connect to 3rd party APIs with visual data
binding editor
Integration with enterprise data via APIs, Web
Services, LDAP, or other custom data sources
Cordova/Phonegap
Android
iOS
Windows Phone
B2B Enterprise Apps
STRENGTHS
Accelerate enterprise mobile app development with Appery.io,
the cloud-based platform with visual development tools and
integrated mBaaS.
Appery.io BY EXADEL
FULL PROFILE LINK
dzone.com/r/ 7Quh

Web
Hybrid
Native
TAGS -JAVASCRIPT- -HOSTED- -MOBILE MIDDLEWARE- -IDE--
-USAGE ANALYTICS-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @appmachine
FREE TRIAL Freetouse, but cannot publishappswithout a
license
Designer uses a drag-and-drop building block
paradigm
Web design effort results in completely native
code output
Extensible via JavaScript and custom web
service integration
Built in CMS, analytics, and push notications
Web crawler allows users to use existing
materials and plugins from their site in their
AppMachine app
Android
iOS
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
AppMachine offers Apps-as-a-Service, a new code-free or
code-lite way to create custom mobile apps, both native and web.
AppMachine BY APPMACHINE
FULL PROFILE LINK
dzone.com/r/ jPGR

Web
Hybrid
Native
TAGS -JAVASCRIPT- -ON-PREMISE- -OAUTH2- -DRAG-N-DROP--
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @BlackBerryDev
FREE TRIAL Opensourcesolution
Built on open source Apache Cordova to
provide cross-platform capabilities
Allows developers to reuse current JavaScript
libraries or any public javascript libraries
Large network of supported developer tools,
making it easier for developers to migrate to
developing native BlackBerry apps
Allows developers to reuse many existing web
assets when porting to systems such as iOS and
Android
Cordova/Phonegap
Blackberry
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
Build cross-platform web apps with the BlackBerry 10 Webworks
SDK, now powered by Apache Cordova.
BlackBerry Webworks BY BLACKBERRY
FULL PROFILE LINK
dzone.com/r/ rCNp

Web
Hybrid
Native
TAGS -JAVASCRIPT- -JAVA- -BUG TRACKING- -HOSTED-- -ON-PREMISE-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @bridgeitmobi
FREE TRIAL Opensourcesolution
Allows native mobile browsers to access
hardware features such as the camera,
microphone, and contacts
No native application packaging or app store
submissions required to publish apps
Automatic installation triggers when a web app
uses BridgeIt
BridgeIt's Javascript API is open source and
available on GitHub
Android
iOS
Windows Phone
Blackberry
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
BridgeIt is a simple way to develop hybrid HTML5 apps that run
on cross-platform mobile devices. Write once, run everywhere for
mobile apps.
BridgeIt BY ICESOFT
FULL PROFILE LINK
dzone.com/r/ NLpH

Web
Hybrid
Native
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
27
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
MADP
TAGS -JAVASCRIPT- -JAVA- -C#- -IDE-- -VERSION MGMT-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @ClickSoftware
FREE TRIAL Nofreetrial
HTML5 and native mobile and Windows
desktop applications
Dynamic forms based on work type or role
A growing community enables downloads of
ready-to-use apps from the ClickAppStore
Inherited integration with backend ERP, CRM,
and asset management tools
Predictive intelligence built into apps
Cordova/Phonegap
Enterprise Apps (for
internal use)
STRENGTHS
ClickMobile provides visual tools that enable drag-and-drop
creation of forms, elds, workflows, and functionality to cover
business scenarios.
ClickMobile BY CLICK SOFTWARE
FULL PROFILE LINK
dzone.com/r/ MLaA

Web
Hybrid
Native
TAGS -C#- -ON-PREMISE- -DRAG-N-DROP-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @componentone
FREE TRIAL 30-dayfreetrial
Share code with Windows Store and WPF
controls to target multiple platforms
Data visualization controls include charts,
maps, and gauges
Allows for reporting with a PDF library and
viewer
Display and edit RTF and HTML natively in
XAML
Manage Microsoft Excel les with FlexGrid and
XLSX library
Windows Phone
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
Studio for Windows Phone includes 30+ UI controls with unique
functionality for building enterprise apps.
ComponentOne Studio BY COMPONENTONE
FULL PROFILE LINK
dzone.com/r/ HvQ4

Web
Hybrid
Native
TAGS -C/C++- -ON-PREMISE- -MOBILE MIDDLEWARE- -IDE-- -USAGE ANALYTICS-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @appmethod
FREE TRIAL 30-dayfreetrial, nocommercial deployment
Appmethod compiled apps run directly on the
CPU to improve speed and responsiveness
AppMethod uses high-performance, natively
compiled, object-oriented languages such as
C++ and Object Pascal
Includes an IDE with code editors, project
management, visual design, and integrated
debuggers
Appmethod's enterprise mobility services
provide point-and-click connectivity to RESTful
cloud services and enterprise databases
Android
iOS
Consumer Apps
Enterprise Apps (for
internal use)
B2B Enterprise Apps
STRENGTHS
Appmethod is an app development platform for building natively
compiled, multi-device apps with a single source codebase.
Appmethod BY EMBARCADERO
FULL PROFILE LINK
dzone.com/r/ GNRL

Web
Hybrid
Native
TAGS -HOSTED- -ON-PREMISE- -MOBILE MIDDLEWARE- -REST + SOAP--
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @IBMMobile
FREE TRIAL Opensource, but requiresalicensefor commer-
cial use
Integrates native, HTML5, and third-party code
in the same app
Command Line Interface allows the customer
to use familiar native and web tooling
Mobile middleware capabilities for native
applications, with device storage, advanced
analytics, security, and integration for
SOAP-based and SAP enterprise back-ends
Includes application development lifecycle
tools for design, testing, integration, security,
analytics, and user engagement
Cordova/Phonegap
Android
iOS
Windows Phone
Blackberry
Enterprise Apps (for
internal use)
B2B Enterprise Apps
STRENGTHS
IBM Worklight Studio is designed to provide an enterprise
environment for cross-platform mobile app development.
IBM Worklight BY IBM
FULL PROFILE LINK
dzone.com/r/ u4hy

Web
Hybrid
Native
28
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
MADP
TAGS -JAVASCRIPT- -JAVA- -ON-PREMISE- -MOBILE MIDDLEWARE-- -IDE-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @icefaces
FREE TRIAL Opensourceversionavailable
Automated device theming enables a single
web application to adopt the look of the native
mobile device it is viewed from
Extends the ICEfaces Ajax Push capabilities
with Cloud Push, leveraging native platform
push capabilities to deliver notications even
when the application is not active
Extends the ICEfaces framework with a suite of
mobile controls for UI development
Android
iOS
Windows Phone
Blackberry
Enterprise Apps (for
internal use)
STRENGTHS
ICEmobile is an easy and cost-effective way to mobilize Java EE
web applications. Go beyond HTML5.
ICEmobile BY ICESOFT
FULL PROFILE LINK
dzone.com/r/ hkyX

Web
Hybrid
Native
TAGS -C#- -HOSTED- -ON-PREMISE- -REST-- -OAUTH2-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @iFactr
FREE TRIAL Opensourcesolutionavailable
Designed to support the latest native and
HTML5 technologies so applications can easily
be updated for new devices
Keeps mission-critical data in sync without
proprietary middleware, either online or
offline
Includes a coding-optional UI prototyping tool
Supports hosted and on-premise
environments
Android
iOS
Windows Phone
Enterprise Apps (for
internal use)
STRENGTHS
iFactr specializes in bringing legacy mobility to modern consumer
grade devices.
iFactr Enterprise Platform BY IFACTR
FULL PROFILE LINK
dzone.com/r/ Qh4k

Web
Hybrid
Native
TAGS -JAVASCRIPT- -JAVA- -OBJECTIVE-C- -C#-- -IDE-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @infragistics
FREE TRIAL Unlimitedfreetrial
Full-featured data visualization controls
including charts, maps, and gauges which
are used to create any type of interactive
dashboard and analytics apps
Automatic adaptive CSS styling on mobile
devices
Responsive web design built into data grids,
charts, and other controls
Native UI controls with the same data
visualization feature-set in Objective-C,
Android, and C#
Android
iOS
Windows Phone
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
An enterprise ready toolset for hybrid and native apps running on
desktop, mobile, or the web.
Infragistics Ultimate BY INFRAGISTICS
FULL PROFILE LINK
dzone.com/r/ HuQ4

Web
Hybrid
Native
TAGS -JAVASCRIPT- -ON-PREMISE- -IDE- -REST-- -SOAP-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @intel
FREE TRIAL Freesolution
XDK's interface is built on HTML, CSS,
JavaScript, and a Node-Webkit back-end
Integrated with design, test, and build tools to
improve productivity
Includes theme templates and a UI designer
Able to deploy apps across a variety of app
stores and form factors
Includes an emulator debugger, JS debugger,
and JS remote debugger for Android devices
Android
iOS
Windows Phone
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
The Intel XDK includes built-in tools that let you design HTML5
responsive apps, as well as app performance tools.
Intel XDK BY INTEL
FULL PROFILE LINK
dzone.com/r/ X39z

Web
Hybrid
Native
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
29
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
MADP
TAGS -JAVASCRIPT- -JAVA- -OBJECTIVE-C- -REST + SOAP--
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @kofax
FREE TRIAL Requirestheapproval of anEval License
Delivers many mobile capture and
engagement use cases from a single open
platform under full customer control
Real-time data extraction, validation, and
entry, eliminating the need for tedious manual
entry
Captures and improves image lighting, blur,
jitter, optics, background, and document size
Automatic correction of data
Cordova/Phonegap
Android
iOS
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
With the Kofax Mobile SDK, apps can be enhanced with
functionality for processes such as mobile deposit, mobile bill
pay, and more.
Kofax Mobile Capture BY KOFAX
FULL PROFILE LINK
dzone.com/r/ v46x

Web
Hybrid
Native
TAGS -JAVASCRIPT- -HOSTED- -ON-PREMISE- -MOBILE MIDDLEWARE-- -IDE-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @kony
FREE TRIAL 90-dayfreetrial
Open and standards-based platform
Customer has several choices for the
deployment model
Connect with any enterprise or third-party
system to mobilize and orchestrate your data
Transition from design to development and
back using the bi-directional integration with
Kony Development Cloud
Choose from hundreds of cloud-based APIs
spanning UX/UI, device features, utilities,
security, and i18n
Android
iOS
Windows Phone
Blackberry
Enterprise Apps (for
internal use)
STRENGTHS
An integrated platform that helps users dene, design, develop,
deploy, and manage multi-channel cloud-connected app
experiences.
Kony Development Cloud BY KONY
FULL PROFILE LINK
dzone.com/r/ kWs3

Web
Hybrid
Native
TAGS -ON-PREMISE- -MOBILE MIDDLEWARE- -IDE- -VERSION MGMT--
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @runrev
FREE TRIAL Freecommunityeditionavailable
Offers unique always on coding which has no
compile step, leading to an iterative process
Run the same code on Mac, Windows, Linux,
iOS, Android, and servers
Code in natural language without arcane
symbols
Self documenting, making it easy to read and
remember the meaning of written code
Uses a drag-and-drop development paradigm
Android
iOS
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
Always on coding. No compile step. Iterative and cross platform,
with natural language programming for desktop and mobile.
LiveCode Commercial BY RUNREV
FULL PROFILE LINK
dzone.com/r/ 9jzr

Web
Hybrid
Native
TAGS -JAVASCRIPT- -JAVA- -MOBILE MIDDLEWARE- -IDE-- -VERSION MGMT-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @MendixSocial
FREE TRIAL Communityeditionavailable-freeupto10users
Models are interpreted at run-time, which
supports rapid change cycles
Unique approach to business and IT
collaboration for full app delivery cycle
Single-click deployment of apps in the cloud or
on-premise
Launchpad for unied end user access to
apps connected to the Mendix App Store or
corporate app store
No-strings Community Edition to build and
deploy apps for up to 10 users for free
Cordova/Phonegap
Enterprise Apps (for
internal use)
STRENGTHS
Mobile isn't an island. Build once, use anywhere with Mendix - a
platform to build, integrate, and deploy multi-channel enterprise
apps.
Mendix App Platform BY MENDIX
FULL PROFILE LINK
dzone.com/r/ W3wd

Web
Hybrid
Native
30
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
MADP
TAGS -JAVA- -OBJECTIVE-C- -PERFORMANCE ANALYTICS- -VERSION MGMT--
-USAGE ANALYTICS-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @MicroStrategy
FREE TRIAL 10nameduser licenses
Code free, click-to-congure development
Build once and deploy across iOS and Android
devices
Enables pre-caching, transactions, and
multimedia
Integration with Sharepoint and WebDAV
environments
Pre-built infrastructure with security,
scalability, and performance
Provides a wide array of app performance and
usage analytics
Android
iOS
Blackberry
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
MicroStrategy's code-free app platform helps enterprises create
iOS and Android apps that make your workforce mobile.
MicroStrategy Mobile BY MICROSTRATEGY
FULL PROFILE LINK
dzone.com/r/ fzVb

Web
Hybrid
Native
TAGS -JAVASCRIPT- -JAVA- -MOBILE MIDDLEWARE- -IDE-- -REST + SOAP-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @OracleMiddle
FREE TRIAL Nolimitstofreetrial, licenserequiredtodeploy
apps
Complete end-to-end multichannel-support
for mobile and traditional web, as well as social
Supports native, hybrid, and mobile web
architectures
HTML5, JavaScript, and Java MVC framework
for cross-platform mobile client application
development
Modular and reusable
Integrated security with full mobile app
management
Android
iOS
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
Oracle Mobile Platform is a flexible product for building a variety
of apps securely for multiple devices with a variety of data
integrations.
Oracle Mobile Platform BY ORACLE
FULL PROFILE LINK
dzone.com/r/ uUhy

Web
Hybrid
Native
TAGS -JAVASCRIPT- -JAVA- -IDE- -VERSION MGMT-- -USAGE ANALYTICS-
-HOSTED- -REST + SOAP-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @outsystems
FREE TRIAL Freeversionfor individual users, noALMor
stagingcapabilities
Create once for all devices utilizing responsive
web design
True no lock-in: customers can detach onto
industry-standard application stacks with
open Java or C# code; no proprietary runtime
Can use flexible deployment scenarios from
on-premises to public, private , or hybrid cloud
Allows creation of more complex systems,
including those using large volumes of data
and non-trivial workflows
Not just for building single-function apps
Cordova/Phonegap
Enterprise Apps (for
internal use)
STRENGTHS
OutSystems Platform empowers developers to create, deploy, and
manage amazing mobile and web applications more efciently
with current skills
OutSystems Platform BY OUTSYSTEMS
FULL PROFILE LINK
dzone.com/r/ GMRL

Web
Hybrid
Native
TAGS -JAVASCRIPT- -JAVA- -OBJECTIVE-C- -MOBILE MIDDLEWARE-- -IDE-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @AntennaSoftware
FREE TRIAL Nofreetrial
Offline functionality via store-and-forward
messaging and data synchronization
Comprehensive app and device management
through an integrated, centralized dashboard
Enterprise integration streamlined through a
mobile middleware layer with precongured
adapters for most enterprise backends
Integrated with the BPM, case management,
and decisioning systems from Pegasystems,
providing the choice of model-driven or
code-based development
Cordova/Phonegap
Android
iOS
Windows Phone
Blackberry
Enterprise Apps (for
internal use)
STRENGTHS
Antenna Software enables enterprises to build, run, and manage
mobile apps to optimize crucial business processes from the eld
to the front ofce.
Pega AMP BY PEGASYSTEMS
FULL PROFILE LINK
dzone.com/r/ TQv6

Web
Hybrid
Native
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
31
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
MADP MADP
TAGS -JAVASCRIPT- -ON-PREMISE- -REST-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @DXPhoneJS
FREE TRIAL 30-dayfreetrial
Provides a native UX through hybrid apps
Comprehensive set of touch-optimized
widgets
Device-optimized kinetic scroller
SPA view management
View caching and state management
Provides data access layers
Supports jQuery and optionally supports
Knockout.js for MVVM user interface
development
Cordova/Phonegap
Enterprise Apps (for
internal use)
STRENGTHS
PhoneJS, part of DevExtreme, allows developers to create native
applications using HTML5 and JS with a single codebase from
within Visual Studio.
PhoneJS BY DEVEXPRESS
FULL PROFILE LINK
dzone.com/r/ dCPM

Web
Hybrid
Native
TAGS -JAVASCRIPT- -MOBILE MIDDLEWARE- -USAGE ANALYTICS-
-PERFORMANCE ANALYTICS-- -REST + SOAP-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @progresssw
FREE TRIAL 30-dayfreetrial
Easily meet the web and mobility requirements
of your users
Easily assemble, manage, and deploy web and
mobile apps: powerful applications at low cost
Leverage multiple data sources with Progress
data integration for web and mobile apps
Deliver powerful native apps without writing
device specic code
Rich PaaS support for all your web/mobile or
mobile-only apps
Android
iOS
Enterprise Apps (for
internal use)
STRENGTHS
Rapidly develop & deploy business apps using the mobile,
data integration, self-service, and collaboration capabilities of
Progress Pacic.
Progress Pacic BY PROGRESS SOFTWARE
FULL PROFILE LINK
dzone.com/r/ xsYW

Web
Hybrid
Native
TAGS -HOSTED- -IDE- -VERSION MGMT- -IDE-- -REST + SOAP- -SSO
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @salesforce
FREE TRIAL 30-dayfreetrial andfreedevaccounts
Over 2K third-party apps built on the
Salesforce1 Platform
Private AppExchange allows companies to
build a customized corporate app store
AppExchange Accelerate Program fuels the
next wave of enterprise ISVs on the Salesforce1
Platform
Integrated JavaScript framework support,
including Angular, Backbone, and Polymer.
Salesforce1 Mobile app container makes it easy
to distribute enterprise apps securely
Android
iOS
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
Salesforce1 Platform combines its popular PaaS with a
declarative app builder that allows users to visually create mobile
apps.
Salesforce1 Platform BY SALESFORCE
FULL PROFILE LINK
dzone.com/r/ Y3Ww

Web
Hybrid
Native
TAGS -HOSTED- -ON-PREMISE- -MOBILE MIDDLEWARE- -IDE-- -SSO-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @SAPMobile
FREE TRIAL 30days, unlessusingSAPHANAor if theuser
runsanon-premiseversionthroughtheir AWSaccount
Open OSGi architecture
Uses Apache Cordova and its standard (but
extended) plug-in architecture
Uses SAP-provided SDKs and IDEs or the
technology of your choice (XCode, jQuery,
Sencha, Xamarin)
No more proprietary hybrid web container
Replaces several proprietary technologies with
open source technologies
Android
iOS
Windows Phone
Blackberry
Consumer Apps
Enterprise Apps (for
internal use)
Partner Apps (B2B)
STRENGTHS
SAP provides an integrated platform to help developers build
any-device apps that can run on-premise and in the cloud.
SAP Mobile Platform BY SAP
FULL PROFILE LINK
dzone.com/r/ wbdP

Web
Hybrid
Native
32
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
MADP
TAGS -JAVASCRIPT- -ON-PREMISE- -SSO- -REST + SOAP-- -DRAG-N-DROP-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @sencha
FREE TRIAL 30-dayfreetrial
Large selection of out-of-the-box UI widgets
and data sources
UI Themes for iOS, Android, Windows Phone,
BlackBerry, and Tizen
Utilizes hardware acceleration to improve app
performance
History, back button, and deep linking
capabilities
Integrated solutions for native packaging and
device features
Integrates with Sencha Cmd to provide
deployment and development tools
Cordova/Phonegap
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
Sencha Architect, a visual app builder, provides a way for devs to
build cross-platform, HTML5 apps for the web and mobile.
Sencha Architect BY SENCHA
FULL PROFILE LINK
dzone.com/r/ 9bzr

Web
Hybrid
Native
TAGS -JAVASCRIPT- -ON-PREMISE- -IDE- -REST + SOAP-- -DRAG-N-DROP-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @smartface_io
FREE TRIAL Freecommunityeditionavailable
Design editor lets users see what they are
building as they build it
Provides native outputs for iOS and Android
Integrates with Sencha Cmd and Touch to
package for the web or native mobile apps
On-device debugging allows users to plug in
devices via usb to test and debug in real time
Android
iOS
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
A software solution that enables users to develop iOS and
Android native applications that can be published to their
marketplaces.
Smartface App Studio BY SMARTFACE.IO
FULL PROFILE LINK
dzone.com/r/ zCrN

Web
Hybrid
Native
TAGS -HOSTED- -MOBILE MIDDLEWARE- -IDE- -VERSION MGMT--
-USAGE ANALYTICS-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @telerik
FREE TRIAL 30-dayfreetrial
Includes a comprehensive mobile UI library
Supports all three development approaches:
web, hybrid, and native
Integrates with Apache Cordova
Addresses the entire lifecycle of the project
(from design to deployment)
Modular platform that can be integrated with
other tools and services
Cordova/Phonegap
Android
iOS
Windows Phone
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
A modular platform that combines a rich set of UI tools with
powerful cloud services to develop web, hybrid and native apps
Telerik Platform BY TELERIK
FULL PROFILE LINK
dzone.com/r/ PLMa

Web
Hybrid
Native
TAGS -HOSTED- -ON-PREMISE- -MOBILE MIDDLEWARE- -REST + SOAP--
-OAUTH2-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @verivosoftware
FREE TRIAL No-cost evaluation
Works with any device-side IDE, framework, or
app architecture
Comprehensive offline capabilities,
including incremental data sync and online
authentication
Authentication, authorization, and encryption
are used to secure apps
Open architecture integrates with top tools
and frameworks
Enables code reuse across multiple projects
Cordova/Phonegap
Android
iOS
Windows Phone
Enterprise Apps (for
internal use)
STRENGTHS
Verivo Akula is an enterprise-grade platform for building mobile
apps that helps IT to ensure proper corporate governance across
all their apps.
Verivo Akula BY VERIVO
FULL PROFILE LINK
dzone.com/r/ H6Q4

Web
Hybrid
Native
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
33
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
MADP & FRAMEWORKS
TAGS -JAVASCRIPT- -HOSTED- -ON-PREMISE- -REST--
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @wijmo
FREE TRIAL 30-dayfreetrial
The Adaptive Widget Framework allows
the widgets to work in a desktop or mobile
environment
Seamless integration with popular frameworks
like AngularJS, Knockout.js, Breeze, and more
A high performance DataGrid that supports UI
virtualization
Data visualization controls that offer touch
interaction on mobile devices
An Event Calendar Control that offers full
scheduling capability out-of-the-box
Cordova/Phonegap
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
Wijmo is a suite of UI Controls for mobile and web application
development. It offers enterprise charts and grids powered by
HTML5.
Wijmo BY COMPONENTONE
FULL PROFILE LINK
dzone.com/r/ thUJ

Web
Hybrid
Native
TAGS -HOSTED- -ON-PREMISE- -IDE- -REST + SOAP-- -OAUTH2-
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @WSO2
FREE TRIAL Opensourcesolution
Self-service provisioning of workspaces
including source repository, issue tracker, and
build conguration
Automate and integrate continuous build,
continuous test, and continuous deployment
activities
Perform one-click actions for code branching,
versioning, and promotion
Dashboards display application status, health,
service assets, activity, and lifecycle stage
Cordova/Phonegap
Enterprise Apps (for
internal use)
STRENGTHS
An open source mobile application lifecycle management tool
that manages the creation and delivery of the app to the device.
WSO2 App Factory BY WSO2
FULL PROFILE LINK
dzone.com/r/ Qx4k

Web
Hybrid
Native
TAGS -C#- -F#- -IDE- -REST + SOAP--
TARGETS
SYSTEMS
USES
CATEGORY MADP TWITTER @xamarinhq
FREE TRIAL 30-dayfreetrial, but cannot shipapps
Enables fully native iOS, Android, and Windows
mobile apps with a shared codebase
Allows developers to build native apps in Visual
Studio
.NET mobility scanner scans code to determine
how much can be mobilized
Component store offers hundreds of libraries,
cloud services, and UI controls
Xamarin Test Cloud tests apps using
object-level user interface testing
Android
iOS
Windows Phone
Consumer Apps
Enterprise Apps (for
internal use)
STRENGTHS
Reuse your favorite .NET libraries, and still incorporate
platform-specic libraries and frameworks when you want to.
Xamarin BY XAMARIN
FULL PROFILE LINK
dzone.com/r/ UWJf

Web
Hybrid
Native
TAGS -RESPONSIVE LAYOUT- -ADAPTIVE LAYOUT- -CORDOVA- -MVC--
-OPEN SOURCE-
BROWSER SUPPORT
IDEs SUPPORTED
LAYOUT STYLE
CATEGORY MobileWebFramework TWITTER @kendoui
FREE TRIAL Opensourcesolution
Complete set of HTML5 widgets and features
UI tools for ASP.NET, PHP, and JSP available
Provides a high-performance MVVM
framework that uses declarative bindings and
two-way syncing between web and mobile
views and models
Lightweight, built-in templating library
Animations take advantage of CSS3 hardware
acceleration
Eclipse
App-centric(navigation, layouts,
workflow, tryingtobelikea
nativeapp)
STRENGTHS
A large open source jQuery library, featuring over 24 UI controls, a
complete mobile solution, and professional grade widgets.
KendoUI BY TELERIK
FULL PROFILE LINK
dzone.com/r/ 9Gzr
WebKit
Firefox
34
2 01 4 GUI DE TO MOBI L E DEVELOPMENT
dzone. com/research/mobi l e
FRAMEWORKS
TAGS -ADAPTIVE LAYOUT- -NATIVE PACKAGER- -MVC- -EXT JS--
BROWSER SUPPORT
IDEs SUPPORTED
LAYOUT STYLE
CATEGORY MobileWebFramework TWITTER @senchatouch
FREE TRIAL 30-dayfreetrial
Integrates with Sencha Space, Architect, and
Cmd to provide deployment, development,
and native packaging tools
Utilizes hardware acceleration to improve
performance of apps
History, back button, and deep linking
capabilities
UI Themes for iOS, Android, Windows Phone,
BlackBerry, and Tizen
Eclipse
App-centric(navigation, layouts,
workflow, tryingtobelikea
nativeapp)
STRENGTHS
Sencha Touch is an HTML5 mobile application framework that
enables devs to build cross-platform user experiences.
Sencha Touch BY SENCHA
FULL PROFILE LINK
dzone.com/r/ YsWw
WebKit
Windows Phone
Firefox
TAGS -CORDOVA- -MVC- -ADAPTIVE LAYOUT-
-RESPONSIVE LAYOUT-- -OPEN SOURCE-
BROWSER SUPPORT
IDEs SUPPORTED
LAYOUT STYLE
CATEGORY MobileWebFramework TWITTER @dojo
FREE TRIAL Opensourcesolution
Offers a UI widget collection, Dijit, and 2D
graphics framework GFX
Has an extensive collection of UI components
for mobile devices
Object stores for easy binding of data between
UI widgets and data sources
No compiling step necessary for web and
mobile web applications
Highly optimized events, DOM, and HTTP
requests/WebSockets
Eclipse
WebStorm
App-centric(navigation, layouts,
workflow, tryingtobelikea
nativeapp)
STRENGTHS
Dojo is a JavaScript and HTML5 toolkit for building high quality,
standards-based desktop and mobile web apps.
Dojo Toolkit BY DOJO FOUNDATION
FULL PROFILE LINK
dzone.com/r/ JWfV
WebKit
Windows Phone
Blackberry
TAGS -CORDOVA- -ADAPTIVE LAYOUT- -RESPONSIVE LAYOUT- -OPEN SOURCE--
BROWSER SUPPORT
IDEs SUPPORTED
LAYOUT STYLE
CATEGORY MobileWebFramework TWITTER @jquerymobile
FREE TRIAL Opensourcesolution
Includes ThemeRoller software for users to
create device-agnostic custom themes for
their apps
Ajax navigation with many different page
transitions
Platform and screen-agnostic UI widgets
Graded browser support (mobile and desktop)
Flexibility to choose between auto-
enhancement via data attributes or write
markup to reduce DOM manipulation and
improve performance
Eclipse
Visual Studio
NetBeans
IntelliJ IDEA
Content-centric(flat content,
interactiveelements)
STRENGTHS
jQuery Mobile is a cross-platform framework, built on jQuery and
the jQuery UI foundation.
jQuery Mobile BY JQUERY FOUNDATION
FULL PROFILE LINK
dzone.com/r/ 3zjG
WebKit
Windows Phone
Firefox
Opera Mobile
Amazon Silk
TAGS -ANGULARJS- -CORDOVA- -OPEN SOURCE-
-ADAPTIVE LAYOUT-- -RESPONSIVE LAYOUT-
BROWSER SUPPORT
IDEs SUPPORTED
LAYOUT STYLE
CATEGORY MobileWebFramework TWITTER @ionicframework
FREE TRIAL Opensourcesolution
Extensive library of simple, native-style UI
components and layouts
Support for a wide array of touch gestures
Complex navigation capabilities, allowing for
non-linear navigation instead of linear browser
history
Utilizes hardware acceleration and minimal
DOM manipulation to improve app
performance
Integrates with AngularJS to utilize more tools
and frameworks for mobile development
None
App-centric(navigation, layouts,
workflow, tryingtobelikea
nativeapp)
STRENGTHS
Ionic is an open source HTML5 mobile app dev framework based
on AngularJS that lets web developers build native-quality
mobile apps.
Ionic Framework BY DRIFTY
FULL PROFILE LINK
dzone.com/r/ jrGR
WebKit
Firefox
2 0 1 4 G U I D E T O MO B I L E D E V E L O P ME N T
35
dzone.com/research/mobile
|
dzone.com
|
research@dzone.com
|
(919) 678-0300
A
ACCELEROMETER - A sensor that measures
the acceleration (change in speed) of an
object.
ADAPTIVE LAYOUT - A website layout
that uses media queries to change the sites
design for specied devices or window
sizes. This is a more manual strategy than
responsive design.
API (APPLICATION PROGRAMMING
INTERFACE) - A specication for how
various applications can interact with a
set of software components. Applications
can include APIs for external use by other
software.
APPCACHE - An HTML5 standard that allows
a web application to be cached and available
ofine.
B
BUSINESS-TO-CUSTOMER (B2C) - An
application built for the average consumer.

BUSINESS-TO-BUSINESS (B2B) - An
application built specically for use within
another business.
BUSINESS-TO-EMPLOYEE (B2E) - An
application for internal business use (i.e. an
enterprise app).
D
DEVICE API - A mobile platform-specic API
that lets applications access specic mobile
hardware functionality (e.g. accelerometer,
gyroscope).
E
EMULATOR - An application that duplicates
the functionality of hardware or operating
systems for testing purposes.
F
FEATURE PHONE - A mobile phone with
internet access and music playback that lacks
the full functionality of a smartphone.
G
GYROSCOPE - An instrument that measures
the orientation of a device.
H
HTML5 - A specication that denes the
fth major revision of HTML. It is often
used as an adjective to describe web apps
that use newer HTML, CSS, and JavaScript
specications (e.g. HTML5 apps).
HYBRID APP - A mobile application written
in HTML, CSS, and JavaScript that uses a
web-to-native abstraction layer, allowing the
application to access mobile device APIs that
pure web applications cannot access.
M
MADP (MOBILE APPLICATION
DEVELOPMENT PLATFORM) - MADPs are
development tools, sometimes including a
mobile middleware server, that build hybrid
or native apps for each platform using one
codebase. Includes MEAPs and MCAPs.
MBAAS (MOBILE BACK-END-AS-A-
SERVICE) - A service that connects mobile
applications to cloud databases while
also providing user management, push
notications, and social integrations.
MCAP (MOBILE CONSUMER APPLICATION
PLATFORMS) - A platform for developing
mobile consumer apps.
MEAP (MOBILE ENTERPRISE
APPLICATION PLATFORMS) - A platform
for developing mobile enterprise apps.
MOBILE MIDDLEWARE - Technology that
provides application management functions
that allow native and hybrid applications to
communicate securely with on-premise and
cloud-based enterprise applications.
MVP (MINIMUM VIABLE PRODUCT) -
A version of a product with only the features
that are absolutely necessary to go to market.
N
NATIVE APP - A mobile application that is
written in a programming language that is
directly compatible with the target platform.
NATIVE BRIDGE - An abstraction layer that
gives a non-native application access to
mobile device APIs.
NATIVE PACKAGER - A tool that builds a
native wrapper and native bridge around a
mobile application written in HTML, CSS, and
JavaScript, creating a hybrid app.
NATIVE WRAPPER - A component that
packages a non-native app so that it is viable
for native app store distribution.
NFC (NEAR-FIELD COMMUNICATIONS)
- A feature, based on technical standards,
that allows devices to establish radio
communication with other nearby systems or
mobile devices.
O
OAUTH - A common open standard for
authorization.
P
PUSH NOTIFICATIONS - Short messages
that mobile applications can send to users
even if the application isnt open.
R
RESPONSIVE LAYOUT - A website layout
based on a uid grid, allowing the site to have
hundreds of dynamically generated states
with mostly minor diferences based on
browser window size. A less manual strategy
than adaptive layouts.
S
SAAS (SOFTWARE-AS-A-SERVICE) - An
application provided over a network by the
vendor with no installation required.
SAML (SECURITY ASSERTION MARKUP
LANGUAGE) - A common XML-based open
data format for authentication.
SDK (SOFTWARE DEVELOPMENT KIT) - A
set of programming tools and resources built
specically to aid software development on a
particular platform or technology.
SOA (SERVICE-ORIENTED ARCHITECTURE)
- A software design pattern where pieces
of software provide functionality to other
applications as a service.
SSO (SINGLE SIGN-ON) - A feature for
access control systems that allows users
to log in to multiple, independent software
systems using one set of credentials by
internally storing and automating multiple
login credentials.
SMS (SIMPLE MESSAGE SERVICE) - A phone
service using standardized communication
protocols to send short text messages.
U
USER EXPERIENCE (UX) - A term to describe
all aspects of the end users interaction with
an application.
V
VIEWPORT - An HTML meta tag that tells the
browser how to behave when it renders the
web page. The viewport is also a term for the
section of the web page in view.
W
W3C (WORLD WIDE WEB CONSORTIUM) -
The main international standards organization
for the World Wide Web, developing
common web language specications such as
HTML5 and XML.
WEBVIEW - A view that displays web pages
within an application.
GLOSSARY OF TERMS
2008-14 New Relic, Inc. All rights reserved.
Speed up your app today
www.newrelic.com/mobile-monitoring
Slow mobile apps
can kill your business.
New Relic Mobile is a SaaS performance
tool that gives you code-level visibility
into your mobile software so you can
pinpoint problems and solve issues
before they afect your users.
Apps using New Relic Mobile right now
C
M
Y
CM
MY
CY
CMY
K
NewRelic-Ad.pdf 1 5/16/14 4:35 PM

You might also like