Your SlideShare is downloading. ×
IBM / worklight - native-web-or-hybrid-mobile-app-development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

IBM / worklight - native-web-or-hybrid-mobile-app-development

7,289
views

Published on

Published in: Technology, Business

2 Comments
10 Likes
Statistics
Notes
  • IBM Worklight has brought in a new era in mobile application development which helps enterprises to develop apps in a cross platform environment.

    http://www.omniesolutions.com/IBM-worklight-mobile-apps-development.aspx
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Worklight server is great is a good ,
    From My experience Native + work light server = best option but it cost more time but give best result you expect.

    Hybrid = less time cost but application is not fast enough as you expect you live inside sandbox your user experience is not good
    when you navigate between more than one HTML file you lose worklight js support, you must be in main application html file to keep support to WL namespace
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
7,289
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
389
Comments
2
Likes
10
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Native, Web or Hybrid MobileApp Development?WorkLight Webinar Series
  • 2. Agenda Introduction Understanding the different approaches • Native apps • Web apps and HTML5 • Hybrid apps The business context Q&A2
  • 3. Introduction Native Apps Web Apps Hybrid Apps 101101101011011 <!DOCTYPE html PUBLIC 101101 <!DOCTYPE html PUBLIC 110110110110110 <html> <! - - created 2003-12-12 - - > 101011 <html> <! - - created 110110110110101 <head><title>XYZ</title> 011110 2003-12-12 - - > </head> <head><title>XY 101101011011011 <body> 110110 Z</title> <p> </head> 011011011011011 Voluptatem accusantium do 110110 <body> <p> 011101011101111 Totam rem aperiam eaque 110110 Voluptatem </p> </p> 110110110110101 </body> 110110 </body> </html> </html> 101000001101011 1011013
  • 4. Examples of Purely-Native Mobile Apps4
  • 5. Characteristics of a Purely-Native Mobile App A binary “executable image”, that is explicitly downloaded and stored on the file system of the mobile device Distributed through the popular app store or marketplace of the device, or via an enterprise distribution mechanism Executed directly by the operating system • Launched from the home screen • Does not require another “container app” to run it Makes explicit use of operating-system APIs5
  • 6. Native App Development Software Source Resources Code (e.g. images) Application Source Code SDK Tools Executable Compiler, Linker Packager (Binary) Distributable Package App Stores6
  • 7. iOS – Native App Development Software Source Resources Code (e.g. images) Objective-C, Application Source Code C++, C SDK Tools Executable Compiler, Linker Packager (Binary) Xcode Distributable Package .app App Stores7
  • 8. Android – Native App Development Software Source Resources Code (e.g. images) Java Application Source Code (some C, C++) SDK Tools Executable Compiler, Linker Packager (Binary) Distributable Android SDK Package .apk App Stores8
  • 9. BlackBerry – Native App Development Software Source Resources Code (e.g. images) Java Application Source Code SDK Tools Executable Compiler, Linker Packager (Binary) BlackBerry Java Distributable Plug-in for Eclipse Package .cod App Stores9
  • 10. Windows Phone – Native App Development Software Source Resources Code (e.g. images) C#, VB.NET, etc. Application Source Code (Sliverlight) SDK Tools Executable Compiler, Linker Packager (Binary) Visual Studio, Windows Phone Distributable Developer Tools Package .xap App Stores10
  • 11. Native App Development Summary Java Languages Obj-C, C, C++ Java C#, VB.NET, etc (Some C, C++) Visual Studio, BB Java Eclipse Tools Xcode Android SDK Windows Phone Plug-In Dev Tools Executable Files .app .apk .cod .xap BlackBerry App Windows Phone Application Stores Apple iTunes Android Market World Market Similar approach, but different source code and expertise results in expensive development and maintenance11
  • 12. Characteristics of a Purely-Native Mobile App A binary “executable image”, that is explicitly downloaded and stored on the file system of the mobile device. Distributed through the popular app store or marketplace of the device, or via an enterprise distribution mechanism. Executed directly by the operating system • Launched from the home screen • Does not require another “container app” to run it. Makes explicit use of operating-system APIs12
  • 13. Native App – Interaction with Mobile Device Graphics Touch Screen, Mobile Operating Keyboard System Touch Events Data WiFi Calls, Data GSM Network Audio Microphone OS-Specific APIs Audio Speaker Native API Calls Wide Range of Images, Video Camera App Services Activation Vibration Accelerometer, Orientation Compass Location GPS Data Storage13
  • 14. Native App – High-level APIs and Built-in Apps Downloaded Apps Built-in Apps API Apps Calls APIs API High-Level GUI Calendar Contacts, Push Browser Calls More APIs Toolkit API Email API API API API Calls Low-Level File Network Graphics Camera Multi- Audio More APIs System tasking14
  • 15. GUI Toolkit Provides App With “Native” Look Downloaded Apps Built-in Apps API Apps Calls APIs GUI Toolkit Browser API15
  • 16. Mobile Web Apps and Mobile Browsing Downloaded Apps Built-in Apps Apps APIs High-Level GUI Calendar Contacts, Push Browser More… APIs Toolkit API Email API API API Rendering Engine (e.g., Webkit)16
  • 17. Mobile Browsing and Mobile Web Apps Dremel: Launch using 2B: Web App Google, Wikipedia: QR-Codes Mobile-optimized websites YouTube: Web App17
  • 18. Mobile Browsing vs. Mobile Web AppsPure Mobile Web Sites Pure Mobile Web Apps • Visited by browsing • Installed and launched • Static, navigational UI • Interactive UI • Generic look & feel • Touch optimized • Server-side rendering • Client-side rendering • Require connectivity • Available offline18
  • 19. JavaScript Toolkits for Mobile Web App UI SenchaTouch Example: jQuery Mobile: Crossword Puzzles for iPad Boston Event App19
  • 20. HTML5 and related technologies Static Pages Dynamic Pages Web Applications w3c.org whatwg.org Main HTML5/CSS3 features on mobile • Bitmapped and vector graphics, including animations • Offline support and data URLs • Geolocation • Video and Audio • Continuous communications with the server • More…20
  • 21. Characteristics of Mobile Web Apps Entirely written using web technologies • HTML, CSS and JavaScript Code is executed by the browser, not by the OS Various launch mechanisms • Typing URL, clicking hyperlink, scanning QR Code or clicking home-screen shortcut Installation is optional Combine cross-platform HTML5 and device-specific features optimize apps • Touch-optimized look & feel • No address bar • Suggestion to pin to home screen • Offline availability21
  • 22. Native App – Interaction with Mobile Device Graphics Touch Screen, Mobile Operating Keyboard System Touch Events Data WiFi Calls, Data GSM Network Audio Microphone OS-Specific APIs Audio Speaker Native API Calls Wide Range of Images, Video Camera App Services Activation Vibration Accelerometer, Orientation Compass Location GPS Data Storage22
  • 23. Web App – Interaction with Mobile Device Graphics Touch Screen, Browser Mobile Operating Keyboard System Touch Events Data WiFi Web App Calls, Data GSM Network (HTML, CSS, JS) Microphone Audio OS-Specific APIs Audio Speaker Wide Range of Images, Video Camera W3C Services Calls Activation Vibration Accelerometer, Orientation Compass Rendering API Calls Engine Location GPS Data Storage23
  • 24. Native vs. Web Device Development Approval Speed App Store Access Cost Process Native Full Very Fast Expensive Available Mandatory Web Partial Fast Reasonable Not None24
  • 25. Introducing Hybrid Apps Device Development Approval Speed App Store Access Cost Process Native Full Very Fast Expensive Available Mandatory Hybrid Web Partial Fast Reasonable Not None25
  • 26. Characteristics of Hybrid Apps A Hybrid App is a native app with embedded HTML It has all the benefits of native apps: full access to APIs, app- store presence, etc. Selected portions of the app are written using web technologies The web portions of the app can either be downloaded from the web or packaged within the app26
  • 27. Hybrid App – Interaction with Mobile Device Graphics Touch Screen, Hybrid App Mobile Operating Keyboard System Touch Events Web Portion WiFi Data of App Calls, Data GSM Network HTML, CSS, JS Audio Microphone HTML API OS-Specific APIs Audio Speaker calls Wide Range Images, Video Camera Rendering Engine API Calls of Services Activation Vibration API PhoneGap Accelerometer, Orientation Compass Native Portion Location GPS API Calls of App Data Storage27
  • 28. Hybrid App Examples Bank of America Facebook Morgan Stanley Lotte Card (Korea)28
  • 29. Hybrid App Development Native Sources HTML Sources Server Software Source Resources Code Application Source Code (e.g. images) SDK Tools Executable Compiler, Linker Packager (Binary) Distributable Package App Stores29
  • 30. App Development Comparison Device Development Approval Speed App Store Access Cost Process Native Full Very Fast Expensive Available Mandatory Native Low Hybrid Full Speed as Reasonable Available Overhead Necessary Not Web Partial Fast Reasonable Available None30
  • 31. No Single Approach Is Right For Everyone Target Audience App Function Time and Budget IT Resources31
  • 32. An Inherent Tradeoff Native App Hybrid App User Experience Web App Mobile Web Site Cost and Time-to-Market32
  • 33. Choosing What’s Right For You Native Web Hybrid • Existing in-house • Direct distribution to • Breaking the native skills the hands of users development tradeoff • Targeting a single • Pilot application • Existing in-house web mobile OS development skills • Out-of-store visibility • Dominant native via search engines • Taking the future into functionality consideration • Rich UI requirements33
  • 34. Future Trends Future device fragmentation Accelerated enterprise adoption New features and complementing technologies New distribution channels34
  • 35. Mobile is Strategic. Not Tactical. Flexible Development Secure and Scalable Integration Ongoing Monitoring and Control35
  • 36. For More Information Resource Location www.worklight.com Industry Whitepapers Technology Reports Expert Webinars dev.worklight.com Developer Zone Self-Guided Tutorials Technical Resources36