One awkward product-design problem in my side project PairTake is that front/back recording depends on the phone's camera capabilities. Installing the app doesn't guarantee that the hardware can run both cameras together. On unsupported devices, the app falls back to a single camera. That leaves a messaging decision: the headline feature is simultaneous capture, while the useful fallback is ordinary recording with a preview-only teleprompter. Calling it a dual-camera app is accurate on compatible devices, but the compatibility condition needs to be clear before someone plans a shoot around it. The app can save a combined picture-in-picture or split-screen clip on supported devices. Basic capture, layouts, and the teleprompter are free with no watermark. Pro adds separate front/back video files and higher-spec options such as 4K and 60fps, subject to support. I'm the developer; I'm not looking for people to buy Pro to check whether dual capture works. For anyone who has shipped a hardware-dependent app: where would you put the strongest compatibility explanation—first screenshot, opening description, or the first camera session? And what wording makes the fallback understandable without burying the main use case? For context: iOS: https://apps.apple.com/app/id6795962171 Android: https://play.google.com/store/apps/details?id=com.xionity.dualcamera   submitted by   /u/shixuan_lzq [link]   [comments]