Developing on mobile Safari/ui+wkwebview feels very much like developing on the IE of olde. It's hard not to perceive malice in the form of wanton disregard towards open web technology when observing how many stupefying bugs exist in parallel to the immense profitability of the app store.
No, it really doesn't, and you're blowing it out of proportion.
What "stupefying bugs" exist in Safari that aren't much more simply explained by Apple being something of a laggard when it comes to implementing web standards?
pointer event madness. file selector crash. <option> crash. rem bugs. insane RAM usage. crash from RAM usage. crash from greedy CSS selectors. canplay event never fired on media.
That's just from the last few weeks. Can't imagine anyone who has built a moderately sized web app would think Safari's biggest problem is just being a little slow on the uptake.
In better news, wkwebview is a big improvement. Hopefully it's a sign of things to come.
Do you have bug reports for any of those? That RAM usage in particular suggests that the problems are more likely either specific to your application or an extension
Webkit devs are aware of these and they have been fixed in Webkit core, but Apple doesn't provide any info about when the fixes may see the light of day.
iOS Webkit still has the 300ms click event delay even though Android released a simple fix over a year ago.
To work around this, you'll have to use a library like FastClick (which is not perfect) or write some Javascript to hijack touch events.
I've also run into a number of CSS animation issues which are just bizzare. For example, "position: fixed" doesn't apply when a CSS transform is also applied to an element.
