![]() ![]() ![]() Apps should use APIs and frameworks for their intended purposes and indicate that integration in their app description. Keep your apps up-to-date and make sure you phase out any deprecated features, frameworks or technologies that will no longer be supported in future versions of an OS. ![]() Here is the relevant excerpt from the guidelines:ΔΆ.5.1 Apps may only use public APIs and must run on the currently shipping OS. There is a configurable blacklist where you can put any domain after all. However, it's hard to argue, that it is possible to configure it to block anything you want including ads, tracking or whatever. Moreover, it is advertised nowhere that it can. Your app uses a VPN profile or root certificate to block ads or other content in a third-party app, which is not allowed on the App Store. Guideline 2.5.1 - Performance - Software Requirements Therefore, this Apple's policy has absolutely nothing to do with security or privacy. The code of AdGuard Pro is open and available on Github. Instead, it uses a public API ( NEPacketTunnelProvider) to configure a local VPN tunnel and intercept the outgoing DNS requests. It does NOT install any profile or certificate. I'd like to address a popular concern that I often see on the internet. IMPORTANT NOTE for those who are not too familiar with AdGuard Pro. It appears that what we did after the previous crackdown is not enough, and they want us to remove everything that can be potentially used for blocking tracking and ads outside of Safari. Long story short, Apple didn't allow us to push a new update to the App Store. Ad blockers have almost conquered the desktop browsers, but corporations don't want it to happen in their walled gardens, and protect them fiercely. Google, Apple, Amazon and now Apple again. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |