It’s super easy. Simply place a Physical Web beacon near the person, place, or thing where users might want more information, then use PHY.(dot)net to point the beacon to destination page/content or create your own on the platform with info or an action the users might want relating to the beacon placement. If you later want to promote or change your location specific content just log in to PHY.net from wherever you are and change it. As soon as your changes are made, your changes are instantly* seen by your users. If you move your location moves like a retail store for instance, simply move the beacon to the store with everything else.
Content is usually designed by our users to be location specific which means beacon specific but it's really up to you as to what serves your use case best.
This simplicity is the single biggest advantage for the Physical Web deployments over iBeacons, which typically take skilled installers to “pair” with individual beacons during setup and “tune” the beacon network and the environment which it's placed in. It usually costs more to deploy, install and maintain an iBeacon than to buy it.
*if using Chrome, Nearby or other physical web browsers besides one built using our Nearby SDK like our PHY.net Browser, the changes may take ~5 minutes or more to show up. This is because some Physical Web browsers choose to cache destination url content based on app session or metadata server configurations.