Check the acquisition promise
Read the store headline, screenshots and description. What problem is the app promising to solve?
Study the storefront ↗Johannes Doerr · iOS
Explore the ad evidence, study the storefront, and build your next acquisition hypothesis.
01 / Creative research
Read the store headline, screenshots and description. What problem is the app promising to solve?
Study the storefront ↗Explore apps with direct store-link matches. Compare their hooks and formats without assuming the same approach works here.
Browse observed advertisers ↗Store rankings and revenue estimates describe market context. They do not establish ad spend, conversions or ROAS.
Review the market context ↗02 / Storefront & product
Study the product story and store experience behind the acquisition funnel.
03 / Market context
Keep revenue, downloads and store rankings separate from advertising performance.
The bugs I mentioned in an earlier review were resolved with an iOS update - I forget which one, it’s been a while. Midiflow has been stable for a while now, and I’ve been using it without incident. As I said then, the feature set and power this app has is great. I couldn’t do what I do without it. One perplexing omission I just discovered is its seeming inability to handle note-off velocities! As far as I can tell, they’re all turned into note-ons with vel=0. I’m OK with this although it sent me on a wild goose chase of troubleshooting that wasted a lot of time. If anyone uses note-off velocities as a modulation source for anything, you may want to look elsewhere - unless Johannes addresses this with an update. He is still unreachable, as far as I can tell. The forum is dead - and the “feedback” button on the top left of the UI (described in the documentation) is gone! It almost seems he doesn’t want to be bothered! Speaking only for myself - the app is working fine (for now) and I’m gonna stick with it as long as it works on my iPad and iPhone. I can’t help feeling a little nervous about the lack of support.
Good set of features for managing your MIDI chain on IOS, but if you run into a bug or have a question there is no response, and the community forum is locked
Midiflow is a focused, full-featured, and efficient app for routing MIDI data among devices connected to an iOS tablet/phone. It is intuitive to setup, and basically worked straight away. The fact that it runs in the background is a crucial feature for any MIDI routing app. Setup and use case is this: Three MIDI-capable devices on a USB hub connected to my iPad Pro via the camera connection kit. Devices include: a digital mixer, a programmable MIDI foot switch, and a DMX lighting controller that has 5-pin (DIN) MIDI In port connected to the USB hub via a USB<->DIN MIDI controller cable. A multitrack audio app sends digital audio to the mixer and midi note instructions to DMX controller. MIDI foot switch needs to send MIDI note and CC commands to the audio app, digital mixer, and DMX lighting controller. As is, only the audio app properly receives and sends MIDI data, since it is acting as a MIDI host app the iOS device; but, the app does provide MIDI thru/router functions to forward the MIDI data to other destination devices. Enter, Midiflow. Midiflow is setup to receive MIDI data from the foot switch and forward these commands also to the mixer and DMX controller devices. Works perfectly! This is a rather simple use case, but good demonstration of Midiflow’s critical function. Add to this its ability to also transform MIDI data while routing it to the proper destinations, while running as a background app on iOS... Just perfect!
Midiflow allows you to send MIDI from app to app in a similar way to what you already do with audio. That way, you can sync apps with each other or se...
| Name | Price | Type |
|---|---|---|
| Send Controller On Load | $1.99 | One-time |
| Controller Conditions | $2.99 | One-time |
| Controller Remapping | $3.99 | One-time |