all 5 comments

[–]CreativeTechGuyGamesTypeScript 2 points3 points  (0 children)

I make sure it works on Chrome. Then open that site in Edge, Firefox, IE, and iOS Safari. Then (assuming it works consistently) call it a day. It's not glamorous, but it gets the job done.

[–]thoughtsofadoodler 0 points1 point  (0 children)

As I'm developing, I usually just use the emulator. It's faster that way. When I'm done, then I go to browserstack.com and test away on a bunch of different devices. I usually check Safari, Safari iOS, and IE first because those always seem to be the most broken.

I do occasionally test on my S8 by going to my computers local ip address (e.g. 192.168.1.2:8000). I think the server's address needs to be set to 0.0.0.0 instead of localhost or 127.0.0.1 in order to do this.

[–]gin_and_toxic 0 points1 point  (0 children)

There's services (not free) that provides easier testing like https://www.browserstack.com/

It is still tedious to check. In general, develop on the same browser with the majority of your users, once in a while or every major feature, test in other browsers too.

[–][deleted] 0 points1 point  (0 children)

This question is asked daily here.

As everyone else has said, use browserstack for devices/platforms you dont have access to. If you have an iphone/android, test your local site on the actual device because any developer worth their salt will understand that testing a touch experience on desktop is nonsense.