<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[QR types & use cases]]></title><description><![CDATA[Social profiles, WiFi, vCards, payments, menus, events — which type fits which job.]]></description><link>https://qrcodestack.com/community/category/6</link><generator>RSS for Node</generator><lastBuildDate>Sun, 30 Aug 2026 14:36:28 GMT</lastBuildDate><atom:link href="https://qrcodestack.com/community/category/6.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 29 Aug 2026 15:10:19 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[A contact QR that survives changing jobs]]></title><description><![CDATA[Most contact QR codes are static vCards: name, title, company, phone and email encoded straight into the pattern. They work offline, forever, with no account behind them — and they are frozen the moment they are printed.
That is fine for a conference badge. It is a problem for a business card you ordered 500 of, if you change your title, your number, or your employer.
The two approaches
Static vCard. The contact details live in the code. Scanning it offers to save a contact immediately, with no internet connection. Nothing to maintain, nothing to pay for, nothing you can ever change.
Dynamic. The code points at a short URL that serves your details. Scanning it opens a page that offers the same contact download. You can update your title or number afterwards and every printed card follows. It needs a working connection at scan time, and it depends on the link continuing to resolve.
Which to choose
Ask how long the card will be in circulation and how likely the details are to change. A card you reprint every year with a landline that never moves: static is simpler. A card you hand out for three years with a mobile number and a title that might change: dynamic pays for itself the first time you get promoted.
What actually happens on the phone
Saving a contact from a QR code is a two-step action on both major platforms — the phone shows the details, then the person confirms. There is no way to write to someone's address book silently, and you should be suspicious of anything claiming otherwise.
Keep the payload small. A vCard with a long photo embedded produces a dense code that scans badly at business-card size, which is exactly the size constraint you cannot escape here.
Put a name next to it
"Scan to save my details" next to the code roughly doubles the number of people who do. A bare square on a card reads as decoration.
]]></description><link>https://qrcodestack.com/community/topic/6/a-contact-qr-that-survives-changing-jobs</link><guid isPermaLink="true">https://qrcodestack.com/community/topic/6/a-contact-qr-that-survives-changing-jobs</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Sat, 29 Aug 2026 15:10:19 GMT</pubDate></item><item><title><![CDATA[WiFi QR codes for a café or guest network]]></title><description><![CDATA[A WiFi QR code encodes the network name, the security type and the password, so a phone can join without anyone reading a password off a chalkboard. Worth getting the details right, because this is one of the few QR types where a mistake locks people out rather than sending them somewhere wrong.
Use your guest network, not your main one
Put the code on the guest SSID. Anything encoded in a QR code on a public table is, by definition, public — a photograph of it is a permanent copy of the password. On your main network that is a real problem; on an isolated guest network it is simply how it works.
Most business routers can run a guest network that reaches the internet but not your till, your printer, or your back-office machines. If yours can, use it.
The details that trip people up
Security type must match. WPA2 and WPA3 are not interchangeable in the encoding. If the code is built for the wrong one, phones will try and fail with an unhelpful error.
Hidden networks need to be marked as hidden. Otherwise the phone looks for a broadcasting network, finds nothing, and gives up.
Special characters in the password. Semicolons, colons, backslashes and quotes have meaning inside the WiFi payload. A password containing them needs escaping. If you have a choice, pick a password without them — it removes a whole class of failure.
Case matters, in both the network name and the password.
Rotating the password
The moment you change the password, every printed code becomes a support conversation. Two ways to live with that:

Change it rarely, on a schedule you control, and reprint deliberately
Point the code at a short URL that opens a page with the current details, which you can update without reprinting — slower for the guest by one tap, but it never goes stale

Put it where someone sitting down can reach it
Table tents and the back of the menu work. A sign behind the counter does not — people connect after they sit, not while they order.
]]></description><link>https://qrcodestack.com/community/topic/5/wifi-qr-codes-for-a-café-or-guest-network</link><guid isPermaLink="true">https://qrcodestack.com/community/topic/5/wifi-qr-codes-for-a-café-or-guest-network</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Sat, 29 Aug 2026 15:10:19 GMT</pubDate></item><item><title><![CDATA[Putting your Instagram profile on a QR code (for a shop window or counter)]]></title><description><![CDATA[The problem worth solving here is not "how do I make a QR code". It is that people walk past your shop, like what they see, and have no way to keep it. Typing a handle into a phone in the street is enough friction to lose most of them.
What to point it at
Your public profile URL — instagram.com/yourhandle. Not a post, not a story, not a link-in-bio page. Someone standing outside your door wants the account, not a specific photo from last Tuesday.
Static or dynamic?
Both work. The question is whether you will ever want to change where it goes.

Static encodes the profile URL directly. It works forever, needs no account, and can never be changed.
Dynamic points at a short URL that redirects. You can change the destination later — to a campaign page during a sale, then back — and you can see how many people actually scanned it.

If the code is going on a window sticker that stays up for two years, dynamic is worth it for the one time you want to redirect it without reprinting.
Where it actually gets scanned

At eye level near the door, not at knee height on the glass
On the counter, where people wait anyway
On the receipt or the bag, which travels home with them
Not on a moving vehicle, and not on the floor

Say what it is
A bare code gets ignored. "Follow us" plus the code beats the code alone, every time. People scan when they know what they are getting.
One honest caveat
Scan counts are not follower counts. A dynamic code will tell you how many people scanned and roughly where from — it cannot tell you who followed, because that happens inside an app we have no visibility into. Compare your scan numbers against your follower growth over the same period and treat the gap as the cost of the handoff.
]]></description><link>https://qrcodestack.com/community/topic/4/putting-your-instagram-profile-on-a-qr-code-for-a-shop-window-or-counter</link><guid isPermaLink="true">https://qrcodestack.com/community/topic/4/putting-your-instagram-profile-on-a-qr-code-for-a-shop-window-or-counter</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Sat, 29 Aug 2026 15:10:19 GMT</pubDate></item></channel></rss>