How much data a QR code can hold depends on its version and error correction level. I set the highest QR version my recipe app would use by testing 54 made-up recipes, and all of them fit. Then I measured 25 real recipes, and 4 didn't. This is what went wrong, how I fixed it, and what testers of the Android build taught me along the way.
Some context: I build small apps on my own, as a hobby. The one I'm working on now is Sievebook, a recipe book app. It collects recipes from links, screenshots and photos of paper into one book, and it can hand a recipe to someone as a QR code.
Why real recipes didn't fit in a QR code
The biggest mistake was the QR code for sharing a recipe.
Long recipes didn't fit.
The recipe is compressed, encoded as Base45 and stored in the QR code's alphanumeric mode. The higher the version, the more modules (dots) and the more data it holds. I'd capped it at version 25 with error correction level M, based on recipes I made up for testing. All 54 test recipes fit. Then I measured again with 25 real recipes, and 4 of them didn't fit.
I did not see that coming.
Well, of course. If it doesn't work on real data, it doesn't work.
Made-up recipes are short. Real ones are long. It was like practicing against a slow pitch and then striking out against a real pitcher. If your test data doesn't look like the real data, the test doesn't buy you any confidence.
Raising the QR version limit
I wasn't ready to give up on it, so I went back in. The cap is now version 30, and the code always uses error correction level L, which spends less space on redundancy and leaves more for data. Before raising it, I checked that version 25 and version 30 codes scan in both directions, Android phone screen to iPad and back. The longest real recipe I tested (705 characters of steps, 1,965 characters once compressed and encoded) didn't fit at version 25; it now fits at version 26. A beef stew with nearly 20 ingredient lines fits on one code too. When a recipe still doesn't fit, the app says why instead of splitting it.
While building this I kept thinking how flexible QR codes are. Really impressive. Whoever came up with them, I want to know what they had for breakfast.

A long recipe now fits on one QR code
Side note: a QR code's size is set by its version, from 1 (21 × 21 modules) to 40 (177 × 177 modules). The more data, the larger the version you need.
Source: DENSO WAVE, "Information capacity and versions of QR Code" https://www.qrcode.com/en/about/version.html
Tester feedback arrives sooner than you think
As soon as the Android test build went out to testers, feedback came in.
Thank you so much, testers. Seriously, I love you.
Two testers plus my own poking around added up to 6 issues. I fixed all of them that day and the next, and shipped a new build to the testers.
For example, an import sometimes produces a line that's neither clearly an ingredient nor a step, and you couldn't edit that line on the review screen. When a warning jumps you to a field, that field is now highlighted. And before tapping "Paste a link", you couldn't tell what you were supposed to have ready, so there's now one hint line under the button.
Once someone said it, every point was obviously right.
It stung a little. I was grateful anyway.
The person who builds an app knows exactly how to use it, which is why they can't see where others get lost. You never trip on the step in your own hallway.
Side note: in a Google Play test track, feedback from testers doesn't affect the app's public rating. Testers can say what they think without worrying about stars.
Source: Google, "Set up an open, closed, or internal test" https://support.google.com/googleplay/android-developer/answer/9845334
Cooking water comes from the tap
Next, the shopping list.
On the screen that sends a recipe's ingredients to the shopping list, every ingredient starts ticked as "to buy". So "water" was ticked too.
This isn't drinking water. It's the water that goes into a stew or a soup.
Come on. That comes out of the tap.
I'm a tap-water-for-cooking person.

On the send screen, only water starts unticked
I checked 24 real recipes from the web. In 6 of them, a water or hot-water line was ticked. So now the box starts unticked only when the name is exactly "water" or "hot water".
Some people do cook with bought water, of course, and some care about the water for stock or rice. They tick it and it goes on the list. Only the starting tick changed.
Sparkling water is usually something you buy, so I left it alone.
One more shopping list fix. When you added an item, left the quantity empty and picked only the unit "bag", the "bag" disappeared. The app was silently throwing it away. Now the quantity starts at 1.

The quantity box starts at 1, so picking "bag" adds "1 bag"
The warning was right, and it's still not fixed
Last, something I haven't fixed yet.
The app has a "may be missing" check: it warns about ingredients that never appear in any step. I imported one omurice (Japanese omelette rice) recipe and got 7 of those warnings.

7 ingredients that appear in no step (a Japanese recipe)
The page had a whole section, "make the chicken rice", and its steps were dropped completely. The ingredient list still had that section's ingredients, so they showed up as used in no step. 6 of the 7 warnings came from that section.
The chicken rice vanished from the omurice. At that point it's just an omelette.
The last one was the app's own mistake. It didn't treat "tomato ketchup" in the ingredients and "ketchup" in a step as the same thing.
It's nice that the warnings were right. But the import still failed, and I haven't decided how to fix it yet.
The next two weeks
I write these updates every two weeks. Here's what's next:
- Getting the iPhone version out
- Checking whether the 6 fixes worked (does the same feedback come back?)
- Deciding how to import sections like "make the chicken rice"
Thanks for reading.
This post was written with AI assistance; the maker checked every fact.

Top comments (0)