\n<\/p>\n
If you haven\u2019t already, make sure you read Sarah Perez\u2019s coverage<\/a> of Apple\u2019s recent \u201cHelping Protect Kids Online<\/a>\u201d white paper. Sarah goes through the entire announcement, but the most interesting part to me was a new Declared Age Range API.<\/p>\n From the PDF<\/a>:<\/p>\n Through this new feature, parents can allow their kids to share the age range associated with their Child Accounts with app developers. If they do, developers will be able to utilize a Declared Age Range API to request this information,<\/strong> which can serve as an additional resource to provide age-appropriate content for their users.<\/p>\n<\/blockquote>\n This is a huge step forward for privacy-focused child safety, meaning Apple can be responsible for the \u201cproof\u201d of age, rather than leaving it to each third-party developer. But where does that \u201cproof\u201d come from?<\/p>\n Apple spends a whole page of the PDF answering that question and explaining why they chose to collect no \u201cproof\u201d at all. Each child\u2019s age range is set manually by whoever controls their device\u2019s parental controls. That means parents stay in control and can trust that apps using this API are gathering nothing from their kids other than their verified age range.<\/p>\n Of course, widespread success relies on developers opting in, and I hope Apple highlights the adoption of this API in every App Store listing. Could they make it mandatory for apps in the Kids category? It\u2019s possible, but they do mention that apps will still be allowed to collect more proof of age where necessary, so it won\u2019t be locked down as the only<\/em> age verification method.<\/p>\n According to Sarah\u2019s article<\/a>, this feature will be released in stages, with some parts shipping in iOS 18.4, and the developer API coming \u201clater this year\u201d. I\u2019ll be happy to hear more about it at WWDC.<\/p>\n Dave Verwer<\/p>\n Developers rely on Superwall to grow revenue<\/a><\/p>\n Join some of the App Store\u2019s biggest apps, from big brands like Mojo and Citizen, to thriving indies. Test pricing, run paywall experiments, update locked features, and more\u2014all without app updates. Plus, enjoy free revenue tracking and analytics. Superwall is your complete growth toolkit<\/a>.<\/p>\n iOS Versions Market Share in 2025<\/a><\/p>\n I haven\u2019t included an iOS market share report this year, so let\u2019s fix that today! iOS 18 is now installed on about 80% of devices, and if you support 17 and 18, you\u2019ll cover 90% of in-use devices. Thanks to TelemetryDeck<\/a> for maintaining these reports, they\u2019re super useful. They also have a minor point release chart<\/a> if you\u2019re considering requiring a specific point version.<\/p>\n Designing a custom lazy list in SwiftUI with better performance<\/a><\/p>\n The default list or lazy stack controls in SwiftUI will meet most needs without too many problems, but what if it runs out of performance and you need something custom? Matthaus Woolard<\/a> has a solution that prioritises performance while remaining completely within the SwiftUI framework.<\/p>\n SwiftUI Performance – Selectively using UIKit<\/a><\/p>\n While it\u2019s great to stay all in on SwiftUI, there are other solutions to the same problem. In this article, Majid Jabrayilov<\/a> tackles the same issue but chooses to use cell reuse of a collection view while retaining the ease of development that SwiftUI gives when it comes to the collection view cells.<\/p>\n SwiftUI Phase Animation \u201cBug\u201d<\/a><\/p>\n Chris Eidhof<\/a>:<\/p>\n I noticed that phase animators weren\u2019t behaving as expected, and I initially assumed I\u2019d found a bug in SwiftUI. It took me way too long to realize the problem here, that\u2019s why I am writing this up. Spoiler alert: there is no bug<\/em> .<\/p>\n<\/blockquote>\n It turns out that there were a couple of things going on. This is worth a read.<\/p>\n Customizing and Animating SF Symbols in SwiftUI<\/a><\/p>\n I thought I knew everything about using SF Symbols until I read Gabriel Theodoropoulos<\/a>\u2019 latest post. If you think there\u2019s nothing else to learn, double check by getting to the bottom of this post. \u2705<\/p>\n Spatial Rendering for Apple Vision Pro<\/a><\/p>\n I\u2019ve had this repository<\/a> from Warren Moore<\/a> in my list of \u201cthings to check out\u201d for a while now. Finally, seeing the release of this video made me do it. It\u2019s an hour-long overview of his Swift-based renderer for visionOS, and while the content of his talk went way over my head, I\u2019m sure there are many of you that will get more out of it than I could.<\/p>\n Senior iOS Developer – Productivity Team @ komoot GmbH<\/a> \u2013 As a Senior iOS Developer, you\u2019ll be an essential part of our newly established iOS Developer Productivity Team. You\u2019ll work closely with other iOS developers and help them perform at their highest technical level. \u2013 Remote (within European timezones)<\/em><\/p>\n iOS framework developer @ Nutrient (formerly PSPDFKit)<\/a> \u2013 Design APIs that will affect hundreds of apps, and create UIs used by millions of users. Collaborate globally in a small team working on the leading document SDK for iOS, macOS and visionOS. Make the most of a flexible schedule, and attend annual retreats at exciting places around the world. \u2013 Remote (Anywhere)<\/em><\/p>\n iOS Engineer @ Bevel<\/a> \u2013 We\u2019re building at the forefront of consumer health. We are a small team that deeply cares about our craft. You\u2019ll get a chance to work on something that improves the health of tens of thousands of people! \u2013 On-site (United States in NY)<\/em><\/p>\n\n
News<\/h2>\n
Code<\/h2>\n
\n
Videos<\/h2>\n
Jobs<\/h2>\n