Keyboard

For a long time the keyboard experience on iOS remained the same as it was when the original iPhone launched all the way back in 2007. With iOS 7 the keyboard received a visual overhaul, but the layout and correction functions remained the same. This has been a prominent criticism of the stock iOS keyboard over the years, with the single suggestion implementation of iOS's autocorrect seeming archaic compared to other smartphone keyboards. Apple addresses this with two solutions in iOS 8. The first is QuickType, Apple's new suggestion and correction feature.

The above two images will be instantly recognizable to anyone who has used the Google keyboard for Android, or third party keyboards like SwiftKey. The way quicktype functions is nearly identical to the suggestion feature on Google's and other smartphone keyboards. A bar above the keyboard gives three suggestions as the user types, with the box turning white and the text turning blue to indicate that a typed word will be autocorrected.

QuickType is not Apple's only solution to complaints about the iOS keyboard. While it offers a better method of correcting typos, the keyboard itself is still functionally identical to its predecessor. Because Apple can't possibly hope to address every single user's desire for keyboard input on their own, they have finally included the long requested ability to use third party keyboards on iOS 8. How keyboards and other extensibility options are implemented is discussed in the next section, but there are a couple of things specific to third party keyboards that should be noted.

The first is that third party keyboards will be system wide; there's no need for developers to implement them in their applications on their own. The second, and possibly most important, is that third party keyboards run in an extremely restrictive sandbox by default. They don't have access to the information from other applications on the phone, or access to WiFi or cellular networks. However, third party keyboards can ask for access to typed words and networking to do prediction, but for privacy and security reasons that is never something that can be enabled by default. I recently took a look at the beta version of SwiftKey for iOS 8, and you can read my impressions about the actual third party keyboard experience on iOS there.

One last point about the stock keyboard. The shift key is the same as on iOS 7.1. Users (like myself) that are frustrated with its new design as of iOS 7.1 are out of luck. A return to the iOS 7 style of having the shift key arrow as an outline when it is turned off is my biggest recommendation for improving the iOS keyboard from its current state.

Extensibility

When the iPhone was first launched, iOS wasn't even designed to support third party applications. Apple's original stated intent was that users would use web apps through Safari. Obviously things turned out quite differently with the introduction of iOS 2.0 and the App Store. However, iOS itself was never conceived with a massive library of native applications in mind. Because of that, and because of security reasons, each app has traditionally been completely segregated from all others.

Applications on iOS have never really had a proper way of sharing data and integrating with each other, with the exception of the select few services that Apple has built into iOS over the years like Facebook and Twitter. This has always posed a problem with working on files across multiple apps. It also greatly limits the ability to share content through other applications, as the iOS Share Sheet is limited to the services built into iOS unless a developer adds support for other applications on their own.

Extensibility changes this. Extensibility in iOS 8 is really an umbrella term for new features like share extensions, action extensions, custom photo filters, and document provider extensions. Some of these have been covered at other points in this review, and the parts being focused on here are Action Extensions and Share Extensions. Much like the improvements to iCloud, these are additions that are hard to talk about now as they are yet to be implemented by developers. This is just a small overview of things to come once developers start using the new tools given to them.

Action Extensions do what their name implies, they perform actions that extend the functions of applications. An example would be an extension for the Bing Translate app shown at WWDC. Rather than Apple having to work with Microsoft to make translation with Bing a system wide feature, Microsoft can simply make an Action Extension and have it appear in the Share Sheet in any application.

Share Extensions also do what their name implies. They allow applications to put their own options for sharing in the system's Share Sheet. This is a massive improvement over the previous system that only included limited options and the small handful of services that Apple had integrated into the OS like Twitter and Facebook. Share Extensions are very similar in function to how Intents are able to share files and content between different apps on Android, and it addresses what has been a major iOS shortfall for years. The example Apple gave at WWDC was the ability to open the Pinterest app interface within Safari to share a photo.

iOS also has contextual awareness relating to extensions. Because the Share Sheet can only display four icons in each row, only the extensions that relate to what the user is doing will be shown. If the user is looking at the photos application the Share Sheet won't show an extension for text translation as it doesn't relate to the task at hand. Apple also allows the order extensions are displayed in to be customized so that frequently used extensions are always displayed in the Share Sheet without having to scroll.

One final part of extensibility that pertains to iPhone 5s users is that developers are now able to use Touch ID authentication in their applications to unlock passwords stored as keychain items. The fingerprint data itself is never shared with applications, only whether or not the fingerprint was successfully identified or not.

As I said above, the iOS security model has always used application sandboxing to prevent malicious access to information. With extensibility you may be wondering if Apple has had to compromise on security to enable these new features. Fortunately, the answer is no. With the way extensions work on iOS 8, the extension is part of its parent application's container. Extensions can only reach out to other applications by way of the operating system, which has various checks and balances to make sure things are being done in a safe and secure manner. I don't believe users should have any concerns about the security of their devices when upgrading to iOS 8.

iCloud and Continuity Health and Medical ID
Comments Locked

164 Comments

View All Comments

  • robinthakur - Friday, September 19, 2014 - link

    Er, no that's nonsense. If I start typing a message to somebody in my address book on an iOS device, it turns blue if they have iMessage but to Android users it's green which means it is an SMS and it reaches them perfectly fine. Honestly, if it worked the way you say it did, it would be totally pointless. iMessage syncs with all Apple kit so this benefits people who use iPads and Macs, which is fine because it makes life easier. If I send a Hangout on my HTC One M8 to somebody with a Google account but who doesn't have Hangouts enabled, it goes through fine, but they never reply. Which is the more useless? I wanted to like Hangouts, but the hideous green interface or the fact that hardly anybody I know user Android makes it suboptimal and tend to just leave it in the SMS setting which is a far worse solution than on my old iPhone with iMessage because I could send without cellular signal and send pictures,voice etc. for free over wifi. Seriously, of the two implementations, I definitely prefer (and miss) iMessage.
  • Impulses - Wednesday, September 17, 2014 - link

    Well, for one thing, people that initiate a group chat on iMessage just end up annoying those of us who have to interact with it thru SMS and can't seamlessly reply to the whole group etc ... So that's one reason not to use it.

    Photos sent over iMessage also end up overcompressed when sent to an MMS recipient, and trying to explain to someone why you would prefer they email it or Dropbox it is like pulling teeth.

    Granted, you could rightly state most of those issues stem from user ignorance, but I'm the end it's really Apple's attempt at transparently blending a universal system with a proprietary one that's causing the confusion.
  • WinterCharm - Wednesday, September 17, 2014 - link

    False. That's completely wrong. If the messages app detects that not everyone in the group you are messaging has iMessage, it simply forces the entire group to use SMS, so it's seamless for everyone.
  • grayson_carr - Wednesday, September 17, 2014 - link

    No, you are wrong. It forces the entire group to use MMS, not SMS. There is a difference. In many countries, SMS is free, but MMS (used for group texts, pictures, etc.) is not.
  • Impulses - Thursday, September 18, 2014 - link

    False. That's completely wrong. I've been in plenty of conversations with iPhone users (most of my friends) where one of them suddenly goes "why isn't Frank responding, is he not coming?" because they don't realize I'm not on iMessage and my replies ate only going to the originator of group chat.

    Thanks for playing but try again. I could get around that by initiating a group SMS for everyone in the chat (once I figure who THAT is after a few replies), but it's a big hassle since each individual reply from each person will come in under the thread for that particular person.

    Usually the chat originator just ends up repeating what I've said, it's a pain, and iMessage can eat me.
  • sherifone - Thursday, September 18, 2014 - link

    Thats because on Android group MMS is a crap show. Apple supports the standard correctly and on Android it is handled on an app by app basis, sometimes very poorly. It is your phone/app's fault you didn't get the message.

    iOS detects that there is a non iMessage user in the conversation and it turns into a group MMS. There is no such thing as a group SMS, just FYI.

    This works flawlessly among my android and iOS friends. Mostly because my Android friends are educated in the way MMS/Group messaging works and took the time to find a functional app and/or phone.
  • Impulses - Thursday, September 18, 2014 - link

    I didn't fail to receive any messages, read my comment. Point is turning it into a hybrid group MMS/instant message convo is not very helpful to others and turns into a mess, because I can't easily reply to the group and I'm basically forced into the conversation as well... With no option to back out of it or ALL subsequent replies. It's not just non-iPhone users that are affected either.

    It might seem all transparent and easy to use for them, except when it ceases to be. I've lost track of the number of times an iMessage user has sent a group message asking something (like everyone's address for wedding invitations, etc) and the rest of the iMessage users blindly reply. Other iMessage users don't (and shouldn't) see those replies, only the originator, but I end up seeing all of them...

    Any time you send a group MMS to someone on iMessage every other user you sent it to is invariably gonna see that iMessage user's reply, which doesn't follow standard SMS/MMS logic.
  • robinthakur - Friday, September 19, 2014 - link

    Yep, definitely agree since I mopved from iPhone to Android, I was shocked at how backwards messaging still is on the platform, most still use SMS and Hangouts has hardly any traction. All my friends who are iPhone users regularly bitch and moan that they have no idea if i've read something, and that they receive multiple identical texts from Hangouts and I would say they now message me less because it is just hassle for them. Hopefully my iPhone 6 plus arrives soon.
  • retrospooty - Wednesday, September 17, 2014 - link

    clearly you havent used Hangouts. It's fully integrated with text messaging. It just works
  • robinthakur - Friday, September 19, 2014 - link

    Is that why both my HTC One M8 and my brother's Motorola G send the same message multiple times to recipients which drives them crazy? As the sender, I have no idea this is happening until I start getting complaints that i've just sent the same text 5 times. It seems such a simple app, the fact that it doesn't actually work must be pretty embarrassing for Google. In all my years of using iMessage, it never screwed up that badly and generally worked pretty slickly across all my devices with a decent carrier. Google would help themselves if they got rid of having Messages AND Hangouts in the AOSP. Most users have no idea which one to use and opt for Messages and then think that Android is incredibly backward as a result.

Log in

Don't have an account? Sign up now