Famous last words, I know, but I'm probably never switching back to iOS.
-
@ppatel It's unacceptable. It's not like iPhones are cheap, and Apple gets a lot of free good will in the Blind community because they were the first to do accessibility right, but I'm really struggling to give them any free passes at this point.
@NoahCarver Oh definitely. I gave them a free pass until a few years ago. Android's Braille support has come a long way. It's got other problems. On the balance scale, I'd say they're quite equivalent these days.
-
@NoahCarver Oh definitely. I gave them a free pass until a few years ago. Android's Braille support has come a long way. It's got other problems. On the balance scale, I'd say they're quite equivalent these days.
@ppatel What are the issues you're still seeing on Android? Had a Pixel for over three years and there were more than a few which royally annoyed me. Last straw was the lack of HID Braille support plus (at the time) really broken support for the Mantis Q40. All that's been fixed now AFAIK but my Pixel 5 wasn't ever going to get the necessary kernel updates to make Bluetooth ID Braille a thing and I had had enough.
-
@ppatel What are the issues you're still seeing on Android? Had a Pixel for over three years and there were more than a few which royally annoyed me. Last straw was the lack of HID Braille support plus (at the time) really broken support for the Mantis Q40. All that's been fixed now AFAIK but my Pixel 5 wasn't ever going to get the necessary kernel updates to make Bluetooth ID Braille a thing and I had had enough.
@ppatel In writing this out, I'm realizing just how much I've stupidly lived by the "grass is always greener on the other side" philosophy without recognizing it... ugh.
-
@ppatel In writing this out, I'm realizing just how much I've stupidly lived by the "grass is always greener on the other side" philosophy without recognizing it... ugh.
@NoahCarver GBoard. No matter what device I use, that thing is incredibly slow. When you have to wait for the letter to respond upon landing/key press, it almost makes it not worth using. If I weren't attached to my Bluetooth keyboard, I'd chuck my Pixel 9 pro out the nearest window.
-
@ppatel In writing this out, I'm realizing just how much I've stupidly lived by the "grass is always greener on the other side" philosophy without recognizing it... ugh.
@NoahCarver The annoying thing is that this issue isn't seen by many other people. Apparently it got fixed for most people.
-
@NoahCarver GBoard. No matter what device I use, that thing is incredibly slow. When you have to wait for the letter to respond upon landing/key press, it almost makes it not worth using. If I weren't attached to my Bluetooth keyboard, I'd chuck my Pixel 9 pro out the nearest window.
@ppatel Ah. Good to know. I used Braille keyboard wherever I could so never dealt with it long enough to find it notice.
-
@NoahCarver The annoying thing is that this issue isn't seen by many other people. Apparently it got fixed for most people.
@ppatel Aaaaaaaaand that's why I never noticed it. Makes sense now. Ugh. Sorry. That's got to be frustrating.
-
@NoahCarver This is the most aggrevating bug when using a display with iOS these days. It's bloody annoying. Hard to do work when the keyboard just can't let you input.
@ppatel @NoahCarver I found that turning off single letter navigation fixes it for now
-
@NoahCarver GBoard. No matter what device I use, that thing is incredibly slow. When you have to wait for the letter to respond upon landing/key press, it almost makes it not worth using. If I weren't attached to my Bluetooth keyboard, I'd chuck my Pixel 9 pro out the nearest window.
@ppatel @NoahCarver I agree, GBoard is far from usable, but. Go to settings, preferences, and somewhere down there should be Flick input sensitivity. Move the slider to low and it should at least, be not that horrible.
-
@ppatel @NoahCarver I found that turning off single letter navigation fixes it for now
@tjolsen @ppatel @NoahCarver Yeah, was typing on Pixel 8 yesterday, running 17.1 Beta and was pleasantly surprised that GBoard was actually responsive finally. Otherwise yeah, it's been so darned sluggish for a while. Here's hoping they've figured it out.
-
@tjolsen @ppatel @NoahCarver Yeah, was typing on Pixel 8 yesterday, running 17.1 Beta and was pleasantly surprised that GBoard was actually responsive finally. Otherwise yeah, it's been so darned sluggish for a while. Here's hoping they've figured it out.
@mcourcel @tjolsen @NoahCarver I'll have to download the 17.1 beta then. I'm really tired of Gboard.
-
The reason for this attempted jumping of ship, by the way, is a bug which I've posted about on here. Basically, if you use a Braille display with an iOS device, your software keyboard can and will disappear at the most inopportune time after you've disconnected the display regardless of what the "use on screen keyboard" setting is set to. The only way to get it back is to reconnect the display assuming you're near it, press the "show/hide keyboard" command a few times, disconnect the display, and wait for it to happen all over again. This has been in 2 major iOS versions now, and Apple has not fixed it even though I and others have reported it multiple times. It happened several times over the last two weeks and I'm expecting it to keep happening.
@NoahCarver I have not had this, but I'm 100 percent display user due to my hands not being made for touch screen use.
-
@ppatel What are the issues you're still seeing on Android? Had a Pixel for over three years and there were more than a few which royally annoyed me. Last straw was the lack of HID Braille support plus (at the time) really broken support for the Mantis Q40. All that's been fixed now AFAIK but my Pixel 5 wasn't ever going to get the necessary kernel updates to make Bluetooth ID Braille a thing and I had had enough.
@NoahCarver @ppatel Sorry to jump in, but I have one major issue that prevents me from coming back to Android: absence of the magic tap. And as a phone is, well, a phone, I absolutely want to answer calls quickly and reliably, whatever messenger is used. Unfortunately, Android doesn't have such a thing.
And the second issue is keyboard responsiveness. Maybe it's better on Pixels, but I heard mixed reviews from users. -
@NoahCarver @ppatel Sorry to jump in, but I have one major issue that prevents me from coming back to Android: absence of the magic tap. And as a phone is, well, a phone, I absolutely want to answer calls quickly and reliably, whatever messenger is used. Unfortunately, Android doesn't have such a thing.
And the second issue is keyboard responsiveness. Maybe it's better on Pixels, but I heard mixed reviews from users.@menelion @NoahCarver @ppatel Android has had the magic tap for years and years, ever since Talkback introduced multitouch.
-
@menelion @NoahCarver @ppatel Android has had the magic tap for years and years, ever since Talkback introduced multitouch.
@TheQuinbox @NoahCarver @ppatel Does it work for every messenger or only for the phone app? I've never heard you can answer a WhatsApp or a Telegram call with magic tap on Android.
-
@TheQuinbox @NoahCarver @ppatel Does it work for every messenger or only for the phone app? I've never heard you can answer a WhatsApp or a Telegram call with magic tap on Android.
@menelion @TheQuinbox @NoahCarver Unlike with iOS, Magic tap needs to be implemented by each app. Otherwise, the app doesn't respect it. It's far more integral in iOS's implementation.
-
P pixelate@tweesecake.social shared this topic
