• Share
  • Email
  • Embed
  • Like
  • Private Content
The API and APP-ification of the Web
 

The API and APP-ification of the Web

on

  • 3,781 views

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

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

Statistics

Views

Total Views
3,781
Views on SlideShare
3,495
Embed Views
286

Actions

Likes
6
Downloads
59
Comments
0

11 Embeds 286

http://www.3scale.net 137
https://twitter.com 74
http://jamesfeltonkeith.com 44
http://librosweb.es 7
http://architects.dzone.com 6
http://wpcomwidgets.com 5
http://www.pinterest.com 5
http://tweetedtimes.com 4
http://www.spundge.com 2
http://ifldev1.dynhost.nicta.com.au 1
http://python.dzone.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

The API and APP-ification of the Web The API and APP-ification of the Web Presentation Transcript

  • The API- & APP-ificationof the WebSteven Willmott3scale networks@3scale - http://www.3scale.net(and possibly everything else)
  • This Work is Licensed Under Creative CommonsCreative Attribution 3.0
  • “Welcome to the App-Economy”“What will win? Apps v’sHTML(5) ”“The Death of the OpenWeb?”
  • Some Hyperbole but..There is probably something going on…
  • And some of has to do withSPAs…
  • Single Page Web ApplicationsServer (REST / JSONAPI)ButtonsInfinite ScrollPush UpdatesEmber.jsAngular.jsBackbone.js…Single HTML Page & URL Per Pagemany Pages per Site / AppPages ServerWholeServerSPAs Serve a Single Page of HTMLand use in page controls to operatedynamically
  • e.g….(From http://www.angularjs.org)
  • 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, ModernBrowsers Needed, Framework overload…– (and a few others we’ll mention later)
  • Examples
  • Evernote: The Platform Imperativee.g. Evernote“Capture Everything - Access anywhere”MobilePlatformsDesktopPlatformsWebBrowsersTopApps
  • App Like User Experiencehttps://www.evernote.com/Home.action#st=p&n=acfb0b6e-8681a424246chttps://www.evernote.com/Home.action#b=7bc900cc5876&st=p&n=a6d5-8681a424246cSingle PageParam Driven
  • Zendesk: Speed and Slickse.g. ZendeskReal TimeUpdatesNo PageRedrawsEffectively a .jsAppAPI UserCommunity• App.js Example• Same Agility for All• More Robust API• 90+ Integrations
  • Value…• Platform strategy• Uniform user experience• Fast, Responsive, No Page Reloads, Push• API Enables 3rd Party Use, Javascript componentsmake that use easier• Both also have: dev communities & mobile apps
  • Adoption and Impact on the Web
  • Who Will Adopt?(assuming the tech works)Mobile Natives>> SAAS>> Ecommerce>> ContentImpact ismoreAnd moreradical
  • But there are issues…Links?Referencing?Crawling &Indexing?UIFragmentation?…Openness?RSSFollowing?Discovery?SEO?
  • Adoption Complexity & DisruptionLinkingReferencingSeamlessBrowsingDiscoveryMobile NativeBusinessesOS Specific UI is App Specific App StoreSAAS Businesses In app is fineUI is oftenSpecificPrimary DomainOnlyeCommerceBusinessesItems need to beaddressablefrom anywhereCommon CheckOut MetaphorsAre usefulMostly forPrimary DomainContent BusinessesNeeds toaddressablefrom anywhereExpectConsistent WebUISEO is Critical
  • 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
  • Technical ChallengesChanging Architecture of the Web
  • Link-a-bility• Hyperlinking• Fragment Referencability• Web Links Still Work• Fragments Still Work• Param Schemes Needto be Complete• Avoid HeaderInformationhttp://www.gluecon.com/….• Links need to be immutable/persistent• Always addressable in the same way• Fragment Identifiers need the rightsemantics
  • Browse-a-bility• Automatically detect anadequate handler for Content• Possibly offer choices forhandlers• Mobile Situation isimproving• Browser Requirementsare a problem• HTML5+JS are becominggeneral compute canvas• Huge problem is testing /reliability• Browsing needs to seemlessly navigatebetween sites and always be able tohandle content automatically• Android: URI Event Subscription Handlers• IOS: Hard code apps to handle referals
  • Crawl/Index/Discover-a-bility• Explore and ClassifyPages/Fragments• Index, Rank and Return themupon Search• Not under the control ofWebmasters• Early SEO fix “#” FragmentURLS (Indexed by Google)• Google allows ParamIncludes (not clear howstrong)• Reality: Chicken/EggSituation• In addition to Linking• Meta-data is critical• Page Content is critical• URL Content is critical• “machine identification of content /value”Metadata ContentReputation / Value
  • Follow-a-bility• RSS Feeds for certain types ofcontent• Have a Consistent Handle on“what’s new”• RSS Now has a limitednumber of consumers• “social” is touted as thereplacement• Consistent APIs May behelpful (but don’t exist yet)• Replacement/Augementation with PubSubHUb?• Subscribe to a feed• Receive every item on the feed (and notmiss any)• Single Common Standard• It’s Polling but Structured
  • Script-a-bility• APIs form the basis forinteractions• Events scripted acrosssites/platforms• APIs are starting to becomemore widespread• Standardization on oAuth isHelping• Still a ton of work to do theplumbing• Still sometimes a littlecomplex for the end user• Underlying APIs expose functionality• No human UI Interaction needed• Scripting platforms allow simpleinteractions to occur in an automated way
  • Conclusions
  • Beyond the WebLive Scribe PenText and Audio$150SmartNotebookPhoto & TagsNew App$25-30MobileDesktopWebPhysical
  • Other Examples:Box + Printers & ScannersPhilips HueAPI Platform + Apps is Key for MixingDigital and Non-Digital
  • SPA Helps Align the Web witheverything else..
  • • Vast majority of Apps are still not SPA• Most apps still “decide” between Native first v’sHTML5 first• Mobile commerce is mostly separated “Web”commerce• Most APIs feeding mobile are still hard wired into asingle Apps• Auth on mobile and the Web are often stillcompletely different• Physical devices now linking in… isn’t this all obvious?Not so much…Next 2-3 years will see radicalchange in mainstream usage
  • Big Ideas to Take Away123SPAs Will see increasing adoptionPotentially Disruptive Change tothe Web itselfLots of work to do to make itseamless & open
  • Thank you!steve@3scale.net@njyx, @3scaleWe make Awesome API Management Tools:http://www.3scale.net/
  • References• http://blog.stevensanderson.com/2012/08/01/rich-javascript-applications-the-seven-frameworks-throne-of-js-2012/• http://www.avc.com/a_vc/2012/12/rethinking-mobile-first.html• http://pandodaily.com/2012/12/06/html-javascript-and-the-app-ification-of-the-web/