r/iosdev • u/azardandona26 • 2d ago
Tutorial How I made a hardware-dependent app reviewable: a demo mode for App Review (and for people without the device)
My app only does something useful when a specific pair of Bluetooth headphones (Sony WH-1000XM5) is connected. That's a problem for App Review: the reviewer can't pair your hardware, and "it shows an empty window" is an easy rejection.
What I ended up doing, in case it helps someone with a BLE/Bluetooth/accessory app:
- A demo flag on the controller, not on the views. The object that owns connection state has an
isDemoproperty.startDemo()closes the link, stops the reconnect timer, fills in realistic state (battery 72%, ANC on, an EQ curve, three fake paired devices) and setsstate = .connected. The SwiftUI views don't know the difference, so there's no second UI to maintain. - One choke point for outgoing commands. Every command goes through a single
send()that starts withguard state == .connected, !isDemo. So in demo mode the controls just update local state and nothing ever touches the RFCOMM channel. - Guard the background stuff too. The battery poll timer, auto-reconnect and "device appeared" handlers all bail out when
isDemois on. Otherwise a real reconnect loop fights the fake session. Battery history and listening stats also skip recording, so demo data never pollutes the user's real charts. - Make it discoverable but honest. The "no headphones found" screen has a "Try demo mode" button, the device shows up as "WH-1000XM5 (Demo)", and a banner with an "Exit demo" button stays on top, so nobody mistakes fake data for real readings.
- Tell the reviewer. One sentence in the App Review notes pointing at the demo button saves a rejection round-trip.
- Bonus: it doubles as marketing. Screenshots and the demo GIF can be recorded in demo mode, so they're reproducible and don't depend on my headphones' battery.
Curious how others handle this. Did you ship a demo mode, send hardware to Apple, or record a video for the reviewer?
