Swype pioneered a new way to type on smartphones–now it’s dead
arstechnica.com
arstechnica.com
RIP Swype.
Honestly I'd like it to go further. Like a keyboard gesture to autofill my email address into a text area.
Anyway, I love it. Y'all crazy.
This always make me laugh when said figuratively.
Regular typing on phone keyboards with predictive suggestions is really helpful for me getting the spelling correct, because it gives good early feedback and can often susgest based off a full misspelling (though, I always get the impression that suggestions are not designed for my style of misspelling, for example I keep misspelling 'susgestion' in this reply and it can't cope with the extra s). The annoying side effect is that I sometimes end up with completely the wrong word.
For me, Swype style is faster, if and only if I know how to spell a word.
If I don't know the correct spelling, gesturing is useless. It predicts a completely different word.
(Side note: unlike other teens, my spelling massively improved after I got my first cellphone at age 15 and used nokia's T9 predictive texting. Simply because after you made a mistake, it stopped predicting valid words)
Typing one or two letters then hitting the suggestion has always been way more consistent for me.
thumb swiping works fine for 3-word responses, anything more than that and it's the index finger that goes to work.
I swipe almost 100% of the time but I feel the system could be improved massively with some better prediction. The Android keyboard consistently gives me the wrong input for some really common words. How does "sine" appear so often instead of the everyday word I was trying to type (I think it's "don't" but I can't remember exactly)? Why doesn't it learn as I correct it every time? Why doesn't it look at the context.
Added advantage of not needing to look at the screen all the time to work, something that was previously only possible with tactile keyboards back in the day.
Also in particular annoying when I go back and forth between two languages. Then I have to switch language on my keyboard every other time I want to type anything. And I have to get used to the different layout, which with swiping seems to be even more annoying.
As for multi-language, SwiftKey seems pretty good, you don't need to switch between languages, it handles two (maybe three) at the same time relatively well.
I don't trust any of the closed source options.
Who wants to start a bounty on an open source replacement?
You made my day!
You can swipe for "navigation" and set new long-press strings.
It linked to the patent[0], and it struck me that in the abstract, it ends with: "The present invention then generates a list of possible words associated with the entered part and presents it to user for selection."
That's kind of a... specific... outcome of the swiping and I'm surprised that's in there. As I understand it, people get all up and arms about ridiculous patent titles, but it's the full abstract that determines what it exactly covers, and if you deviate just a bit, the patent doesn't apply. In the case of the Google keyboard I use, when I finish swiping it doesn't "present a list of possible words for selection" - it just chooses the "best" one. There is a list elsewhere of alternatives, but I wonder if that's just different enough of a UX that the patent doesn't apply.
IANAL. They probably dropped the ball in writing "presents it to user". If they had stopped at "generates a list of possible words associated with the entered part." There would very likely be a sub-process that generates a list of possible words in all other implementation, that sub-process should be violating the patent regardless of what the user sees.
I think there wasn't interest because handwritting seems like old tech :)
But the glory of it initially was that it made it possible to go fast on much smaller screens. I first used it very happily on a Nokia 700 (Symbian Belle phone) with a 3.2" screen that can't have been more than 4cm wide.
I briefly hoped that swipe typing would become popular enough to stall the trend for bigger and bigger screens on phones, or at least make it economic for some manufacturers to provide at least one small phone. But it seems like the opposite happened, huge screens were popular enough to make swiping pointless for most people.
To be honest, though, I never did like using gesture based swipe typing. It always felt like a sloppy and imprecise input method to me.
I use GBoard now and it has this horrible "correct the previous word" feature that I can't turn off. Unfortunately, or perhaps fortunately, Google is big enough to keep it around forever without really listening to us. But this feature is awful. For an example, I'll type something like "a little bit of mambo" and, for some reason, it'll decide to replace "of" with "if" or something along those lines. It's not a consistent thing with any combination but I really don't want to have to erase two words to correct something that I had already dubbed correct before moving on.
I've been having this exact problem with both swype and SwiftKey. anyone know a gesture keyboard without this crap?
I think when Nuance purchased Swype all they wanted is the patent, and simply didn't want to spend resources on developing Swype when they could get money through royalties. The original Swype preferred to be sold to OEMs, but OEMs typically want to make their Android version unique, so might actually prefer to implement their own keyboard with that functionality. This plus the fact that Swype quality degraded since Nuance's purchase makes me believe that they just went the route of permitting other companies for using their patent in exchange for royalties.
- displaying originating city/state based on area code of a calling number
- swipe to unlock the phone
- rounded corners
and is trying to get money from anyone who uses it
Typing through swiping is a bit more innovative.
To be honest, I think there shouldn't be any patents on software. That field is thrives on building on top of work of others, and things change quickly, so patents are actually stifling innovation. At least if software patents can't be eliminated they should be much much shorter.
trolling comes down to their use of patent ownership and how they (ab)use it to make cash.
That said, gestural input does feel significantly more natural compared to trying to cram a QWERTY layout onto a pocketable screen. For me the ideal midground has proven to be a "dumb" keyboard that has a layout designed for touchscreens from the outset; "MessageEase" (which I plug at every opportunity) uses a combination of single taps and directional swipes with a layout based on letter frequency.
It takes a bit of adjusting to, but it provides a great balance between precision and speed, while also having plenty of room for less common symbols and Ctrl/Alt/modifier keys that are useful for SSH, all without having to tap through extra layers or menus.
I encounter one frustrating problem with Gboard that I never encountered on other keyboards, and I don't know if it's a bug or if I'm "using it wrong". Sometimes I will swipe-gesture a word and the keyboard simply won't recognize it as a gesture. I could be moving my finger all over the place for 5 seconds and it'll just type the last letter I land on. I backspace and do the same thing again and it works.
Am I accidentally making some sort of "out of bounds" gesture without realizing it? Is my phone too slow to start noticing that I'm swiping? Or is this just a random bug?
Software companies do not get acquired for the software. They get acquired because they offer access to something that BigCo can't easily replicate, usually a loyal audience in a sector that BigCo covets (e.g., Facebook and Instagram). Sometimes it can be about intellectual property, but as we see in this case, they have big fancy lawyers and you don't, and they'll work hard to circumvent you, so you'll have to have a very robust and thorough IP base to get them to decide it's better to just buy you.
Swype is by no means the first innovative phone app to get NetScaped like this. It happens all the time.
If you're building a company in this space, where the platform operators are also the main distributors and therefore don't need your audience, be very careful. It's dicey. [This may be a good argument for alternative app stores a la Amazon's Android offering.] Blockbuster anti-trust cases only happen for companies that are the darling of 1996 Silicon Valley and the symbol of the nascent internet revolution (i.e., not you).
Simply put, a technology advantage is still hard to really to quantify in business or acquisition strategy unless it already has a large amount of users or a huge advantage over building it yourself.