I'm building an app that revolves around users scanning each other's QR codes and sharing information. This would be the main feature of the app, but often times the information in the QR code can get very large, and so it gets harder and harder to scan. In this case, should I encode only a URL in the QR code and pull the information from there? Obviously this approach would require Internet connection.

4 Answers 4


I think it will depend entirely on exactly how much information you would like to store. After a certain point QR's storing the data directly becomes unwieldy if not impossible.

Taking a look at this website: http://www.qrcode.com/en/about/version.html

You can see that as you add more data the QR code must become much bigger.

enter image description here

If you want to store just 500 alpha-numeric characters with Low error correction (may not be preferable if it can be printed) then your QR code will need to be 65 x 65 modules, not pretty but usable. If you need more data than that stored you can have up to 4,296 characters with version 40, the highest supported version, although your QR will look like that 177 x 177 monster on the right of the picture. Any more than that and you have to use a URL to point to your data (or find another encoding than alpha-numeric).

Using a URL also has the benefit of it being dynamic after the QR is created. So if the app generates a new QR evry time this may not be an issue, but if you'd like your users to have their own QR that doesn't change, allowing them to print it or share on social media yet stay updated then you'd want to point to a URL.


This is a good idea but let's go a step further? Why are they exchanging information and what's the frequency?

Can we use Bluetooth and pair them and send it back and forth?

Even better what about nfc? Maybe bump them to send it or bump them to establish a bluetooth connection and send the large data.

But large QR codes is going to be annoying after a point test it on some users and see what they think.

  • Bluetooth might be slower than just scanning a QR code though.
    – Someone
    Jul 9, 2015 at 23:56
  • But what about the frequency you said back and forth sure for one time but if they go back and forth a few times they are already paired. We need to know more about the setting Jul 9, 2015 at 23:57
  • QR Codes can be used over a large sistance where the users aren't near each other. I could send it as Photo, print it on a poster or fax it. NFC and Bluetooth dont seem like the best solution to me
    – BlueWizard
    Jul 10, 2015 at 9:00

Going with the existing approach of your app, without requiring internet, you might consider using multiple QR codes. Two could probably be displayed on a smartphone, for example, at the same time. Beyond two, this might start seeming unwieldy, though.

Putting a URL in a QR code, as you noted, is a commonly used solution. It will scale better to a much larger data size.

Overall, however, the main thing about QR codes is that it is a "standard" that (almost) any QR code reader should be able to consume. Do you really need your app for the communication part, or just to store and use the exchanged data in some way? If your app is focussed on the communication, then there are methods of communicating that are much more scalable to bigger data. These include bluetooth and WiFi, for example.

  • 1
    I think that a QR code would be the quickest exchange of information. The idea is that they scan the code and bam they're done.
    – Someone
    Jul 9, 2015 at 23:56
  • Actually, with something other than QR codes... the exchange of information could happen with a minimum of consent/acknowledgement from the user, or, potentially, even in the background. Scanning a QR code requires you to get both devices out, facing each other, with apps opened, decent lighting for focus/recognition, etc. The main thing about QR codes is some "universality". You could scan a QR code off of a roll of toilette paper, for example.
    – David
    Jul 10, 2015 at 0:15
  • Right, but with something like bluetooth they would have to pair their devices. I'm not finding fault but do you think bluetooth would actually be faster?
    – Someone
    Jul 10, 2015 at 2:15
  • There is also the iOS "Multipeer Connectivity Framework". That might be worth looking into.
    – David
    Jul 10, 2015 at 2:19
  • Hm, so it's just for iOS?
    – Someone
    Jul 10, 2015 at 14:35

I agree with @someone in that QR code is better and faster solution in exchanging some kind of data and agree with @David too ,in that it's not the best for some other data types.

good discussion: What are the key differences between QR codes, NFC, Bluetooth and RFID?

I think you should determine your app scope.for example it's goal can be exchanging short texts,email addresses,contact information and URLs. a minimal app with high functionality with focus on sharing without any need to WiFi or Bluetooth. with acceptation this approach,you wont require Internet connection.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.