Feature request
B1 App has no audio playback UI for MP3 files attached to service plan items. Churches that upload click tracks, song previews, or rehearsal recordings currently have no way to play them in-app.
Current behavior
MP3 files attached to plan items as links fall through to the device's generic browser/handler. There is no inline player — no play button, no scrub bar, no pause. Volunteers have to leave the app to hear audio.
Expected behavior
Tapping an audio file on a plan item opens an inline player within B1 App:
- Play / pause
- Scrub bar with time display
- Works for click tracks, song previews, and any attached MP3
Why this matters
Click tracks are a standard part of worship team planning. Leading ChMS platforms have inline audio playback and churches expect this as a standard feature. Without it, worship teams cannot fully evaluate B1 Services.
A church migrating to B1 (July 2026) uploads MP3 click tracks to every plan. Their worship team specifically needs in-app playback before they can fully evaluate B1 Services.
Dependency
This feature requires the audio upload UI to be built first — see issue #961. Audio must be uploadable through the B1 interface before in-app playback is meaningful.
Feature request
B1 App has no audio playback UI for MP3 files attached to service plan items. Churches that upload click tracks, song previews, or rehearsal recordings currently have no way to play them in-app.
Current behavior
MP3 files attached to plan items as links fall through to the device's generic browser/handler. There is no inline player — no play button, no scrub bar, no pause. Volunteers have to leave the app to hear audio.
Expected behavior
Tapping an audio file on a plan item opens an inline player within B1 App:
Why this matters
Click tracks are a standard part of worship team planning. Leading ChMS platforms have inline audio playback and churches expect this as a standard feature. Without it, worship teams cannot fully evaluate B1 Services.
A church migrating to B1 (July 2026) uploads MP3 click tracks to every plan. Their worship team specifically needs in-app playback before they can fully evaluate B1 Services.
Dependency
This feature requires the audio upload UI to be built first — see issue #961. Audio must be uploadable through the B1 interface before in-app playback is meaningful.