So let’s get into what you all thought on Apple platform growth. I’ll begin with a couple of outstanding themes: SwiftUI, AI, and enhancements to Xcode.
AI is an apparent one as of late, however it’s clear that it means various things to totally different individuals. 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 overlook when the whole lot 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 principally be blissful to take no matter Apple deems to bless us with on this space subsequent yr as there have been only some particular strategies.
It was the identical for Xcode, too. Enhancements to the standard and efficiency of Xcode was in all probability the commonest “want” that I noticed within the outcomes, however once more there have been only a few specifics. I hear this yearly and it generally appears like I’m utilizing a distinct Xcode to everybody else. It’s not at all good, however my expertise with it appears nowhere close to as dangerous as different individuals’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 growth change locations in the case of steering on app structure. Apple used to firmly encourage an MVC method, however that has gone as of late. 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 method, resulting in fragmented use of languages, instruments, and design rules. This inconsistency resulted in lots of poorly designed apps on the Play Retailer, and sadly, the blame usually fell on Android itself fairly than the person apps — customers merely stated, “Android sucks.” Happily, Google now provides clear tips 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 assumed I agreed with Apple’s current stance of being utterly structure agnostic, particularly in the case of SwiftUI code. It’s laborious to provide generic recommendation about app structure, however this information does an amazing job. They’ve a complete studying pathway on the topic, too.
The subject of documentation got here up a number of instances, too. Whereas there wasn’t something significantly new stated, the identical previous factors stay. James Clarke :
Bettering 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 accomplish that properly.
Additionally, from Daniel Steinberg:
Convey again the previous Programming Guides. There are massive 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 interchange the previous programming guides, they don’t do it properly sufficient. I perceive that the “ebook fashion” format will need to 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 current take by hoping for:
Opinionated stuff (Swift Format Guidelines and many others)
It was an enchanting look at what you all assume, and I hope you discovered the outcomes attention-grabbing! Thanks for studying.
Dave Verwer
