|
Do you have some user research you could share? I remember thinking about this exact problem (branching conversations, in particular audio), but I couldn't find a reasonable consumption pattern. Looking at how I consume podcasts, it's a completely passive experience - I probably have something in my hands and can't talk. Choosing paths is just too much interactivity. I figured that maybe that's just a wrong mode to look at it and people can consume the whole thing differently, not as a podcast. Ok then, I'm an obsessed power user/fan, I consume the whole thing, all branches. Given how human attention/memory works, that means returning to earlier parts of recording after listening to branch at least some of the time, multiple times experiencing 'where did we start? Let me go back a bit. Oh, that topic was the starting. Let me forward a bit now that I know it'. That's horrible, I think. You were at least more reasonable than me when thinking about it and decided to have only 1 level of branching ; ) In similar vein, what happens when comment gets added after I already listened/how do I know which parts are 'the definite experience'? Unlike previous two issues, those questions are answerable, but I'd still like to hear what you think the answers are! |
Definitely will be modifying the experience to be fully handsfree.
I think the context issue is what can make this actually work or not. Currently it's not built out but my thinking is to have a short context of what was commented on i.e. 10 seconds before the comment. That way you can jump back into the conversation from a new comment left.
I think the context can also be determined by how long it's been since you listened to the last audio - meaning a comment left after a week might have 60s of context vs a comment after 10 mins might just have 5s.
And yes, the UI isn't great at showing what you already listened to now but that needs to be obvious too.