For instance in my lab, we've used QR codes containing YAML to allow any user to load up the appropriate configuration file in a custom built generic-purpose app to interact with a specific tangible system.
A concrete use of that would be as follow— imagine a museum with various installations, all of which you can interact with using your smartphone. Each installation could have a QR code next to it, which you scan from an app— which would then load up the proper UI for you to interact with the installation (the QR code could point to interpretable markup code for building a UI , etc.).
QR codes are great when you need to give your users instant access to more than ~20 characters of information (less than that and is just faster to type) OR non human interpretable information. Unfortunately, most people use them for URLs, which actually fill both these criteria.
For instance in my lab, we've used QR codes containing YAML to allow any user to load up the appropriate configuration file in a custom built generic-purpose app to interact with a specific tangible system.
A concrete use of that would be as follow— imagine a museum with various installations, all of which you can interact with using your smartphone. Each installation could have a QR code next to it, which you scan from an app— which would then load up the proper UI for you to interact with the installation (the QR code could point to interpretable markup code for building a UI , etc.).
QR codes are great when you need to give your users instant access to more than ~20 characters of information (less than that and is just faster to type) OR non human interpretable information. Unfortunately, most people use them for URLs, which actually fill both these criteria.