MixReview.App
Beta Testing
Thank you for testing MixReview. Please work through the core workflow at least once — in both the web app and the iOS app. Report anything that feels broken, confusing, or unfinished.
Links
iOS App
Install
Report a Bug
tally.so
Core workflow
Start here. Work through these tasks in order.
Sign up and log in
Choose a plan
Create a project and an album
Upload tracks (batch upload)
Rename a track, replace a single variant
Add a client
Test playback in the admin area
Test playback in the client area
Install and test the iOS app
Delete tracks, albums, and projects
Full checklist
If you have time, go through these in detail.
Account & access
Sign up
Log in
Log out and log back in
Onboarding / first steps feel understandable
Plan selection
Open the pricing / plan selection flow
Select a plan
Plan names, limits, and wording are clear
Projects
Create a new project
Rename or edit a project
Open and navigate a project
Delete a project
Albums
Create a new album inside a project
Open and navigate an album
Delete an album
Tracks & upload
Test batch upload
Tracks are recognized and grouped correctly
Rename a track
Replace one single variant
Delete a track
Files and names appear correctly after changes
Clients
Add a client
Client assignment flow is clear
Open the client view
Client only sees the correct content
Playback — admin area
Play tracks
Switch between versions
Playback starts quickly and reliably
Track names and version labels are clear
Tested on desktop and mobile browser
Playback — client view
Open the client area
Play tracks and switch between versions
Review flow is easy to understand
Interface feels clean and focused
iOS app
Install via Apple App Store
Open projects / albums
Test playback and version switching
Navigation and general usability
No crashes or major UI glitches
When reporting a bug
Please include: what you were trying to do · what you expected · what actually happened · device & OS · browser or iPhone model · screenshot or recording if possible.
After testing
What felt confusing?
What felt especially good?
Was anything missing?
Would you feel comfortable using this in a real client workflow?
Report a bugWrite an e-mail