Building Apps Across Different Platforms
April 2012
Agenda
» About 12snap
» The App
» Why To Develop Cross Plattform
» How To Develop Cross Plattform
Company facts and figures
» Founded: 1999 » Headcount: 50 (2012) » Projects: 640
» Offices: » Munich (headquarters) » Helsinki, Finland » Huizen, Benelux » Washington, USA
» Awards: » 4 Cannes Lions » 5 CommAwards » 2 Communicator Awards
4
12snap – At A Glance
» A pioneer in the mobile marketing space
» An outstanding combined skillset in technology, creative development and brand management
» International references and global campaigns
» Development of innovative and creative marketing and CRM solutions
» Winner of four Cannes Lions
4
5
Client portfolio
6
Service Portfolio
Mobile Internet Mobile CRM
Digital Campaigns Mobile Applications
Tips, tricks & support directly to your Nokia N96. Your subscription is now activated and your 1st tip will arrive soon. If you no longer wish to receive My Nokia tips & tricks to your mobile, reply to this message with MYNOKIA STOP
The App
Fit For Travel
Why Cross Plattform
Mobile Market Fragmentation - Germany
0%
5%
10%
15%
20%
25%
30%
35%
Market Share Installed Base
Android iPhone Symbian Blackberry Windows Phone Others
Quelle: Nielsen 2011
Shifting Dynamics in Mobile Market
0%
10%
20%
30%
40%
50%
60%
70%
Dec-10 Dec-11
Market Share Sales in a Week
Android iOS Symbian WP7 RIM Other
Quelle: Kantar 2011
Differences in Platforms
Language: .net Dalvik (Java) Objective - C
Interfaces:
Resolution: 800x480 240x320 to 1280x720
320x480 & 640x960
Microsoft Java OSX
Brands: Few Nokia, Samsung, HTC, LG
A Lot Samsung, HTC, LG, ZTE, Asus
Acer, Huawei, Panasonic
One Apple
Versions: WP7 & WP7.1 A Lot A Few
Firmware Fragmentation Android
Different User Experience (WP7)
Example Fit For Travel
Example Fit For Travel
Example Fit For Travel
How To Develop
Cross Platform Tool Comparison
Native Cross Platform HTML5
Tools Native SDKs (iOS, Android, WP7) Titanium, RhoMobile PhoneGap, Platform Webview
Language Native Language Javascript, Ruby HTML5, Javascript, CSS3
Runtime Native “Native” Webbrowser
Advantages Full access to platform features Using full potential of platform
Using of unique platform features
Write once run “on all” Translated to native code thus
good performance “Known” language
Usage of known platform the web Write once run “everywhere”
“Easy” debugging
Disadvantages
Requires complete new programming of app for new
platform Developer in high demand for
Android and iOS
Debugging is difficult New language concept has to be
learnt Dependent on cross platform
provider for support One Size doesn’t fit All
Performance is lower Functionality limited
Bugs in browser can crash a concept
One Size doesn’t fit all
Conclusion
No Short Cut to Cross Platform Development
» Selection of process depends on the idea
» Native is the best but also the most expensive way
» Native allows for the best user experience and integration into platform
» Cross Platform tools can be a short cut but often not as efficient thus cheap as hoped
» For Cross Platform the concept has to take into account the tool used
One App Doesn‘t Fit All
Rather develop one platform perfect,
than many platforms in a hurry.
23
Benedikt Hanswille * [email protected] * @hbenny * +49 (172) 8986073
Recommended