[thaumasiotes]

I use swipe-style input (don't know whether it's actually swype) for most things. It's somewhat annoying that it can't tell the difference between words with identical swipe patterns.

I find it more annoying that it can't even attempt to render words that it doesn't know. The reason is exactly the same as its inability to distinguish "isn't" from "orange" -- there just isn't enough information in a swipe to identify any intended letters. But a failure to recognize a novel word means you can't correct the IME - you have no other option but to switch input methods.

[Aerroon]

I think Swype could rely more on repeatable patterns. Eg if you're swyping in a straight line and want a letter included from that you should do a little loop on it. Eg with "our" I do a little loop on "u" and it doesn't pick "or" anymore. But it does then also pick "out"...

It should be way more accurate on the starting and ending characters. If I'm starting with "i" I'm not going for "orange".

One thing that frequently trips me up are names. I'm swyping a regular word and it thinks I want to use a name I've never used before.

[lights0123]

SwiftKey definitely notices if you do an extra movement on a letter—it's quite easy to differentiate between "to" and "too" with that strategy, even when it doesn't have the rest of the sentence for context.

[thaumasiotes]

> It should be way more accurate on the starting and ending characters. If I'm starting with "i" I'm not going for "orange".

The whole point of using a very-low-fidelity input method is that it's faster. How much care and effort are you planning to put into entering each word?