2 ms·
It's a difficult problem and the costs of the security model are passed mostly to devs in the form of their time getting through the review process and being ca
by mattgreenrocks 5y ago
It's a difficult problem and the costs of the security model are passed mostly to devs in the form of their time getting through the review process and being careful to plan features that fit within the subset of allowable behavior.
Concrete example: I have a small Mac utility in the App Store. I've had to can an unreleased feature because of App Store restrictions; specifically, using IOKit to read some device information. It's a shame. I also dread submitting every update; I never know if the reviewer will 'get' what my program does or not, as well as have the necessary equipment on hand to test it.
Cost of doing business, I suppose. It was meant as a learning exercise and has made some money, so it's all good. I may consider selling it via Paddle in the future.
- ghaff 5y agoYou can mitigate the tradeoffs to some degree but there are always going to be tradeoffs between security and convenience (and sometimes functionality as in your case).
- dylan604 5y ago>as well as have the necessary equipment on hand to test it. It's Apple doing the testing of software on hardware built by Apple. Why would you think that they would not have the equipment to test it?
- mattgreenrocks 5y agoMy app only really makes sense if you have more than two separate audio devices. Many testers probably only have the built-in speakers and maybe some headphones, and thus never have problems with macOS choosing the wrong one.