Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS Custom Keyboard Megathread
- Thread starter Shawzborne
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Ah, I see. You need to wait until we get the TouchPal Wave feature in the iOS keyboard. Android already have it.
http://www.touchpal.com/index.html#why
Anyone else notice that Swype is the ONLY 3rd party keyboard that's in the top 100 paid OR free apps? Not even Swiftkey or TouchPal are in the top 100 free.
Me thinks finally opening up that API was a big deal to the fanboys and tech media, but to the average consumer, the stock keyboard "just worked" fine -- and got even better with Quick Type on iOS 8. And with the continuing implementation issues (Messages freezing, spotlight search, quick reply, etc), most people aren't bothering with them.
Me thinks finally opening up that API was a big deal to the fanboys and tech media, but to the average consumer, the stock keyboard "just worked" fine -- and got even better with Quick Type on iOS 8. And with the continuing implementation issues (Messages freezing, spotlight search, quick reply, etc), most people aren't bothering with them.
It also may be the fact that the App Store charts are dominated by games and things that the under 25 crowd downloads. No, they don't care about this stuff.
It is also normal for Android users to get a new device and immediately download their preferred keyboard.
I think even without the issues we're having, we'd still be seeing the same thing.
It is also normal for Android users to get a new device and immediately download their preferred keyboard.
I think even without the issues we're having, we'd still be seeing the same thing.
Currently using Swype although Swiftkey looks better but to enable full access just to use Swiftkey Flow is stupid when Swype did not require any access and works the same.
This is probably the reason why Swype is still currently top 100 while Swiftkey and other keyboards are not. Most users do not want external keyboards to access their data no matter how trustworthy they are. Not even if it's free.
Most of my issues have been resolved since the last iOS update - I don't use a ton of apps, though, other than iMessage and email...
I totally agree. I also decided to buy Swype yesterday after all because they (finally) released there update which included 16 new languages including Dutch. Unfortunately you do have to set it (temporary) to 'full access' in order to download another language other then the 5/6 which are in the app (e.g. Dutch). I don't get why they don't include it within their app as Path Input does (other then file size).
I turned off the 'Full access' after i downloaded my Dutch language for Swype and it still works like a charm on my iPad mini2.
I would never use Swiftkey as long as:
- their keyboard needs full access in order to use swipe/gestures
- you can't use swipe/gestures on the iPad
So i understand why Swype is so high in the App Store ranking/sales the recent days.
Touchpal could also get higher in the (local) rankings if they would support more languages.
One annoying thing is that apps which are yet to be updated for iOS 8 use the zoomed keyboard, as you need to swipe differently on it.
Wait... if one 3rd party keyboard is less buggy than another... wouldn't that imply the problem(s) may not be as much iOS related as 3rd party related? I'm not a programmer (nor play one on tv)... so my ignorance is no doubt showing, sorry. Sure love my Swiftkey... wish it would disappear, or fail to come up or completely lock up imessage with a funky screen.
Another translation keyboard is in the App Store called 'Slated'. iMore wrote an article about it. I just added it to the topic start post.
Last edited:
I can lock up the messages app with either Swype or swiftkey, whereas other apps using either keyboard will not lock up as such.
Not to say the above don't display graphical anomalies in 3rd party apps, but I think it's clear where the inherent issue lies imo.
I don't mind the full access request, and I've had fewer bugs with the last iOS update. (Using Swiftkey and Adaptxt at the moment.)
Bought it, it's really cool. I just wish there was a way to translate when someone writes back in the translated language.
Trying Swype (since it's free today) and since y'all say it's more stable than my beloved Swiftkey. So far it is. I'm curious... why do they only show the long press action on each key in the "Dark" theme? Why not also in the "Light" or others? I do like that keyboard shifts from caps to lower case like Swiftkey and unlike the others.
The iPad version of Path Input (yup non-universal unfortunately) is now again (temporary) free.
It also has a number keypad next to the 'smaller' keyboard on an iPad.
I suggest you also give that a try if you don't like Swype on your iPad. Swiftkey can't even be used on the iPad if you want to use gestures/swipe. Path Input doesn't need Full access to work (not even to select another language).
I'm switching between the Swype and Path Input on my iPad mini2 to determine which one i like to use most. The Swype keyboard is full size and the Path Input keyboard is smaller as far as letters concerned but there is a permanent number pad.
It also has a number keypad next to the 'smaller' keyboard on an iPad.
I suggest you also give that a try if you don't like Swype on your iPad. Swiftkey can't even be used on the iPad if you want to use gestures/swipe. Path Input doesn't need Full access to work (not even to select another language).
I'm switching between the Swype and Path Input on my iPad mini2 to determine which one i like to use most. The Swype keyboard is full size and the Path Input keyboard is smaller as far as letters concerned but there is a permanent number pad.
I love path Input on the iPad purely because it has both the alpha and numeric keypads on screen at the same time which makes swiping quicker as there is less distance to travel between letters. I wish the other keyboards would offer this layout on the iPad.
Done - thanks for the 'free' heads up!
My one-sentence review is "Path Input for iPad looks to be one of the best 'swipe' keyboards on the iPad right now."
Unfortunately I'm a typer and not a swiper, and Path Input for iPad's excellent swipe layout makes it cumbersome for tap-typing. Dang.
-----
My current keyboards of choice are TouchPal for shorter work (messages, calendar appointments, browser searches) and Fleksy for longer work (notes, forum postings, e-mail).
The custom keyboards just don't work properly. In the messages app there's still a bug that sometimes prevents the keyboard from popping up. What I mean by this is that when you click on the messaging field where you'd input the message upon clicking it, it should pop up the keyboard. Sometimes it doesn't and stays unresponsive, which means that you manually have to access the app switcher, force close the app, and restart it to have access to the 3rd party keyboard once more.