Mobile Experience Type

Native
1. What it is
  1. Runs natively on the hardware of the device
  2. Uses the native programming language (such as Java, Objective C, or C++)
2. Strengths
  1. Can use full features of operating systems
  2. Can be on the app store
  3. Can access as buttons on phone
3. Weaknesses
  1. More expensive / time consuming to develop
    1. Different devices
    2. different operating systems = different code bases
  2. If you want to update, they have download the new version
  3. Data is all downloaded on the device meaning space is taken up
Web
1. What it is
  1. Web site with interactivity
  2. Uses HTML, JavaScript, CSS
  3. Accessed through the web browsers
2. Strengths
  1. Can run on all devices using same code
  2. Doesn't have to go through OS Protocalls
  3. No need for user to update - website is just changed on the back end
3. Weaknesses
  1. Requires an internet connection
  2. Not as much access to the hardware or user data
  3. Not on app store
  4. Not as easy to add to device shortcuts
Hybrid
1. What it is
  1. Combine web and native
  2. Web app as base, with wrapper of native code around it
2. Strengths
  1. Base code is the same for all platforms
    1. Require a wrapper to contain the website as an installed app
  2. No need for web browsers
  3. No need for user to update - website is just changed on the back end
  4. Can appear on app store and on home screen
3. Weaknesses
  1. Trying to please both platforms at the same time = no one perfectly happy
  2. Won't run as smoothly as native app
  3. Require internet connection
Research your assigned type and make sure you understand what it is
1. Research and consider strengths and weaknesses for this type

Next up

Mobile Experience Type

Description

Resource summary

Similar

	Created by Sarah Herzog about 4 years ago