Live data from Hacker News

FUTO Swipe – A new swipe typing model

swipe.futo.tech

131–140 of 261 posts

Re: FUTO Swipe – A new swipe typing model

#131
post #129
post #104

Earlier quoted context omitted.

> Gboard swipe typing works flawlessly, FUTO still an Alpha project I agree. I find that swipe typing on Gboard feels much better than FUTO's because I think it adapts to my typing style. I tried FUTO about six months ago, and it was a bit frustrating so I switched back to Gboard. Hopefully, it has improved since then, but I haven't checked.

> Hopefully, it has improved since then, but I haven't checked. Good news then because you're currently in a thread about how FUTO has improved!

Just because they say so doesn't necessarily make it true, which is why I included the "hopefully" and "haven't checked".

Re: FUTO Swipe – A new swipe typing model

#132

What I really want is a swipe model that can tune to multiple languages simultaneously when a keyboard layout can support it (English + German, German + French, etc). I rarely need more than 2 languages simultaneously, but the "switching between 2 languages" point is painful.

Trilingual here. Gboard on my pixel 10 pro does support swipe type while code switching between multiple languages. Works reasonably well. Accuracy is a bit lower for words that are collisions across languages

Re: FUTO Swipe – A new swipe typing model

#133

Lots to be desired, unfortunately. I tried 3 different words. It nailed the first 2 but the third was impossible: The word "serverside" is impossible to swipe. I tried 10x, never did it even come close.

I don't think server side is in their dict without a dash. I don't know how to type dashed words in swipe. SwiftKey cant do it either. Long words usually work very well though. That's most of what I use swipe for. Short words I tap, long words I swipe.

e.g.,

Broadside Surfside integration financially illiterate calibration fantastical proliferation haphazardly horrifically striations proliferation (all typed first or second try except antidisestablishmentarianism which admittedly I got carried away)

Re: FUTO Swipe – A new swipe typing model

#135

This keyboard seems to ship with a dictionary that includes a lot of curse words. No more ducking around.

What dictionary are you using? I installed the app on android and am not able to type "fuck", neither with the inbuilt dictionary nor from an imported English (UK) dictionary from their site. Even typing it manually doesn't seem to add it to the dictionary, which makes it really annoying to use.

Re: FUTO Swipe – A new swipe typing model

#137
Fun fact for the first apple keyboard layout on the first iphone, the touchscreen hadn't the resolution to tell appart which letter you meant to type in, so it changed dynamically the "hitboxes" of the letter buttons when you typed a certain letter. (for instance if you typed the letter "i", the hitbox of "t", and "n" were changed to be bigger, because there is a high probability you were hitting those next. Here is an article that talks about it : https://www.cnbc.com/2017/06/26/creation-of-the-first-iphone...

Re: FUTO Swipe – A new swipe typing model

#140
post #137

Fun fact for the first apple keyboard layout on the first iphone, the touchscreen hadn't the resolution to tell appart which letter you meant to type in, so it changed dynamically the "hitboxes" of the letter buttons when you typed a certain letter. (for instance if you typed the letter "i", the hitbox of "t", and "n" were changed to be bigger, because there is a high probability you were hitting those next. Here is…

>the touchscreen hadn't the resolution to tell appart which letter you meant to type in

Is that really true? My memory of the original iPhone's touch screen is that it was pretty much pixel-accurate.

The article mentions that the keyboard wasn't accurate enough: "But by early 2006, the iPhone keyboard still didn’t have the accuracy Apple needed to ship the phone." I don't think that means the screen wasn't accurate; all it means is that the original iPhone had a small screen, so the buttons on the keyboard were tiny, and hitting them precisely was difficult. That's why the hit boxes of more likely keys were enlarged.

Post reply on HN