WEBVTT - Android Users Finally Get Their iMessage

0:00:04.559 --> 0:00:08.280
<v Speaker 1>Android devices finally get their own I message I'm rich

0:00:08.320 --> 0:00:11.800
<v Speaker 1>jamiro this is rich on tech. Daily texting on an

0:00:11.880 --> 0:00:14.720
<v Speaker 1>iPhone is a complete joy. You can see when messages

0:00:14.760 --> 0:00:17.560
<v Speaker 1>are delivered, when they're read, and you can even send

0:00:17.720 --> 0:00:20.800
<v Speaker 1>large pictures and videos with ease. Now, I might not

0:00:20.840 --> 0:00:23.119
<v Speaker 1>agree with how I message hijacks your phone number to

0:00:23.200 --> 0:00:25.520
<v Speaker 1>do all this, but it works for millions of people

0:00:25.640 --> 0:00:28.840
<v Speaker 1>and they love it. I'm like Android, where texting is

0:00:28.880 --> 0:00:31.680
<v Speaker 1>a total mess case in point, you have no idea

0:00:31.720 --> 0:00:34.960
<v Speaker 1>if your messages are ever delivered or seen. Pictures are

0:00:35.040 --> 0:00:38.360
<v Speaker 1>sent as tiny attachments, and don't even start with videos.

0:00:38.600 --> 0:00:40.599
<v Speaker 1>They look so bad on the other end, you might

0:00:40.600 --> 0:00:43.320
<v Speaker 1>as well have taken them on a phone in the nineties. Now,

0:00:43.400 --> 0:00:46.159
<v Speaker 1>Google says it has finally figured things out with a

0:00:46.200 --> 0:00:49.280
<v Speaker 1>new service called Chat. And before you say no way,

0:00:49.360 --> 0:00:52.239
<v Speaker 1>I am not signing up for yet another Google messaging

0:00:52.280 --> 0:00:54.600
<v Speaker 1>app or a new service, the good news is you

0:00:54.720 --> 0:00:57.880
<v Speaker 1>don't have to. That's because Chat is not a new app.

0:00:57.960 --> 0:01:01.520
<v Speaker 1>It's a new set of texting standards that carriers around

0:01:01.600 --> 0:01:04.640
<v Speaker 1>the world are now finally agreeing to think of it

0:01:04.680 --> 0:01:08.080
<v Speaker 1>as texting two point zero. Chat is the friendly consumer

0:01:08.120 --> 0:01:10.880
<v Speaker 1>facing household name but on the back end, it's really

0:01:11.000 --> 0:01:15.120
<v Speaker 1>OURCS or rich Communication services. Google has been talking it

0:01:15.200 --> 0:01:17.720
<v Speaker 1>up for years, but it seems like they finally got

0:01:17.720 --> 0:01:20.480
<v Speaker 1>the support of major carriers here in the US, including

0:01:20.560 --> 0:01:24.600
<v Speaker 1>AT and T, Verizon, Sprint, and T Mobile, plus dozens

0:01:24.680 --> 0:01:27.319
<v Speaker 1>around the world. Now The Verge has the full, long

0:01:27.400 --> 0:01:30.479
<v Speaker 1>and exclusive story, but basically, Google is going to pause

0:01:30.560 --> 0:01:33.520
<v Speaker 1>work on its other chat app called Alo to go

0:01:33.680 --> 0:01:37.160
<v Speaker 1>all in on support for Chat on Android phones, specifically

0:01:37.440 --> 0:01:40.680
<v Speaker 1>with an app called Android Messages. Chat is going to

0:01:40.760 --> 0:01:43.400
<v Speaker 1>let you see when people read your texts and when

0:01:43.440 --> 0:01:46.680
<v Speaker 1>they're typing back. Plus you can group text with ease

0:01:46.840 --> 0:01:50.040
<v Speaker 1>and send full resolution pictures and videos. There is one

0:01:50.080 --> 0:01:52.559
<v Speaker 1>big change. All of your messages will now be sent

0:01:52.720 --> 0:01:56.320
<v Speaker 1>using data instead of your text messaging allowance, So if

0:01:56.360 --> 0:01:58.440
<v Speaker 1>you send a giant video, it's going to use up

0:01:58.440 --> 0:02:01.720
<v Speaker 1>your data. Hopefully apps will have resolution options for when

0:02:01.720 --> 0:02:04.480
<v Speaker 1>it comes to sending pictures and videos, and if someone

0:02:04.480 --> 0:02:07.440
<v Speaker 1>on the other end does not have support yet for Chat,

0:02:07.680 --> 0:02:11.000
<v Speaker 1>your message will just default back to the typical SMS.

0:02:11.639 --> 0:02:14.680
<v Speaker 1>One thing Chat will not have is end to end encryption.

0:02:14.800 --> 0:02:17.120
<v Speaker 1>A lot of people are talking about this online. This

0:02:17.200 --> 0:02:20.280
<v Speaker 1>means that someone could theoretically intercept your messages and see

0:02:20.280 --> 0:02:23.520
<v Speaker 1>what you're sending or receiving. But today's SMS doesn't offer

0:02:23.560 --> 0:02:26.359
<v Speaker 1>that protection either. I Message does. That's why people are

0:02:26.360 --> 0:02:29.399
<v Speaker 1>talking about it, but again that's a proprietary system. Chat

0:02:29.480 --> 0:02:31.799
<v Speaker 1>will be available to any wireless carrier around the world,

0:02:31.880 --> 0:02:33.720
<v Speaker 1>and I have a feeling once this ball gets rolling,

0:02:33.760 --> 0:02:36.359
<v Speaker 1>it's going to be a pretty quick pickup because terrible

0:02:36.400 --> 0:02:40.000
<v Speaker 1>texting is one of the big disadvantages of Android versus iPhone.

0:02:40.080 --> 0:02:42.919
<v Speaker 1>And think about it. These carriers and these networks, they

0:02:42.960 --> 0:02:44.760
<v Speaker 1>want to sell phones, and they don't want to just

0:02:44.760 --> 0:02:47.200
<v Speaker 1>sell iPhones, they want to sell all phones. So the

0:02:47.280 --> 0:02:51.440
<v Speaker 1>question remains, will Chat work with iPhones? So far, Apple

0:02:51.520 --> 0:02:53.600
<v Speaker 1>is not saying but there's really no technical reason why

0:02:53.639 --> 0:02:56.240
<v Speaker 1>they couldn't add the functionality to their phones. But there

0:02:56.240 --> 0:02:58.399
<v Speaker 1>are a lot of reasons why Apple might not want

0:02:58.400 --> 0:03:00.960
<v Speaker 1>to get on board I Message, which is a major

0:03:01.080 --> 0:03:03.799
<v Speaker 1>lock in feature for iPhone users. Once they get used

0:03:03.800 --> 0:03:06.240
<v Speaker 1>to it, it works everywhere on their iPad, on their iPhone,

0:03:06.240 --> 0:03:08.680
<v Speaker 1>on their Mac computer, it's really tough for them to

0:03:08.680 --> 0:03:11.120
<v Speaker 1>give this service up. So when is this magic gonna happen?

0:03:11.240 --> 0:03:14.200
<v Speaker 1>Google says hopefully this year. Keep in mind. Google has

0:03:14.240 --> 0:03:16.839
<v Speaker 1>been talking about RCS for a while now, but now

0:03:16.840 --> 0:03:18.560
<v Speaker 1>that all these agreements are in place and they did

0:03:18.560 --> 0:03:20.880
<v Speaker 1>this big interview with the Verge, it's just a matter

0:03:20.919 --> 0:03:23.880
<v Speaker 1>of time before the switches are flipped. Sprint already has

0:03:23.919 --> 0:03:27.160
<v Speaker 1>support for the service between two compatible Android phones. T

0:03:27.360 --> 0:03:30.000
<v Speaker 1>Mobile promises support in the second quarter of this year,

0:03:30.360 --> 0:03:32.960
<v Speaker 1>but Verizon and AT and T haven't really given a

0:03:33.080 --> 0:03:35.880
<v Speaker 1>solid timeline at first. The main app to support all

0:03:35.920 --> 0:03:39.800
<v Speaker 1>this rich texting functionality will be Android Messages, but apparently

0:03:39.840 --> 0:03:42.840
<v Speaker 1>Samsung's messaging app will also have support, and there will

0:03:42.880 --> 0:03:45.240
<v Speaker 1>be a desktop version of the apps. You can finally

0:03:45.320 --> 0:03:48.320
<v Speaker 1>send and receive text from your computer without a lot

0:03:48.320 --> 0:03:51.800
<v Speaker 1>of workarounds. It is unclear if third party apps like

0:03:51.880 --> 0:03:55.080
<v Speaker 1>my current favorite, which is called Pulse SMS, will be

0:03:55.120 --> 0:03:58.680
<v Speaker 1>able to handle the new rich functionality. But finally, it

0:03:58.760 --> 0:04:01.680
<v Speaker 1>is about time an modern texting experience gets in the

0:04:01.760 --> 0:04:05.400
<v Speaker 1>hands of all cell phone users, not just iPhone folks.

0:04:05.760 --> 0:04:07.520
<v Speaker 1>Thanks so much for listening. If you like the show,

0:04:07.600 --> 0:04:09.720
<v Speaker 1>please leave a review. I'm Rich Jamiy. You can find

0:04:09.760 --> 0:04:12.200
<v Speaker 1>links to everything I mentioned here. Just go to richon

0:04:12.400 --> 0:04:15.160
<v Speaker 1>tech dot tv. I'll talk to you real soon.