NFC recipe binder paired with a smart display

Oct 28, 2026 Last reply: 5 hours ago 4 Replies
Jump to replies (4)

Most kitchen setups I see either leave recipes scattered across bookmarks and cookbooks or rely on shouting voice commands with messy hands. This build takes a different route: a physical binder of printed cards, each one tapped by a phone, and the recipe appears on a smart display. It keeps the tactile joy of flipping through a recipe collection while still getting the benefits of a digital pipeline, and that combination is what makes it stand out to me.



The hardware side is tidy. An Echo Show 8 Gen 2 has been unlocked and runs View Assist. Mealie lives on the maker's local LLM box running Gemma4, and the Mealie integration in Home Assistant is arranged so the pipeline runs through it first. Each card is designed on a PC with a picture of the dish, printed at Walmart photo, then an NFC tag goes on the back with the recipe name written to it. The cards sit in a binder with sports card protective pockets, which seems a smart way to keep everything in one spot without any custom fabrication.



What impresses me most is the cleanup step. The maker says Gemma strips ads and commentary out of online recipes, leaving only the information you actually need, and a photo of a cookbook page was processed the same way. The demo shows a japchae guide with four servings of dangmyeon noodles, a three minute cook time, and step one of four on screen; tapping Next on the touchscreen moves through the preparation. The maker calls the girlfriend approval factor up by twenty points, which sounds about right.



There is one open question: only one recipe is loaded so far, and the day shown was testing and trial and error, so nobody knows yet whether tapping a card might accidentally scan the one behind it in the sleeve. The maker has floated a 3D printed enclosure with laminated recipes as a fallback if that turns into a nuisance.


The decision to reject phone shortcuts is the shrewdest part in my view. A shortcut would be needed per recipe on two phones, so the tag tap wins on maintenance alone. Pairing that with Mealie first in the pipeline also keeps everything under local control, and given the maker's point about protecting recipes in case of fire, holding them on the local box seems a wise call.

Does a recipe need to be sitting in Mealie before the tag will do anything, or can a card be written first and the recipe imported later? Also curious whether anything shows up on the phone screen during the tap, or if it is a single quick action.

On the ordering, recipes are loaded into Mealie before the NFC tag gets used, so the import comes first. On the phone side, tapping brings up an NFC Tag Read prompt, and then the display switches to the recipe guide. So there is a brief confirmation step on the phone before the screen takes over.

One idea worth considering: if the accidental scan of cards behind turns out to be real, going straight to the 3D printed enclosure with laminated recipes early might save rework, since the maker already sees that path. A QR code could also be worth testing on a spare card, as it would be faster and cheaper than tags, though losing the tactile tap feel would be a real cost.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required