Mobile Experience Type

Mobile Experience Type

1. Native

   • What it is
     • Runs natively on the hardware of the device
     • Uses the native programming language (such as Java, Objective C, or C++)
   • Strengths
     • Can use full features of operating systems
     • Can be on the app store
     • Can access as buttons on phone
   • Weaknesses
     • More expensive / time consuming to develop
       • Different devices
       • different operating systems = different code bases
     • If you want to update, they have download the new version
     • Data is all downloaded on the device meaning space is taken up

2. Web

   • What it is
     • Web site with interactivity
     • Uses HTML, JavaScript, CSS
     • Accessed through the web browsers
   • Strengths
     • Can run on all devices using same code
     • Doesn't have to go through OS Protocalls
     • No need for user to update - website is just changed on the back end
   • Weaknesses
     • Requires an internet connection
     • Not as much access to the hardware or user data
     • Not on app store
     • Not as easy to add to device shortcuts

3. Hybrid

   • What it is
     • Combine web and native
     • Web app as base, with wrapper of native code around it
   • Strengths
     • Base code is the same for all platforms
       • Require a wrapper to contain the website as an installed app
     • No need for web browsers
     • No need for user to update - website is just changed on the back end
     • Can appear on app store and on home screen
   • Weaknesses
     • Trying to please both platforms at the same time = no one perfectly happy
     • Won't run as smoothly as native app
     • Require internet connection

4. Research your assigned type and make sure you understand what it is

   • Research and consider strengths and weaknesses for this type