Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Who are SWmobile? - IT MegaMeet

Who are SWmobile? - IT MegaMeet

Intro to the SWmobile meetup group
Cross Platform tools (presented by Tom Spencer)
MBaaS

Scott Alexander-Bown

June 01, 2013
Tweet

More Decks by Scott Alexander-Bown

Other Decks in Programming

Transcript

  1. SW Mobile - what is it? •  200+ members • 

    Est. Feb 2012 •  Meetup.com/swmobile •  Locations o  Bristol o  Bath
  2. All of your platforms! •  Android •  iOS •  Mobile

    Web / HTML 5 •  Responsive web •  Windows phone •  Blackberry •  Cross platform •  ....
  3. Previous meetups •  Last meetup o  Going Freelance (29/05/2013) • 

    Previous meetups o  Building apps for both iPhone and iPad o  Hacking iPhone and Android o  What's new in Android/iOS
  4. Upcoming meetups •  UI prototyping o  When: end of June

    o  Bristol Uni •  Programming tools tips swap
  5. What are Cross Platform Tools? What are they? Tools and

    frameworks. The promise: •  Write once •  Run on multiple devices & platforms #swmobile
  6. Why should I use them? Because there are a ton

    of devices out there. And they all have separate native SDKs. #swmobile
  7. How many devices? Depends who you listen to... iOS and

    Android are the main ones. BlackBerry and Windows Phone are worth considering. #swmobile
  8. So what are my options? There are lots of cross

    platform tools. Here are some of them.* Web Native * There are loads more. #swmobile
  9. Native Frameworks Recipe: •  Write in one language. •  Press

    compile. •  Native binaries produced for each platform. Corona SDK Appcelerator Titanium Adobe Flash Builder #swmobile
  10. Mobile Web Recipe: •  Write in HTML / CSS /

    JavaScript. •  Put on server. •  Share URL. HTML5 Sencha Touch jQuery Mobile #swmobile
  11. Hybrid Recipe: •  Write in HTML / CSS / JavaScript

    / native code. •  Wrap in native shell. •  Native binaries produced for each platform. #swmobile
  12. Which one should I go for? Things to consider. • 

    Native will always win on performance. •  Web will always win for flexibility. •  Right now, HTML5 support is not good enough on most of the devices in the wild (looking at you, Android). •  Hybrid is a great happy medium, when implemented well, as seen by GMail and Basecamp. •  Otherwise native frameworks are probably* the best. •  But make sure you choose a framework which will last, and will be regularly updated. #swmobile
  13. Agenda: •  Intro •  What is it? o  Key features

    o  The players •  Roll your own? •  Kinvey: code samples •  Costs •  Demo (if time) •  Final thoughts
  14. Key features •  User auth o  Social login - Google,

    Facebook, Twitter, Linkedin etc •  User management •  Data storage o  save and sync data objects o  files (large files) •  Cloud code •  Analytics •  Push
  15. Why not just roll your own? •  Pace •  Learning

    curve •  Stack risk •  Connecting to 3rd party apis •  Scaling
  16. All your platforms belong to us... •  Great support: o 

    Android o  iOS o  Windows o  HTML5 o  Node.js o  Phonegap, Appcelerator
  17. Code sample: Login in with Twitter * Note: requires some

    boilerplate code to get the OAuth token Code sample: kinvey.com
  18. Kinvey: 3rd party data integration •  Facebook •  Twitter • 

    4Sq •  Google Places •  Yahoo local •  LDAP •  ql.io - api aggregator
  19. Demo (if time) •  Poke around the console •  Update

    something on the device - show on console •  Update something on the console - show on device
  20. Final thoughts... •  Flavour of the month •  Free to

    try •  Big time and effort saving •  Great for Proof of Concepts / Hacks Think about •  Where is your data? •  Data export •  Vendor lock in •  Performance for smaller/low use apps •  Costs