Why we built the QR code entry for Feedr, and why it matters

The friction problem nobody talks about

Here's the thing about asking 200 people to do something extra: most won't. Even if it takes 30 seconds. We learned this the hard way when we were researching the market. We sat in on five different events. At one conference breakout session with 180 people, the speaker asked the room to text a number for live polls. Exactly 23 people did. At a university lecture, the professor shared a URL for comments. Maybe 40 students out of 300 opened it.

The friction isn't just inconvenience. It's cognitive load. People are already focused on the content. Asking them to switch context, download an app, create a password, confirm an email, then come back and participate is asking too much. We wanted Feedr to be the opposite of that experience.

So we built around the QR code. Not because QR codes are trendy. But because they're frictionless. Your phone has a camera. Your camera reads QR. Your browser opens. You're in. No account, no app, no second step. Just participation.

What actually happens when someone scans

When an audience member points their phone at the QR code the host displays, they're sent straight to a live comment room in their browser. Not an app. Just the web. They see the live feed of comments from everyone else in the room, they can type and post, they can upvote comments they agree with, and on Creator tier and above, they'll see emoji reactions. That's it. Within two seconds of scanning, they're part of the conversation.

The host, meanwhile, is managing the session from their phone or tablet, running the app on iOS or Android. They're seeing every comment come in, they can pin the ones that matter, moderate if they need to (on paid tiers), and watch engagement happen in real-time. The audience member has zero awareness of which tier the host is using. They just experience a clean, simple comment stream.

The QR code itself is unique to that session. Host starts a new session, gets a new code. We've intentionally kept it that way because it prevents confusion and accidentally merging two separate events into one room.

Why no accounts changed what we could offer

Removing the account requirement wasn't just nice-to-have. It shaped our entire product philosophy. Because we're not storing attendee profiles, we're not collecting email addresses for follow-up marketing. The host gets a basic session report on the free tier showing comment counts and top upvoted items. That's useful for a speaker who wants to know what resonated. On the Pro tier, there's a full analytics dashboard. But it's about the content and engagement patterns, not individual user data.

This also means we move fast. We launched the free tier with 3 sessions per month and a 100-person audience cap. No artificial waiting lists, no email verification bottlenecks. A speaker can test it today. If they like it and need more room, they upgrade to Creator for unlimited sessions and 500 audience members. If they're running a massive event, Pro handles unlimited audience with the analytics dashboard included.

The tradeoff is that hosts are device-based. Your identity on Feedr is tied to the phone or tablet you're using to run sessions, not to an account. It sounds like a limitation until you realise how much simpler that is. No password recovery. No account migration headaches. No 'verify your email' emails cluttering inboxes.

A moment from launch week

During our beta, a podcaster ran a live recording with about 80 listeners. She scanned the QR code on screen, the audience joined in seconds, and comments started flowing. One listener asked a question she'd been wondering about for months. She answered it live. That answer, plus the audience's follow-up comments, became the most engaging 12 minutes of the episode.

After the recording, she messaged us. 'If I'd forced them to download something, I'd have lost half the room before we got started.' She was right. That's the QR code's real job. It's not trendy. It's not a gimmick. It's the thing that keeps people in the room when they could easily leave.

What it isn't (and why that matters)

Feedr isn't a video conferencing tool. The audience can't see or hear each other. They're not joining a Zoom call. They're posting comments and upvoting in a shared space, and the host is reading and responding in real-time. It's asynchronous in the best way. A listener can take their time composing a thought. Others can upvote good questions before the host answers. The conversation feels different because it is.

We're also not building polls or word clouds or any of the fancy visual effects some platforms offer. There's a reason. We're trying to stay out of the way. The host needs to focus on their content. The audience needs to focus on participating. Anything that distracts from that conversation is noise.