iOS does not support alternative virtual keyboards. Ans as of now, the iOS keyboard is nowhere nearly as good as either Swype, SwiftKey Flow or SlideIt.
Of course, iOS is compatible with bluetooth keyboards (Apple's or a couple of Logitech ones), but that isn't the point I'm arguing.
I understand. Nope, that's not an iOS feature.
"the iOS keyboard is nowhere nearly as good as either Swype, SwiftKey Flow or SlideIt". That's an opinion - I personally can't stand the swiping style keyboards.
But you were right, if using 3rd party keyboards is what you're after then Android will suit you better.
What I'm lamenting is Apple's resolve to stick to their dated technology instead of adopting anything like this. Everyone from ShapeWriter to Nuance to SlideIt have been lining up for the chance to have AAPL integrate their technology into its mobile OS or at least to open up the OS to enable their respective input solutions to work system-wide within iOS, but Apple has remained as headstrong in its arrogant resort to stay away from technology that makes more sense than their own, outdated, inefficient brainchild, as they come across so rather often.
Feel free to lament. There's a lot of thought that goes into these things though, and Apple has chosen not to pursue the 3rd party keyboard API just yet (and potentially may never)
Perhaps it's a case of Apple not wanting to jump into such functionality half hearted. Usually when Apple a a new features, it impresses - even if they weren't the first to do it, they normally do things well (Copy and Paste and the App Store introductions are good examples, they took their time, but the execution at the time was first class).
Apple would never just release a 3rd party keyboard API, there would be guidelines, etc. To ensure the experience isn't sub-par. People may not like this, "it's my phone - let me do what I want with it".
But it's a godsend for less techy people, they can install things from the App Store without fear of screwing things up. Just a quick search on Google Play shows there are issues with letting devs have free reign, such as:
"I have a Samsung Galaxy Music and the keyboard cut off . It does not display fully."
(https://play.google.com/store/apps/...sImNvbS5kb3VidGVjaC5pbnB1dG1ldGhvZC5sYXRpbiJd)
Can you imagine that on an iOS device? I really can't. Apple would never allow users to replace something as essential as the keyboard and have it function poorly.
Now I'm not saying it will never happen (it could). But if it does, I'd imagine there will be rules/guidelines to ensure at least all the base functionality is present and correct. And I imagine, rather than being 'headstrong in its arrogant resort to stay away from technology', Apple just hasn't had the time and resources at its disposal to implement it** (considering they had to move engineers from OS X to iOS 7) or perhaps they genuinely don't want to introduce it.
Luckily we have choice, if you don't like the iOS keyboard you have Windows Phone, Blackberry 10 and Android to choose from amongst others.
**Yes I know Apple has a ridiculous amount of money but capable engineers that meet Apple's/Google's/Amazon's requirements don't grow on trees. So it's not a case of just hiring more staff.