iCloud

iCloud is somewhat difficult to talk about due to the fact that many of the improvements require developer implementation. The first part of the iCloud story is iCloud Drive. While I have used iCloud Drive, I cannot show any screenshots of it as they would have to be from the section in the Finder application on the beta version of OS X Yosemite, and that remains under an NDA. However, the above screenshot from Apple's website is how iCloud Drive and the document picker appear on iOS and OS X. iCloud Drive will also be accessible on Windows via Apple's iCloud.com website.

iOS was designed without a user accessible filesystem, and each application has traditionally had its own files private and inaccessible by other applications. This is great from a simplicity and security standpoint, but it makes working on files in multiple applications effectively impossible. iCloud Drive changes this and provides a potentially massive increase in productivity abilities on iOS devices. In a way, iCloud Drive is a service to compete with all the cloud storage services offered by other companies. Files can be put into it and organized in any way the user likes. But in another way, iCloud Drive is the repository for the files from all iCloud enabled applications across iOS and OS X.

Applications that use iCloud for file storage can now mark their application file container as public. This means that files created in that application will be accessible to other applications that provide an option to choose iCloud Drive as a file source. It should now be possible to start a document in Notability and then open it in Pages to continue working on it. Any changes made in Pages are saved back to the original document in Notability's app container, and the file is also continually visible in Pages alongside all the other documents created in the app. This is a huge step forward for productivity on iOS. No longer are users stuck with the tools provided in the application they initially created a document in.

iCloud Drive and the iCloud document picker rely heavily on developer support and it will be interesting to see if and when developers decide to start implementing it in their applications. Support for iCloud among third party applications isn't massive, with many past difficulties implementing iCloud and Core Data scaring off developers despite the improvements made in iOS 6 and 7. I personally believe that the functionality and inter-app communication offered by iCloud Drive will be too big for developers to ignore going into the future.

SMS and Phone Call Relay

When I was an iPad user I thought it was very cool that iMessages directed at my iPhone's phone number were able to be pushed to my iPad and could be sent from the iPad using that same phone number. Unfortunately, the experience wasn't as good when communicating with the many people I know who don't have an Apple device or just don't use iMessage. Being able to have SMS messages pushed between all my devices has been a feature I've wanted for quite some time, and with iOS 8 that finally becomes a reality. SMS Relay will sync SMS messages between all of a user's iOS and OS X devices. There's just one catch: it won't be available until October and so it will likely launch alongside OS X Yosemite. My impressions below are from the iOS 8 beta.

As you can see above, SMS messages are being pushed to an iPad. The most interesting thing about Apple's SMS Relay is the requirements for it to work. When it was demoed at WWDC I assumed that it would require some sort of connection via Bluetooth 4.0 or an 802.11 WiFi link. This is not the case. The only requirement for using SMS Relay is to have all devices connected to the internet on any network, and to be logged into iCloud and the Messages app on those devices.

This means that a text message sent from an iPhone while travelling will appear on an iMac sitting at home. Apple likely avoided any implementation that involved a direct connection between devices to prevent issues with syncing. If SMS Relay required devices to be in contact over Bluetooth or WiFi, any SMS messages sent or received when the user was away from their other devices would not sync and there would be large gaps in the SMS conversations on other devices.

Apple has not documented how their SMS Relay works but my best guess is that it utilizes iMessage to send the messages from the iPhone to the iPad or Mac, displaying them with a green bubble rather than a blue one. If this is the case, SMS messages sent from iPads and Macs would then send a silent iMessage to the iPhone, which would then send out an SMS to the receiving device.

Phone calls can also be made and answered on an iPad or a Mac. Unlike SMS, this feature does require both devices to be on the same WiFi network.

SMS Relay is definitely my favorite feature in iOS 8. Not everyone has an Apple device and therefore not everyone has iMessage. The ability to have SMS messages synced just like iMessages is one that I've wanted for a very long time and it's exciting to know it will be here soon.

Handoff

Handoff is a new feature in iOS 8 and the soon to be released OS X Yosemite that allows you to begin a task on one device and continue it on another. It works by detecting nearby devices that are logged into the same iCloud account using Bluetooth LE, and allowing the user to transition between the same applications on different devices. On OS X the icon for an application appears as an additional section of the dock, and on iOS it appears either on the lock screen or the app switcher depending on if the device is unlocked. Currently Handoff works with the following list of Apple's applications:

  • Safari
  • Mail
  • Contacts
  • Calendar
  • Reminders
  • Maps
  • Messages
  • Pages
  • Numbers
  • Keynote

Handoff can also work between websites and apps, and Apple is providing APIs for developers to implement Handoff in their applications. An example would be Facebook implementing Handoff so a user could transition between the Facebook website on their Mac and the Facebook app on their iPhone or iPad.

Handoff and continuity in general is a key part of Apple's strategy for providing a seamless experience across all their devices, and it's very different from the strategy that Microsoft is employing. With Windows Phone 8 and Windows 8, Microsoft is trying to create an interface and applications that run on all Windows devices. I don't agree with such an approach because inevitably you will end up with parts of the software that don't fit in with the device being used.

The most common area where I see this arise is complaints that the Windows 8 Start Screen feels out of place on traditional devices and seems designed with touchscreen laptops and tablets in mind. Apple is creating a unified experience across all their devices by allowing them to work together and employing similar design conventions, but keeping OS X and iOS separate and running on the devices where they make sense. Which approach is better is obviously a matter of opinion, but given that the adoption of Windows 8 was only 14% as of Q2 2014 I think Microsoft's solution isn't resonating with consumers.

Third generation iPad users should be aware that much like Airdrop, they are excluded from Handoff features despite the Broadcom BCM4330 sporting Bluetooth 4.0. I don't know the reason why Handoff isn't supported on the iPad 3 as it seems capable from a hardware standpoint. When Airdrop didn't come to it with the release of iOS 7 some users speculated that the reason was the single stream 802.11n WiFi. I don't really believe this is the case, as jailbreak solutions to enable Airdrop on the iPad 3 work perfectly in my experience. I would really like to know Apple's official reason behind the exclusion of both Handoff and Airdrop on the iPad 3, but right now it seems more of a decision to artificially limit for the iPad 3 than any inherent hardware deficiency.

Camera and Photos Keyboard and Extensibility
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