Wireless charging: because it’s always reliable, convenient, and available.
Do you support any older iOS versions? Anything that uses video, PWA or features added to other browsers >2 years ago? If yes to any of those questions, I have to think you don’t actually support/test in iOS safari. Which btw often works differently between iphone and ipad. And their simulator support only goes back a couple of versions, despite the fact that Safari does not auto-upgrade and is tied to major os releases. So if you have users with older devices, you cannot ever take for granted that your app/website will work fine for them without testing on either a simulator (excludes OS versions over like ~2 years old), or maintaining and testing on a physical library of devices with older versions that you make sure you always refuse updates on.
It’s abysmal to support safari ios unless you don’t care about lower income/education users who have 5 year old devices.
You are right, I don’t, because they don’t need PWA to use the website, and there is no video content, life is good, and those who can’t use it are dropped, we are not going to sacrifice developer capacity to support a very minority of users.
That’s the apple user credo. “If I can’t do it, it’s really better anyhow because I didn’t need to”.
A decent web browser isn’t deeply tied to the operating system version and isn’t 5 years behind on some features while pigheadedly refusing to ever implement others. A decent web browser doesn’t force you to use it. You choose it among other options and seek it out. A decent electronics company doesn’t force you to buy proprietary cables just to charge their devices.
Congratulations though, your website users are all wealthy westerners.
Wireless charging: because it’s always reliable, convenient, and available.
Do you support any older iOS versions? Anything that uses video, PWA or features added to other browsers >2 years ago? If yes to any of those questions, I have to think you don’t actually support/test in iOS safari. Which btw often works differently between iphone and ipad. And their simulator support only goes back a couple of versions, despite the fact that Safari does not auto-upgrade and is tied to major os releases. So if you have users with older devices, you cannot ever take for granted that your app/website will work fine for them without testing on either a simulator (excludes OS versions over like ~2 years old), or maintaining and testing on a physical library of devices with older versions that you make sure you always refuse updates on.
It’s abysmal to support safari ios unless you don’t care about lower income/education users who have 5 year old devices.
Safari and videos are a nightmare to work with, there’s always something that doesn’t work right, when Chrome and Firefox work fine.
Are you me? I feel like I never speak to anyone who knows that pain like I know it.
You are right, I don’t, because they don’t need PWA to use the website, and there is no video content, life is good, and those who can’t use it are dropped, we are not going to sacrifice developer capacity to support a very minority of users.
That’s the apple user credo. “If I can’t do it, it’s really better anyhow because I didn’t need to”.
A decent web browser isn’t deeply tied to the operating system version and isn’t 5 years behind on some features while pigheadedly refusing to ever implement others. A decent web browser doesn’t force you to use it. You choose it among other options and seek it out. A decent electronics company doesn’t force you to buy proprietary cables just to charge their devices.
Congratulations though, your website users are all wealthy westerners.
They are the farthest thing from it, lmao, you dont even know how wrong you are, but I see you stí´ possess the teenage angst of ios v android wars