What Should a Maker Put Behind a QR Code at a Madrid Tech Meetup?

A maker’s meetup QR code should open one mobile-friendly page with their name, a one-line maker bio, two or three strongest shipped projects, what they are building now, and one obvious way to continue the conversation.

At a meetup, the scan usually happens while both people are standing, talking, and switching attention. The destination cannot depend on your spoken explanation. It must identify you, load the work in a sensible order, and remain useful when the other person reopens it on the train the next day.

What must be visible immediately after the QR scan?

Your name, what you build, and your strongest relevant project must be understandable before the visitor needs to hunt through the page.

Use a short bio rather than a slogan that only makes sense in conversation. The first project needs a recognisable logo or name, a plain description, and a direct link. If you are attending to find collaborators, put the active build close to the top; if you are meeting customers, lead with the shipped product.

Test the page on mobile data and without being signed in. The QR is merely the transport mechanism; the public page is what earns the second look.

Identity: name, photo if useful, and one-line maker focus.
Proof: a shipped project with a working destination.
Momentum: one clearly labelled project in progress.

What is the quick way to prepare the page with IndieShow?

The quick way is to claim an IndieShow handle, add and reorder your projects in the dashboard, then encode that stable public URL in the QR.

IndieShow’s editor lets you add project logos, descriptions, tags, links, optional metrics, status sections, profile details, social links, and a page colour while viewing a live preview. Build the page first and generate the QR only after the handle is final.

The same indie-show.com/yourname URL works on a badge, a slide, or a phone lock screen. When your priorities change, edit the projects behind it; do not print a new QR for every launch.

Claim your IndieShow pageStart by claiming a handle; after that, the dashboard shows the $15 one-year pass and $30 lifetime option See the editor and publishing options.

How many projects should a meetup page show?

Show enough work to establish a pattern, but make the first three projects the ones you are genuinely prepared to discuss with strangers that evening.

A long catalogue is acceptable when it is grouped by status, because the visitor can stop after the top entries. The mistake is not having many projects; it is giving every experiment equal priority. Move retired work to Archived and keep unfinished work under Building or Working on.

Write descriptions that can restart the conversation without you: what the product is, who it helps, and what someone can do at the link. Avoid unexplained internal project names.

What should the follow-up action be after a Madrid meetup?

The follow-up should be one action aligned with why you attended, such as opening the current product or visiting the professional social profile where you actually respond.

Do not force the visitor through five equal social icons before they can find the project you discussed. Add only the profiles you maintain and make sure the project link from the conversation is present on the page.

If the QR appears on a public badge or slide, never place private contact details or unpublished client material behind it. Treat the destination as permanently shareable.

For project ordering and the single-page rationale, see: how to showcase multiple side projects · link in bio vs. a personal website

How does IndieShow make the QR useful after the event?

IndieShow keeps the QR useful by letting the stable handle point to an updated mix of shipped, building, and archived projects after the meetup ends.

The next morning, move the product people asked about higher, fix any unclear copy, and verify the links. Later launches can replace the current build without invalidating the QR already printed on your material.

That is the practical advantage of using IndieShow behind the code: the physical QR stays fixed, while the public maker page can keep pace with what you are actually building.