Extending iMessage

The Message app is the most used application on iOS. This isn't really a surprise when one thinks about how people use their phones, but it does identify an area that the developer community hasn't been able to tap into despite users spending a great deal of their time there. For someone like me, it was difficult to imagine that there really was anything that developers could do with iMessage, as my use case is just sending images, videos, and text in the same way that you could with SMS and MMS. Of course, I make use of some other convenient features like group chats, read receipts, etc, but none of these areas seemed to present a way for third party developers to add value. Of course, that's when I think about how I use messaging, but there's a whole world of messaging beyond the most basic functionality that SMS and iMessage provide. Apple is tapping into those ideas for iMessage in iOS 10, and they're bringing developers along for the ride.

Apple has taken a two pronged approach to upgrading iMessage in iOS 10. The first are the features that come by default, the features that are part of iMessage itself. I actually covered some of these in my macOS Sierra preview, although in a limited manner as macOS Sierra is not capable of using most of the new features itself and is just able to receive messages that use them. The two main features added to iMessage by default in iOS 10 are message effects and Digital Touch messages.

Message effects work as you'd expect, with animations that can be applied to the actual message bubble itself or as an effect that plays in the background behind the scrolling list of messages. For bubble effects Apple provides an invisible ink effect that requires you to swipe across the message to reveal it, a gentle effect with tiny text, a loud effect which enlarges the bubble for a moment when it's viewed, and a slam effect which crashes the message into the screen, complete with dust effects as it touches down. As for screen effects, you have balloons, confetti, lasers, fireworks, and a shooting star. There's not a whole lot else to say about message effects, as other messaging apps have implemented these features before. If you're a fan of them then you'll be happy to see them brought to iMessage, and if you're not you'll just have to hope all your contacts feel the same way.

Anyone who has used an Apple Watch will be familiar with Digital Touch. In this case it has been modified since you're using it from an iPhone instead of a watch, and the list of things you can send have been expanded as well. To bring up Digital Touch you simply tap the icon with two fingers on a heart which sits next to the text entry field. Once you do so you'll be presented with a condensed version of the Digital Touch UI in the space where the keyboard would normally be. This UI works in a similar manner for iMessage apps, although I'll touch on that more in a bit. 

In the condensed UI there's a small drawing canvas where you can perform Digital Touch actions. On the left side you have a button that allows you to change the color of the pen used when drawing, and below that is a camera button which expands the UI and allows you to draw on top of a photo taken with the camera.

The expanded UI will first show a preview of all the actions you can perform. These all work in the condensed UI as well, but you may not know about all of them until you bring up the expanded version as the condensed view only shows three actions on the right side and switches between two sets every few sections to show all six. To be honest, the Digital Touch interface is kind of confusing, and I wouldn't be surprised if it receives some tweaks in future minor updates to iOS 10. I'm don't really much value in Digital Touch on the iPhone either, especially since actions like tapping don't translate well from the Apple Watch where it would actually trigger the Taptic Engine to simulate your wrist being tapped.

The second side of the iMessage improvements is the creation of a developer ecosystem centered around iMessage. This API will allow developers to create their own mini-applications that run inside of iMessage. This really covers three types of applications, the first of which being sticker packs, the second being interactive messages, and the third being other types of apps that work with media. You can see an example above of the new Super Mario Run sticker pack which is available in the iMessage app store. Interactive messages cover applications that send messages with content which can then be opened by the receiving user in the corresponding application. Apple's example was sending a message with the menu for a party being planned, which can then be modified and commented on by the receivers. Finally, the other category of app is for working with media, and an obvious example is implementing a GIF application for sourcing reaction images in the iMessage app itself.

I'm not really someone who makes heavy use of emoji or effects in message apps, and so I don't have a whole lot else to say about the changes Apple has made to iMessage in iOS 10. However, the popularity of these features in other messaging apps makes it clear that many users value these capabilities, and so it makes perfect sense for Apple to bring them to iMessage. Most interesting for me is the idea of the iMessage App Store, and whether or not it's going to be possible to monetize applications like sticker packs. Line has already shown that people will pay money for such things, but that relies on developers not rapidly creating a race to the bottom for prices, which is what has happened in the iOS App Store to an extent. Like many of the new technologies that Apple introduces in new versions of iOS, only time will tell how things play out.

Expanding Widgets and 3D Touch Swift Playgrounds: Looking to the Future
Comments Locked


View All Comments

  • sonicmerlin - Wednesday, September 14, 2016 - link

    Really? Hiccups and frame drops make a powerful phone look weak. Smoothness adds to the sensation of fluidity of user experience. Aesthetics are a constant stimuli while using something as personal as a cell phone.
  • tipoo - Wednesday, September 14, 2016 - link

    We [probably] live in the first world, what else are we supposed to have?

    And nor does first world mean developed world.
  • Ranger1065 - Thursday, September 15, 2016 - link

    The fact that you feel the need to differentiate between the terms "first world" and "developed world" is symptomatic of a first world mindset, as is quoting Wikipedia as an authority.

    If people are seriously concerned about " a tiny bit of judder while scrolling in safari,"
    count yourselves lucky you don't have any real problems.

    I don't live in the first world and I don't give a damn about political correctness or terminological exactitude, when all it amounts to is splitting hairs....just for the record :)
  • star-affinity - Wednesday, September 21, 2016 - link

    I would't say I'm "seriously concerned" about those things, but when you're talking about a device that's beeing used extensively I absolutely think it's worth discussing user experience.

    Of course a lot of thing seems rediculous when looked at "the grand scale of things", but I still don't thing one thing has to exclude the other. It's always difficult to compare your own life to the rest of humanity, because there will probably always be someone who has a worse situation in life than you. So does that mean we shouldn't strive for quality and a good experience when using smartphones? I think not.
  • robinthakur - Friday, September 23, 2016 - link

    If you don't live in the "first world" perhaps you'd feel more at home at an Android site ;)
  • tipoo - Saturday, September 16, 2017 - link

    Or you could look up any other source you wanted with the information at your fingertips and find I'm right about the definition. First world just meant US and it's allies, second meant the USSR and it's allies, and third world meant unaligned. Not anything about riches or poverty.
  • robinthakur - Friday, September 23, 2016 - link

    I agree, it got so bad on my iPhone 6 plus about a month ago, that I got judder scrolling from one home screen to the next, so in a fury I went and bought an S7 Edge to play with until the iPhone 7 was released. It's actually very very smooth overall and if it integrated into the rest of my kit and Apple services (Apart from Apple Music) then I might consider using it. Overall, the tight design language throughout the hardware and the operating syMornistem and polished first party features made me order the iPhone 7.

    iPhone used to be the smoothest scroller and was a major factor in me staying on iPhone before iOS8 because I can't stand frame rate drops (I like my games 60+fps too) so this is also a big deal for the 7/iOS10 and how they choose to optimize in the future. The phone should never feel 'slow' in normal day to day operation using OOTB features...
  • lilmoe - Tuesday, September 13, 2016 - link

    Also, take a look at those improved Javascript benchmarks, seems like iOS10 came with a CPU upgrade too!

  • Meteor2 - Tuesday, September 13, 2016 - link

    Now I know Anandtech won't do a day-of-release view of the iPhone 7, but when can we expect to see a review?
  • JoshHo - Tuesday, September 13, 2016 - link

    When it's done.

Log in

Don't have an account? Sign up now