Playlists and bookmarks look like small, almost obligatory features — the kind every content app has. But in an app people open daily for a few quiet minutes, they're doing more work than their size suggests.
A bookmark in Koinonia isn't just a saved link — it's how someone returns to a message that spoke to them weeks later, or picks up a Bible reading plan exactly where they stopped. A playlist isn't just a queue — it's often a deliberate collection, built around a season of someone's life, a theme they're studying, or a minister they keep returning to.
We've seen playlists used in ways that weren't part of the original design intent at all — someone building a themed collection to share informally with a small group they lead, effectively turning a personal organisation tool into a lightweight teaching resource. We didn't build sharing for that use case explicitly, but the fact that people found a way to make playlists serve that purpose told us the underlying feature was solving a real need, not just a checkbox on a features list.
Because those actions happen daily, they had to be fast — saving something can't interrupt the moment of listening or reading. So bookmarking and playlist additions are single-tap actions, visible immediately, with no extra screen to navigate through.
That speed requirement drove a specific interface decision: the bookmark action lives directly on the now-playing screen, not buried in a menu, because the moment someone wants to save a message is almost always the exact moment they're listening to it — a passage lands, and they want to mark it before the thought passes. Any extra tap between that impulse and the save action is a chance to lose it.
Small features like these rarely make it into a marketing screenshot. But they're often the reason an app becomes part of someone's daily routine instead of something they open once and forget, because a routine is really just a series of small, frictionless actions repeated often enough to become automatic.
