4 ms·
That's a pretty BS excuse, they could trivially provide guidelines for input systems that don't fragment things subtantially. They simply don't care about the
by Daishiman 13y ago
That's a pretty BS excuse, they could trivially provide guidelines for input systems that don't fragment things subtantially.
They simply don't care about the segment and would rather support a good-enough solution than a best-of-breed.
- gfodor 13y agoUh, they certainly could do this, but to say it would be trivial is obviously exaggerating. It would be relatively large undertaking to provide guidelines and an approval process for alternative input systems that potentially affect every app on the user's device. Not to mention it would potentially impact the flexibility has for future innovation on this front.
- cageface 13y agoThey've painted themselves a bit into a corner on this one because there are a lot of apps in the app store now that make very specific assumptions about the behavior of the stock keyboard that would break if they started allowing third party keyboards. It's a pity too because the primitive stock keyboard is easily my #1 frustration as an iOS device user. Once you've gotten used to something like SwiftKey or Swype on Android it's hard not to get angry at Apple when you're forced to go back to their 2007 keyboard. How is this putting the user first?