As an industry we need to try to make sure that if this holds anything back it is Apple users not everyone else. The platform being deliberately broken in a chi

As an industry we need to try to make sure that if this holds anything back it is Apple users not everyone else. The platform being deliberately broken in a childish hissy fit should not be allowed to be an inconvenience to users of other platforms. Instead of not implementing features because they won't work on iOS state that your stuff works on standards compliant browsers, if the user has a system that is deliberately standing in the way of standard features then some things may not work as well as expected and they should contact their system vendor, not the app vendor, for resolution. Unfortunately this will be difficult because iDevice users tend to be a mix of cultishly supportive of their platform¹ and/or bully like in demanding what they want from people that are not Apple, so this stance might be hard for those with commercial interests to take. Away from DayJob I have the luxury of being able to declare Apple platforms to be at best a third-class citizen³, maybe forth³ or worse, when it comes to support in anything⁴ I do, but we'd not get away with that in DayJob. I'll be adding to all my personal online output a statement to the effect “As Apple have a record of not properly implementing standards in a timely manner, and even retroactively breaking features when they have a hissy fit with regulators who try to stop them bullying developers, I can not guarantee that this site/app/other will work on Apple operating systems.”. ---- [1] If <something> doesn't work on the platform <something> must be broken or just a <something> that no one would ever want, it isn't the platform's fault. [2] If <something> doesn't work on iDevices then its name will be beaten up until it gives in and hands Apple its lunch money. [3] 1st class is “if it anything doesn't work, this is a serious problem to be addressed ASAP, how did this shit go live?”, 2nd class is “everything should work, if it doesn't then I'll look into it quickly, maybe less quickly if it is just a display/UX issue rather than broken functionality”, 3rd class is “it should work as it is compliant with relevant standards (official or generally accepted), if it doesn't I'll try to resolve as soon as practical”, 4th class is “I think it might work, if it does work for you then great, if it doesn't then rest assured that I don't actually care”. 5th is “I do not intend this to work for you, instead telling me if I won't make it work you'll go somewhere else, skip a step and just go away immediately”. [4] even things that don't depend on features currently known to be broken by Apple – if they will deliberately break an existing feature now what is to say they won't do the same to others in future?