https://github.com/google/physical-web

The Physical Web: walk up and use anything
https://github.com/google/physical-web

Last synced: 19 days ago
JSON representation

The Physical Web: walk up and use anything

• Host: GitHub
• URL: https://github.com/google/physical-web
• Owner: google
• License: apache-2.0
• Archived: true
• Created: 2014-09-30T18:32:14.000Z (about 10 years ago)
• Default Branch: master
• Last Pushed: 2018-12-05T21:09:11.000Z (almost 6 years ago)
• Last Synced: 2024-05-08T21:30:48.477Z (6 months ago)
• Language: Java
• Homepage: http://physical-web.org
• Size: 31.9 MB
• Stars: 6,004
• Watchers: 582
• Forks: 666
• Open Issues: 93
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

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.



[![Build Status](https://travis-ci.org/google/physical-web.svg?branch=master)](https://travis-ci.org/google/physical-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](http://github.com/google/physical-web/blob/master/documentation/introduction.md) - Most common questions

* [Getting started guide](http://github.com/google/physical-web/blob/master/documentation/getting_started.md) - How you can try it out

* [Technical overview](https://github.com/google/physical-web/blob/master/documentation/technical_overview.md)

* [Eddystone](https://github.com/google/eddystone) - Repo with the specification for the beacons themselves

* [mDNS support](https://github.com/google/physical-web/blob/master/documentation/mDNS_Support.md) - How to use mDNS instead of Bluetooth to broadcast public URLs and local data

* [Wi-Fi Direct support](https://github.com/google/physical-web/blob/master/documentation/WiFi_Direct_Support.md) - How to use Wi-Fi Direct instead of Bluetooth to broadcast local data

* [SSDP support](https://github.com/google/physical-web/blob/master/documentation/ssdp_support.md) - How to use SSDP instead of Bluetooth to broadcast URLs

* [Branding guidelines](https://github.com/google/physical-web/blob/master/documentation/branding_guidelines.md)

* Different Physical Web clients

    * [Android](android)  

    * [IOS](ios)  

    * [Node](nodejs)  This is a minimal client meant for building utilities