Beruflich Dokumente
Kultur Dokumente
Developer 2017
MA HMMO UD MA HD I
Course Prerequisites
Web Technologies
HTML6
JavaScript
Cascading Style Sheets (CSS)
Web Services
Application development frameworks
Use tools to create and publish mobile applications
Contents
Android 79%
iOS 16%
Windows Phone 4%
Others 2%
A typical mobile application
solution
Considerations for mobile
Development
Authentication
and security
Performance
Hardware
features
2. Mobile application
development approaches
Mobile application development
approaches
Mobile application development
approaches
Mobile application development
approaches: Comparison
Native approach (1/2)
Native application is a binary file that is stored locally on
the device
Usually downloaded from an App Store
Specific to one type of device
After downloading, the application interfaces directly
with the device operating system
The application can access all native APIs of the device
Development requires specialized skills
Maintenance is costly for apps that are deployed on
multiple platforms
Native approach (2/2)
The application source code is written in a high-level
language
Source is compiled into an executable binary file, usually
by using specific vendor-supplied tools (SDK)
Native approach pros, cons, and use
cases
Pros
Use cases
Full access to all device functions
Native code runs fast on a device Application requirements:
Cons Access to native device
functions that cannot be
Requires specific skill set for each
platform accessed any other way
Code is not portable to other Complex user interface
platforms
Real-time
Development cycle can be costly
and time-consuming responsiveness
Web approach
Applications that are run on web server; accessed by using
a Mobile Web browser
Can run on many types of devices
Access to device-specific features is limited
Ability to do advanced graphics is limited
Apps can be deployed and maintained on multiple platforms more
easily
Standard web technologies:
HTML and CSS3
JavaScript
Web approach pros, cons, and use
cases
Pros Use cases
Supports multiple platforms Projects with a short runway
Low cost of development Low budget, limited
Easy to maintain resources
Mobile Web applications
Cons must be distributed within
Limited access to native an organization,
device functions without having to go
through a public App Store
Hybrid approach
Applications that are run on a device in a native
container
Can be downloaded from an app store
Can run on many types of devices
Can access many device-specific features through a
bridge
In-house web application skills can be leveraged
Apps can be deployed and maintained on multiple
platforms more easily
Hybrid approach pros, cons, and use
cases
Pros Use cases
Supports multiple platforms In-house web development skills
Mitigates development and can be leveraged
maintenance costs Time to market is a high priority,
Supports many device functions but fast performance and full
access
Cons to device functions is secondary
A trade-off between Rapid distribution is required on
performance and functionality, multiple platforms
and lower cost and portability Need to manage development
and maintenance costs
Why use a hybrid approach?
Native Vs Cross-Platform Approach
3. Mobile solution offerings
IBM MobileFirst
IBM MobileFirst
Mobile Development
Foundations
MO DULE 2
Mobile Development Foundations
Course I - Roadmap to Mobile Web Development