61–70 of 167 posts
What it may mean is that you don't have very many customers. If you were mainstream, you'd have more IE users... just like the rest of the Internet.
It's okay not to be mainstream... but, if time tracking is a competitive and profitable space, your competitors may be happy to share this blog post with their prospective users.
Earlier quoted context omitted.
What percentage of your users were on IE?
I think around 70-80%; the product the Web app was supporting was targeting schools/non-profits and other demographics where IE usage is high.
Aw man. As a bootstrapping web business guy, I can say I've had way more problems with supporting iPads and iPhones than IE. IE costs me $0 to support, and I don't even bother (nobody asks!). Supporting hip and popular Apple browsers can run me a grand in a fast minute. Pleasing early adopters without working really well on the iPad3 is a tough sell. I think startups fighting to support I'm not crazy about getting an…
Well done! I expect the contrarians to pour in screaming about not leaving anyone out and elitism and corporate users and blah blah blah... But seriously, fuck IE. if you don't have to support it then don't! More power to you! My biggest wish as a developer is for some major site to stop supporting IE. I do feel for the users but I feel it's a necessary evil to get the IE team to either ditch or fix Trident or whatev…
I have more trouble with Firefox than modern versions of IE. I also have a Pentium III that's running Windows 7 and IE9 now (and will be able to upgrade to IE10), and if that can upgrade to IE9, it's utterly and completely disingenuous to claim that the "smallest fraction" of Windows users can upgrade to it. Instead of being rational, you come off as a sneering cheerleader and, y'know, that can entirely be your bag i…
Aw man. As a bootstrapping web business guy, I can say I've had way more problems with supporting iPads and iPhones than IE. IE costs me $0 to support, and I don't even bother (nobody asks!). Supporting hip and popular Apple browsers can run me a grand in a fast minute. Pleasing early adopters without working really well on the iPad3 is a tough sell. I think startups fighting to support I'm not crazy about getting an…
"Early adopters" - surely we're beyond calling IPad owners early adopters? As for desktop and tablet support, is it really that hard with excellent toolsets such as Bootstrap etc. ?
Like the retina display, which does seem to require some dev love to look decent, according to statements on this very site.
Earlier quoted context omitted.
Well, adding support for Retina displays is definitely an iOS-specific thing (at least right now). But orientation changes? Is that not a general "mobile issue" for you? Or is (are) the WebKit build(s) in iOS doing something specifically bad compared to (say) Android?
Well, adding support for Retina displays is definitely an iOS-specific thing (at least right now). Not "right now". As long as you intend to support "retina displays", it will always be an Apple-specific thing. If you want to support something as general as high-DPI devices, you know, something concrete and not an Apple marketing-term, there are certainly lots of those being made and sold as we speak. They run Androi…
But I'm guessing that Android phones with high-dpi screens that support that query are still at the single digit percentage of browser statistics.
You are blocking IE - I know because I changed my user agent on my firefox browser and you blocked me, and that is not cool!
You don't even offer an option to let me try anyway!
Use feature detection if you must, ignore IE completely in testing if you wish, but do not actively block it or you are just as bad as those who only support IE.
Why? This is a sub-optimal approach. The same machine with the same OS and the same version of the same browser can render very different looks just because they user has different settings.
How do you know that your user even has a visual display? Does it matter to you if they have a portrait or landscape display?
> future versions of IE will probably be standards compliant
Are you saying that all your code is standards compliant and you're not using any browser-specific extensions?
There is also the demographic for their product, which is the more-likely reason for low IE rates. I wouldn't be surprised if the big Mac-OS screen shot on the home page turns off Windows users as well.
Earlier quoted context omitted.
Well, adding support for Retina displays is definitely an iOS-specific thing (at least right now). But orientation changes? Is that not a general "mobile issue" for you? Or is (are) the WebKit build(s) in iOS doing something specifically bad compared to (say) Android?
Well, adding support for Retina displays is definitely an iOS-specific thing (at least right now). Not "right now". As long as you intend to support "retina displays", it will always be an Apple-specific thing. If you want to support something as general as high-DPI devices, you know, something concrete and not an Apple marketing-term, there are certainly lots of those being made and sold as we speak. They run Androi…