Community Media Association  Player App Review Mobile Developer Group – 24 th  January 2011 @ianibbo This work is licensed...
Why? <ul><li>To help structure our learning </li><ul><li>Real problem
Real deadlines
Need to simplify down to essentials
Discover team roles / issues
Discover client expectation issues
Discover technical problems / innovations
(And see if it's possible to deliver something substantial as a community project....) </li></ul></ul>
What is it <ul><li>A Cross device app to play the range of stations streamed by Community Media Association. </li></ul>
Architecture Streaming Server Twitter Mailing List Website Backend App PhoneGap CMA Player App
Technical Choices  (1) – Native or HTML5 <ul><li>Ease of Reuse vs Native Functionality / Look and Feel
Desire to see what can be achieved with HTML5 app
Initial Dead ends with HTML5 <media> element cross device
Breakthrough with Tool support for access to native libraries via JavaScript.
H/T to Jimmy Wales & Net Neutrality comment. </li></ul>
Technical Choices  (2 – Post HTML5 choice) <ul><li>Multiple Cross Device Toolkits Around
Trialled many, JQueryMobile,...
Upcoming SlideShare
Loading in …5
×

GIST Mobile Developer Group - CMA Player App Review

911 views

Published on

A technical review of the GIST foundation project to build a multi channel radio player app for the community media association as the basis of a shared learning experience around mobile technology.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
911
On SlideShare
0
From Embeds
0
Number of Embeds
45
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

GIST Mobile Developer Group - CMA Player App Review

  1. 1. Community Media Association Player App Review Mobile Developer Group – 24 th January 2011 @ianibbo This work is licensed under a Creative Commons Attribution 3.0 Unported License.
  2. 2. Why? <ul><li>To help structure our learning </li><ul><li>Real problem
  3. 3. Real deadlines
  4. 4. Need to simplify down to essentials
  5. 5. Discover team roles / issues
  6. 6. Discover client expectation issues
  7. 7. Discover technical problems / innovations
  8. 8. (And see if it's possible to deliver something substantial as a community project....) </li></ul></ul>
  9. 9. What is it <ul><li>A Cross device app to play the range of stations streamed by Community Media Association. </li></ul>
  10. 10. Architecture Streaming Server Twitter Mailing List Website Backend App PhoneGap CMA Player App
  11. 11. Technical Choices (1) – Native or HTML5 <ul><li>Ease of Reuse vs Native Functionality / Look and Feel
  12. 12. Desire to see what can be achieved with HTML5 app
  13. 13. Initial Dead ends with HTML5 <media> element cross device
  14. 14. Breakthrough with Tool support for access to native libraries via JavaScript.
  15. 15. H/T to Jimmy Wales & Net Neutrality comment. </li></ul>
  16. 16. Technical Choices (2 – Post HTML5 choice) <ul><li>Multiple Cross Device Toolkits Around
  17. 17. Trialled many, JQueryMobile,...
  18. 18. PhoneGap seems right balance of ease of use and functionality
  19. 19. Reasonable access to phone specific API's
  20. 20. Good per-device communities / Support
  21. 21. Devs reasonably free to select web frameworks of choice </li></ul>
  22. 22. Final Approach <ul><li>n-Tier architecure. Servers, aggregator / service layer.
  23. 23. HTML5 web app
  24. 24. App gets management info from service API, streams directly from Streaming Server </li></ul>
  25. 25. Why Middle Tier <ul><li>Missing station detection
  26. 26. Pre-parsing and processing ease burden on client app – Just deals in clean verified JSON, no XML parsing client side.
  27. 27. Ability to enhance and augment station data before supplying to client
  28. 28. Usage Tracking </li></ul>
  29. 29. Approach - Strengths <ul><li>HTML5 / Javascript – Reusable, readily available skills
  30. 30. Makes cross device apps with shared codebase possible
  31. 31. Multiple development platforms
  32. 32. Really Easy to Develop
  33. 33. Multi-Function App, less likely to be rejected by store
  34. 34. Team seemed to work well (Looks at @guru) </li></ul>
  35. 35. Approach - Weaknesses <ul><li>Access to some native controls problematic – Specifically volume in our case.
  36. 36. Does depend on a server component – Single point of failure (But then so is the streaming server)
  37. 37. Looks different to a purely native app
  38. 38. Still experimenting with background play </li></ul>
  39. 39. Live Demo (eek!)
  40. 40. Community Project Angle <ul><li>Is it possible to build something substantial in the short term on a community basis rather than a commercial basis.
  41. 41. To have a shared learning experience
  42. 42. ..and deliver something solid and useful to a local organisation along the way
  43. 43. YES! </li></ul>
  44. 44. Summary (1) <ul><li>Final push to go-live
  45. 45. PhoneGap really easy to use
  46. 46. Works well with other tools
  47. 47. Familiar technology
  48. 48. Obvious it doesn't produce native apps
  49. 49. Does the job – Does it do it pretty enough?
  50. 50. Community Project – Awesome! </li></ul>
  51. 51. Summary (2) <ul><li>Huge thanks to the team for supporting this GIST project, @guru, @jagusti, @billbest.
  52. 52. @guru and @jagusti are ace team member and you should work with them!
  53. 53. @community_media and @billbest are ace too, you should work with them too, and support them in any way you can!
  54. 54. PhoneGap worked best for us as a cross-platform HTML5 development tool. </li></ul>
  55. 55. Discussion <ul><li>General Discussion
  56. 56. Any Feedback on App greatly appreciated! </li></ul>
  57. 57. Thanks!
  58. 58. Refs / Notes <ul><li>Project git repository:
  59. 59. https://github.com/gistfoundation/gist-cma-player </li></ul>

×