I think there are too many differences between Android and IOS.
One should try to match at least the most common are some of android on IOS.
Thus, a programmer would have less expenses the Android app in iOS reprogram.
Below is just a small example of the often occurs during programming.
B4X:
'Android
Dim txtName As EditText
txtName.Initialize("txtName")
txtName.Typeface = Typeface.CreateNew(Typeface.SANS_SERIF, Typeface.STYLE_NORMAL)
txtName.TextSize=30
txtName.Gravity=Gravity.LEFT + Gravity.CENTER_VERTICAL
txtName.InputType=txtName.INPUT_TYPE_TEXT
txtName.SingleLine=True
txtName.Text="Filippo"
txtName.Hint="Standort"
'IOS
Dim txtName As TextField
txtName.Initialize("txtName")
txtName.Font = Font.CreateNew2("ArialMT", 30)
txtName.TextAlignment=txtName.ALIGNMENT_LEFT
txtName.KeyboardType=txtName.TYPE_DEFAULT
txtName.Text="Filippo"
txtName.HintText="Standort"
I can see where you're coming from, but to my mind it's better that the terminology used reflects that of the underlying OS. When I want to do something new, I consult the Apple or Android documentation as well as the B4i / B4a documentation. If the terminology used was different it would be much harder to do that.
I fully agree with Steve and moster67.
For me it's wrong to adapt a language to another one, we must adapt to the new language.
I am collecting the differences and will post something in a near future.
There are many factors considered when implementing an API. Compatibility is one of the more important factors. However there are other important factors as well.
Font is a good example here. In iOS the font object holds the size as well as the font type. This is different than Android. I decided that it is more reasonable to follow iOS design here and not "fight" with the native APIs.
There are other cases like colors and date values which are the same as in B4A even though the underlying API uses a different approach.