37
5 Reasons Why Your Website Is[n’t] a Native App DAVID WESST

5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Embed Size (px)

Citation preview

Page 1: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

5 Reasons WhyYour Website Is[n’t]

a Native AppDAVID WESST

Page 2: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)
Page 3: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)
Page 4: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

WTF? WTF?

I’m such a genius!

Page 5: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

What are we doing?

12:38Web page titlehttp://www.url.com

Your Website

Your App

Page 6: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

What are we doing?

12:38Web page titlehttp://www.url.com

Your Website

Your App

Page 7: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

You Me

Conversationing

Page 8: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Half Full?

Half Empty?

It Depends

Page 9: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Goals for Today

5 Reasons… …Why this is a good idea

…Why this is a bad idea

Understand and Consider the User Experience

Examples and Demos of Tools

Get You Thinking About “Why”

Page 10: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

David Wesst

Page 11: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

David Wesst

12:38Web page titlehttp://www.url.com

Page 12: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 1USER INTERFACES

Page 13: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 1

Responsive UI’s are Great!

Device UI’s are different than Web UI’s

Page 14: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

DemoWWW.PRAIRIEDEVCON.COM

Page 15: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

DemoOPAL

Page 16: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Demo - OPAL

Page 17: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Demo - OPAL

Page 18: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Demo - OPAL

Page 19: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 2PAGES VS SCREENS

Page 20: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 2

Single Page Applications are Cool

Sites aren’t always SPA

Page 21: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

DemoSINGLE PAGE APPLICATIONS

Page 22: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 3DEVICE SECURITY

Page 23: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 3

Device API’s work in the Browser

The Web Shouldn’t Be Using Your Hardware

Page 24: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

DemoDEVICE API’S

Page 25: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 4JAVASCRIPT IS JAVASCRIPT

Page 26: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 4

JavaScript Works Everywhere

JavaScript is used Differently Everywhere

Page 27: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

DemoJAVASCRIPT FTW!

Page 28: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Git NPM Bower

Package Developers

Package Consumers

Page 29: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 5INSTALLATION

Page 30: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason 5

Half Empty You Don't Install a Website

Half Full Websites CAN be integrated with desktops!

Page 31: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Reason +/- 5

You Don’t Install a Website

You Don’t Install a Website

Page 32: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

DemoA REAL LIFE MOBILE/WEB APPLICATION

Page 33: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

The Point

Page 34: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Quick Recap – The Questions

How will we interact with the website?

Will our site perform well as an SPA?

What does the "app" do differently than the site?

Can we share our JavaScript between projects?

Do they ACTUALLY want the website to be in a store, or do they want specific functions added to the website that cannot be added without native device access?

Page 35: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

The Point

Web Apps CAN be Native Apps, under the right circumstances Proper planning and architecture

Not easy if website was originally planned this way

Web is gaining more ground on device APIs

JavaScript is JavaScript Hybrid Apps are really cool, again with proper planning

JavaScript can be interpreted anywhere, but that doesn’t mean it’ll work

Installation You need to “sell” your app.

Page 36: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Thank You!

Bryan Payne (@Lead_Manage) Program Manager, UGME – University of Manitoba

WolframHempel (github.com/WolframHempel)

Page 37: 5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)

Who am I?

David Wesst (@davidwesst)

Application Developer, University of Manitoba

http://davidwesst.com/talks