How, what and what else
0 likes597 views
The document discusses mobile optimization and provides an overview of native mobile applications versus web applications. Native applications are written for specific platforms like iOS or Android and provide richer experiences but require multiple versions. Web applications can target multiple platforms with one codebase but are slower and cannot work offline. The best approach depends on factors like the audience, interactivity needs, and whether offline access is required. Examples provided include a native event guide app that needs offline maps versus a web-based event streaming app requiring constant internet.
More Related Content
What's hot (19)
Viewers also liked (8)
Similar to How, what and what else (20)
Recently uploaded (20)
How, what and what else
- 1. How, What and What Else? Or Mobile, What even is it?
- 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. 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. Mobile, should we? Yes ● Mobile internet access is becoming the norm ● It should now be a core consideration of any web based project
- 5. Okay, but how? This is where it gets interesting ● Native Applications ● Web Applications
- 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 they're very small
- 7. Going Native Benefits: ● Native brings speed and capabilities that Web can't ● Brings offline capacity not available to web ● A richer, more interactive experience
- 8. Going Native Cons: ● Much harder to update quickly if there is a problem ● Multiple phone platforms require multiple versions, increasing cost in support and development.
- 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. Casting the Web Benefits: ● More flexible development model ● Can target multiple platforms with a single codebase ● Can integrate into existing web properties a lot easier
- 11. Casting the Web Cons: ● Can't take it offline, users must have internet access to use the app. ● Slower than native due to multiple layers between code and user
- 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. Native Application Example An Interactive Event Guide: ● Tour map with Audio Descriptions ● Continual internet access not required ● Interactive elements require access to hardware on device
- 14. Web Application Example Event Streaming: ● Full internet access is required ● Streaming doesn't require special video or audio requirements ● Use Browser capabilities to provide things like user registration and logins
- 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.