Like I said, you can gate by capabilities but not by hardware. I was referring to your last paragraph about the supposed explicit compatibility settings in the

Like I said, you can gate by capabilities but not by hardware. I was referring to your last paragraph about the supposed explicit compatibility settings in the App Store per hardware. That is not a thing. Your example is specifically a capability, and one that requires PCIe, therefore needs thunderbolt. Apple themselves may gate those capabilities behind different product classes, but as a developer you cannot. That in turn makes it very difficult to know specifically why something isn’t supported. For example you can connect DACs and controllers to non-M iPads https://support.focusrite.com/hc/en-gb/articles/360012532199-Connecting-your-USB-C-iPad-with-your-Audio-Interface https://support.focusrite.com/hc/en-gb/articles/360012532199... There are also capabilities that diverge in other axes like newer A series chips support things where an M series doesn’t. Hardware raytracing was an example of that for a while. Or still is because there are different gens of M series chips for sale.