Physical Web Implementation Status
Extends the web's URL to physical objects, enabling interaction without downloading apps via a discovery service.
What is Physical Web Implementation Status?
The Physical Web is an open-source project that extends the web's URL model to physical objects, allowing them to broadcast web links that nearby devices can discover and interact with. It solves the problem of app overload by enabling tap-and-use interactions with smart objects like vending machines, posters, or bus stops without requiring users to download dedicated apps. This creates a scalable system for the Internet of Things (IoT) where everyday objects become seamlessly accessible via the web.
Developers and companies building IoT solutions, smart city infrastructure, retail experiences, or any physical object that needs to provide digital interaction without forcing app installations.
It offers a lightweight, open-standard alternative to proprietary app ecosystems, reducing friction for users and lowering development overhead for creators of smart physical objects.
Overview
The Physical Web: walk up and use anything
Use Cases
Best For
- Creating interactive public installations like museum exhibits or information kiosks
- Building smart retail experiences where customers can access product info via posters or displays
- Developing IoT devices that need to provide configuration or status pages without a custom app
- Implementing wayfinding or location-based services in airports, malls, or campuses
- Prototyping connected physical products quickly using web technologies
- Enabling ad-hoc interactions with rental cars, scooters, or other shared mobility services
Not Ideal For
- Applications requiring secure, authenticated interactions before access (e.g., banking ATMs or private medical devices)
- Systems that need low-latency, real-time control (e.g., industrial IoT or gaming peripherals)
- Projects where users are in areas with poor or no internet connectivity
- Environments dominated by a single vendor's proprietary ecosystem (e.g., Apple HomeKit or Google Nest)
Pros & Cons
Pros
As an open specification released early for experimentation, it avoids vendor lock-in and encourages broad adoption, as highlighted in the 'Open Design' section.
Eliminates the need for users to download dedicated apps for each smart object, reducing friction and scaling interactions, which is core to the project's philosophy.
Supports multiple broadcast methods like Bluetooth Eddystone, mDNS, Wi-Fi Direct, and SSDP, making it adaptable to different environments, as documented in the README.
Addresses the explosion of smart objects with a lightweight discovery service that doesn't require app overhead, ideal for public installations and retail experiences.
Cons
URLs are broadcast openly, which can expose devices to spoofing or malicious links, a security concern not deeply addressed in the documentation.
Requires compatible beacons and user devices with Physical Web clients, limiting adoption in ecosystems without widespread support or standard integration.
Most interactions depend on web content accessed via URLs, which fails in offline scenarios unless local protocols like mDNS are meticulously configured.
Frequently Asked Questions
Related Projects
Physical Web Branding GuidelinesThe Physical Web: walk up and use anything
URL Validator 1, URL Validator 2
IEEE: Enabling the Internet of Thingsby R. Want, B. Schilit, S. Jenson
Video: Introduction to the Physical WebUbiquity Dev Summit 2016
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.