PhoneGap mobile development
•
16 likes•2,746 views
Max Firtman is a mobile and web developer based in Buenos Aires, Argentina. PhoneGap is an open source framework that allows building cross-platform mobile apps using HTML, CSS, and JavaScript. It works by packaging web apps so they can be deployed and run as native mobile applications. PhoneGap supports many mobile platforms but each still requires separate compilation. Debugging mobile web apps can also be challenging. The speaker provides advice around maintaining a single codebase, embracing platform differences, and focusing on performance and the best experience for each context.
Report
Share
Related slideshows
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to PhoneGap mobile development
Similar to PhoneGap mobile development (20)
More from Maximiliano Firtman
More from Maximiliano Firtman (20)
Recently uploaded
Recently uploaded (20)
PhoneGap mobile development
- 2. who am I? mobile+web developer mobilexweb.com blog @firt
- 3. where? buenos aires ~ argentina patagonia football meat & wine tango
- 4. speaker
- 5. books Image from my house
- 7. coming soon... also by @estellevw
- 9. .com
- 10. why mobile?
- 11. mobile ‣ absolutely personal ‣ +5 billions ‣ make us focus ‣ read our context... ‣ ... always... ‣ ... and everywhere.
- 12. then... what is the problem?
- 13. mobile is a minefield Photo by World of Good (Flickr) Malvinas / Falklands Islands
- 14. lots of questions Photo by wayneandwax (Flickr)
- 15. we need to learn lots of questions
- 18. native vs web
- 19. WAIT!
- 20. Are you sure?
- 21. native code vs javascript
- 22. browser vs installed apps & stores
- 24. when we say mobile web from a developer’s perspective it’s using HTML, CSS and JavaScript to develop mobile apps (browser or installed)
- 25. Callback
- 27. What is § A platform to create native apps using web technologies § A JavaScript library § A native library for every platform § Compilation helpers
- 28. Features § Open Source § Multi-platform § Latests -even future- standards § First class apps
- 29. WARNING!
- 30. Warning! § PhoneGap is not a UI framework § PhoneGap doesn t include a browser and or a rendering engine § PhoneGap doesn t compile § Every platform need its own compilation § HTML5/CSS3 compatibility varies - www.mobilehtml5.org
- 31. Compatibility
- 32. Compatibility (official 1.2) § iOS (iPhone y iPad) § Android § BlackBerry 4.x, - 7 § webOS § Symbian § Samsung Bada § Windows Phone 7.5
- 33. Compatibility (non-official yet) § BlackBerry PlayBook § Meego 1.2 Harmattan (Nokia N9)
- 34. Stores § Apple AppStore § Android Market, Amazon AppStore § AppWorld § AppCatalog § Nokia Store § Samsung Apps § Windows Marketplace
- 35. Abilities § Accelerometer § Camera (video/photo) § Compass § Contacts § File Management
- 36. Abilities § Geolocation § Multimedia § Network Information § Notification § Storage
- 37. Abilities
- 38. Architecture
- 40. Requirements
- 41. To develop § Download PhoneGap www.phonegap.com § Use your HTML5 IDE
- 42. To compile § Install SDKs § Dreamweaver CS5.5 or IDEs § Or you can use PhoneGap Build
- 43. Compile ourselves § Xcode for iOS - available in Mac App Store § Android SDK - developer.android.com § BlackBerry WebWorks - blackberry.com/developers/browserdev/ widgetsdk.jsp § Nokia Web Tools for Symbian - developer.nokia.com § Windows Phone SDK - microsoft.com/ download
- 44. To compile on the cloud Get an account at build.phonegap.com
- 45. To test § Simulatos and Emulators (www.mobilexweb.com/emulators) § Real devices § Ripple Simulator § Can we use a desktop browser?
- 47. we are using the browser engine... so why package it?
- 48. is it safe to use an embedded web view?
- 50. Challenges § HTML5 and CSS3 support § Debugging & Profiling § Performance & Memory usage § BlackBerry 5
- 51. Challenges § Screen sizes & orientations § DPIs § User Interface - should we emulate native UI? § Performance & JavaScript Best Practices
- 52. Debug
- 53. Debug § Weinre (debug.phonegap.com) § iWebInspector for iOS (iwebinspector.com) § Pray?
- 54. Plugins
- 55. Plugins § Native code to add more support § Every platform should have its native code § We need a plugin community
- 56. Advices
- 57. Advices § Try to maintain one source code § Define CSS and JavaScript per platform for porting § Embrace differences § Best experience for every platform
- 61. good practices
- 62. don’t be fanatic photo by Kurt Christensen (flickr)
- 63. be multiplatform
- 64. be futurefriend.ly
- 65. best experience for every context
- 66. you can reach a good спасибо! experience firt.mobi twitter: @firt mobilexweb.com