What Your Audience Left Behind: Understanding Feedr's Basic Session Report

The moment we realised hosts needed a memory

When we first launched Feedr, we focused entirely on the live experience. The QR code goes up, audience floods in via their browser, comments stream in real-time, host moderates or pins the best ones. It was electric. But then sessions ended, and hosts found themselves with nothing but a phone screen that had gone dark.

A university lecturer told us she'd received genuinely useful feedback during her lecture, but by the next day, she couldn't remember which comments came from which students or in what order. A conference speaker said he wanted to know which questions got the most upvotes so he could address them in his follow-up email. These weren't edge cases. This was a pattern.

So we built the basic session report. It's free. It's simple. And it's there the moment your session ends.

What actually gets captured, and how you find it

Here's the practical bit. When you end a Feedr session on your phone (iOS or Android), the app generates a report. It contains every comment your audience posted, in the order they appeared, along with the upvote count for each one. That's it. No analytics graphs. No demographic breakdowns. No fancy filtering. Just the raw conversation, ranked by what your audience found most valuable.

You access it from the session history on your host dashboard. Tap the session, and the report loads. It's a snapshot. Some hosts take screenshots. Others copy the text and paste it into their notes. One lecturer we spoke to exports it and uses it as the basis for her next lecture outline. There's no single 'right' way to use it, which is partly why we kept it unfussy.

The report works on all three pricing tiers. Free hosts get it. Creator tier gets it. Pro tier gets it. We wanted that transparency point available to everyone, not just paying customers.

Why we didn't over-engineer it

In the early days, there was internal debate. Should we add export to PDF? Word document templates? Email delivery? Analytics on which comments got pinned? We could have built all of that.

But we kept circling back to a single principle: the host should own their data, and the report should be useful immediately. Not useful after you've learned a dashboard. Useful now.

The basic session report is deliberately bare-bones. It's the conversation your audience had with you. Nothing more. If you're on the Pro tier and you want deeper analytics (comment sentiment, peak engagement times, audience growth across sessions), we have a full analytics dashboard for that. But if you just want to know what was said, the basic report does that in under five seconds.

We've also kept it purposefully simple because it survives. Features that try to do everything often break when something changes. A basic text report, sorted by upvotes, is something we can guarantee will work the same way in six months and six years.

How hosts actually use it (beyond what we expected)

The most interesting uses came from watching what people did after they left the app.

A podcast host uses the session report as guest notes. He runs a live Feedr Q&A with his audience during each episode, pulls the report afterwards, and sends the top-upvoted questions to the guest as a thank-you and a record of what resonated. The guest gets a sense of what the audience cared about most.

A corporate trainer uses it as an attendance log. Since no account is needed, audience members just scan the QR code, but they're embedded in the comment stream if they asked or upvoted anything. It's not a perfect attendance tracker, but it gives her a rough sense of who engaged.

A church ran a sensitivity study where they tested two different versions of a message. They ran Feedr sessions on consecutive weeks and compared the comment reports to see which framing generated more positive feedback. Basic. Effective.

None of these use cases were things we designed for explicitly. They emerged because the report was accessible and real.

What it doesn't do (and why that matters)

Let me be clear about the edges. The basic session report doesn't filter by audience member name or email, because audience members don't have accounts. They join via QR, post as themselves or anonymously, and that's it. The report captures their words, not their identity beyond what they chose to share in their message.

It doesn't automatically send anywhere. You have to pull it manually from the app. We've had requests for scheduled email delivery, but we haven't built it because we've watched too many email notification features go unused. If you want it, you get it. If you don't care, you don't have to look.

It doesn't include timing data at a granular level. You see the comments in order, which tells you when something was said relative to other things, but not the exact timestamp. That's intentional. For most hosts, knowing that the top three questions came early, middle, and late in the session is enough information. If you need deeper temporal analysis, that's what the Pro analytics dashboard handles.

The value of simplicity after the noise stops

I think the session report matters because it exists at the moment when the live energy ends and the real work begins. Your event is over. The audience has logged out. The QR code is gone. Now you're alone with what they said to you.

That conversation deserves to be preserved in a way that's as straightforward as the conversation itself was. Not buried in an interface. Not locked behind another login. Not cluttered with metrics that don't apply to what you're trying to understand.

A basic session report is almost boring. It's text and numbers. It's the opposite of flashy. But boring is the right texture for something you're going to come back to weeks later, looking for a specific insight or proof that someone asked about something important.