Somewhere, deep in the bowls of Redmond an alarm has gone off.
It’s labelled: ‘Somebody wants to pay us money, by choice’
Everyone is confused. It’s never happened before.
There are lots of software keyboards for smartphones and tablets alike, but one stands head and shoulders above the rest… However you can't have it. Last year, Microsoft bought Nuance for just shy of $20 billion, mainly for its voice-to-text tools. Nuance also owned Swype, which it killed off in 2018. Microsoft, meanwhile, …
"It’s never happened before." - or rather, not often.
When they revamped the Word macro language back in the day, they naturally dumped support for the old one. UK Ministry of Defence had invested millions over recent years in creating desktop productivity tools using it. Suddenly, it all broke. How much MILITARY-SCALE(!!!) budget cash would M$ require to reinstate its support in Word? Nothing doing came the reply, we have moved on.
Of course in MoD a drop in desktop productivity is hardly noticeable and might even be construed as a good thing. But the state of MoD is not Redmond's fault.
They are not confused, they are just trying to decide which coffee machine to use next. In five minutes they will have forgotten what all the fuss was about.
They're more likely to see just how badly they can screw it up, charge a subscription fee to use it claiming it will get frequent updates, then assign a troop of dyslexic myopic dyspeptic Howler Monkies to do the coding for all future releases.
Something about clowns, monkies, flying feces, and the Peter Principle? =-Jp
Historic user of Swype and then SwiftKey.
I have to say that I disagree about SwiftKey's prediction being good. I've finally abandoned it because I was fed up of the completely ludicrous suggestions it came up with far more often than not. I don't remember what Swype's were like, just a sense that I used to have far less trouble 'then' than I did 'now'.
"psychic[psychotic] keyboard."
My Xperia had whatever bog-standard keyboard there was - then, after a system update, ended up with Swiftkey being the only option. I probably wouldn't have noticed, but only when I went into the settings to try to tame the thing did I notice that it was Microsoft Swiftkey. Still make more mistakes on entry that what I used to
Hmm. I'm no great user of text on a mobile, but I do use Duolingo in German, Spanish (and English, of course) and I note that the predictive text with swiftkey will generally suggest an easy 80% of the correct answers to a translation challenge - often without hitting any key, but almost always after an initial key is pressed.
Since Duolingo's translations are rarely things one might expect to come up with in normal speech - "My dog is unemployed and has only one eye" - I have wondered how much phoning home to the mother ship is going on.
It doesn't seem to care which language I'm typing, apart from its inability to generate umlauts and other diacritics.
Given the way Windows is being developed, I expect they are more likely to remove Swiftkey from W10/W11 due to lack of use and well it's more Apple-like(*)...
I like MS's website [ https://www.microsoft.com/en-us/swiftkey ] not a mention of Swiftkey for Windows...
(*) The continued absence of a swype-like keyboard bundled with iOS is still surprising given Apple's legendary focus with iOS on ease of use and user experience.
Thanks for listing some of your favourite features, some of those are new to me.
If Swype isn't coming back, and I'm stuck with GBoard on a new phone, all I ask for is ONE feature from Swype – when the cursor is in a word, just press the Swype key to select the word. I don't have the coordination, especially when walking, to double tap precisely on one word.
OK, maybe another feature request from Swype. When entering a string of numbers without having a dedicated number row, you can press the letters that have the numbers, and one of the autocomplete words will be your string of numbers - for example, typing qwerty will offer 123456. It saves just that little bit of time vesrus long-pressing each key for the number.
LOOK, JUST GIVE US SWYPE BACK!!11@@!!!
The problem is that many of us use swiping to type nowadays as it can be vastly quicker than pecking at individual non-keys, and virtually none of the open source options support this.
I've been trying to use AnySoftKeyboard for the past month or two which does, but sadly it's pretty rubbish compared to Gboard etc - inefficient enough possibly to force me back to being spied on by Gboard again.
They'll bring it back, but with a fiendishly complex interface that differs depending on whether you've logged in with your Microsoft account, or with your Microsoft 365 account with the same exact address, also at Microsoft.
If you've used your Microsoft 365 account, certain Swype actions won't be available unless an extra security setting is accessed through powershell, for most people, sometimes. This is for security.
I'm not saying it is better or worse than any other particular keyboard.
But, while I'm a reasonably proficient and fast touch typist on a standard querty board, I find the querty layout on a screen is just bizarre and difficult to work.
MessageEase uses a completely non-querty grid with swiping and circling motions.
I find it pretty damned good, but have never knowingly met anyone else who uses it.
Are you out there? Or did you try it and decide against using it?
Swype is probably the thing I miss most about having a Windows Phone (other than websites giving up on forcing me to an app because no-one made windowsphone apps, oh, and the Nokia Lumia's camera).
I figured some of the issue was just me not adjusting to the change instantly, but yeah, it really was *better*.
Please. PLEASE continue development of Swype!
The swype-to-activate copy, paste, cut, Numpad, Arrows, Capitals, quote-space, no-spaces, alternative selection, typed word caps-change... the list is not short, and the swype engine is SO MUCH BETTER than any other keyboard available. Couple it with SwiftKey's Prediction? you'd never need to do word replacement, but this is accurate without 'learning' your 'voice' style.
Hands down the best thing I"m still carrying on my S21 that I bought on my gen-1 'Galaxy S'
Especially since, as a disabled person, I can only operate my phone one-handed, any you can be sure I'm not going to be tapping on the screen holding an S21 Ultra and walking... but Swyping? That's doable.
Please don't continue to develop Swype. The first version I used on my Galaxy S was fantastic, it seemed to know what I was typing before I did. The next few updates were cosmetic and made it look great with themes etc. However, at a certain point the prediction started getting worse and worse with each upgrade, I was actually glad when they abandoned it, as it hasn't degraded any further. Despite all that it is still better than any of the alternatives I've tried.
Talk about a blast from the past. I last used it on my old Nokia N8 and then when I (had to eventually) move to Android it just wasn't available. Sony's keyboard had a reasonable swipe built in and then they moved to Swiftkey which was a bit better at it. Unfortunately even though "Swype keyboard" is in the Play store search suggestions/autocomplete, it doesn't show up under any of the results. Does mean you can only still use it if you (once) bought it?
I don't use keyboards that don't actually have keys or boards, but I have long been mentally asking MS to take my money for Streets and Trips. It was IMO the best of the consumer mapping programs for PC, and they won't take my money for that either. I use 2013, the most recent version, in a perpetual trial version in a VM (where I roll it back to the not-yet-run state after each use). It's the best I can do when the ability to pay for it does not exist.
I use Yandex keyboard on Android.
I actually find its predictions better than the competition. But that's damning with faint praise. Without exception, every keyboard I've tried on mobile has had me wanting to throw my phone through the window half the time. especially when [as pointed out by others] they will all ignore a word you type multiple times a day and instead insert some random word so irrelevant it makes you shake your head in disbelief.
Oh dear. Why does someone always feel the need to make that tediously predictable quip, whenever a Russian company is mentioned. Or similar about the CCP when a Chinese company is mentioned?
Because no US company would ever spy on its users would it?
Besides which, given my lack of military or industrial significance, neither Mr. Putin or the CCP are ikely to be in the least bit interested in my humdrum existence --unlike all those companies in the good ol' US of A which see my personal data as ammunition in their unending attempts to part me from my money.
I'll try Yandex, haven't found a good replacement yet for the Samsung keyboard on mine which does the whole random word thing plus the added bonus of if you catch half a pixel of the delete key while swiping it will delete half your message.
Utterly infuriating.
I don't think you'll ever find a keyboard you like for that. There are phone keyboards for technical stuff, which just have the extra punctuation on the main keyboard. Adding extra things like syntax and variable prediction would take even more screen real estate, and writing code needs quite a lot of that for other stuff. Phones just are ill-suited for writing code, and I don't think a different keyboard organization will fix the reasons why.
I have a feeling it might be possible to write language dependent keyboards. Code is ideal for some predictive text and I used to use swiping commands 40 years ago so it should be possible to come up with some multi-fingered commands for inputting language features. I guess I'll need to write it on the PC to start with!
This is a "keyboard" which is implemented in (that is, created by...) SOFTWARE!
What's the big deal?
Somebody, who is bitching about the lack of a really great SOFTWARE KEYBOARD, either write the NGK (Next Great Keyboard), or cause it to be done.
Just ask the software gurus, or, better yet, their managers: software can solve all problems; it can even build a new airplane.
Does 737 MAX ring a bell?
... that people who say corporations are sending us their best products are naive... at best.
Who say that corporations would never deliberately buy and retire superior technologies, are also naive... at best.
Who also say, markets are purely demand driven so corporations MUST sell better products to stay competitive, are naive at best.
See a trend here? And this is just example... 546,234 of our fine and lovely capitalist consumer world.
[...] "or "wont" from "won't" [...]
Someone in probably the 1930s published a chronological series of books purporting to be autobiographical based on their years growing up in England. It was interesting that the contractions used "wont" and "dont" - always omitting the apostrophe. That made me wonder if it was down to the author/printer*** - or a fashion at the time. Never thought to notice if any possessives also were contracted.
***As a student, broadcaster Robert Robinson had dealings with the Oxford(?) publishing house - which he said specialised in salacious material to supplement their earnings from academic publications. It is possible the typesetting and printing was done in another European country.
Microsoft paid $20B for the speech to text software?! I've used it on windows 10 virtual keyboard, it's a total waste of time.
I don't know why people rave about SwiftKey but Swype was definitely better than GBoard in accuracy and functionality.
One thing that is missing from both is undo. I can't understand why. What do these developers have against undo?
It's so easy to implement and it's crucial sometimes.
I do like Swiftkey more than Gboard (especially after Gboard's recent update), but I'm in somewhat of a niche and like to use Gboard's Japanese handwriting input.
Swiftkey doesn't have Japanese handwriting support and likely never will (as Microsoft translate doesn't either - Windows has an IME for it though, so Microsoft have had the data for it for years).
I'd use Swiftkey and Gboard's Japanese handwriting keyboard together if only Microsoft would make switching between different company's keyboards quick. Instead it hijacks the keyboard and you have to go digging into the settings to change it.
And Gboard does allow quick switching to different company's keyboards. You just can't quickly switch back.
Ugh. I've never understood why anybody would want that atrocity.
The only reason I'm going to swipe to a different character on a phone is because my finger landed on the wrong character in the first place. With that abomination I'd not only not be able to slide my finger to the correct character and get it, I'd have to hit delete twice to remove the correct character and the wrong character, try again, and then probably have to hit delete a few times again. That is, if I'd actually managed to hit delete.
It's unusable. Take your broken keyboard and shove it up your backside.
I have an iPhone but just found that SwiftKey is available. I may give it a try. Apparently Swype was available but got pulled when it was discontinued (so can't buy it since I didn't before)...
Generally I think iPhone autocorrect and predictions are pretty decent except for two issues that massively bug me:
* It almost always uses "ate" when I want "are"
* It almost always uses negative contractions when I want the positive ("couldn't" vs "could")
I use Swiftkey and have done for probably 10+ years. A few years back, I started noticing it seemed to be going downhill rather badly. It would randomly delete words I'd just typed and occasionally I'd type a word only to look up and see it was total gibberish e.g. I'd see dsczkudjr instead of the word gibberish! Some of the predictions were miles off what I was looking for. And then, one day, I noticed it no longer said SwiftKey on the space bar; it now said Microsoft Swiftkey. 'Ahhhh!' I thought, 'That explains it!' I've now set my expectations accordingly i.e. at rock bottom.
So be careful what you wish for: if they bring back Swype, you can be sure it will not be the Swype you remember. Nostalgia is not what it used to be, after all.
I remember buying Swype back in the day, I really enjoyed it, but when Gboard gained similar functionality I dont think i reinstalled it when moving to a new phone.
Might give it another shot.
If you've bought it, you need to go to your purchases and you can navigate to it there. I had to scroll all the way back to July 2013!
...but I'd actually like to see a decent, no-frills reliable T9 keyboard for Android.
My fat thumbs mean that I definitely rely a lot on auto correction and word prediction, but the muscle memory that I built up working my way through the ranks of early non-smart phones means that a T9 keyboard is still probably the fastest way for me to write a message.
I have attached my resume for your reference and hope to hear from you soon as I am currently working on the techno gym kit for the rest of the week but I will be back from the ancestral lands and I will be back from the ancestral lands and the rest of the week but will be back from Tuesday morning for the rest I will be back
I am late to this party, but I (Cliff Kushler) was the first guest to the Swype party, having invented it and the many features referenced above. I just want to mention that, in the process of Swype's original acquisition by Nuance, its recognition engine was grievously damaged by virtue of throwing away its custom database (which contained much vital information) and forcing it to get by with the linguistic databases that were in use in other Nuance software. Swype's current ability to correctly recognize words from hastily and inaccurately traced paths is a mere shadow of its former, pre-acquisition self.
One other feature which did not survive the acquisition is also one that I sorely miss. Two things:
1) When entering a large chunk of text, it is natural to forge ahead, Swyping furiously and of course not noticing that some word along the way was mis-recognized.
2) It is VERY painful to try to accurately re-position the cursor by tapping the screen.
The original Swype allowed you to double-tap a word elsewhere in the editing space, select an alternate word from the actual original word list generated from the entered trace path (this was stored in a temporary buffer) so that the actual intended word was almost always there, thus replacing the mis-recognized word with the correct word. Then, the text cursor would automatically and immediately "snap" back to the current position where you are actually ready to continue entering text. So, recovery from a mis-recognition was "Double-tap the word, select the correct word from the list, and continue with no further fuss." If I say so myself, it was elegant, and I miss it every day.
If Microsoft wishes to re-create the original Swype keyboard, I would be delighted to assist...
OMG Hi Cliff, thank you for coming to the party! I need to know one thing, what version is the best to use that has all the features in it's glory. I've got the following versions
2.2.3
2.3.0
3.2.1
3.2.2
3.2.3
3.2.4
Maybe 2 things, have you got a better version that works, in your opinion, the best?
Cliff, amazing to get the chance to say thank you to the guy who developed what is still the very best keyboard for Android. I still use it, and desperately wish for an up-to-date version. Are you working on a keyboard with similar features, by any chance?