The App We Refused to Build
Six months before launch, our first beta user sent a message that changed our roadmap. She was a conference speaker who'd just tested Feedr with 80 people in a hotel ballroom. Her feedback: 'Please don't make them install something.' That one line became our north star.
The Friction We Saw Coming
When we started building Feedr, the obvious path looked like this: create an app, ask your audience to download it, hope they do it during your talk. We'd seen that movie before. Friends working in events told us the same story every time: 30% of attendees never get the app installed. Another 20% install it and panic because they don't know how to use it. By the time you're five minutes into your session, a quarter of your room is distracted by their phones instead of engaged with your stage.
The old approach asks the audience to meet the tech halfway. We decided to go the other way. What if the tech met the audience where they already were: in a browser. No registration. No account creation. No 'forgot my password' tangent. Just scan a QR code with whatever phone they're holding and they're in the room, ready to listen and comment.
What We Built Instead: Radical Simplicity for Attendees
The real work wasn't building an app; it was stripping everything away until what remained was frictionless enough that a casual attendee wouldn't hesitate to join. That meant browser-based signup was non-negotiable. QR code scan lands you at a live comment stream. You can upvote what matters. You can add your own thought. You react with emoji if you like. That's it. Everything works on whatever device landed in your hand as you walked into the room.
The host's experience is different. We put all the control on iOS and Android. The speaker or event organiser runs the session from their phone: they see the live comment stream, they can pin comments, invite guest moderators, and later review what happened. But the audience? They have no app to manage, no account to remember, no friction. Scan and participate.
Why This Matters More Than It Sounds
Most platforms design for engagement by adding features. We designed for engagement by removing barriers. When a speaker at a university lecture can simply show a QR code and within seconds have genuine real-time interaction, something shifts. The audience isn't thinking about whether they're using the right tool. They're thinking about the talk.
We watched this happen during the first full month after launch. A church preacher in Manchester ran a session with 120 people. She told us that for the first time, she could see what questions her congregation actually wanted answered, live, without raising hands or waiting until coffee breaks. A podcast host used the comment stream to surface topics his listeners wanted unpacked in future episodes. That's not the app doing anything clever. That's a real human need finally having friction removed.
The Host Still Gets Power
Keeping the audience experience minimal doesn't mean giving up control. Hosts working with the Creator tier upward get moderation tools that let them review comments before they appear live. They can pin the comments that matter most. They can invite other people to help moderate. On the Pro tier, they get a proper analytics dashboard that shows what resonated, how long people stayed, which topics sparked the most discussion. All of that happens on the host's device, not cluttering the attendee experience.
We started with the free tier capping sessions at 100 people and 3 per month. That was deliberate. We wanted to see how people used Feedr when the stakes were low, before they committed budget. Creators who run regular sessions scale to 500 audience members and unlimited sessions. Teams running big events go Pro and get the full analytics picture. But every tier keeps one thing sacred: the audience joins via QR, no app, no account, no exceptions.
The Question Nobody Asked
Here's what surprised us: nobody asked for an audience app. Not our beta testers, not our early paid users, not the creators running dozens of sessions each month. They asked for better moderation tools. They asked for analytics. They asked whether they could run sessions with 500 people instead of 100. But they never once said, 'What if we made the audience download something?' That silence told us everything. We'd solved a problem people didn't even know they had, because the problem had become so normal it was invisible.
Building Feedr without an audience app meant we had to be ruthless about what went on the host's phone instead. It meant turning down feature requests that would have added noise to the attendee experience. It meant having actual conversations with speakers and event organisers about what they actually needed to do their job, rather than guessing based on how other platforms work.
When you strip away the requirement to download, install, and log in, what's left? Just you, your audience, and whatever you actually came here to say. Isn't that worth reconsidering what 'engagement' really requires?
Ready to try Feedr by MRVL?
One tap to download. No sign-up wall.