The API and APP-ification of the Web

32
The API- & APP- ification of the Web Steven Willmott 3scale networks @3scale - http://www.3scale.net (and possibly everything else)

description

Session Talk at Gluecon 2013 by @njyx of 3scale: http://www.3scale.net/

Transcript of The API and APP-ification of the Web

Page 1: The API and APP-ification of the Web

The API- & APP-ification of the Web

Steven Willmott 3scale networks

@3scale - http://www.3scale.net

(and possibly everything else)

Page 2: The API and APP-ification of the Web

This Work is Licensed Under Creative Commons Creative Attribution 3.0

Page 3: The API and APP-ification of the Web

“Welcome to the App-Economy”

“What will win? Apps v’s HTML(5) ”

“The Death of the Open Web?”

Page 4: The API and APP-ification of the Web

Some Hyperbole but..

There is probably something going on…

Page 5: The API and APP-ification of the Web

And some of has to do with SPAs…

Page 6: The API and APP-ification of the Web

Single Page Web Applications

Server (REST / JSON API)

Buttons

Infinite Scroll

Push Updates

Ember.jsAngular.jsBackbone.js…

Single HTML Page & URL Per Pagemany Pages per Site / App

Pages ServerWhole

Server

SPAs Serve a Single Page of HTML and use in page controls to operate

dynamically

Page 7: The API and APP-ification of the Web

e.g….

(From http://www.angularjs.org)

Page 8: The API and APP-ification of the Web

Obvious Benefits of SPAs

• Lots of Benefits:– Slick interfaces, Similarity to Mobile/Desktop– App Speed, no need for Page Reloads– Interface variants are easier– Realtime / Push updates

• And Downsides: – JS Skills at a premium, Less Tooling, Modern

Browsers Needed, Framework overload…– (and a few others we’ll mention later)

Page 9: The API and APP-ification of the Web

Examples

Page 10: The API and APP-ification of the Web

Evernote: The Platform Imperative

e.g. Evernote

“Capture Everything - Access anywhere”

Mobile Platforms

DesktopPlatforms

Web Browsers

Top Apps

Page 12: The API and APP-ification of the Web

Zendesk: Speed and Slicks

e.g. Zendesk

Real Time Updates

No Page Redraws

Effectively a .jsApp

API User Community

• App.js Example• Same Agility for All• More Robust API• 90+ Integrations

Page 13: The API and APP-ification of the Web

Value…

• Platform strategy• Uniform user experience• Fast, Responsive, No Page Reloads, Push• API Enables 3rd Party Use, Javascript components

make that use easier

• Both also have: dev communities & mobile apps

Page 14: The API and APP-ification of the Web

Adoption and Impact on the Web

Page 15: The API and APP-ification of the Web

Who Will Adopt?(assuming the tech works)

Mobile Natives>> SAAS

>> Ecommerce >>

Content

Impact is more

And more radical

Page 16: The API and APP-ification of the Web

But there are issues…

Links?Referencing?

Crawling & Indexing?

UI Fragmentation?

…Openness?

RSS Following?

Discovery? SEO?

Page 17: The API and APP-ification of the Web

Adoption Complexity & Disruption

LinkingReferencing

Seamless Browsing Discovery

Mobile Native Businesses OS Specific UI is App Specific App Store

SAAS Businesses In app is fine UI is often Specific

Primary Domain Only

eCommerce Businesses

Items need to be addressable

from anywhere

Common Check Out Metaphors

Are usefulMostly for

Primary Domain

Content BusinessesNeeds to

addressable from anywhere

Expect Consistent Web

UISEO is Critical

Page 18: The API and APP-ification of the Web

So – How do We Move Forward?

• Things we MUST Preserve:– Link-a-bility– Browse-a-bility– Crawl/Index/Discover-a-bility– Follow-a-bility

• And a new thing we want to Gain including:– Script-a-bility

Page 19: The API and APP-ification of the Web

Technical Challenges

Changing Architecture of the Web

Page 20: The API and APP-ification of the Web

Link-a-bility

• Hyperlinking• Fragment Referencability

• Web Links Still Work• Fragments Still Work• Param Schemes Need

to be Complete• Avoid Header

Information

http://www.gluecon.com/….

• Links need to be immutable/persistent• Always addressable in the same way• Fragment Identifiers need the right

semantics

Page 21: The API and APP-ification of the Web

Browse-a-bility• Automatically detect an

adequate handler for Content• Possibly offer choices for

handlers

• Mobile Situation is improving

• Browser Requirements are a problem

• HTML5+JS are becoming general compute canvas

• Huge problem is testing / reliability

• Browsing needs to seemlessly navigate between sites and always be able to handle content automatically

• Android: URI Event Subscription Handlers• IOS: Hard code apps to handle referals

Page 22: The API and APP-ification of the Web

Crawl/Index/Discover-a-bility• Explore and Classify

Pages/Fragments• Index, Rank and Return them

upon Search

• Not under the control of Webmasters

• Early SEO fix “#” Fragment URLS (Indexed by Google)

• Google allows Param Includes (not clear how strong)

• Reality: Chicken/Egg Situation

• In addition to Linking• Meta-data is critical • Page Content is critical • URL Content is critical• “machine identification of content /

value”

Metadata Content

Reputation / Value

Page 23: The API and APP-ification of the Web

Follow-a-bility• RSS Feeds for certain types of

content• Have a Consistent Handle on

“what’s new”

• RSS Now has a limited number of consumers

• “social” is touted as the replacement

• Consistent APIs May be helpful (but don’t exist yet)

• Replacement/Augementation with PubSubHUb?

• Subscribe to a feed• Receive every item on the feed (and not

miss any)• Single Common Standard• It’s Polling but Structured

Page 24: The API and APP-ification of the Web

Script-a-bility• APIs form the basis for

interactions• Events scripted across

sites/platforms

• APIs are starting to become more widespread

• Standardization on oAuth is Helping

• Still a ton of work to do the plumbing

• Still sometimes a little complex for the end user

• Underlying APIs expose functionality• No human UI Interaction needed• Scripting platforms allow simple

interactions to occur in an automated way

Page 25: The API and APP-ification of the Web

Conclusions

Page 26: The API and APP-ification of the Web

Beyond the Web

Live Scribe PenText and Audio$150

Smart NotebookPhoto & TagsNew App$25-30

Mobile

Desktop

Web

Physical

Page 27: The API and APP-ification of the Web

Other Examples: Box + Printers & Scanners

Philips Hue

API Platform + Apps is Key for Mixing Digital and Non-Digital

Page 28: The API and APP-ification of the Web

SPA Helps Align the Web with everything else..

Page 29: The API and APP-ification of the Web

• Vast majority of Apps are still not SPA• Most apps still “decide” between Native first v’s

HTML5 first• Mobile commerce is mostly separated “Web”

commerce• Most APIs feeding mobile are still hard wired into a

single Apps• Auth on mobile and the Web are often still

completely different• Physical devices now linking in

… isn’t this all obvious?Not so much…

Next 2-3 years will see radical change in mainstream usage

Page 30: The API and APP-ification of the Web

Big Ideas to Take Away

1

2

3

SPAs Will see increasing adoption

Potentially Disruptive Change to the Web itself

Lots of work to do to make it seamless & open

Page 31: The API and APP-ification of the Web

Thank you!

[email protected]@njyx, @3scale

We make Awesome API Management Tools:http://www.3scale.net/