Moving the Web into the Physical World with Beacons
summary
Prototypes built with Ruby, Rails and JavaScript demonstrate beacons broadcasting URLs to trigger local web apps: a bus stop prototype shows next departures by proximity, an airport prototype lists flights and lets users subscribe to status updates. Technical specifics: Bluetooth Low Energy, iBeacon vs Eddystone payloads, $10–$50 per beacon, typical range 10–30m (up to 50m). User tests report experiences as instant, personal and easy but raise device dependence, battery and payment skepticism.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:33Scenario
- 1:47Beacons
- 2:35Locationbased services
- 3:06QR codes
- 3:37Technical facts
- 4:23Major players
- 5:26What does it mean
- 6:42Bus stop prototype
- 7:16Beacon notification
- 7:59Web app
- 8:47Other uses
- 10:24Master Thesis
- 11:26Prototyping Status
- 11:36Statistics
- 11:54Chrome
- 12:39Questions
- 13:06Beacons are web technology
- 13:41You dont need an app
- 14:00Beacons are really good
- 14:25Conclusion
- 16:20Apps
- 18:05URL Shortener
related talks
20mBeacons, Eddystone and the Physical Web
21mInteracting with the Physical Web
21mHow to Prototype an Airport
33mBuilding the Physical Web together
08mPhysical Web
46mSpinning the physical web with android and bluetooth 5
38mThe Physical Web: building on top of the open web
34mEddystone™, the open beacon format from Google (en)
