Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Mobile Application Development

No description
by

Bas Jaburg

on 10 April 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Mobile Application Development

MOBILE PHONE TIMELINE
How far have we come in 31 years?
Let's have a look...
NOKIA
MOBIRA SENATOR
First Car Phone
$ 6,200
10 KG
DYNATEC 8000X
1 KG
1 Hour Battery
Stored 30 Numbers
NOKIA MOBIRA
CITYMAN
5 KG (Mostly Battery)
14 Hours Talk Time
$ 6,300
First Handheld Cell Phone
MICRO TAC
First Flip Phone
$ 3,000
5 KG
1982
1984
1987
1989
NOKIA 1011
First Digital Handheld Phone
470 gr
90 mins talk / 12 hours standby
Stored 99 Numbers
SIMON PERSONAL COMMUNICATOR
$ 900
Touch screen
450 gr
1 hour battery life
Only produced for 6 months
NOKIA 9000 COMMUNICATOR
30 Hours Battery Life
400 gr
8 MB Storage
Graphical User Interface
MOTOROLA STAR-TAC
$ 1000
110 gr
Stored 100 numbers
4 Hours Standby
NOKIA 5110
220 gr
Standby up to 180 hours
Talk time up to 3 hours
First App: Snake
ERICSSON R380
First Marketed as "Smart Phone"
Touch Interface
Landscape and Portrait Mode
BlackBerry 5810
8 MB Flash Memory
First Marketed Email Device
10 Days of Standby Time
SonyEricsson W800i
"Walkman-Phone"
1GB External Memory
Internet Browser
Multimedia Phone
True Internet
GPS Integration with Nokia Maps
OVI Store
Wi-Fi
5 Megapixel Camera
Nokia N95
1992
1993
1996
1998
2000
2002
2005
2007
and then...
2007
2008
2009
2010
2011
2012
2013
iPhone
4GB $499
No 3G
No GPS
No Apps
64 GB Max Memory
8 Megapixel Camera
1136 x 640 pxls
1080 HD Recording
64 GB Max Memory
8 Megapixel Camera
1280 x 720 pxls
1080 HD Recording
Near Field Communication Chip
HTC G1
First Android Phone
256 MB RAM
320 x 480 pxls
BlackBerry Storm
2006
"iPhone Killer(!)"
Touch interface
480 x 360 pxls
BlackBerry Z10
16 GB
$ 999
BlackBerry 10 OS
Windows Phone 8
16 GB
$ 999
so what did Nokia do?
Windows Mobile Smartphone & PocketPC Edition
ActiveSync Integration
.Net Compact Framework
SQL Server Pocket Edition
iPhone 5
App Store - Downloads
1.000.000.000
Introduction
5.000.000.000
10.000.000.000
15.000.000.000
25.000.000.000
30.000.000.000
THE REAL SMARTPHONE REVOLUTION
iOS
COCOA
ObjC
Android
BlackBerry
J2ME
Traditional Mobile Web
WML
HTML5
APPLICATION DEVELOPMENT
Device
Detection
Security
Frameworks
Data
Integration
ApplicationUpgrades
New
Devices
New OS & OS Updates
New Browser & Browser Updates
PRODUCTION SERVICES
MOBILE ECOSYSTEM CHANGES
2005
2006
2007
2008
2009
2010
2011
2012
2013
Mobile & Traditional Web
Mobile Operating Systems
Tablets
wap 1.2
wap 2.0
iPhone WebKit
Android Webkit
Mobile HTML5
Media Queries
HTML 3
HTML 3.2
HTML 4
Windows CE
Flash, Ajax, CSS
CSS 3.0
HTML 5
DoJo, JQuery, MochiKit, Prototype, YUI
WebKit w/
Javascript
1.0 1.5 1.6 2.0 2.2 2.3 3.0 4.0 4.2
1.0 2.0 2.2
10
4.0 4.1 4.2 4.3 4.5 4.7
7.0 7.1
5.0
6.0
7.0
8.0
Smartphone Sales 2012
Source: IDC
Conclusion
Market is changing rapidly
Android is number 1
Cause 1: Already 8 different Android versions!
Problem: Android fragmentation
Cause 2: Every manufacturer has his own implementation
So what can we do?
By helping the client making the correct choise
Android example: 24.000 different combinations possible
Examples of choices
Make an estimation on which platform, Operating Systems and Devices are really necessary (Android Top 5 covers 95% of market)

Native versus Hybrid versus Web development

Using a Mobile Enterprise Application Platform (M.E.A.P) for development
Mobile Web
online
HTML 5 /CSS 3
limited device specifics
limited security options
it is not a product
App
Online and Offline
rich user experience
HTML 5 / CSS3 and/or native full device specifics
it IS a product
What do we need?
A development environment
a development license
a developer
with a 'mobile' mindset
And what does that mean??
There are 5 areas that need to be considered
Design
Memory
Responsiveness
Power consumption
Security

Design
apps are used during seconds rather that minutes, hours or days
quick use, quick storage
you have to present useful information quickly
enable for touch as no (useful) keyboard or mouse is present
there is a limited resolution,
for iPhone
320 x 480
640 x 960
640 x 1136
for iPad
1024 x 768
2048 x 1536
for Android
loads!
Memory
When it comes to memory management it is the old days again (semi-automatic garbage collection, no swap-file, 'multi-tasking')
Responsiveness
Apps have to be quick, snappy and responsive
When shutting down, save the state
Power Consumption
Be careful with transferring data, since it is the single most power-intensive operation!
number 2 is receiving!
There is a 'sandbox'
which provides security
but you need to use secure coding practices
Security
What Equipment?
an Intel Based Mac
test devices
Apple’s Portal for all iOS Developers Worldwide
Costs € 79 per year (€ 299 for Enterprise license)
Let’s you download the SDK
Gives access to Provisioning Portal
Let’s you agree on the iOS Developer Program Agreement

What is the iOS Development Center?
the iOS Developer Program Agreement
Cool
Superieure User Experience
Push Notifications
Camera
Kompas
NFC
Accelerometer
Gyroscoop
Adresboek
SMS
GPS
Audio/Video
Local Storage
Click2Call
APP
WEB
HTML 5/ CSS 3
GPS
Audio/Video
Local Storage
Click2Call
Web User Experience
Easy maintenance
On line
low budget
Hybrid
How does that actually work?
Probleem
Position: Fixed
Hybrid
Development Effort
Native
Native
Hybrid
time
app 1.0
app 3.0
Mobile Application Development
Bas Jaburg
22 April 2013
What does a typical development street look like?
Experience
Allianz HelpMe App
Let's look at market distribution
Toekomst
C# / XAML / Silverlight
Samen met ASR bouwen aan nieuwe apps
CR neemt regie, ASR voert uit onder begeleiding
Gaandeweg neemt ASR over
Bedankt!
Full transcript