Native Apps vs. Mobile Sites

Native App vs. Mobile Web Sites: Meghan Palagyi
Native App
Pros
1. Own the conversation
2. Simplify web publicshing & web design support
3. Can still find info on web (yelp, google maps, etc.)
4. Younger generations may not experience hurdles like older
5. Some interactions (banking) are just better via the organizations native apps
6. Speed of access
7. Suited to specific needs
Cons
1. Maintain ios & Android
2. What about people who don't have smartphones?
3. Must be web-literate (accessibility)
4. Can actually be MORE accessible if follows APP dev rules (at least for IOS)
5. Too much storage used on device
6. Apps on desktop?
7. Another step users have to take.
8. SPEED-BUMP too many confused, how to download, how to find
9 Trust: financial security + privacy (for us FIRPA, etc)
 
Mobile Web Sites
Pros
Anyone w/ a web browser can use if the site is responsive
2. We don't care about the device
3. Access to anyone
4. Fast, easy, access no need to download
5. Can behave like apps
6. Browser security is more trusted as it's newer
7. Want desktop as well
8. Workday: all products are mobile first via web socket.
Con
1. Need internet connection
2. Web sites on ipads or mobile are often not full service...e.g. some functionality is not available...especially things like transactions.
3. Mobile experience is possibly subservient to responsive design
Use Cases App vs Website
APP
Pros
1. Maps, camera access, hardware access
2. Access to PII + secure networks
Cons
1. Trust or management for native app? There is for websites
ARTICLE: APP AS WE KNOW IS DYING: http://blog.intercom.io/the-end-of-apps-as-we-know-them/
API strategies: APIs open up access to devs to further functionality that you would not allow on your website.
Students Use all sorts of modes
1. Want tech but also want a human being at the end of the service chain. (SERVICE DESIGN)
Registrar Office person in charge of iStanford: ANgie Chan-Geiger