Beruflich Dokumente
Kultur Dokumente
Prepare
Assess
Mobile
IT
capability
and
ini?ate
lifecycle
Iden?fy
and
engage
stakeholders
Select
and
provide
guidance
to
developers
Develop
Dene
architecture,
security
and
compliance
standards
Establish
approved
methods
for
access
to
enterprise
systems
Provide
guidance
on
data
and
content
management
Roll-out
Develop
Mobile
App
Policy
Sustain
Implement and op?mize groups, policies and Create and manage opera?ons accounts Deploy self- service tools Plan distribu?on groups Create trouble- shoo?ng guides Set up metrics Create user communica?ons Automate maintenance and service ac?vi?es
The first two phases of the lifecycle focus on app development and are referred to as Mobile App Development. The last two phases, which focus on deployment and management, are referred to as Mobile App Management. Mobile App Development Mobile app projects are often initiated within business units such as sales and marketing. The first two areas where apps are often developed are in field service organizations and product teams. It is important to distinguish the differences between apps developed for public use and apps that are created for in-house use. Most companies have different workflows, lifecycles, and processes for public facing vs. enterprise apps. Many public apps are currently developed and published without IT based on existing marketing and branding programs that exist around product lines. In cases where mobile consumer apps are an extension of existing campaigns, IT may have little need or desire to be involved in the public app process. For public apps that fall within the purview of established marketing campaigns, mobile devices are another delivery channel in addition to media and web properties. Since most of the content delivered through the mobile app follows the same compliance, regulatory and disclosure requirements as existing channels, the content can be reused under the governance of existing information that has previously been vetted with legal and compliance organizations. Only if new content is developed for
2012 MobileIron
P a g e | 2
2012 MobileIron
P a g e | 3
Source
code
agreements
Intellectual
property
Support
and
Maintenance
Non-disclosure
Digital
Certificate
Use
Use of third party developers Digital rights Upgrades Reuse of code, code sharing
Mature organizations have standardized methods for accessing enterprise resources through mobile apps. Mobile IT can help app sponsors significantly accelerate development time by making enterprise-specific libraries and APIs that define authentication, data protection and security methods available to their selected developers. Developers use the libraries and enterprise tools to shorten development cycles and save valuable time during future security and compliance reviews as well as during connectivity and integration testing. Select App Architecture The app platform (or mobile OS) and architecture selected impacts the cost, scope, timeframe, maintenance, and, most importantly, end user experience with the app. Although selection is dependent on the scope, feature set, and function of the app, some general guidelines and decision choices are described below. Most enterprises have standardized on iOS as the enterprise mobile app platform. This decision was based on the early dominance of iOS in the enterprise today. Since Android continues to emerges as 2012 MobileIron P a g e | 4
Native apps: These apps are built to run exclusively on the device and are self- contained binaries that are installed and reside in local storage. Native apps are ideal for high performance, optimal user experience requirements. Also, native apps have the highest level of integration with on-board hardware and device capabilities. The downside is that they are more expensive and time consuming to develop and need to be built individually for each mobile platform. Web apps: For fast development at a low cost, web apps allow developers to reach the widest audience with a common set of tools and source code. Some customization is possible to address a variety of device capabilities but there are some drawbacks. Off-line use is not possible and the user experience is not as rich as with native or hybrid apps. The level of access to hardware capabilities is limited. With the evolution of HTML5 capabilities and greater integration with web to hardware interfaces, web apps are quickly becoming the preferred architecture platform for many developers.
2012 MobileIron
P a g e | 5
Content
Management
System
(CMS)
Many
first
generation
apps
have
embedded
rich
media
content
within
the
app,
often
causing
the
app
to
grow
very
large
in
size.
By
developing
apps
with
advanced
content
delivery
and
management
systems,
developers
are
able
to
reduce
the
size
of
the
app
by
installing
a
shell
that
downloads,
synchronizes,
and
manages
the
content
with
a
CMS.
For
many
companies,
the
initial
business
case
for
deploying
tablets
was
to
replace
workflows
that
involved
the
distribution
and
management
of
large
volumes
of
printed
documents.
Migrating
documents
into
an
app
or
synchronizing
them
manually
quickly
became
difficult
to
manage
and
maintain,
especially
where
documents
needed
to
be
updated
or
modified,
often
for
compliance
purposes.
The
use
of
a
CMS
allows
companies
to
make
the
model
scalable,
sustainable
and
cost
effective
while
delivering
a
superior
user
experience.
CMS
Benefits
Initial app download size and times are greatly reduced. Content is available offline use. Content can be managed for compliance purposes. Content is delivered intelligently, downloading only what the user needs. Content can be managed by user or group membership. Content can be tracked for audit purposes. Content can be optimized and delivered efficiently.
2012 MobileIron
P a g e | 6
2012 MobileIron
P a g e | 8
FAQs
Self-Service
Guides
Training
and
Education
o Online
o Classroom
o Documents
and
User
Guides
o Help
Desk
training
Shared
responsibility
model
User
Agreement
Compliance
remediation
o Notification
o Self-remediation
guide
Sustain The last phase of the App Lifecycle is the Sustain phase where the app is in production and the role of Mobile IT is to support, maintain, upgrade and eventually retire the app. Important tools for day-to-day operations for administrators can be categorized into app control policy and management, app distribution management, and app upgrades and maintenance. App Control and Distribution App Control Policy and Management includes functions such as whitelisting, blacklisting, making apps required or recommended, and the compliance actions taken when devices fall out of compliance with corporate policy. Since every app cannot be reviewed for appropriate use, users will need to be educated on corporate policy along with the reasons for disallowed apps so that they can make an educated judgment when new apps become available. Also, certain apps may be allowed to be on the device but not allowed for business use. Clear communications detailing app policy, with examples of appropriate and inappropriate app use, will assist users in understanding how to safely and securely use apps for business purposes. App Distribution is managed through distribution lists or groups that determine which apps get distributed to which user. These groups can be managed individually but for large distribution lists, must be managed through a corporate directory structure such as Active Directory in order to scale and automate the distribution process. Administrators will need the ability to manage individual membership in groups in order to define how apps get distributed to specific users and departments.
2012 MobileIron
P a g e | 9
2012 MobileIron
P a g e | 10
2012 MobileIron
P a g e | 11