• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Swiftkey 4

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
It's little things like that which made me stop using Swiftkey even though I purchased it.

It's as if the developers simply can't conceive that some people might not like the idiosyncrasies of Swiftkey (the numpad, spaces after predictions no matter what, no tap to word correct, no dictionary editing).

I left at the Flow beta but Swiftkey 3 was more sluggish than some of the alternatives too. You probably wouldn't notice on faster phones but wow it's noticeable on mine.
 
Not sure I like the way flow works with word suggestions. Seems like it'll insert what it thinks is the right word, and if I want to change it I have to tap on that word to get the other options? Stock keyboard will show options and you can change it, or start typing the next word. Think I like that option better.

I do hate how the stock KB won't let you choose word options in the search bar though, only get one word suggestion, and if it's wrong you have to erase and type it out old fashion way. annoying.
 
Kinda like this Kii keyboard. I couldn't get past the oddities with Swiftkey, so I stopped using it. Kii is more like the stock keyboard with extra features. I like it.
 
I love Swiftkey, and the Flow feature just left beta today. It's the fastest keyboard I've used, for sure. Text prediction is next to none (though Flow's prediction isn't great yet.) And the general layout is the best I've used. As well, the developer has been extremely active in updating it over the app's lifespan.

I did kindof like Kii for the customization options, but the layout was awkward. Prediction was different from SwiftKey (in a bad way,) and little quirks ended up driving me back to Swiftkey in about a week.
 
DLeRium said:
I hate that you're have to use the stupid number layout (should give us an option to change that).
Click to expand...

The 10key layout in the number section is one of the main reasons I still use Swiftkey, I can't stand having the numbers in a row. I'd have gone back to Swype if they gave the option to change to a 10key style.
 
middlehead said:
The 10key layout in the number section is one of the main reasons I still use Swiftkey, I can't stand having the numbers in a row. I'd have gone back to Swype if they gave the option to change to a 10key style.
Click to expand...

I know some people like it and all, but I feel that's the beauty of choice? I can understand when the app first came out and devs didn't have a chance to bake in a toggle yet, but if you look at their uservoice there's more than a few suggestions about a number row, all with quite a few votes.
 
Apex said:
Does Swiftkey Flow still add a space in email addresses and url's? That was one thing I couldn't get used to in the beta. With Swype, you could have the auto-spacing enabled, and when you swipe the .com it knows well enough not to bork your url with a space.

Did Swiftkey Flow fix that, or was that a setting somewhere?
Click to expand...

I think that's partially dependent on the browser/email program. I believe it's up to the browser developer to program the text box into "URL mode" or "numpad mode" etc and then they keyboard loads whichever layout that is. So doing a quick test, the default browser treats the URL box as a standard text box so it's going to auto space and auto caps (because it's also a search box). In the gmail app, when I insert an email address it turns flow off completely AND disables prediction AND includes the shortcut button for @XYZ.com at the bottom.

IIRC the dolphin browser treats URLs in a similar fashion and doesn't use prediction/flow. Chrome treats the URL as a search box and that's why it autospaces.
 
DLeRium said:
did the tablet one go on sale? I think it was only the standard one, which I bought for 10 cents. TBH I haven't used it at all though because I'm not a fan of Swiftkey.
Click to expand...

That's when I bought it too. The tablet one wasn't on sale at the same time.
 
lopri said:
@podspi: Is the tablet version worth a separate buy? What size tablet did you try it on?
Click to expand...

I use it on my OG Kindle Fire (7"). At the time of purchase, the feature it added was the 'split' mode so you can type with just two thumbs. Overall I ended up not using split mode, so for me it wasn't really worth it, but I really like the product and the fact that they have included all updates (instead of spinning off the product like so many other devs) makes me feel pretty good about supporting them (especially since they are going to have a tough time moving forward. Stock keyboard is not as good imho, but it is most of the way there).
 
I've got both versions of swiftkey, love it.

Swiftkey 4 adds the flow stuff, which is quite impressive.
 
gorcorps said:
I think that's partially dependent on the browser/email program. I believe it's up to the browser developer to program the text box into "URL mode" or "numpad mode" etc and then they keyboard loads whichever layout that is. So doing a quick test, the default browser treats the URL box as a standard text box so it's going to auto space and auto caps (because it's also a search box). In the gmail app, when I insert an email address it turns flow off completely AND disables prediction AND includes the shortcut button for @XYZ.com at the bottom.

IIRC the dolphin browser treats URLs in a similar fashion and doesn't use prediction/flow. Chrome treats the URL as a search box and that's why it autospaces.
Click to expand...

Ugh, that's terrible. OK thanks for testing that, I appreciate it.
 
Swiftkey seriously went downhill for me towards the end of the beta, almost every fourth word was interpreted incorrectly regardless of my accuracy. It also seemed to forget my custom words. After a factory reset I decided to give the jellybean keyboard another try. It's better than SK in almost every meaningful way. It makes considerably fewer mistakes, is quicker to correct with the corrections appearing above the keyboard unlike SK's completely pointless predictions. It also requires considerably less custom words adding to the dictionary and reverts corrections on backspace which SK doesn't do. The only advantage I found with SK was punctuation input. That's it. It really did turn into a poor product for me. The input algorithm seems to weight predictions very highly often overriding your physical pattern because it thinks the user is just being sloppy.
 
Okay so after uninstalling the beta I've since tried the actual finished release and it's much better. And was able to make the keys smaller so now keyboard takes up less screen real estate.

I tried that Kii keyboard but performance was randomly choppy when doing gesture based typing so that only lasted about an hour on my phone.
 
I was using Swiftkey up until I got the Note 2. I am not willing to give up the top number row that the stock Samsung kb has. Besides, the Samsung keyboard uses swype so it is good enough.
 
Huge fan of Swiftkey here, and updated it yesterday to test Flow.

It was okay, if not somewhat clumsy in predicting my gesture. In fact I was a little surprised that it couldn't get some of the words I use often (words that, had I tapped, are predicted correctly by only one or two taps in the exact same sentence). Flow honestly feels like just a novelty at this point for me. I'll probably turn it off soon and just continue typing like I always have (tap - tap - space).

I'm currently content with Swiftkey and have zero complaint, but just out of curiosity: does Swype or any other keyboards out there support simultaneous multiple language libraries like Swiftkey? This was the main reason I bought Swiftkey way back when it first came out. In my day to day text/chat I use only 50% english, and almost all the time I switch language several times within a sentence, so multiple language prediction is a must for me.
 
Red Storm said:
Okay so after uninstalling the beta I've since tried the actual finished release and it's much better. And was able to make the keys smaller so now keyboard takes up less screen real estate.

I tried that Kii keyboard but performance was randomly choppy when doing gesture based typing so that only lasted about an hour on my phone.
Click to expand...

Kii's as fast as the stock keyboard for me. Hell it looks like the stock keyboard.
 
What's the name of that Keyboard that was advertised during CES a few weeks ago that it would put SwiftKey's prediction to shame?
 
Chocu1a said:
I was using Swiftkey up until I got the Note 2. I am not willing to give up the top number row that the stock Samsung kb has. Besides, the Samsung keyboard uses swype so it is good enough.
Click to expand...

Samsung keyboard on note 2 actually uses SwiftKey Flow not swype.

I agree though on the number row.. I wish SwiftKey would make that an option.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top