So let’s get into what you all thought on Apple platform improvement. I’ll begin with a number of distinguished themes: SwiftUI, AI, and enhancements to Xcode.
AI is an apparent one today, but it surely’s clear that it means various things to completely different folks. Some wished for enhancements to Xcode 16’s AI code completion, whereas others wished for higher integration APIs so customers can entry app-specific knowledge through pure language. Some even wished for enhancements to CreateML, which is a simple framework to neglect when all the pieces you examine is so dominated by LLM information. It’s clear that AI is on all of your minds, although.
Individuals are additionally clearly wishing for continued enhancements to SwiftUI, however appeared to largely be glad to take no matter Apple deems to bless us with on this space subsequent yr as there have been only some particular options.
It was the identical for Xcode, too. Enhancements to the standard and efficiency of Xcode was in all probability the most typical “want” that I noticed within the outcomes, however once more there have been only a few specifics. I hear this yearly and it generally looks like I’m utilizing a special Xcode to everybody else. It’s on no account good, however my expertise with it appears nowhere close to as unhealthy as different folks’s. I do want the phantom errors would go away, although. 👻
Lastly, I need to contact on a few particular feedback. First, Siamak (Ash) Ashrafi on how he has seen iOS and Android improvement swap locations on the subject of steering on app structure. Apple used to firmly encourage an MVC strategy, however that has gone today. Whereas, Android:
Within the early days, Android builders confronted a scarcity of steering on app structure. With no greatest practices supplied, each developer carried out their very own strategy, resulting in fragmented use of languages, instruments, and design ideas. This inconsistency resulted in lots of poorly designed apps on the Play Retailer, and sadly, the blame typically fell on Android itself moderately than the person apps — customers merely stated, “Android sucks.” Happily, Google now gives clear pointers and greatest practices, serving to builders create strong, constant, and high-quality Android apps.
He provided a hyperlink to Google’s Information to app structure and I loved studying it. I believed I agreed with Apple’s latest stance of being fully structure agnostic, particularly on the subject of SwiftUI code. It’s arduous to offer generic recommendation about app structure, however this information does an incredible job. They’ve an entire studying pathway on the topic, too.
The subject of documentation got here up a number of occasions, too. Whereas there wasn’t something significantly new stated, the identical previous factors stay. James Clarke :
Enhancing API documentation for Apple APIs giving utilization examples.
It’s that final half about “examples” that comes up over and over, and I’m assured it’s why blogs that take an Apple API and add code examples of utilizing it achieve this effectively.
Additionally, from Daniel Steinberg:
Convey again the previous Programming Guides. There are huge matters that want these overviews and never API by API docs
I miss them too, Daniel! I perceive what Apple is attempting to do with including articles in and across the API documentation, and people articles are nice! Nonetheless, as a lot as Apple may intend them to switch the previous programming guides, they don’t do it effectively sufficient. I perceive that the “e book type” format should have been extra work to keep up than shorter articles are, however I miss the best way they guided you thru a subject.
Lastly, bless Marius Felkner for echoing my latest take by hoping for:
Opinionated stuff (Swift Format Guidelines and so forth)
It was an interesting look at what you all suppose, and I hope you discovered the outcomes attention-grabbing! Thanks for studying.
Dave Verwer
