Live data from Hacker News

Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

ios-countdown.win

601–610 of 826 posts

Re: Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

#601
post #510

It will be hard, but I’m transitioning out of Apple ecosystem regardless of whether they improve. Just like Windows 11, I get ads whether I want them or not - just got a push notification for a new financial product (!!!) despite going out of my way to opt out. iOS 26 made my 16 Pro, practically brand new, feel slow. I upgraded because my 13 mini was slow, and I chose Apple in the first place because they had some of…

I'm curious why my experience with Windows 11 is so different from what I regularly read. It was some years ago now, so I don't remember exactly what configuration steps I went through, but presumably I turned off ads when I first installed. And so, I don't get ads. I don't recall ever seeing an ad embedded in Windows. Are people talking about Edge (which I don't use) or inside the Microsoft Store (which I very rarel…

Your Windows 11 experience strongly, strongly depends on where you are. Are you inside the EU? 90% of the crap people complain about is simply illegal and you don't see any of it.

Re: Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

#602

Earlier quoted context omitted.

Not always , if we go back to the 1980s. But in very modern times, they've lost all the learnings from back then.

lol, no, they sucked even more in the 1980s. Did you ever notice that "About this software" is the first thing on the first menu of every application? Is that because people have to know what version of the software they are using every time they start it? It's still like that today, and it's very very stupid. Other OSs get it right and put the version information on the last menu, where it doesn't clutter up the mos…

Heh, you're going to mention a mouse without bringing up the puck?!

Re: Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

#603

Earlier quoted context omitted.

Extremely common pitfall in UI engineering. If you treat all input as a queue that's divorced from output, you end up with situations like this. It's kind of a paradox, but in many cases you need to actually discard touch inputs until your UI state has transitioned as a result of previous inputs. This gets extremely nuanced and it's hard to write straightforward rules about when you should and shouldn't do this. Some…

https://developer.mozilla.org/en-US/docs/Glossary/Debounce

Okay, how long is the debounce window? Where in the input pipeline do you debounce (obviously not immediately on keystrokes)? Will debounce work for long-running requests, which are event-driven and not time-driven?

I have seen, far too many times, naive approaches like wrapping all click handlers in a "debounce" function cause additional issues and not actually solve the underlying problem.

Re: Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

#604
"caved to the blue bubble pressure"

As an Android user, I truly don't understand this "pressure". I exchange SMS/MMS with various users, some Android, some iPhone. I am in group chats with both Android and iPhone users. I feel there is no major issue. It's interoperable. We all see each other's emojis/photos/videos/etc. There are only minor technical rough edges: for example an iPhone's user emoji reaction sometimes (not always?) shows up as separate text instead of the emoji appended at the bottom of the text bubble... And I am pretty sure videos are sent in a lower quality. But is any of this really enough to cause a "blue bubble pressure"?

I asked ChatGPT to explain but only got this vague answer: "Group chats with a mix of iPhone and non-iPhone users can be less seamless (e.g., lower video quality, no read receipts, or issues with group chat features)."

I had to open my texts to check: I indeed have read receipts when texting Android users, but not iPhone users. And this is funny but up to this very second, I had never noticed this difference... because, at least to me, read receipts is such a minor feature that I rely on very infrequently.

This leaves me still as perplex: why the "blue bubble pressure"?

Re: Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

#605
post #126

Earlier quoted context omitted.

Gboard is a lot better than the native keyboard. Strange that OP is going to such lengths to complain when iOS supports other keyboards. The main benefit I've found with Gboard is a larger vocabulary, and perhaps a less aggressive autocorrect that doesn't constantly try to correct technical terms into similar common words.

I’ve tried Gboard and SwiftKey on iOS. Not sure if Google just gave up on updating the iOS variant or if Apple holds it back intentionally (probably a bit of both) but they pale in comparison to their Android counterparts. I’d prefer a useable stock keyboard but I take your point.

SwiftKey also crashes daily. There's no good keyboard for iphones, at least for my stubby fingers. I've literally won local mobile typing speed contests (so it's not user error I dare say) and the last five-ish years that I've been on ios have been a total and utter misery. If I had some cash floating around I would be back on android.

Re: Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

#606
post #90

Earlier quoted context omitted.

And to be clear 'do anything to fix them yourself' is as simple as install a third-party keyboard from the official Play Store, if you had such an issue as this with the default 'GBoard'.

You can install third-party keyboards on iOS too, I'm not sure why that's not considered an option in this case.

3rd party keyboards are frequently banned from some of the bank apps, delivery services and so on.

This way you have to keep the default one anyway and make even more typos when yet another app forces you to get back to Apple’s keyboard.

I can’t even search stuff in my local delivery with SwiftKey

Re: Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

#607

@ozzyphantom: You might consider being more specific about your grievances in the text of your countdown page. As it stands, it's a bit vague, describing the keyboard as "broken" and autocorrect as "nearly useless". Sure, the video you link to is more descriptive, but it's a lot to ask of a visitor to click through and watch a separate video. As for the underlying issue, I have experienced similar typing issues on my…

[dead]

Re: Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

#609

Earlier quoted context omitted.

The YT video they linked is excessively clear about what the issue is. There's no point in explaining it again. https://www.youtube.com/watch?v=hksVvXONrIo

> Sure, the video you link to is more descriptive, but it's a lot to ask of a visitor to click through and watch a separate video.

It's a 2 minute video. It gets the point across faster than any blog post.

Re: Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

#610

@ozzyphantom: You might consider being more specific about your grievances in the text of your countdown page. As it stands, it's a bit vague, describing the keyboard as "broken" and autocorrect as "nearly useless". Sure, the video you link to is more descriptive, but it's a lot to ask of a visitor to click through and watch a separate video. As for the underlying issue, I have experienced similar typing issues on my…

I see where you’re coming from, this was an impulsive creation after months/years of frustration without any expectations. For anyone curious of my experience here are my main pain points: - autocorrect failing to correct minor mistakes - autocorrect “correcting” a mistake with another mistake - autocorrect “correcting” correctly typed words - swipe to type is painfully behind Gboard (third-party keyboards are univer…

> Clearly tapping a letter “taps” a different letter

My iPad Mini 6 sometimes gets into this state, especially after deleting something, when tapping one of the keys in the lower right corner becomes completely impossible, it always registers as this different key (I don't have the iPad nearby to check which one), and it stays broken like this until I press a few other keys. It's incredibly frustrating and it's been there since day 1.

Post reply on HN