Starting with the release of iOS 17, tvOS 17, watchOS 10 and macOS Sonoma, developers will be required to explain why they're using so-called required reason APIs. Apps failing to provide a valid reason will be rejected started in spring of 2024.
"Some APIs... have the potential of being misused to access device signals to try to identify the device or user, also known as fingerprinting. Regardless of whether a user gives your app permission to track, fingerprinting is not allowed," Apple wrote. "To prevent the misuse of certain APIs that can be used to collect data about users’ devices through fingerprinting, you’ll need to declare the reasons for using these APIs in your app’s privacy manifest."
Based on the information that's been shared, kits will be tuned to a single developer, and other developers on the team may not be able to experience Vision Pro to its fullest because a snug fit between the face and the Light Seal is required.
Information on Apple's developer website also mentions a workflow for unpairing an AirTag when returning a kit, which suggests Apple is using its item trackers to keep tabs on the headsets. Vision Pro developer kits are shipped in a lockable Pelican case that needs to be kept locked when the headset is not in use, and developers must keep the headsets in a secure location. An AirTag could perhaps be included in the storage case to allow it to be tracked down in the event of a theft.
Arc may be overkill for those who use just a handful of tabs at a time, but if you spend much of your day working in websites, I recommend giving it a try.
Reincubate released Camo Studio 2.0.5 with two oft-requested features for the virtual-camera system: 4K resolution and green screen support.
The new Belkin BoostCharge Pro at first glance looks to arrive with some pretty unremarkable specs at first glance – 10,000mAh batteries with 20W USB-C are hardly anything to be excited about. But where the new release does standout from everything else on the market is the built-in Apple Watch fast charger.
Google is delaying the broad expansion of its Find My Device feature, and it says it’s doing so with personal safety in mind. “User safety and the prevention of unwanted location tracking is a top priority for Android,” Google’s Erik Kay announced in a blog post today. “At this time we’ve made the decision to hold the rollout of the Find My Device network until Apple has implemented protections for iOS.”
Oh no. I am using UserDefaults in my hobby project, one of the APIs that Apple identified as requiring privacy mainfests.
Time to spend a few more weekends figuring out alternative methods?
Thanks for reading.