2 added 377 characters in body
source | link

There's no guidelines in Material for QR codes. And there will never be

And as we're at it, no mobile framework or guideline will ever have it either!

See, QR codes are meant as an easy way to transmit information from real, physical world to a virtual dimension. Basically, a bridge that joins the information gap between the physical world and its binary representation as data. It's just a type of barcode that started in Japan to transmit information from car parts to computers without the need of inputting lots of info. I'm explaining this so you can visualize it:

car part(physical) --> database (virtual/computational)
magazine ad (physical) --> mobile app (virtual/computational)
business card (physical) --> website (virtual/computational)

However, you're already in virtual world, and the info you want to transmit is in the same virtual plane or dimension. Just picture a common QR user flow:

user sees QR code --> takes picture --> phone scans the information and actacts accordingly --> user gets output 

Now your user case:

user is using your app --> user sees QR code --> user has the QR code in her phone, so she doesn't know how to scan that code --> ??

Additionally, the teachers will need an additional step for something that quite probably could be easily automated. Even if the idea is to add the QR code just in case the teacher want to print it for her classes, there's no need to display it in the app. As human beings, we can't get any info from that code, so it will only add friction and nothing else

In short

No need to overcomplicate something as easy as this: just show a link or button (maybe a FAB?) and problem solved

There's no guidelines in Material for QR codes. And there will never be

And as we're at it, no mobile framework or guideline will ever have it either!

See, QR codes are meant as an easy way to transmit information from real, physical world to a virtual dimension. Basically, a bridge that joins the information gap between the physical world and its binary representation as data. It's just a type of barcode that started in Japan to transmit information from car parts to computers without the need of inputting lots of info. I'm explaining this so you can visualize it:

car part(physical) --> database (virtual/computational)
magazine ad (physical) --> mobile app (virtual/computational)
business card (physical) --> website (virtual/computational)

However, you're already in virtual world, and the info you want to transmit is in the same virtual plane or dimension. Just picture a common QR user flow:

user sees QR code --> takes picture --> phone scans the information and act accordingly --> user gets output 

Now your user case:

user is using your app --> user sees QR code --> user has the QR code in her phone, so she doesn't know how to scan that code --> ??

In short

No need to overcomplicate something as easy as this: just show a link or button and problem solved

There's no guidelines in Material for QR codes. And there will never be

And as we're at it, no mobile framework or guideline will ever have it either!

See, QR codes are meant as an easy way to transmit information from real, physical world to a virtual dimension. Basically, a bridge that joins the information gap between the physical world and its binary representation as data. It's just a type of barcode that started in Japan to transmit information from car parts to computers without the need of inputting lots of info. I'm explaining this so you can visualize it:

car part(physical) --> database (virtual/computational)
magazine ad (physical) --> mobile app (virtual/computational)
business card (physical) --> website (virtual/computational)

However, you're already in virtual world, and the info you want to transmit is in the same virtual plane or dimension. Just picture a common QR user flow:

user sees QR code --> takes picture --> phone scans the information and acts accordingly --> user gets output 

Now your user case:

user is using your app --> user sees QR code --> user has the QR code in her phone, so she doesn't know how to scan that code --> ??

Additionally, the teachers will need an additional step for something that quite probably could be easily automated. Even if the idea is to add the QR code just in case the teacher want to print it for her classes, there's no need to display it in the app. As human beings, we can't get any info from that code, so it will only add friction and nothing else

In short

No need to overcomplicate something as easy as this: just show a link or button (maybe a FAB?) and problem solved

1
source | link

There's no guidelines in Material for QR codes. And there will never be

And as we're at it, no mobile framework or guideline will ever have it either!

See, QR codes are meant as an easy way to transmit information from real, physical world to a virtual dimension. Basically, a bridge that joins the information gap between the physical world and its binary representation as data. It's just a type of barcode that started in Japan to transmit information from car parts to computers without the need of inputting lots of info. I'm explaining this so you can visualize it:

car part(physical) --> database (virtual/computational)
magazine ad (physical) --> mobile app (virtual/computational)
business card (physical) --> website (virtual/computational)

However, you're already in virtual world, and the info you want to transmit is in the same virtual plane or dimension. Just picture a common QR user flow:

user sees QR code --> takes picture --> phone scans the information and act accordingly --> user gets output 

Now your user case:

user is using your app --> user sees QR code --> user has the QR code in her phone, so she doesn't know how to scan that code --> ??

In short

No need to overcomplicate something as easy as this: just show a link or button and problem solved