Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
How, What andWhat Else?Or Mobile, What even is it?
First things first● This presentation is a summary of my  experience and investigations, outside of my  role in the LGSA● ...
Mobile, What even is it?Some mobile facts:● An estimated 50% of Australians who  access the internet do so via mobile devi...
Mobile, should we?Yes● Mobile internet access is becoming the norm● It should now be a core consideration of any  web base...
Okay, but how?This is where it gets interesting● Native Applications● Web Applications
Going Native● Native Applications are written specifically  for a single mobile platform● Two biggest smartphone platforms...
Going NativeBenefits:● Native brings speed and capabilities that  Web cant● Brings offline capacity not available to web● ...
Going NativeCons:● Much harder to update quickly if there is a  problem● Multiple phone platforms require multiple  versio...
Casting the Web● Web Applications are built in the same way  that your websites are● Target Standards instead of specific ...
Casting the WebBenefits:● More flexible development model● Can target multiple platforms with a single  codebase● Can inte...
Casting the WebCons:● Cant take it offline, users must have internet  access to use the app.● Slower than native due to mu...
So how do we decide?Depends on your project requirements:● Who is your audience?● What level of interactivity do you need?...
Native Application ExampleAn Interactive Event Guide:● Tour map with Audio Descriptions● Continual internet access not req...
Web Application ExampleEvent Streaming:● Full internet access is required● Streaming doesnt require special video or  audi...
Some final thoughts● Mobile should never be an afterthought● There is more than one way to skin a cat● Native vs Web, it a...
Upcoming SlideShare
Loading in …5
×

How, what and what else

797 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

How, what and what else

  1. 1. How, What andWhat Else?Or Mobile, What even is it?
  2. 2. First things first● This presentation is a summary of my experience and investigations, outside of my role in the LGSA● http://collaborynth.com.au
  3. 3. Mobile, What even is it?Some mobile facts:● An estimated 50% of Australians who access the internet do so via mobile devices● 8% do so via tablets● Mobile optimised content is becoming an expectation
  4. 4. Mobile, should we?Yes● Mobile internet access is becoming the norm● It should now be a core consideration of any web based project
  5. 5. Okay, but how?This is where it gets interesting● Native Applications● Web Applications
  6. 6. Going Native● Native Applications are written specifically for a single mobile platform● Two biggest smartphone platforms: ○ iOS (iPhone, iPad) ○ Android (Multiple Phones and Tablets)● There are others, but theyre very small
  7. 7. Going NativeBenefits:● Native brings speed and capabilities that Web cant● Brings offline capacity not available to web● A richer, more interactive experience
  8. 8. Going NativeCons:● Much harder to update quickly if there is a problem● Multiple phone platforms require multiple versions, increasing cost in support and development.
  9. 9. Casting the Web● Web Applications are built in the same way that your websites are● Target Standards instead of specific phone platforms: ○ HTML ○ Javascript
  10. 10. Casting the WebBenefits:● More flexible development model● Can target multiple platforms with a single codebase● Can integrate into existing web properties a lot easier
  11. 11. Casting the WebCons:● Cant take it offline, users must have internet access to use the app.● Slower than native due to multiple layers between code and user
  12. 12. So how do we decide?Depends on your project requirements:● Who is your audience?● What level of interactivity do you need?● Will your users need offline access to content?● Do you see the App evolving quickly?
  13. 13. Native Application ExampleAn Interactive Event Guide:● Tour map with Audio Descriptions● Continual internet access not required● Interactive elements require access to hardware on device
  14. 14. Web Application ExampleEvent Streaming:● Full internet access is required● Streaming doesnt require special video or audio requirements● Use Browser capabilities to provide things like user registration and logins
  15. 15. Some final thoughts● Mobile should never be an afterthought● There is more than one way to skin a cat● Native vs Web, it all depends on what you want to do.

×