webinos - Architecture and Strategy

Preview:

DESCRIPTION

A summary of the architecture discussed at the webinos Open Day. Covers strategy and positioning. Fudamental innovations in data ownership and the evolution or browsers to embedded serversPresented by Nick Allott of UbiApps

Citation preview

ARCHITECTURE WRAPUP

ECOSYSTEM

EcosystemData ownershipBrowsers and ServersConclusions

Platform Positioning

Tizen B2GArduino PI Chrome OS

B2G

Tizen

ChromeOS

Chrome

PhoneGap

Webinos – like Chrome – is a virtualised application environmentNOT and OS in its own right

Web Stores HTML5 missing bits

Manifest Identity – signing Declaration of intent Payment gateway DRM UI integration APIs Portable policy (esp for multi device)

CRX

WGT

vs

Monetisable offline web applications need WGT/CRX or equivalent

OS creating application distribution monopoly

Web stores may create web application monopoly

OS creating networks services

Bookmarks and preferences sync - the Google Alternative

We need open governance framework Where we are in mobile

Chrome: Google dominance Android: Google dominance Webkit: Apple dominance WAC: Operator dominance Meego: Nokia dominance Limo: Samsung dominance Tizen: Samsung-Intel dominance

Adoption requires balance

DANGER!!Operating Systems

are becoming

Control point for application

Control point for monetised services

DATA OWNERSHIP

Inverting Data Ownership

DBApp 1

DBApp 2

DBApp 3

Company 1

Company 1

Company 1

User

User Contact data

User Contact data

User Contact data

User Contact data

Shifting data, under consumers control

Health Care Permissioning and Privacy

DOCTOR 1

DOCTOR 2

TRAINER 2

Micro PZP

Micro PZP

PZH ?

Same scenario for In car telematics and swapping insurers.

Same scenario for Smart Meters.

Distributed Health Monitoring

DOCTOR 1PZH ?

Data sources must be aggregated from different device “owners” - but data still

belongs too user

EVOLVING BROWSERS TO APPSSERVERS ON DEVICES

“Open” Web App Framework

W3C Widgets

Chromium EmbeddedOR Android - WebView

XACML = WAC + Subject = person

W3C + WAC + Webinos

Each of these elem

ents can be improved (e.g.JS

ON

m

anifests etc) but These elements are standardised,

testable agreed and can be deployed now

Web Renderer

Policy

APIs

Contacts

Calend

ar

GeoLocati

on

Orie

ntati

on

Others

Packager

Apps

CRX

Decoupled Browser(Warning disruptive!!)

Standard Browser(Firefox, Chrome, Safari ec..)

Supporting web sockets

Websocket – with domain origin test

Widget URI OR HTTP URI OR FILE URI

Also remote http (normal website)

User grants access of domain to feature

(ala geo-location)

Policy

APIs

Contacts

Calend

ar

GeoLocati

on

Orie

ntati

on

Others

Packager

Apps

Client/BrowserServer

Webinos as a Server

Widget RendererPolicy

APIs

Contacts

Calend

ar

GeoLocati

on

Orie

ntati

on

Others

Packager

Apps

WRAP UP

DLNA for personal data, services and devices

What the demos will show you

WAC/W3C Widget/ Tizen like Application framework (PCs and Mobile)– Running on lots of devices– Open source - open governance

Web on TVs (with mobiles) Web as an Automotive framework Web as an IOT platform (interoperability, ID,

Security) Devices working together

Final Takeaways Convergence is a trend

– What is you platform for developing apps for cross devices

– How will they work together Webinos is OPEN

– Not led by any SINGLE company Webinos is a consumer centric view of privacy

and security Free to join… Free to use...

Questions…