3 ms·

iPod Touch was 3.1.2 (about 2 years old) which I will readily admit is rather old but I have reasons for sticking to it on that device. I don't believe 5+ is

iPod Touch was 3.1.2 (about 2 years old) which I will readily admit is rather old but I have reasons for sticking to it on that device. I don't believe 5+ is available for my hardware. Now I don't really expect it to work but it would be one of those nice-to-haves if it did. The Nook I think is up-to-date as of a week or 2 ago. My company does not enforce a standard browser but iPad and Android Tablets would be expected for anything I adopt as well as the standard Windows browsers. I'm not aware of anything that works well everywhere and gives a nice experience which is what this framework tries to do so. Anyway I totally appreciate the work and understand the difficulties involved.

ryanwatkins 14y ago
iOS 3 on any device has a tiny marketshare - Instapaper showed it at less than 1.2% of iOS, and that was nearly 9 months ago. (http://www.marco.org/2011/11/30/more-ios-device-and-os-version-stats-from-instapaper http://www.marco.org/2011/11/30/more-ios-device-and-os-versi...) The support matrix for Enyo is here - http://enyojs.com/docs/platforms/ http://enyojs.com/docs/platforms/ Opera Mini and mobile are just not supported. You need to draw the line somewhere. 'Broad' support is good. 'Everything' support is futile, for the feature set desired in a mobile application framework, with the resources the Enyo team has. Enyo is good at creating 'apps' - often things delivered in a PhoneGap-like container or something with defined browser support like Chrome Web Store. Its probably not the general framework for any and all website development needing to support all platforms.