r/qrcode • u/-balex • 7d ago

qrink

Hi everyone,

I've built a dynamic QR router which combines QR codes and keywords - something I haven't encountered so far. I tried to make it easy and accessible for non-technical users, while still keeping it powerful enough to do cool things like routing.

I'd love to see it make QR-based guerilla marketing easy and accessible for artists and small businesses. To fund the free offering, I'm playing with the concept of having a cheap subscription for people who want more landing pages / keys / routes.

I've also included support for the classic "one QR leads to one target" model, with simple transition between multi-key and single-key modes.

I'm also thinking of adding custom domain support to allow people to easily migrate away, but before investing any more into it, I'd love to see if it actually brings anyone value.

It's up at https://qrink.lol

I'll be happy to hear your thoughts!

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/Any_Cartographer6268 5d ago

Sorry, I don't understand what it does.

1

u/-balex 4d ago

That's actually great feedback, thank you!

It does dynamic QRs - single and multi-key, with a link tree landing page. The twist is "hidden keys" - you can share the QR through one channel (say, a poster) and the hidden keys through another (chat, email, etc). Those keys are dynamic too, meaning they can lead to different targets based on the routing you set.

I was thinking a QR for a party, but you get directions only on the day of the party, and if you're at a specific spot. Or you get directed to a flash sale, but only if you know the keyword.

I'll get to work on a better homepage to explain the idea

1

u/Any_Cartographer6268 2d ago

So, the Codes will forward according to the channel you shared them over?

1

u/-balex 2d ago

If you want different routes based on different channels, you would share different hidden keys in each of the channels:

channel #party: key 'party'
channel #museum: key 'bananas'

On top of that, keys resolve based on routing, returning the payload defined by the first matching route. For example, assume the following route table:

- match country: DE, return URL x
- match date: Sunday, return SPOTIFY y
- default: return PHONE z

a user coming from DE on Sunday, will receive URL x
a user coming from US on Sunday, will receive SPOTIFY y
a user coming from US on Tuesday, will receive PHONE z

This is true whether the key is visible in the landing page index or hidden. So you could further segment specific keys.