The choir’s need
Members need current music and the correct practice recording. Administrators need to update that material and keep member information current without relying on a developer for routine changes.
A member’s practice workflow
- Find the current repertoire, with older pieces kept in an archive.
- Open a piece and select the relevant vocal part or mix.
- Listen with playback and speed controls, and consult the associated PDF or lyrics.
- Return to the choir’s current information and internal updates.
Protected audio supports seeking through the recording. The practice interface coordinates the available voice recordings so members can work with the material relevant to them.
Administration without editing code
Administrators add a piece, attach its documents and recordings, assign a group and mark it as current. Staged uploads break this into manageable steps. Existing material can be edited or archived through the interface.
Different people need different access: rehearsal material, member information and administrative changes each have their own permission rules. The server checks those permissions as well as the interface showing the relevant controls.
One application, two connected workflows
Members can find current pieces, choose their voice-part recording and practise alongside the score. Administrators keep the repertoire, recordings and internal information up to date through the same application.
I connected recordings and documents to the piece they belong to, with current repertoire separated from the archive. Protected audio supports seeking, so members can return to a passage without downloading a whole recording first.
My responsibilities
I handled product structure, responsive interface design, implementation, data relationships, media delivery and role-aware administration. The application uses PHP and MySQL, with server-rendered pages and focused browser interactions for search, uploads and practice controls.
Private application, public explanation
The screenshot shows repertoire administration using fictional data. The client application and member information remain private.
The delivered communication features are notices and an organization-wide feed. They are separate from the direct chat and other workflows illustrated in Aurora.
Explore the fictional Aurora demo →. Aurora is a separate interface demonstration, not a copy of or access to the client application; its role chooser is only a preview control.
