Not the same thing. You have to think of iOS and Android more like cities as the cost to switch between them is pretty high. More so leaving Apple. Apple has insanely expenisve lock in cost to leave. Easy to get in hard to leave.All you seem to be saying here is that the "fix" you want implemented exists on the Android platform, and that it has almost zero effect. If your fix has next to no effect, which is proven overwhelmingly on the android platform, then I wonder at the real purpose of all of this. Are you just wanting your preference to be law while my preference is outlawed? As it stands, your preference exists (Android) and my preference exists (Apple).
No it allows you to use Apple but not have the hard lock in. You can choose to not use side loading. It have zero affect on you if other use it.So, your choice is valid and mine isn't. So much so that you're wanting a huge government agency to enforce, by law, your preference, and veto my preference by law. So, not really about "choice," right?
You could "choose" to develop it on the Android platform. That's a choice, no?
That statement alone proves how little you understand anything about software development. Lets see if friends and family use only iOS then Android is not an option. That is even before you get into the fact that swapping over is not that easy in terms of skills and time. I for example have a decade of knowledge in iOS developlent. Swift and objective-c knowledge and very little in terms of Android. Could I learn it yes but it it is a slower process.
That is like asking a brain surgeon to go heart surgery. It is just surgery. They could choose to do it. Not the same thing. It is a specialized skill set.