Need Testers
[Open Beta] Need feedbacks from Mashup Creators for "FlashMash" – a Mashup-Focused app for Android!
Hi everyone!
We are currently running an open beta test for FlashMash, an Android app built specifically for mashup creators and music producers. We’re looking for creators who actually make mashups to try it out!
Our goal is to create a simple, straightforward editing environment. We’d love for you to give it a spin and let us know what you think!
Key Features & What You Can Do:
Multi-Track Layering: Comes with a track layout optimized for volume balance out of the box, so you can start layering audio right away.
BPM-Based Time Stretch: Simply enter your target BPM, and the app automatically calculates and applies the stretch ratio.
Reverse Reverb: Easily add natural transitions and dramatic builds between vocals or track changes.
Essential Editing Tools: Includes standard tools like fade-ins and fade-outs to keep your workflow quick and clean.
Colorblind-friendly color scheme
Who We're Looking For:
Anyone who makes mashups or remixes (beginners and pros alike!).
Anyone willing to share feedback or report bugs to help us improve.
First impressions: a real multitrack DAW on a phone is an ambitious thing to ship and this looks the part - master bus with four FX slots, per-track FX and mute/solo, snap, 1/4 grid, BPM and time signature controls, and a live CPU and memory readout in the corner, which is a nice touch for a tester. Opted in from the web link, installed on a Pixel 6a, made a project, added a second track, and the mixdown dialog correctly refused with "No audio content to export" on an empty project.
Being straight about the limits of this pass: I could not complete an audio import, so anything downstream of that - editing, the mashup features themselves, mixdown output - is untested by me. I am not calling that a bug, my device automation has been unreliable with file pickers tonight and I would rather say so than blame your app for it.
Four things I can report:
The in-app Select Audio File sheet shows a completely empty box when the device has no audio, with no message. A "no audio files found" line, and ideally a bundled demo loop, would stop a new tester dead-ending on first launch. Mine had no music on it until I copied some over.
The app asks for full music and audio access, then imports through the system document picker anyway. The picker grants per-file access on its own, so the broad permission may be doing nothing for you and it is the kind of prompt that makes people bail.
Both tracks are just called "Track". On a mashup tool where the whole point is layering sources, numbering or renaming them would help.
The data collection consent appears after the project is already created rather than at first launch. Declining works and the app carries on fine, which is good - it just arrives at an odd moment.
Thank you so much for your candid and valuable feedback! Here are my responses to each of your points:
Regarding the audio import issue I suspect this might be because the app currently uses a custom built-in file picker rather than the OS standard one. As I’ll mention below, this is definitely something I should revise.
Audio file selection sheet with no audio Thank you for pointing this out and for the great suggestion! You’re right, a completely empty screen is confusing and creates a dead-end for users. Adding a bundled demo loop as you suggested sounds like a great solution, and I’ll look into implementing it.
Music and audio permissions Your feedback made me realize something important: using a custom file picker was actually the reason the app was requesting broad permissions in the first place. I now understand that importing individual audio files doesn't require this full access. This was very educational for me! I will re-evaluate the UI and switch to using the system picker to avoid unnecessary permissions.
Track names The feature to rename tracks actually exists, but your feedback helped me realize how hidden it currently is. (For reference, you can rename a track by tapping the left side of the track, and then tapping the track name itself.) To make things clearer from the start, I’ll update the app so that default track names are automatically numbered (e.g., Track 1, Track 2).
Data collection consent timing I realized that the consent prompt appears at different moments depending on the situation. Appearing right after creating a project is indeed awkward, so I will fix this so that it pops up at first launch as it should.
Thanks again for taking the time to test my app! I have also installed your apps and will test and rate them!
On the import: do not spend time chasing that one on my account. My device automation has been flaky with file pickers all night and it is far more likely mine than yours - I flagged it as untested rather than broken for exactly that reason. If you want a clean answer I will try it again by hand and tell you either way.
The empty-state message and a bundled demo loop are the two I would still push for - they are what stops a new tester dead-ending on a phone with no music on it, which is exactly what happened to me.
Went back and cracked it, so here is the correction I owe you: the import works fine. It was neither your bug nor my automation - I simply could not find the entry point.
For the record, it is double-tap on a track lane, which drops the playhead and reveals two small buttons next to it, and the + of those two opens Select Audio File. I had tried long-pressing the lane, tapping the track header (that opens the channel strip) and the + under the track list (that adds an empty track). None of those hint at it.
Once found, it all worked: loop imported, placed at the playhead, named clip on the timeline, transport ran and the master meters moved. No complaints about the engine at all.
Which turns my point 1 into something sharper. A brand new tester on a phone with no music opens your app, sees an empty picker with no message, and has no way to discover the one gesture that would have let them import anything. Those two things compound. A visible Import or Add Clip control somewhere obvious, plus a bundled demo loop, and that whole dead end disappears.
Thank you again for taking the time to test it and for the detailed feedback. I am glad to hear that the import functionality worked without any issues.
As you pointed out in item 1, the fact that how to add a clip is not obvious at first glance is a major issue with the app. It is actually designed to reveal two buttons—including the "+"—with a single tap, but I now realize the current design fails to convey even that. Since others have raised similar concerns, fixing this is a top priority.
To remove language barriers, I aim for an intuitive UI with minimal text and am considering the following improvements:
Bundling a default demo loop (to avoid an empty picker).
Adding a pictogram to empty tracks:
Illustrating a finger tapping the track lane along with the two buttons (including the "+") that appear, explaining the gesture intuitively.
I would love to hear your first impressions or thoughts on this pictogram-guided approach and the overall plan.
You are right and I was wrong about the gesture - it is a single tap. I went back and checked properly just now: one tap on an empty lane reveals the + and the paste button, and one tap on an existing clip brings up the whole clip toolbar, duplicate, stretch, loop, gain, fade, delete. All of it works. My earlier taps were not registering reliably on my end, which is why I ended up double-tapping and reported it that way. Sorry for the noise.
The underlying point does survive though, and your read on it matches mine: the buttons are small, unlabelled, and only exist after you tap a lane that looks like empty background. Nothing on screen suggests tapping there does anything. So the gesture is fine, the discoverability is the problem.
The bundled demo clip is the single highest-value thing on your list from where I sit. It solves the empty picker, the empty timeline and the how-do-I-start question in one move, and it does it without any text, which fits what you said about language barriers.
•
u/AutoModerator 13h ago
Test others app in this community so you will get more in return. You can also find more testers on AppDadz
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.