So if not Apple's platform, which platform would be a better pedagogical platform for education in mobile programming?
I am not aware of a mobile OS that exists for an optimal pedagogical experience. Or a set of programming languages and libraries that exist for pedagogically optimal exploration. Your choices are basically Android/Kotlin or Apple/iOS. I do both. It's not obvious to me that either is a great "leading to code" environment. Your comment about Apple docs up to dates was... I find figuring out Google's Android APIs much more difficult and it's a huge flux between what's trending cool and what will actually run on a given device.
As an educator, I would guess that having more consistency betwixt student devices would be a big win. Apple definitely wins here.
What may have decided it though was the student body's more common device. If more students were packing iPhones than droids, then it makes sense for that to be your text.
I'm personally more in favour of supporting Android development in a teaching environment for one simple reason: you don't need a Chromebook to develop for Android, but you do need a Mac to develop for iOS. Even if you own an iPhone, running an Android emulator is free and easy. If you own an Android, there's no way to run a simulated iPhone without more accompanying hardware. If you've purchased a Windows-based laptop at the start of your education, you're basically locked out of the iOS course unless you borrow someone else's Macbook or start messing with horrible virtual machine solutions that violate the EULA.
I don't even think for a second that Google's docs are any better than Apple's. In fact, I think they're much worse. What I intended to convey with that paragraph is that I don't think that Apple should be the educator that teaches people to code for mobile.
I haven't kept up with Android's new APIs but I do know that Android is great for backwards compatibility. If you know the basics for Android, you can adapt to whatever fancy framework Google pumps out this year quite fast, or you can choose to stick to the "traditional" API that'll always be supported. Normal apps can do just fine without even some of the older stuff like fragments. Whatever Google is doing, is not necessarily the best way to develop code for their platforms.
I am not aware of a mobile OS that exists for an optimal pedagogical experience. Or a set of programming languages and libraries that exist for pedagogically optimal exploration. Your choices are basically Android/Kotlin or Apple/iOS. I do both. It's not obvious to me that either is a great "leading to code" environment. Your comment about Apple docs up to dates was... I find figuring out Google's Android APIs much more difficult and it's a huge flux between what's trending cool and what will actually run on a given device.
As an educator, I would guess that having more consistency betwixt student devices would be a big win. Apple definitely wins here.
What may have decided it though was the student body's more common device. If more students were packing iPhones than droids, then it makes sense for that to be your text.