I was speaking in specifically about native applications and not Web Browser based applications. Taking what I said out of context to get on your soap box and expose the dangers native applications is disingenuous and doesn't add credence to your opinion.
You're setting your argument up for failure before you even present it when it's foundation is a clear and intentional misinterpretation of someone else's words.
Again, I disagree. You're beginning with the assumption that native is the only, and best solution. As a user, this is simply not true. You may _prefer_ to develop for native, but that doesn't mean its the best choice for the user.
Very, very few apps need to be developed natively.
The vast, vast majority would be better if developed for the browser.
This obviously depends on exactly what you're talking about, I concede there are some specific applications that require it. Maybe _your_ specific app requires in, in which case, _you_ have to live with the trade-off of the gatekeepers.
> You're beginning with the assumption that native is the only, and best solution.
I never said anything of the sort, you're again manipulating what was said to give you an opportunity to stand on your soap box. I said Apple and Google control the distribution channel and have an interest in protecting it.
Web Apps are at a distinct disadvantage on both platforms because Apple and Google control the channel to dissuade them from reaching mass adoption.
If anything I said that these actions might actually help Web Apps.
You're setting your argument up for failure before you even present it when it's foundation is a clear and intentional misinterpretation of someone else's words.