Why we made the QR code the whole entry point
A church pastor messaged us three weeks after launch. He'd used Feedr at a Sunday service with 200 people. 'I didn't have to ask anyone to download anything,' he wrote. 'They just scanned and started commenting.' That single message crystallised something we'd suspected during development: the friction of asking an audience to install software, create accounts, remember passwords, is the thing that kills real-time engagement before it even starts.
The moment we realised app downloads were the problem
Before Feedr, I spent two years running live Q&A sessions at tech conferences using other platforms. Every single time, the host would say: 'Please download the app from the App Store' and watch the room collectively... not do it. A few people would, sure. But the majority sat there. Some pulled out their phones and got distracted. The engagement rate was always miserable. I kept thinking: this shouldn't be hard. An audience member shouldn't need to prove they own a smartphone, find the right app among hundreds, wait for a download, create login credentials. They should just join and participate. So when we started building Feedr, the QR code wasn't a feature; it was the whole point. No downloads. No sign-ups. No friction. You scan, you're in, you can comment within seconds.How a QR code becomes your entire onboarding
The technical challenge was simpler than the psychology. A QR code is just a URL. The real work was making sure that URL did exactly one thing: get an audience member into a live comment stream in under three seconds. We spent weeks testing the experience. What happens if their phone is in low-light? What if they're on a slow connection? What if 150 people scan the same code within 30 seconds? On the host side, running Feedr on iOS or Android, the session is live within moments of going online. The audience scans the code the speaker projects, and instantly they see the live comment stream. No waiting. No confirmation screens. No 'please enter your name' forms that slow things down. One of our early beta users, a lecturer at a polytechnic, told us the first time she used it, a student scanned the code during her lecture and posted a question within 15 seconds. She answered live. Five other students then asked follow-up questions. The engagement that session was something she'd never seen before in the room. She attributed it entirely to the fact that scanning took less thought than opening an email.What the QR code lets you do that other platforms don't
Because there's no account system, there's no registration delay. Because there's no app requirement, the barrier to entry is literally as low as 'can you point your phone camera at something.' This matters more than it sounds. We've watched podcasters use Feedr in their studios during live recordings. The QR code sits on a graphic for the entire episode. Listeners who hear about it can jump in at any moment without prepping their device beforehand. We've watched conference speakers project a QR code on their closing slide and watch real-time comments flow in while they're packing up their laptop. We've watched church preachers use it during services where 85 per cent of attendees are over 60 and would normally never engage with 'digital tools.' The audience comment stream is live for the host on their phone. They can see upvotes in real time, which means they can spot which questions or comments the room cares about most. On Creator or Pro tiers, hosts can pin comments to keep important ones visible, moderate submissions before they appear, and even assign a guest moderator with a special invite link. But the foundation stays the same: the audience experience is zero friction.The constraints that shaped the design
Keeping things simple meant saying no to a lot. We didn't build video conferencing into Feedr. We didn't build polls or word clouds (though the backend work for those is running in the shop). We didn't require audience members to create accounts or even give their names, though the host can see how many people are active in the stream. Those constraints were deliberate. Every feature we add is a tap, a decision, a moment where someone might close the browser tab instead. The QR code only works because the rest of the experience matches its simplicity. You scan, you see comments, you post. That's the loop. If we'd added friction on the other end, we'd have broken the whole thing. The free tier gives you three sessions per month and room for up to 100 audience members, which is enough for someone testing the format. Creator tier gets you unlimited sessions and space for 500 people. Pro adds an analytics dashboard so you can see which comments drove the most upvotes, when people were most active, what the session felt like in aggregate. But again: those are add-ons. The core experience, the QR and the comment stream, works the same on every tier.What we learned about audiences from watching thousands scan
After six months of seeing people use Feedr in real rooms, a pattern emerged. Audiences behave differently when joining is effortless. They ask more questions. They disagree more openly (though we built moderation tools so hosts can manage that). They upvote each other's comments, which means you get real signals about what the room cares about. One lecturer told us that Feedr comments revealed gaps in her explanation that she'd never heard about before. Students would ask clarifying questions in the stream instead of raising their hand or staying silent. A podcaster said listeners were commenting on topics he hadn't expected, which gave him ideas for future episodes. A conference speaker mentioned that the upvoted comments became the basis for a blog post afterwards. The QR code did that. Not because it's clever technology, but because it removed the one thing that would have stopped people from participating in the first place. You don't need an app to change how an audience behaves. You just need to make it easy.The QR code works because it respects the fact that most people just want to be heard, and they shouldn't have to jump through hoops to do it. Does your event or presentation format leave room for that kind of spontaneous feedback right now?