I have just realised that my application does not work well with browsers other than Google Chrome and I’m wondering whether it’s possible to detect the user’s browser and then send a popup which advises them to use GC if they were using IE for example?
Though when you say ‘does not work well’, which aspect of your app is this? It might be off putting to a user to be informed they need to switch web browsers…
People with IE are used to those ugle scrollbars because that’s all that they see on the internet. So, I wouldn’t force them to change browser.
There are some issues with popup animations and Safari. I think this works fine if they simply show/hide instead. So, that might be a better UX solution for your users than requiring them to change browsers.
Just some thoughts in case they’re helpful for you or others who have the same problems.
@Bubble, do end-users still experience problems with blurred backgrounds (on popups) with Safari? If so, it’d be great to have an app-wide option to have popups not display blurred backgrounds when end-users are using Safari.
My problem with IE is to do with the navigation strategy that I use in my single page application which allows users to use the forward/backward buttons on the browser without the page refreshing - simply doesn’t work with IE (if you have a single page application you’ll understand). Secondly, some text elements do not appear for some odd reason in IE and finally, the majority of my users will have Google Chrome installed. GC has a browser usage share of 55%-60% in contrast to IE’s measly 8% (I actually think it’s much less than that now), so at least 92% of my visitors won’t be using IE.
Yeah, I understand. Just wonder if there’s an easier solution for your users. We have video conferencing within our app and only Support Chrome and Firefox for video (mainly because Safari and IE don’t fully support WebRTC yet). So, I know users really don’t like changing browsers - it’s a lot of friction so it has a material drop-off rate. That’s all.
Do you use URL parameters to determine the “page” of your single-page app? It’s a good practice to enable users to click “back” and have it navigate to the prior view instead of leaving your app if it’s a 1-page app. Seems to work fine in IE as well.
I haven’t seen issues with text not appearing in IE, but haven’t tested for that recently. Any idea what conditions might be present for this to be a problem? …I would think Bubble would be happy to fix any bugs like this too (and it’d be helpful to the whole community if you reported them, myself included.) Cheers.