google /physical-web

The Physical Web: walk up and use anything

★ 5,957⑂ 646👁 3⑃ 561● 393▤ 17
JavaApache-2.0Created 2014-09-30physical-web.org
下载:Android Client 0.2.1android-0.2.1 ↓0.2.12016-09-01
+0
日增长
5,957
stars
646
forks
3
watchers
561
prs
393
issues
17
releases

README

The Physical Web



The Physical Web is an effort to extend the superpower of the web - the URL - to everyday physical objects. Our premise is that you should be able to walk up to any “smart” physical object (e.g. a vending machine, a poster, a toy, a bus stop, a rental car) and interact with it without first downloading an app. The user experience of smart objects should be much like links in a web browser, just tap and use.

At its base, the Physical Web is a discovery service: a smart object broadcasts relevant URLs that any nearby device can receive. This simple capability can unlock exciting new ways to interact with the Web.





 Why URLs?

The URL is the fundamental building block of the web, giving remarkable flexibility of expression. It can be:

 a web page with just a tiny paragraph of info
 a fully interactive web page
 a deep link into a native application

 Why We're Doing This
The number of smart objects is going to explode, both in our homes and in public spaces. Much like the web, there is going to be a long tail of interactivity for smart objects. But the overhead of installing an app for each one just doesn’t  scale. We need a system that lets you walk up and use a device with just a tap. The Physical Web isn’t about replacing native apps; it’s about allowing interaction for the times when native apps just aren’t practical.

 Open Design
The Physical Web must be an open standard that everyone can use. This can’t be a product that is locked down by a single company. Like many web specifications, this is an open source design that is being released early so everyone can experiment and comment on it. There is much to discuss and add to this specification.

 Contents
 Introduction/FAQ - Most common questions
 Getting started guide - How you can try it out
 Technical overview
 Eddystone - Repo with the specification for the beacons themselves
 mDNS support - How to use mDNS instead of Bluetooth to broadcast public URLs and local data
 Wi-Fi Direct support - How to use Wi-Fi Direct instead of Bluetooth to broadcast local data
 SSDP support - How to use SSDP instead of Bluetooth to broadcast URLs
 Branding guidelines
 Different Physical Web clients
     Android  
     IOS  
     Node  This is a minimal client meant for building utilities

Top issues

Latest release

Android Client 0.2.1 android-0.2.1 Pre-release 2016-09-01
Create demos section with FatBeacon and Wi-Fi Direct demos
Bug fixes
Removed beacon configuration

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON