In this report we can see that the Androd (70%) is more used than iOS (28%).
But we must keep in mind a very important topic.
The young peope (16 - 24 years old age) prefer iOS (44%) instead of Android (30%).
That means what the future will be iOS and not Android.
Younger users prefer iPhone, older generatiosn prefer Android.
While Android is the most popular choice overall globally , Gen Zs and Millennials are still more likely to be iPhone users: The future is for the younger generations.
These numbers track our daily rendezvous usage. Yesterday, for example, we had 210k Android connections and 87k iOS connections which is roughly a 70/30 split.
Interestingly, on the weekends (i.e., when school is not in session) the split goes to 80/20 in favor of Android, which suggests that we have quite a few schools using iPad as their primary development environment.
Young people prefer iPhones to show off at school... they also prefer it because their parents buy them iPhones so that they are not inferior to other peers. When young people grow up, their independent lives will determine whether they will still want an iPhone or Android for 1/2 the price or even 1/3.
The lesser use of iOS in AI2 is surely also because it is newer than Android and because it has some deficiencies due to being in beta status. In addition, it also influences that you must pay an annual fee to Apple and that it is more complicated to upload apps to the Apple Store.
Outside of App development, what is true is that young people increasingly tend to use Apple and once they have started using it, they do not abandon it even when they are older (although the cost of iPhones is higher than of Androids). Statistics in the EU since 2018 clearly certify this trend that every day Apples are more used globally with annual increases of 3% to 5% to the detriment of Android (young people are getting older)
There are less iOS users online. Could the reasons be that iOS is not fully supported? Therefore, more advanced tutorial won't work on iOS?
On iOS, there are quite few things won't work. For example, the ListView can't change dividerThickness, element color, ElementCornerRadius, ElementMarginWidth... ImageHeight & width must be at 200 and lastly ListViewLayout can only stay at MainText. And not being able to use extension makes things even more difficult...
Recently, I tried to make an App to work on Android and iOS and it was quite painful at this beta stage... 
I have an app with +10,000 blocks compatible with Android and iOS. To do this, I have created a function that converts certain color and size characteristics of the layouts based on the operating system of the mobile that uses it (iOS or Android).
I think there are fewer people who contribute to the development of components on iOS than on Android. Android requires only a little knowledge, iOS apart from knowledge, requires a Mac Book, iPhone and a paid developer account on the App Store. If you have all this, you can contribute to the development yourself and develop, for example, the ListView component for iOS.
Too bad...I borrowed the iPhone to test...and thought it would work with few adjustments.
@ewpatton tells us that only @ 2% of AI2 users make use of extensions in their apps. I well remember the days before extensions, developers then were more creative and pioneering in finding solutions. It often required more blocks coding to get there, but we all learned much more about that and how AI2 (AI1) worked. This should probably be the case for ioS users, who should be coming up with innovative methods using the components and blocks that exists now, which have a much greater spread and functionality than in the early days.
Bear in mind that AI2 is intended as an educational platform for school children (even perhaps grown up ones too) to learn about coding. We are, I guess, lucky that MIT provide such good support to developers working outside of that sphere.
I put 2 procedures as these:
a) For the not Compatibility of the Notifiers text colours (the Android Notifiers blackground colour is black and the iOS is white). I have this function:
b) For the issues with Layouts /Labels automatic/fill parent Dimensions I have a special init block to put fix dimensions (only where I have problems) as this:
c) All the others blocks ara compatible between iOS and Android.
force define 44 + 30 == 100, good math 
.
Ok, lets put the jokes away.
I'm not quiet sure, bc once they notice how expensive Apple device are if not payed by their parrents they won't all stay at apple. Maybe Android won't survive but there is gonna be someone cheaper who will be the winner.
I mean my class mates asked a teacher (after they found out he earns more then they thought) why he doesn't own an iPhone bc he is so "ritch". They didn't even notice that he is still way to far away from "ritch" and I think he isn't really over the normal income.
@Ferran_SIMON Good tricks!! How about ListView? How do you deal with ListView that many of those parameters not supported I mentioned above? (the ListView can't change dividerThickness, element color, ElementCornerRadius, ElementMarginWidth... ImageHeight & width must be at 200 and lastly ListViewLayout can only stay at MainText.)
Thanks!
May be ypu don"t say right read. Others, not iOs and not Android are the difference of your math.
Sorry. I don't use ListViews in my App. I use ListPickers And the ListPickers have good compatibility between iOs and Android.
Ik, ik it was a joke . But I didn't know it is a so big ammount. I mean 6% doesn't sound much but if you see it in person amount it is kinda much
I don't even know how to export to iPhone
