There are some bugs in IOS 15, some affect the App Store where it fails to load the account page.
I hope people who are on the beta are reporting bugs into Apple.
@JayJayWM If it doesn’t install on the iPad, then log it via the developer portal that you have access to and they will if its a critical bug investigate.
This isn’t a judgement on you (I’ve done my fair share of questionable tech activity) but I always find it interesting how many people happily use services from subsidiary companies whilst disliking the parent.
The canonical example is usually Instagram and Facebook.
I’m very guilty of this myself. I think as @ndrw says, it’s often a lack of viable competitor.
I have nearly removed Google from my life but literally can’t stop using YouTube for various trailers/info videos etc etc.
Another personal example: I’m still struggling to decouple events from Facebook. A number of friends just make an enormous message group nowadays (which is still WhatsApp anyway), but I really like to have some sense of who’s actually coming and for a big event, there’s a massive difference in visibility between X attending and who actually sends a real reply in a group.
I am finding reachability doesn’t work in safari. It might be because the address bar is now on the bottom, but I feel there are some websites where it can be useful. Been trying a bit and just can’t get it to work!
Playing around with the beta and because of the way that Safari now puts the search bar at the bottom, if you access Gmail through it you can’t access the controls at the bottom of the screen to delete/archive etc
Urgh, that’s grim. Hopefully Apple reconsider a bunch of these changes. They can’t rely on web developers to have to fanny about with workarounds - I’m having flashbacks to Internet Explorer 6.
Whilst they cant rely on developers to cater for it, they do make it incredibly easy for developers to cater for it. In theory it’s as simple as adding env(safe-area-inset-bottom) into their css where they anchor the element to the bottom, so for example if they have it as ‘bottom: 0’, all they need to do is make it bottom: calc(0 + env(safe-area-inset-bottom)).
I haven’t tested this in theory with gmail as I don’t use it but given how many people do I’d fully expect Google to resolve it soon, i’d say the same for any website or web app ran by a decent size company.
People forget that their was a similar issue with the notch when it was first released and the solution for developers is basically the same.
Given the steps they’ve taken to inform developers on how to resolve issues, it’s definitely not a bug
Edit, heres a quick example, if you open it in safari, you’ll see the left button hides behind the bar whereas the right moves above it. Literally all I did for the second button was change bottom: 0px to bottom: calc(0px + env(safe-area-inset-bottom))
This is interesting, there’s a number of factors that I’d have thought would make this pretty impossible to get right, you may make it perfect for you or your testers but not the greater audience. If I just look between me and my fiancee, our reachable zones are quite different, and we’re both right handed, if you look at catering to left handed people as well then it would be different again. I’d be interested to know how you thought to sole those sorts of issues
I wasn’t sure how i’d feel about the safari changes, I haven’t used safari in a long time but have now moved back to it after trialing it and am really liking it so far.
I think the issue for most os just the fact it’s different, but once you get past the muscle memory issues and get use to it, the reachability aspects of it are really great. I really like swiping left and right on the bar to go between tabs quickly too