0:00

Coming up on All About Android, it's me,

0:02

Jason Howell, in studio, and then it's

0:04

everyone else in studio, actually, too. Ron Richards,

0:07

Wynne Twitt Dao, and Michelle Roman all joining

0:09

me here at this table. A little bit of

0:11

Google I O preview, and then a ton of other

0:13

news and a heck of a lot of fun next

0:15

on All About Android.

0:20

Podcasts you love from people you trust.

0:24

This is Twitt.

0:28

This is All About Android, episode 629, recorded

0:30

Tuesday, May 9th, 2023. The

0:35

password paradigm. This

0:38

episode of All About Android is brought to you by

0:40

Delete.me. Reclaim your privacy by

0:42

removing personal data from online sources.

0:45

Protect yourself and reduce the risk of

0:47

fraud, spam, cybersecurity threats,

0:50

and more by going to join delete.me.com

0:52

slash Twitt, and use code Twitt for 20%

0:55

off. Also

0:58

thank you for listening to All About Android. As

1:00

an ad-supported network, we're always

1:02

looking for new partners with products and

1:04

services that'll benefit our audience. 99% of

1:07

our audience listens to most or all

1:09

of our episodes. Grow your brand

1:12

with authentic ad reads that always

1:14

resonate with our audience. Reach out to

1:16

advertise at twitt.tv and

1:18

launch your campaign now.

1:21

Hello, welcome to All About Android, your

1:23

weekly source for the latest news, hardware, and apps.

1:26

For the Android faithful, a very, very, very,

1:29

and one more very special episode

1:31

of All About Android, I'm Jason Howell. And

1:33

I'm Ron Richards.

1:34

Oh, and it's my birthday. Oh, wow, they just went for it. Oh, yes,

1:37

it is my birthday. Okay, well, you'll say your names in a second. Apparently

1:39

there's flame to be had about. Wow, celebrating my

1:41

birthday on All About Android. Spread your germs all over those. Yeah, spread

1:42

your germs all over those. I'm Jason Howell. I'm

1:45

Ron Richards. I'm Jason Howell. I'm Jason

1:47

Howell. I'm Jason Howell. I'm Jason Howell.

1:49

I'm Jason Howell. I'm Jason Howell. I'm

1:52

Jason Howell. I'm Jason Howell.

2:00

Thank you. I'm not keeping

2:02

the hat on the whole show. It's totally

2:04

lit. Is it like one of those

2:06

like joke candles? What, what,

2:08

what year? What, how long do we eat? No. Okay.

2:12

There

2:12

you go. And. Oh my God. Oh my

2:14

God. Burke, Burke.

2:17

I hate you. Okay. Victor,

2:20

go ahead and cut to win. So she

2:22

gets to get in there.

2:23

Hi, I'm with you now. There we

2:25

go. In studio. And finally. Shah

2:28

Raman, it's not my birthday, but

2:30

yeah, I'm glad to be here. I was like, Oh

2:32

God, what did I get myself into? Seriously,

2:35

I drove all the way up for this. Oh my

2:37

goodness. This is exactly why I drove up here. Oh,

2:39

thank you. Yes. Oh, it's sparkle confetti all

2:41

over you. Well, thank you everyone at Twit for

2:43

the wonderful birthday wishes. Also wishing

2:46

a wonderful happy birthday to Florence Ion. It

2:48

was also her, my birthday sister in

2:51

space. We chatted a little earlier. She's

2:54

already down at the shoreline,

2:56

picking up her Google IO badge. She's

2:59

flashing it. If you're a member of the club,

3:02

club twit discord, then you can see in all

3:04

about Andrea channels. She's, I mean, I don't

3:06

know if that's a picture of right now, but she is there.

3:08

She's there. She's got her badge, which is one step closer

3:11

than any of us. And I do

3:14

feel bad. Cause I don't want my birthday to overshadow the fact that we're

3:16

all in the same dang room. We are.

3:18

For the first time ever with this crew. Can I also say

3:20

this one more thing? We've got a room filled

3:23

with people, right? Actually

3:25

more people than we usually

3:26

possibly have ever had for all about Android

3:29

in here. We do have Burke.

3:31

Yes. Behind the board, but Burke is not

3:33

running the board today. It is Victor.

3:36

Victor will be running the board. And I should also mention

3:38

the Victor's birthday is in two days, right? Two

3:40

days. So

3:42

happy birthday to you, Victor as

3:45

well. Thank you. So

3:47

yes, we're all in the same studio.

3:48

How freaking awesome is that? We'll

3:51

eat. We'll eat those later. We

3:52

definitely, I definitely. Yeah. When

3:56

a Michelle would just be sitting here. You'll

3:58

be lucky to get one. I know. But yeah, it's

4:00

good to all be at the table. This is how we used to

4:02

do it, right? And yes, well,

4:04

yeah, once upon a time, you

4:07

would come into the studio almost every

4:09

episode because you lived in the Bay Area. Now

4:12

we're here from all over the country, really,

4:14

right? Like New York,

4:17

Texas, Colorado, Boise,

4:21

Idaho, but I live in Petaloma. Your

4:23

commute was not much on my flight.

4:26

Maybe seven minutes. But yeah, no, it's just

4:28

great that it all coincided with Google I.O.

4:30

tomorrow down in Mountain View. We're

4:32

all very excited to go to the big show,

4:34

the big Google show. Big show. Big one. And

4:36

all hang out together at it. It's

4:38

amazing. Yeah. And we got a lot to

4:41

look forward to at the show tomorrow. And

4:44

actually I'm looking through the news, like

4:46

if you're thinking that you're gonna get like nothing but

4:48

a Google I.O. preview, I'm sorry to

4:50

disappoint you. We're gonna start off

4:52

with a little Google I.O. Just kind of give you a little

4:54

taste because by tomorrow morning, it's gonna be outdated.

4:58

It's kind of already outdated. Yeah, it's

5:00

true. That's true. At this point,

5:02

we kind of know what we know. And then we've got a ton

5:05

of other news. I'd say three

5:07

quarters of which has Michelle's

5:09

name written on it. So- Michelle's

5:11

gonna do some heavy lifting there. Literally. I hope

5:13

you're ready. We'll keep you busy. But

5:15

yeah, we've got

5:16

a lot to talk about this week. So why don't we

5:18

just jump, I don't even know which of these like six

5:20

cameras to look into. Yeah, which is so many cameras.

5:22

I've got one. But why don't we jump into the news?

5:25

Victor, take us there.

5:29

Whoops. That's right. I guess I'm the

5:31

news. Michelle is responsible

5:32

for a lot of the news. That is true. We're

5:34

just gonna take a break. There's so much glitter in my hair. Looks

5:37

like it's an all Google

5:40

I.O. All Android

5:41

news. But

5:43

more so, there's so many people in the studio. I

5:45

couldn't come up with anything better. I'd really

5:47

hope that in honor of my birthday, it would have, the Android

5:50

news bumper would have risen to the level. But I'm

5:52

glad to see that we're consistent. But yeah,

5:55

so as we mentioned, it

5:57

is Google I.O. Eve. We

5:59

are very, very. excited. So yes,

6:01

we want to touch on just what are we going to expect tomorrow

6:04

and when all the nerds have sent them out in view. Well,

6:06

first and foremost, most likely is going to be Android 14, which

6:10

we've been talking about, I feel like we've been talking about for months

6:12

now already. It's like old news again. But

6:15

we're going to get the whole full story behind the update and we're going

6:17

to hear how Google's going to spin the new version

6:19

of Android and not that they need to spin it, but how

6:21

they're going to position it and link it to everything.

6:23

And within that, we're more than likely

6:26

going to find out a lot about how AI

6:29

and search are going to come into play. And we're going

6:31

to talk about that a little later in the show. But

6:33

clearly the race, you know, one of the stories

6:36

of 2023 is becoming the, you know, kind

6:38

of the race for AI with chat

6:40

GP chat, GPT leading the lead

6:42

and everybody kind of catching up. And of course, Bard

6:45

from Google's offering is right there at the forefront of

6:47

that. You know, look forward to

6:49

see how Bard comes to pixel at some point, either

6:52

via Google search or a standalone app,

6:54

which could be an announcement at IO. We'll see

6:57

what comes from that. And then it's

6:59

funny because I feel like

6:59

over the years, IO has vacillated between

7:02

like a developer event, we're talking about the new

7:04

version of Android, or, hey,

7:06

it's a consumer products event. We're going to show you new products.

7:08

But it looks like this year we're getting new

7:10

consumer products. And obviously the story is going to be how they

7:13

all work together in the ecosystem of Android. But

7:15

we talked about it last week. We're going to finally get that

7:17

pixel fold that we've been talking about for over

7:19

a year now. Probably going

7:21

to see the pixel seven a, the pixel

7:24

tablet that we already know exists. Right. So

7:26

those are great new hardware to expect,

7:28

but will we get a pixel eight

7:29

tees? It seems like kind of feel

7:32

like, yeah, probably like didn't

7:34

last year. They showed us what the pixels. Right.

7:36

Exactly. Google's playbook right now is

7:38

to kind of give you a little teaser. Right. We'll,

7:41

we'll head of the leaks. Will they have anything

7:43

to tease for pixel watch two? Do they want to pick

7:45

up on the wearable side? There are some rumors.

7:47

There are some rubri things saying

7:50

that a pixel watch two would happen by the

7:52

end of the year. Right. The end of your hardware. Yeah. Yeah. I

7:54

think the rumors say with the pixel eight launch.

7:56

Right. I mean, because it would be the ecosystem that

7:58

would make sense. right? Yeah, you get

8:01

the phone, get the watch with the tablet. But

8:03

the underlying tech underneath all that is the tensor

8:06

chip and we'll, we'll, we'll, we'll, they tease the tensor

8:08

G3 more than likely. We'll hear about

8:11

how great the tensor G3 works with AI.

8:14

We've had many advancements in

8:16

the realm of AI, specifically how

8:18

our Pixel phones, tensor

8:20

chip made exclusively by Google

8:23

level, but yeah, we could write the IO keynote

8:25

right now, I think with, with Bard.

8:29

Can

8:32

you imagine at the very end of the show?

8:34

And by the way, everything that you've heard

8:36

us say was written by Google

8:38

Bard. Thank you everybody. Have a wonderful

8:41

afternoon. That would actually be pretty impressive.

8:43

Yeah. So that's just a quick rundown of what we're expecting tomorrow

8:45

at Google IO, but is there anything else? Hey Michelle, what are you, what

8:47

are you hearing? Is there anything

8:49

else newsy that we haven't talked about? No,

8:54

I think the big thing to look out for is how Google

8:56

is going to incorporate generative AI into

8:59

everything. So

8:59

from their search products, maps,

9:02

play store development tools, Android,

9:05

Pixel, everything, like that's going to

9:07

be the big focus, the overarching theme,

9:10

I think of this Google IO. AI

9:13

chats. I mean, there's so much AI.

9:16

Yeah. There's the, um, what was

9:18

it? The, uh, the wall street journal had the, the news,

9:21

I think in the last

9:23

couple of days that, and I don't know if

9:25

this is IO driven

9:28

or further down the line, but that,

9:30

you know, Bard essentially would

9:32

get roped into Android in some

9:34

way, either within the search bar that

9:36

we're used to interacting with or as a standalone

9:39

app. But

9:40

being, you know, being that kind of always

9:42

present, always on device thing,

9:45

which really just reminds me of like, Google now days

9:47

of your, you know, more assistant it's what assistance

9:49

is what assistant has been for years now.

9:51

And yes, the thing is that like, I get, I get the

9:54

need to have a product to compete with chat

9:56

GPT.

9:57

And to put Bard out there and the way their

9:59

position.

9:59

There's so much glitter. But

10:04

the positioning barred as a

10:06

like help Bard write your homework

10:08

or do whatever type of, but like, I feel

10:10

like why aren't they saying, Hey, we've been here for

10:13

years with assistant like AI

10:15

has been a piece of our operating system for years. Because

10:17

it has been like we've heard about the machine learning and what

10:19

it can do in the pixel environment, what assistant can

10:21

do for it. I feel bad for the team that's worked on

10:23

assistant all these years to be like, Hey, what about

10:25

us? It really feels like that meme where

10:27

the guy, you know, that meme with the guy and his girlfriend, he's looking

10:29

over and so assistance his, his now girlfriend

10:32

and he's looking over at Bard like, yeah,

10:34

but I mean, and it's obvious, right? Because

10:36

when you're looking at chat,

10:39

you zoom out even farther. Yeah. He's

10:42

over there and he's more banging out. Right.

10:44

Right. Right. like

10:48

up people as well. So it really seemed like just in

10:50

all kinds of manners are shifting just to, and it's

10:53

so weird, right? Because for years it was

10:55

like Google assistant is like the best. Like we'd

10:57

make fun of being, we make fun of Siri and now

10:59

the table haven't have entirely flipped in

11:02

like a different direction. Oh yeah. Google's

11:04

like scrambling and we're just like going to be sitting here in the audience

11:06

watching like, huh, how's this going to go?

11:08

The narrative has shifted to

11:10

the credit goal was perfectly positioned

11:12

to dominate in this space and now

11:14

look at Google like sitting on the

11:16

benches trying to play catch up.

11:19

Yeah. Yeah. I think Google,

11:21

what people kind of underestimate Google's dominance still is

11:23

that, you know, chat GPT, most

11:25

people aren't going to go to chat GPT

11:28

website and interact with them. People have sure played with

11:30

it, but the way people interact with it is going

11:32

to be through services that people are using like, you

11:34

know, existing services. Super true. And

11:37

I still think Google has a huge

11:38

advantage at getting barred in front of

11:40

users, you know, more so than Microsoft does. Yeah.

11:43

That's a really, that's a really good point. I

11:45

mean, if, if Google was to bring

11:47

its barred AI to

11:50

every Android phone,

11:51

you know, that is GMS certified, let's

11:53

say, which I'm sure is exactly what Google

11:56

intends to do at some point. Like

11:58

does that.

12:00

Just just that that exposure

12:02

is

12:03

so valuable. You're right. Most

12:05

people have heard of chat GPT or

12:07

who have heard of chat GPT have interacted

12:10

with it, but it's not in their face every day. They

12:12

have to remember to go to that site. They have to remember

12:14

to have a reason to use it. Meanwhile,

12:17

you've got barred just hanging out on your home screen,

12:19

waiting for you to ask it that dumb question

12:21

or to generate whatever it is. It's going to do.

12:24

I mean, it's always there. So of course you're going to interact

12:26

with it in the same way that we interacted with assistant. I

12:29

couldn't help myself. I just went to Bard and I said, write

12:31

the Google IOK note

12:33

and it said, sure, here's a possible Google IOK keynote

12:35

for 2023. Welcome to Google IO.

12:37

We're here to be with you to share some of today's latest

12:40

news and innovations for Google. This year, we're focused

12:42

on three key areas, making the world a more

12:44

accessible place, helping people live healthier,

12:46

more productive lives and making the world a more sustainable

12:48

place. Pause. Applause. Tell

12:51

it to add more. Speak and then you'll be golden. But

12:54

what's funny is that it's all previous years.

12:56

It's like it's like, for example, we're introducing

12:58

Android 13. And we're talking about Google

13:00

Fit, right? Like it just cherry picking

13:02

stuff from.

13:03

It does a really good job of writing

13:05

last year's. Yeah, exactly. Exactly. As

13:07

much as Google reuses names, that actually might

13:10

not be a bad strategy to use Bard

13:12

for that. And at some point it's going to be right. It's like

13:14

the whole like monkey typing on a keyboard thing.

13:16

Yeah. Well, it's no. It'll come back around

13:19

at Google. They've been feeding Bard all

13:21

of their internal documents for the last year.

13:23

So, you know, I don't

13:25

actually think they've been doing that. But if they had,

13:27

Bart might actually be really good at writing a keynote.

13:30

This is interesting, though, actually, because it not only did to provide

13:32

this, but it provided there's a this

13:34

since I use that they've added this functionality. It's

13:36

just view other drafts. And there are three

13:39

different

13:39

approaches to answering the question.

13:42

Wow. Different drafts that are completely

13:44

different kind of. Yeah.

13:46

It's crazy. It's weird. It's weird.

13:49

I do think I mean, I know that chat GGP

13:51

just it's so hard not to start talking about AI

13:53

and get fall down this rabbit hole. Yeah. Rabbit hole. But

13:55

I know chat GPT just like is

13:57

opening up a lot of the services to your point. Like it's going to be the. underlying

14:00

structure that a lot of people are gonna choose to work with to

14:02

build stuff. And I'm curious to see what comes out of

14:04

that from the innovation of like what other people

14:07

are how they can focus the technology

14:10

and make consumer facing, you know,

14:13

not singular use, but more

14:15

less unlimited, right? Because I do think one

14:18

of the challenges of both chat, GPT and Bard

14:20

and whatever, what is Bing's called? What is that?

14:22

Bing. But like, it's just that

14:25

it's so open-ended and it's so like,

14:27

you could type whatever you want. Like, where do I start?

14:29

But having a focus on it, I think is helpful.

14:32

Well, that's kind of been a challenge

14:34

for things like interacting with Google Home

14:37

and Assistant as well in the past.

14:40

I don't know if that's a challenge that we struggle

14:42

with now because we kind of got used to the limitations,

14:44

but in the beginning, I know I remember

14:47

when Assistant came out and, you know, people

14:49

were writing articles or reference

14:52

documents that you could point to that were like, here

14:54

are like 500 commands you can do with

14:56

your Assistant. And I was like, well, that's neat.

14:58

That really shows the depth

15:00

of what it can do, but I'm

15:02

never gonna remember 99% of these things on the fly. You

15:06

know, it's like you have to program the syntax

15:09

into yourself in order to get the advantage

15:11

out of it. And it seems like where

15:14

they're going with these current systems

15:16

is that syntax kind of doesn't matter anymore.

15:18

It's like, what do you actually want? And we'll

15:21

figure it out for you. But the UI is gonna

15:23

decipher the syntax. Okay, so before we move on around

15:25

the table, I'm gonna turn around the horn one thing you're looking forward to at Google

15:28

IO. Fault. What?

15:29

Fault. Fault. Okay.

15:32

Give me fault. I mean, I wanna say that too. Okay.

15:35

I'm excited

15:36

for the fold. You get the right half. You get the left

15:38

half. I'll get the right half. My real answer for

15:40

my official answer, Android 14. Okay,

15:42

that's fair. And mine is the tablet. Obviously

15:45

that's what I'm so excited to get my hands on that tablet. Oh,

15:47

the poor little Pixel 7a. It's like, but

15:50

I may be a mid range, but you guys love me the

15:52

last couple of times. You

15:55

love the A series. You're always talking about how great

15:57

I am. By the way, I've never heard Jason's Pixel 7a

15:59

voice.

15:59

but I love it. It sounds like a brand character. So

16:02

now every time we talk about the 7A, you need to do

16:04

it that voice. Come on, guys. I

16:06

may be mid-range, but come on. I'm

16:09

powerful.

16:10

Actually, that character is going to be public. What

16:12

is it? Copyright and that character is ending in what?

16:14

Public domain. Public domain,

16:16

too. Okay, never mind. We'll

16:19

just get some generative AI to create a cartoon

16:21

character, like a cartoon pixel 7A with that voice. Like

16:24

with Cliffy's face. Oh, he's a bit more

16:26

or five-fold. All right, so someone out

16:28

there, go to mid-journey or do whatever and type in, make

16:30

a cartoon character out of the pixel 7A. Yeah. And

16:33

let's see what we get. Use this voice. Yes. Thank

16:37

God. All right. Well, let's

16:39

do that. All right. So that's

16:41

our IO preview. Yeah. That's all you get because in like 12

16:43

hours, we'll know everything

16:44

officially. Well, so yeah. So many of you

16:46

probably listening to this, either you're watching live or if you're

16:49

listening to this first thing tomorrow morning after you

16:51

download the podcast, you're driving to

16:53

work, go to all of our respective social media tomorrow and follow

16:55

along with us as we're in the audience

16:57

for the keynote and fun stuff and watch it on Twitter. Right.

17:01

Leo is going to be covering it. Right. Leo

17:03

and Jeff Jarvis is a Andy

17:05

Anotco, I think. Powerline.

17:08

I could be wrong with Andy, but I'm pretty

17:10

sure Andy is in as well for live

17:12

coverage of the keynote, twit.tv slash

17:14

live tomorrow, which is May 10th,

17:16

Wednesday, day after May 12th, Pacific, 1 p.m.

17:19

Eastern. So

17:22

yeah, not very long from now. If

17:24

you're watching, you know, so many people listen and watch

17:26

the show longer

17:29

distance than there is that keynote to tomorrow.

17:32

So, but regardless, that's

17:34

happening tomorrow. And then we've got a

17:37

pretty special interview with Dave

17:39

Burke and Samir Samat from Google.

17:42

We're going to be doing that tomorrow at Google. It will

17:44

not be livecast, but it will be

17:46

put onto our twit news feed. So

17:48

twit.tv slash news

17:50

and so it's not going to. I should just reiterate.

17:53

It's that interview is not going

17:55

to end up on all about Android. Usually these

17:57

interviews end up on all about Android, but we didn't want to.

19:57

on

20:00

your new device, down at the bottom, you'll

20:02

see a create pass key. And so you can say,

20:05

tell Google the Google passkey system,

20:08

this device is a passkey and

20:10

authenticates as me. So

20:12

it's kind of, it's a different way of logging

20:14

into your account, into your

20:16

Google account, specifically, instead of entering

20:19

in your password or the other authentication

20:21

methods. I can,

20:23

for example, go to log

20:25

into my site, choose passkey as my

20:28

login, and then on my phone, authenticate

20:30

with my thumbprint

20:32

or fingerprint or whatever fingerprint

20:34

you use to authenticate with. And

20:36

that will, that will clear

20:38

it and boom, you're into your account.

20:41

Until you can't find your phone. Well,

20:43

I have other devices. I mean,

20:46

I have a ton of devices, but

20:48

B, I can also use my other authentication

20:51

methods, right? It's not only passkeys.

20:53

Right. Right. Right. Yeah. And also

20:55

I think Google will let you back up your

20:57

passkey from your phone to your Google account

21:00

so you can restore it and like, you know, create

21:02

it on another phone. If you happen to lose yours, should

21:04

we try this live

21:05

Jason? Oh, that's a great idea. Jason,

21:07

do it. Listen, why don't we get it all set up? Jason,

21:10

just show us all the security measures you have enabled.

21:12

That's right. Let me show you my total. If

21:16

I could, if we could recreate the time Jason

21:18

locked himself out of his accounts live. Yeah.

21:21

Two factor authentication. It was a, it

21:24

was a thing. Episode of this week

21:26

in Google where Jason set up his two, two

21:28

FA live and then proceeded to lock

21:31

himself out of all this because I used my,

21:33

my Google voice phone number as

21:35

the authentication number

21:37

and you can't log

21:39

into Google account without your two

21:41

FA phone number. And you can't use your two FA

21:44

phone number because it's a Google voice number that you

21:46

used to receive the two.

21:50

It was, it was a little bit

21:52

of a nightmare and it happened in real time on live

21:54

on a show. It was fantastic. It was, it was,

21:57

it was seriously, it's one for the hall of fame. It

21:59

really was like.

21:59

You could search for this week in Google. The episode

22:02

I think was called Two Factor Falling. And if you search

22:04

for that, you'll find it. But hey, I for

22:06

one, welcome the end of the password. I

22:09

think, you know, it's- A long ways

22:11

from the end of the password. I know, but this is a step in the

22:13

right direction. I mean, literally at my

22:15

day job, we now have

22:18

to have to have a 16 character password

22:21

with multiple uppercase, lowercase symbols.

22:23

And it's like, it's hard

22:26

to remember, right? And like, admittedly I've

22:28

got Bitwarden now, keeping track of my passwords that

22:30

way and keeping them a little sorted that way. But it's between

22:33

the frequency that you need to change passwords and

22:35

update them and add into a face. So like, there

22:37

needs to be a new paradigm. So if this is the right

22:39

step in the right direction, I welcome it. Did

22:41

you get the passkey thing

22:44

or did you go and check it

22:46

out for yourself? Not yet. I

22:48

have not yet. I wanted to kind of sit down and be calm before

22:51

I changed all the things and not do it while

22:52

I'm traveling. Why don't you do it live on the show?

22:55

I did it last time. Take one for the team, Wave. Come

22:57

on. Let's do it right now. Yeah, sure.

23:00

That'll only take like an hour of my life. And you get to see WinCry

23:02

for the first time when I start walking with somebody and everything.

23:05

Now I'm looking forward to it too. Especially like just thinking about

23:08

all of our, you know, less tech savvy friends,

23:10

friends and family.

23:12

Looking forward to the day where I don't have to tell my

23:14

dad that he needs to stop using, nevermind, the

23:16

same password for all his accounts. I'll just say

23:18

that much.

23:19

Yeah, it does

23:22

seem like eventually if everything is

23:24

using passkeys, it perhaps creates

23:26

an easier landscape.

23:30

But I think right now it actually makes

23:32

things a little more complicated. Yeah, a little bit more

23:34

complicated. There's a learning curve. There's a password, a pesky

23:36

landscape we have right now. Well, it's gonna be a transition.

23:38

And when will we ever even be there? There

23:40

was a point, was it on, I can't remember which

23:42

of the Twitch shows, probably Security Now,

23:44

but maybe this week in Google or Twitter, I'm not sure. Where

23:47

they basically said like there is a, there

23:50

would need to be a point where everyone,

23:53

like every site you ever went to, every router,

23:56

all these things, they were all over on Paskey.

23:58

And there's so much.

23:59

tied into the password paradigm,

24:03

the password paradigm, that

24:06

like that will probably never happen. I

24:08

mean, as long as passwords are even an option,

24:11

they've been around for so long that it's hard

24:13

to see anytime in the even

24:15

distant future where it's like

24:18

passwords are irrelevant now entirely.

24:21

We can get rid of them entirely. Like, you know what I

24:23

mean? Like old outdated sites

24:25

are still gonna rely on passwords. I mean, it's

24:27

just, I don't know.

24:29

I was getting all hopeful over here, sitting here like for a passwordless

24:31

future, but now I'm just gonna just drag back down to

24:33

earth. I'm gonna destroy the fire. When

24:36

they look back in history, this is

24:38

the time of like turmoil and

24:40

like inconsistency.

24:42

Again, I'm a broken record. I wanna get to the

24:44

Roddenberry future, to the Star Trek future where all

24:46

technology is ubiquitous and everything just works

24:49

and everything is secure and

24:51

lovely, but just keep waiting

24:53

for that. Not in our lifetime. So in corporate

24:55

speak,

24:56

this is, so they're storming, norming,

24:58

forming, sorry, storming, forming, norming and

25:01

performing in terms of team dynamics.

25:03

Sorry, super corporate speak, not very fun at

25:05

all. So I guess you could see like, maybe we're

25:07

going from storming to forming like the

25:09

ultimate solution. And at some point it'll be norming when

25:12

it gets more ubiquitous and then performing when things

25:14

just work. I'm sorry, I've been in corporate life

25:16

too long. But

25:17

that's- I've never even heard of this before. Should we

25:19

do some blue sky, blue

25:22

sky engineering here? Yeah, totally, yeah.

25:24

There are no bad ideas.

25:25

Let's get the whiteboard out. Let's do a post-it

25:27

note exercise. Let's synthesize or

25:29

like ID8, wait. ID8,

25:32

oh, ID8. Blue

25:34

sky solutioneering, that's what I want. Solutioneering, yeah. Oh

25:36

my God, solutioneering, love it. I'd

25:39

never heard that before. I

25:41

kept hearing storming and thinking storming the castle.

25:43

Have fun storming the castle. Okay,

25:46

Princess Bride, sorry. You've

25:48

got the next story.

25:49

Yeah, and we already talked a little bit

25:51

last week about Apple

25:53

and Google joining forces to make trackers

25:56

a little less creepy and to kind of develop

25:58

it together a kind of- of a more

26:00

industry standard for trying

26:03

to detect nefarious

26:05

uses of trackers, especially with Apple already

26:07

having AirTag and having their own proprietary

26:10

solutions. But Google wanting to come

26:12

in there with, I forgot that their

26:14

air tracker was codenamed Grogu. It's

26:17

probably also a copyrighted name. But

26:20

this week, Apple and Google have actually submitted

26:23

a draft specification for this new standard

26:26

for tracking trackers or

26:29

cracking down on trackers. Tracker,

26:31

tracker, tracking, tracker, tracking. Anyway,

26:34

they submitted a draft specification to the Internet

26:36

Engineering Task Force, IETF,

26:39

which is an organization that is

26:41

the quote, premier standards development organization

26:43

for the internet. Now these aren't like, these

26:45

are voluntary standards. It's not like they're the internet

26:48

police and someone's going to come in if some third

26:51

party manufacturer creates a tracker that doesn't adhere

26:53

to these standards. But it is a way for them to kind

26:55

of together draft something, draft basically

26:58

OS level tracking of unwanted

27:01

tracking devices. The OS is tracking

27:03

the trackers. Who tracks

27:04

the trackers? Who tracks the trackers? There we go. Who's

27:06

tracking the trackers? And this would allow- Who's

27:09

trackering the trackers? Who's trackering the trackers? I

27:11

like those words. That's English. So

27:13

that would allow Bluetooth tracking devices to

27:15

be compatible with this across iOS, Android,

27:18

and of course other companies like Samsung, Tile,

27:21

Chipolo. Is it Yuffie? A

27:23

Yuffie? Yeah, Yuffie.

27:24

Yuffie. That will be obviously

27:27

more security is good, more privacy is

27:29

good. So any kind of OEM

27:32

that is kind of interested in this technology is

27:34

obviously interested in this draft specification. So

27:37

product implementation is actually expected

27:39

to be released by year's end. So a little

27:42

update to

27:43

the end of Nefarious AirTag and other

27:46

other new suggestions moving forward.

27:48

It seems awfully familiar. We did talk about this

27:50

a little bit last week, and so I apologize

27:53

that I didn't set this up. But

27:56

there's more detail here though, and especially

27:58

I think it's important to bring up.

27:59

because earlier today on

28:02

Security Now, Steve Gibson talked a lot about

28:04

this. And he

28:06

basically, this episode was episode

28:09

one of two where he's really diving deep in

28:11

the actual spec to really get a sense of

28:14

what's going on there. And

28:16

he said some details about this that

28:18

are kind of interesting to know and

28:21

definitely should know about this. They're

28:23

going to know how long that a user's

28:26

been away from the, or

28:28

the device has been away from the owner and

28:30

then behavior changes when that happens. So that's kind of some

28:33

of the orchestration that's going to happen on

28:35

the OS level. But this

28:37

is interesting. There's going to be a creation,

28:40

Steve says, of an industry-wide pairing

28:42

registry that matches

28:44

verifiable

28:45

ID information of the owner

28:48

of an accessory at the time of pairing. And

28:50

that's going to be a record that associated with

28:53

the serial number of the accessories. So the phone,

28:55

the email. So essentially it's like a tracking

28:57

database of like who owns what

28:59

and all of these tracking

29:01

devices and availability

29:04

made to law enforcement by request.

29:07

So it goes down this kind of dark

29:09

road where it's like, on one hand, yay,

29:12

this is really, this has a potential to be

29:14

really helpful and crack

29:15

down on things that are really bad. On the other hand, it

29:17

kind of opens the door for other really bad things. So.

29:20

This is that Pandora's box again. It's just like, who's

29:23

tracking the trackers now that the tracker trackers

29:25

are tracking.

29:27

You. Yeah. Oh

29:30

gosh. So. I think I'm following.

29:32

And this will not be clickbait headlines. No. As you

29:34

know, when's the first time somebody gets, you know, busted

29:37

or.

29:38

Yeah, the law enforcement, just

29:40

like the legal ramifications of this. And like, obviously

29:42

from an engineering perspective, this probably

29:45

makes, you know, detecting, you know,

29:47

unwanted trackers easier, but the

29:50

easy solution is not always the best solution. It's

29:52

just this effect of life in engineering. So just

29:55

like, okay, I kind of get it that this will

29:57

make it easier, easier. But easier.

29:59

for whom and for what purpose? Yeah,

30:02

easier one way and a lot murkier

30:04

than another. Oh, well.

30:07

Well, I mean, regardless, the

30:09

new specification should work with Finder Network,

30:11

which is like Google's, the Google

30:13

analog to, you know, the Apple's FindMe ecosystem

30:15

that does not just like, you know, find my device,

30:17

like find phones, like tablets, like Google

30:20

has, but kind of like is going to be more a broader scope

30:22

of any kind of like, you know, location

30:25

enabled device. And I

30:27

feel like a downer now having to kind of gone into

30:29

like the dystopian role we have, but

30:32

in my work on, in my ease ultra wideband.

30:34

So that's nice. So

30:36

there we go. There

30:38

we go. That's, wow. In less scary

30:41

privacy news, talk about Google

30:43

TV, my near and dear, I do love my Google

30:45

TV, by the way.

30:47

It's fantastic, but

30:50

it's not without issues. And so I was glad to

30:52

hear that Google's got an update to throwing out that

30:56

are doing two really important things as a Google

30:58

TV owner that I'm very happy

31:00

to see. Google says it will reduce

31:02

wait times at device wake up, which as

31:04

somebody who uses their Google TV, especially with

31:07

kids screaming to watch Bluey, and you

31:09

go to press the power button, you got to wait for it to wake

31:11

up. That those

31:13

couple of seconds are crucial. It's a long time.

31:15

It's a long time. Yeah. And then lastly,

31:18

the thing that I've had the biggest problem with, they're actually

31:20

going to add automatic hibernation of apps

31:22

that have been used for 30 plus days as a

31:24

way, but as a way to save

31:27

space, because there's not a lot of space

31:29

on that device. And I've run out

31:31

of space on it in the past, which is very frustrating

31:34

when I can't have all the apps I want installed

31:36

because I don't have enough

31:38

memory. It's insane. So- I

31:40

don't care about app hibernation on my phone necessarily, because

31:42

I've got tons of stores there on

31:44

Google TV. It's awesome. Yeah. Now

31:47

you mentioned Michelle before the show, that maybe

31:49

this- Yeah, there's actually- There's some detail missing. So

31:51

the hibernation thing

31:52

is actually

31:53

a bit more interesting on Android TV because it's

31:55

going to be supported by every single app on

31:57

Google Play for Android TV because-

31:59

Starting this month, Google Play actually made it a

32:02

requirement

32:03

for all apps, not just new apps,

32:05

but existing apps too, to

32:07

use the app bundle format. And on

32:10

phones, that's actually still only

32:12

required for new apps, not

32:15

apps that were previously using the original

32:17

APK format. So if you're using an Android

32:19

TV device and it's running Android

32:21

TV 12 or Google TV 12 version

32:23

or higher, it's going to be able

32:26

to support this app hibernation feature. Mm-hmm.

32:29

Very cool. That is really cool. And then lastly,

32:31

it's going to add support for the soon to be mandated

32:34

app bundles, which is exactly what... Yeah,

32:37

right. Yeah, which will do that and minimize

32:39

it by 25%, which is fantastic.

32:41

Which you should do anyway. It's not that hard to use app

32:43

bundles. It's like, just do the thing,

32:45

y'all. Just do the thing. I'm not even a developer, and

32:47

I use app bundles. I know

32:50

how to use... No, I actually don't know how to use app bundles,

32:52

but I can imagine it's probably really easy. It's tied up with a little string and you're proving

32:54

it. Yeah, that's all it is, right? Just like

32:56

those old... You just put it in a backpack and...

32:58

Yeah, totally. You hand the backpack over and you say, here's

33:01

your app.

33:01

Yeah, and they just pick out what they need from it

33:03

for your users. See, I could be a developer. Absolutely.

33:05

It's easy. Totally. And what do I

33:07

do all day? Yeah, I could be a developer.

33:10

I'll just use Bart. Okay.

33:14

And finally, to round out

33:16

the news, rolling back app

33:18

updates.

33:20

I'm just going to throw

33:22

this over to you, Michelle, because I will admit,

33:25

this one lost me a little bit.

33:27

Yeah, so basically, the May

33:29

update, security update rolled out this month,

33:31

and it wasn't terribly interesting. I mean, most monthly

33:34

security updates aren't really interesting if you don't

33:36

know exactly what's being fixed,

33:37

but there was one thing that's been fixed that I

33:40

think some users might care about, especially

33:42

if you're a Samsung user, because a couple

33:44

of months back, there

33:45

was this

33:47

exploit that was being taken advantage

33:49

of to do some cool things on Samsung devices, and

33:52

basically, the loophole that users were

33:54

using to take advantage of that exploit has been patched.

33:57

So what you can no longer do

33:59

is...

34:00

you can't downgrade a system app

34:02

anymore

34:03

beyond the factory install version. So say you

34:05

have version 2.0 of

34:08

a particular system application installed

34:10

on the OS,

34:11

but version 1.0 has this cool

34:14

little exploit that you want to take advantage

34:16

of to root your phone.

34:18

Before the May update, you could actually

34:20

roll back the update to that vulnerable

34:22

version and then do whatever

34:24

you wanted. But now Andrew will say, hey,

34:27

the factory installed version is version two, we

34:29

want to let you install anything older than that anymore.

34:32

And this isn't really like a big

34:34

security issue or a big deal because the only

34:36

way you could actually roll back the app is

34:39

if you have physical device access

34:41

and access to developer debugging

34:44

tools. So it's not like some

34:46

rogue app on your phone could maliciously

34:49

roll back updates to all of your system

34:51

apps. It's only something the user themselves or

34:53

someone with physical access could do. So

34:56

it's a minor little tweak, but I think some

34:59

users who were taking advantage of this exploit

35:02

on Samsung devices would like

35:04

to know that this is no longer possible. And

35:06

of course, anytime Google fixes an obvious

35:08

loophole like this, why did they

35:10

let you roll back and up a system

35:13

app beyond whatever was installed in the factory in the first

35:15

place?

35:16

Yeah. Yeah. Why is that? Why

35:19

is that even so long? Why is it even a thing? Google's

35:22

like, I don't know. You're

35:24

right. There shouldn't have been. Yeah. Now it's not. So,

35:27

okay. Good job, Google.

35:29

Good job. You're going to get a lot more good jobs,

35:31

I think, over the course of the next 24 hours. So

35:34

just get used to that, Google. Thank you,

35:36

Michelle. All right. We are going to take

35:38

a little break and thank the sponsor of this episode

35:40

of All About Android. And then we will get into some

35:43

more news. I know it's listed as hardware,

35:45

but that is false. It is just more

35:48

news. We've just got lots of news, news and

35:50

more news coming up. But first, this

35:52

episode of All About Android is brought to you by Delete

35:55

Me. If you've ever searched for your name online,

35:57

have you ever done that? If you

35:59

didn't like...

35:59

how much of your personal information was

36:02

available. Maybe you felt

36:05

exposed, unsafe. You

36:07

see your personal information in a search result and

36:09

you're like, wait a minute, I didn't know that was out there. This

36:12

means that everybody can get to that information. Like

36:15

it just doesn't feel good, right? Since 2010,

36:18

Delete Me has been on a mission to empower

36:20

individuals and organizations by

36:22

allowing them to reclaim their privacy and help

36:24

them remove personal data from online

36:26

sources. They have a wonderful team

36:28

that's driven by a passion for privacy

36:30

and a commitment to making it simple for

36:32

customers, that's you, to use. So

36:35

Delete Me actually helps reduce risk

36:38

from identity theft, credit card fraud,

36:40

robocalls, spam, cybersecurity

36:42

threats, harassment, unwanted communications

36:45

overall. So much of this stuff has

36:47

to do with social engineering and the

36:50

more information and data that can be pulled

36:52

to make that happen, it

36:54

just makes that a heck of a lot easier for them

36:57

to do that. So that's why Delete

36:59

Me is so powerful. Delete Me is the most

37:02

trusted privacy solution available, helping

37:04

thousands of customers remove their personal information

37:06

online. The average person, if

37:09

you didn't know, has more than 2000 pieces of data about them online that

37:14

Delete Me can actually find and remove.

37:16

That's a ton of data. Think about

37:19

how much time that would take to

37:21

just do that. And then, you know,

37:23

if Delete Me is doing that for you, that's the amount of time

37:25

that it saves you. Delete Me has

37:27

removed more than 50 million pieces of data

37:29

for their customers. One customer actually said, I signed

37:32

up and he took it from there, awesome service,

37:35

already seeing results, and I can attest,

37:38

it's super fast. Like when I first signed

37:40

up for Delete Me to try it out

37:43

for myself, initially going into it,

37:45

I was like, I don't really, I'm not really worried.

37:47

Like I'm a public person, I do

37:49

shows online. Like there's not a whole lot

37:51

of information out there that I feel like I

37:53

need to control, but then I didn't really think about

37:56

like the details, the like the

37:58

addresses or phone numbers or whatever. might

38:00

be hidden out there, right? And

38:03

once you put it in, I mean, it was

38:05

a cool process to kind of put the information in

38:07

and then wait a few days. And then I got that report

38:09

back and I was like, holy cow, like that's

38:12

actually a lot. A lot of my information

38:15

spread out amongst the internet. And I guarantee

38:17

you, if it's that way for me, it's

38:19

that way for you too. It's worth checking

38:21

into. So here's how it works. You first

38:23

sign up, you submit some basic personal

38:26

information to kind of feed

38:28

it some of the information that

38:29

you're looking for, right? This is information for

38:32

removal from search engines. Just

38:35

go to joindeleteme.com slash

38:37

twit to kick that off. And then

38:39

Delete Me experts will actually find

38:41

and remove your personal information from more than 580 data

38:43

brokers. That

38:45

helps reduce your online footprint. It

38:48

keeps you and your family safe in the process.

38:51

And then once the removal process starts, you're gonna

38:53

receive a detailed Delete Me report.

38:55

That's the report I was talking about within seven days.

38:58

And then beyond that, Delete Me will

39:00

continue to scan and remove your personal

39:02

information every three months. And

39:05

with automated removal opt-out

39:08

monitoring, they're gonna ensure records don't

39:10

get repopulated after being

39:12

removed. So it's kind of a continuous check

39:15

that these things don't pop up again. This means

39:17

names, addresses, photos, emails,

39:20

relatives, phone numbers, social media,

39:22

property value. I mean, so

39:24

many data points can be tracked

39:26

and deleted. As the data broker industry

39:29

expands, contracts and morphs,

39:32

they're gonna continue to add new sites and features to

39:34

ensure their service is both simple to

39:37

use and effective

39:38

in removing personally identifiable information.

39:41

And since privacy exposures and incidents

39:44

affect individuals differently, their

39:46

privacy advisors ensure that all their customers

39:49

have the support they need when

39:51

they need it. So protect yourself and

39:53

reclaim your privacy by going to joindeleteme.com

39:57

slash twit.

39:58

Make sure when you do that, the code twit

40:01

and that's join delete me dot

40:03

com slash twit use code twit when

40:05

you do that you're going to get 20% off

40:08

pretty awesome check it out for yourself and

40:10

we think delete me for their support of

40:12

all about Android

40:14

all right we

40:17

are back for the news the more

40:20

news that's right over to win with

40:23

the weather's no the weather so

40:25

the

40:26

forecast on background work is Android is

40:28

that it's going to be more consistent at least on Samsung

40:30

so this is a super

40:32

like technical thing but basically

40:34

every time you run any of your favorite Android

40:37

apps there's going to be something happening in the background

40:39

so as Android does we do

40:41

a lot of stuff that

40:43

takes a long time so whether that could be like downloading

40:45

your favorite podcast and your podcast app to

40:47

say actually playing a music file and your

40:50

music player of choice things like this if these are things that take

40:52

a long time and we don't want to make you sit

40:54

and wait there while the thing

40:56

the downloads happen while the things think while

40:58

the music plays you want to be doing other things so

41:01

on Android we have this whole concept of background

41:03

work which is basically a set

41:05

of API tools that we have for doing things

41:08

in the background and allowing you

41:10

as the user to either go somewhere else do whatever

41:13

you want whether that's the same app another app

41:15

and a lot of this stuff gets really

41:17

heady and there's like this concept of within

41:19

background work there's still foreground and background

41:22

work within your background work but there's

41:24

like certain there's like a lot of divisions between so like

41:27

your music player right that happens in the foreground you notice

41:29

that and you get that little notification in

41:31

your shade that's like hey this thing is playing

41:33

or if you have to download

41:35

something very specific and very immediately you'll usually

41:37

get like a download you know notification in your bar so

41:40

that's a foreground service and

41:43

so in Android in recent years

41:46

the Android team has really been trying to get us to

41:48

be a little more careful about how we

41:50

use these foreground services again because

41:52

that notification because they take up a lot more

41:54

resources and because they're basically priority

41:57

things they need to be done now whereas

41:59

kind of more kind of low key things like

42:01

say, when I worked at Trello, you could

42:03

actually like download some boards that you used

42:06

like regularly, like in the background kind of opportunistically

42:08

so that when you go and you go on the subway, maybe

42:10

you might have it there if the app had a

42:13

chance to download it. So there's like certain things that can be deferred

42:16

that can happen opportunistically. So there's like these two different

42:18

splits. Anyway, this is all very complicated

42:20

stuff. And the problem is

42:23

that it's hard to do this stuff right in general,

42:25

you know, like what kind of work do I need to do where?

42:28

And then you throw in OEMs and

42:30

the OS in there. So a lot of times

42:33

if say you're using an app and something is weird

42:35

with something that's happening,

42:39

like some kind of background work,

42:42

it's not always our fault. It's

42:44

not always our fault, just because it's very

42:46

complicated stuff. And again, because different OEMs

42:48

have their different players of OS is implementing these

42:50

different things. There's so much going on at once. There's so much going on.

42:53

Yeah, even explaining it is hard. But so basically,

42:55

in

42:56

an effort to make this an effort

42:58

to make things work the way they're supposed to work,

43:01

Google has announced that they are basically,

43:03

you know, working with partners and strengthening collaborations

43:06

to make all of this junk work

43:08

better. And the first partner they're really

43:10

working hard,

43:12

tightly with on this is of course Samsung. And

43:14

so they have committed to make it. Of course

43:17

Samsung. So all this stuff

43:19

that I mentioned about these like very restrictive

43:21

consumption, you know, like high consuming like

43:24

tasks, basically Samsung

43:26

is promising that on one UI

43:28

six foreground, these foreground

43:30

services, these important things that take up a lot of work

43:33

that the OS is doing will be

43:35

guaranteed to work as intended so long

43:38

as they are developed according to Android's new

43:40

foreground service API policy. So

43:42

I mean, that's good.

43:44

But basically they're telling us if we follow the rule that

43:46

they've already given us, then it should work

43:47

as intended. That's

43:51

that's that's easily written. Don't follow

43:53

the rules, then it's going to break. Okay.

43:56

Yeah, that's it's Google's basically

43:59

trying.

43:59

they made mistakes several

44:02

years back and they're

44:05

slowly trying to crawl their way back into

44:07

fixing it for developers. So the issue

44:09

I think it all stems back from

44:11

the fact that in China, GMS

44:14

isn't allowed, so Google Play services, all

44:16

those APIs for push notifications, for location,

44:20

none of that is available in China. So they

44:22

have to use alternative services, but

44:24

then there's a fragmentation of all

44:26

these alternative services and then all

44:28

these Chinese OEM smartphone makers

44:31

figured out, well,

44:32

you have 10 different apps using 12 different

44:35

services, that's training the battery. So let's

44:37

implement these features that saves

44:40

battery life by killing off these apps

44:42

in the background, but then those features

44:44

make their way into the global versions of

44:46

their software. And then you have this

44:50

massive issue where you have a certain app

44:52

just being

44:53

ended in the background while you're using it, or

44:55

like you're listening to a podcast, all of a sudden it just stops and you don't

44:58

know why, right? So over these years,

45:00

this fragmentation had just caused a lot of these

45:02

problems for app developers, for users,

45:05

and finally Google's been working to implement

45:07

a lot of

45:08

native battery saving features into Android

45:11

to hopefully wean off OEMs from their

45:13

own custom features so that

45:15

Android works more consistently for app

45:17

developers. Yeah, and it's been

45:20

hard because part of that solution has been to kind of

45:23

really enforce rules on us on how we

45:25

use these things to make it better, to try to like circumvent

45:28

some of that, but it only goes so far and it makes

45:30

our job a lot harder because it's honestly, I had

45:32

a hard time explaining it because it's just hard to understand

45:34

and hard to know what the right thing to do is. And so as Michelle

45:38

said, they're trying to fix mistakes

45:41

and make things better, but it's a little bit of

45:43

an underwhelming announcement. I'm sorry

45:45

to be like,

45:47

we're trying to make it work the way it's supposed to work and how we

45:49

promise you would work. So there you go. They

45:52

just need to assign Bard to the task. Pretty

45:54

much, just Bard. How do we fix foreground

45:57

services? Just a couple lines of code, right? Yeah.

45:59

That's all it is. Biggie, not all,

46:02

across all OEMs. So many different

46:04

variables to play. I just can't

46:06

even imagine. Anyway,

46:08

making it work is intended. Yeah. All

46:11

right. Well, cool. Well, thank

46:13

you. And for that, moving on. So

46:15

Android Automotive is looking to

46:18

get a little, to look a little better with material

46:20

design at some point, but

46:22

it looks like the OEMs will have more control over

46:24

it. Michelle, what's the story here? What's

46:27

going on with Android Automotive? So if you're familiar

46:29

with the latest

46:29

iteration of material design, aka

46:32

material U, the colors

46:33

that you get throughout

46:36

your system UI, throughout your applications, that's

46:38

all derived from your wallpaper.

46:40

Whereas in Android Automotive,

46:43

since you're dealing with

46:44

putting software on a car, there's a lot of safety

46:48

things to take into consideration when you're designing

46:50

a UI or any kind of interaction

46:52

that that user has to go through. So you

46:55

can't just like, you

46:56

know, you have to be very careful with how

46:58

you pick the colors and the design so that, you

47:00

know, there's no chance that you can't

47:02

see the button you're about to press or you

47:04

can't see some critical information. Or distracts

47:06

you from driving it. Yeah, distractions, right? So instead

47:09

of like algorithmically determining,

47:12

you know, the colors to use for the UI, Google

47:14

is leaving it up to OEMs to pick

47:17

the colors they want.

47:18

And there's some interesting things they can do with that. They

47:20

can say, oh, depending on your drive mode,

47:23

we can have one set of colors or, you know, when

47:25

you're parked, another set of colors, maybe it's a nighttime

47:27

or daytime, another set of colors. So

47:30

they can do all sorts of things with this

47:32

new system.

47:33

And then applications that, you know, want to opt

47:35

into this, they can use, they can add this

47:38

new library into the applications that will pull

47:40

the colors that are generated or

47:42

that were pre generated by the system into

47:44

their apps. And I'm assuming Google is going to be

47:46

publishing some documentation soon for app developers,

47:49

the documentation they publish right now is for

47:51

the actual Android automotive car makers. So

47:54

none of it was really directly relevant to app

47:56

developers. But I'm assuming this is something

47:58

we'll hear more about, you know,

48:00

Maybe tomorrow The

48:07

right time Perhaps

48:10

Google I oh Yeah,

48:13

well, so

48:14

see I don't have Android auto You

48:16

know and I wrote auto built built

48:19

into my vehicle I'm trying to

48:21

remember because when I was in Costa Rica the vehicle

48:23

that we had did have

48:25

Android well, it had it had it embedded

48:27

Android auto system. That's different than Android Motive

48:31

is there any sort of like what kind I'm

48:33

curious what kind of color customization

48:36

Capability you have with Android automotive

48:38

right now versus this like

48:41

how would this be any different than the customization?

48:43

They're able to do already

48:45

So I think the examples that Google

48:47

gave on the page is more like so

48:49

say you have a particular line of cars You know

48:51

made by the same automaker, but like just different

48:53

models might have slightly different color

48:55

branding, you know Signify a particular

48:58

brand. So maybe if you roll off the

49:00

shop, you know, your car is like red or something

49:02

Maybe you could have a reddish theme. That's

49:05

like still

49:06

Use look the list

49:08

of cars that currently have Android automotive range

49:10

from like a lot of Volvos 2023 Ford

49:13

cars 2023 Lincoln cars, right? So right

49:15

from there from a branding standpoint Ford is gonna

49:17

have blue, right? Blue

49:20

and metallic and that's kind of there if you drive if

49:22

you drive it forward You recognize that as

49:24

a color palette whereas Lincoln and she's

49:27

now and then this is like car brand trivia

49:29

now Like can you can you name the the signature colors?

49:32

But Lincoln is more also metallic, but

49:34

I feel like hints of red in there. Yeah But

49:42

yeah, but it's not a lot I mean in

49:44

the middle II that I'm looking at I just did quickly did a Google

49:47

search and it's as of September 21 So I'm sure there are new

49:49

models. Yeah, yeah, but like that's just an

49:51

example of 2023 Ford's 2023 Lincoln's

49:54

so

49:54

Interesting that makes a lot of sense.

49:57

So I think a lot of times being it

49:59

again big company

49:59

any storming forming, norming, all this big, big corporate

50:02

stuff. Brand identity is

50:05

a thing that people talk about all the time regardless

50:07

of what technical innovation you want, you always have

50:09

to have a strong brand identity, so this makes a lot of sense.

50:12

Because material design, when it first came out, like one of the big complaints

50:15

was that all apps tend to look same-sies,

50:17

and so

50:18

just makes sense

50:20

that they want a strong brand identity to go with it. I do remember

50:22

that. Early material design days,

50:24

it was like, oh, another app has material design,

50:27

and it looks just like that other app that has material

50:29

design. Everything looked so similar. It

50:31

took a- Can't make people happy, huh? It still looks

50:33

better. No, totally, right.

50:34

Andrew doesn't have design. Oh, well, they have design, but I'll just-

50:36

Oh, now it's unified. It's too unified. Now

50:39

it's- I still think it looks better than what

50:41

was before. Yes. Oh, for sure.

50:43

Well, and it's evolved a lot since then. I

50:45

think at some point, the brands were

50:47

able to figure out how do we keep

50:50

unique to our brand, but also still

50:52

kind of follow these design notes, and that

50:54

just took time. They got there eventually, but...

50:56

Well, in other

50:59

Michal news, and

51:03

something that we might actually hear about it, at Google

51:05

I.O. as well, are

51:08

maybe not necessarily this news, but

51:10

I feel like every Google I.O. is another

51:13

opportunity for Google to say, hey, here's a new

51:15

mainline module, and mainline

51:17

for those who may have forgotten or haven't

51:19

heard. It's basically, it's components of

51:21

Android that can be updated

51:23

without the need for a major OS update.

51:26

It's like they're pulled, those components are pulled out

51:28

of that main system. They can be updated

51:32

over the air, so it allows for

51:34

devices to be kept more up-to-date

51:36

in more different ways than

51:39

it could prior to mainline, because prior to mainline, you

51:41

had to have a full system update in order to get

51:44

all of these critical vulnerabilities

51:47

in some cases, but just these major

51:49

updates or major parts of the kernel, all

51:52

these different things updated.

51:53

Now, because of mainline, those, they're

51:57

components that can be updated individually.

51:59

I feel like at Google IO, we often hear

52:02

about like new modules

52:04

that are revealed to be updated

52:06

by mainline. And I'm in the, in the camp

52:09

of more mainline because I, I

52:11

just love that direction. I think it's really power,

52:13

like really strong, um, improvement

52:16

to Android and has been for a number of years

52:18

now. What, uh, what is the news here?

52:21

As far as like what we might see at Google

52:23

IO, but probably not. It sounds like from what you were

52:25

writing, probably not. Yeah, it's probably too late

52:27

for this to end up in Android 14, but,

52:30

um, there's a comment in a recent code

52:32

change that was submitted to the Android open source project

52:35

that said, um, basically

52:38

exactly. They're planning to turn the NFC

52:40

stack into a project mainline module. So

52:43

that would take, you know, all the Android components

52:45

that consist of the NFC code

52:48

and that would turn that into a updatable,

52:51

uh, modular system component. So that

52:53

would be

52:53

consistent across devices and updatable through

52:56

Google play.

52:56

Now the question is, you know, will this

52:59

actually land in Android 15? And

53:01

if so, would it actually become

53:04

a mandatory component

53:05

for OEMs? Because right now there

53:07

are other project mainline modules that

53:10

are actually optional

53:11

for OEMs like Samsung,

53:13

like one plus to implement.

53:15

So the Bluetooth module is one example.

53:18

Um, the wifi module is

53:20

also optional. The ultra wide band is

53:22

also optional. Like, so we don't know. So optional.

53:25

What does that actually benefit? I

53:27

mean, I guess it benefits the OEM, right?

53:29

Yeah. It benefits the OEM because maybe, you

53:31

know,

53:32

maybe there's a lot of issues with something as complex

53:34

as Bluetooth, especially, right? You want to make sure

53:36

that functions really, really well and consistently

53:39

there's no bugs, right? So if you force something

53:41

like,

53:42

um, you know, Google's

53:44

version of the Bluetooth module onto

53:46

everyone, there might be issues and that might just

53:48

cause a lot of things. Don't really know. Yeah. What you're setting yourself

53:50

up for by doing that. Got it.

53:52

Okay. Um, I,

53:55

it was so funny cause actually on the drive up here, I listened

53:57

to a not so recent, but fairly

53:59

recent version. of the Android developers backstage, which

54:01

is a podcast run by former

54:04

guests in the show,

54:05

Chet Haas and Romain Guy, and

54:07

they were actually talking about Project Mainline. It gets really

54:09

confusing at the end and it's really

54:11

funny to see two very prominent members

54:13

of the Android team get confused. But if

54:15

you were kind of curious about

54:18

Mainline and also compared to Project Treble, there's a really

54:20

good 10, 15 minutes at the beginning where

54:23

they talk about it. And the title of it

54:25

is called Mainlining, which I found extremely funny. But

54:28

yeah, if you're kind of curious

54:30

about to get more technical depth on that, you should check

54:34

that out. So

54:35

yeah, Android developers are actually mainlining. But I just thought it was funny

54:37

that I happened to read that and then I looked at the doc and I was like,

54:39

oh, this is perfect. Yeah. I

54:41

mean, I'm sure we're going to hear some news about

54:43

some new mainline components. If you had to guess,

54:46

you're the right one to guess. Yeah, we've already talked

54:48

about some of these that are coming in 14, like the Health Connect.

54:51

Oh, is that one

54:53

of them? Yeah. Yeah, totally. Makes

54:55

a lot of sense. All right. All

54:58

right. More to come. Okay. Well,

55:01

we haven't finished with Michelle yet because Michelle. The Michelle

55:03

Hoxie. All we have is Michelle. Basically

55:06

this whole block by this one store. You guys said you can't

55:08

do an entire show on pre-Google IO. So

55:10

I just offered up whatever news, you know, and

55:12

you all took it. So take

55:14

it away, Michelle.

55:15

So what I hate as a

55:17

consumer, but I kind of sort of maybe

55:20

understand as a developer is that a lot of times certain

55:22

apps will tend to lock into

55:25

portrait mode. So generally the ideal is

55:27

that if you have an app on your Android phone and

55:29

you turn your phone to landscape,

55:32

the app should also turn to landscape. You know

55:34

what I'm saying? Like, that's like in a perfect world.

55:36

That's kind of how it's supposed to work. And

55:38

ideally if I had to read

55:40

whatever, like the official

55:43

spiritual documentation for Android development was, that would

55:45

be like commandment number two or something. But it

55:48

doesn't usually happen like that. And I say that

55:50

as like, we know it's ideal, but as I've said many

55:52

times, people tend to borrow

55:54

things like, oh, responsive layout

55:56

and actually handling rotation. It sucks,

55:58

but it's a thing.

55:59

And so a lot of apps tend

56:02

to lock into portrait, which means that if

56:04

for some reason you're holding your phone

56:06

the wrong way, you might be trying to

56:08

read sideways. But,

56:10

but I was very excited to see that

56:12

Michelle, you figured out a way to maybe get

56:15

past that and make things

56:17

like work the way they're supposed to.

56:18

Just by developers? Yeah, so this is actually

56:20

an official like Google recommended implementation

56:23

that's available since Android 12.

56:25

So, you know, Google recognizes

56:27

that there are a lot of apps out there that still

56:29

lock themselves to portrait mode. And you know, it's

56:32

their prerogative whether or not they want to actually support,

56:34

you know, large screen devices like tablets and foldables.

56:37

Google is still not in the business of forcing developers

56:39

to do that, you know, because that would cause a lot

56:41

of friction and a lot of work for developers to do.

56:43

But they also recognize that, you know, tablets

56:45

and foldables, they're becoming more and more popular. So

56:48

this kind of like conflict between what

56:50

developers want and the experience

56:53

that users are getting right now. So instead

56:55

of, you know, hoping, you know, saying

56:58

Google is telling developers, please, please, please,

57:00

please do this. They've been saying that for years, you know, please support

57:03

large screen devices. So

57:05

kind of nice milligram to come up with is a way

57:08

to override

57:10

the app's request for the orientation

57:12

that they're specifying. So for example, if

57:14

an app says, I want to be in portrait mode all the time,

57:17

the OEM can say, no, you're gonna be in landscape

57:19

mode. But

57:21

as a compromise,

57:22

that app won't just be stretched out to

57:24

fill the entire screen landscape mode because that would make

57:27

it really ugly. A lot of apps would just look really bad.

57:29

So instead what they're doing is they're putting it in a letterbox. So

57:32

the app would still be in its native aspect

57:34

ratio, like a portrait,

57:36

you know, candy bar orientation most of the time,

57:38

but there would be some background, you

57:40

know, filling up the left to right side. And

57:43

that's customized by the OEM. You know, you could

57:45

put like the wallpaper there, you could blur the wallpaper,

57:47

you can maybe have the

57:49

app move to the left side or the right

57:51

side, depending on your device. You know, that's something

57:54

that Google has added there

57:55

and they're hoping OEMs take advantage

57:57

of it, but so far it doesn't seem like any

57:59

really.

57:59

have, although there are some OEMs

58:02

like Samsung and Lenovo that offer their

58:04

own takes on this kind of feature, you know, through

58:07

their various labs features on Samsung

58:09

devices, for example. Yeah. But

58:11

this official Google implementation,

58:13

you know, seems like something they might be using

58:15

on their devices, you know, who knows. And

58:19

you

58:19

know, it's interesting to see that Google has

58:21

this feature,

58:22

but there are some devices like there were, I

58:24

heard from some reviewers complaining about the

58:27

OnePlus pad in the Oppo Find

58:29

N2, you know, like whenever they unfold their

58:31

Find N2, because it's a

58:34

wide body foldable,

58:35

whenever they unfold it, it's in landscape mode.

58:38

So a lot of apps that are forced to portrait mode,

58:40

they have to flip it again just to use apps like Venmo

58:43

or Authy. So

58:45

by using this built in command

58:47

to override the app's orientation

58:50

preference, they could restore that and

58:52

have the app be displayed in a letterbox.

58:54

I like that.

58:55

And so yeah, that is a big problem. And

58:58

on the fold, it does work that way. I do get letterboxing

59:00

and, you know, kind of co-ester one UI

59:02

features where, as you said, I can kind of shift. Like,

59:05

if I'm in bed and I've got my fold open really

59:07

wide and I'm just feeling lazy, I can actually kind of

59:09

shift the UI over to be wherever my thumb is. And

59:12

it would be nice for that to be OS.

59:14

And to be perfectly honest, as a

59:16

developer, if the OS does that for me for

59:18

free, it's

59:19

just more like up

59:21

until now, because we haven't had kind

59:24

of compensation UI like

59:26

that for our bad decisions. You

59:28

kind of just have to pick between we don't have

59:30

time or design resources to implement this

59:32

and hopefully, based on usage

59:35

numbers, oh, well, 80% of our users

59:37

only use our phone like in this situation. Usually

59:39

you kind of think it's okay. But I really don't think

59:41

that...

59:42

I can't imagine a lot of developers would have a

59:44

problem with the OS compensating and doing

59:47

things like letterboxing and adding that on. It just seems like

59:49

reinforcing our laziness.

59:53

We're giving you the night off. It was giving

59:55

us the night off. So I don't want to stay up until

59:58

the end. That's the day you frame it. We

1:00:01

should do it anyway. But thank you Google

1:00:03

for making up for us. And I do want to be

1:00:05

the voice of turning off auto

1:00:08

rotate in the control panel, at least

1:00:10

on the pixel side of things, where it's

1:00:12

like, I want to stay portrait

1:00:14

mode and

1:00:16

so just don't do any rotation. So funny, my

1:00:18

behavior, my default behavior

1:00:20

there has shifted over the years. There was

1:00:22

a time where I hated, I

1:00:25

would not lock it into place because I wanted

1:00:27

the widescreen. At a certain point I was like, yeah,

1:00:29

but the widescreen, home screen is really

1:00:31

ugly and weird and you know. Well,

1:00:33

what I just can't stand is the, in

1:00:37

bed or on the couch or whatever, and

1:00:39

then the, where, where,

1:00:40

where, where, where, where, where, where, where, dance with whatever. And

1:00:42

then you rotate it and then like two seconds later, it

1:00:45

catches up with you. And then you try to go back

1:00:47

and then it flips back and then so just turn it off, just turn

1:00:49

off, don't rotate, keep it, keep it. Like

1:00:51

I do think it's neat to add letterboxing and like, so, because

1:00:53

you don't want that stretch out experience, but then

1:00:56

like you're wasting screen space. You know what

1:00:58

I mean? But these are like

1:01:00

these deep, deep, deep, deep UI

1:01:02

adjustments that they need to work. But whenever

1:01:05

you talk about OEM specific

1:01:07

tweaks that goes back to what you were talking about with the background

1:01:09

stuff, where it's another, another

1:01:11

layer or

1:01:12

another, you know, peel

1:01:15

off of a reality that can happen that needs to be accounted

1:01:17

for. So yeah, but yeah,

1:01:19

just turn auto rotate off.

1:01:21

Yeah, that's all you gotta do. Take it for Rob. All

1:01:24

right, we've got some app news coming up here

1:01:26

in a moment, but first

1:01:29

I

1:01:29

want to give you a little word about, well,

1:01:32

us, not, not,

1:01:33

not you three. We've talked enough about us. Yeah,

1:01:35

not about you three, but about us, twit,

1:01:38

because we actually, so if you

1:01:40

come into the studio as

1:01:43

the three of you did on the wall,

1:01:45

it says, we are dedicated to building a highly

1:01:47

engaged community of tech enthusiasts by offering

1:01:50

them the knowledge they need to understand and

1:01:52

use technology in today's world.

1:01:55

That is the twit mission

1:01:57

statement right there. And we've had that up there since we.

1:01:59

move to the Eastside studio a number of years ago.

1:02:02

Um, and what's critical to that is

1:02:05

the partnerships that we make with

1:02:08

the brands that we trust, because we

1:02:10

vet all of the brands that we actually

1:02:12

work with pretty deeply, uh,

1:02:15

in order to bring sponsors onto the

1:02:17

network. Um, because we know that you

1:02:19

as an audience member, you know, we're introducing

1:02:22

you to these brands, to these companies

1:02:25

and their products and everything like that. We know that you trust

1:02:27

us. Um, did you know that half

1:02:29

of our listeners are in management

1:02:32

positions or above 65%

1:02:34

are involved in

1:02:36

their company's decision-making. So we've

1:02:38

got some really high level people, uh,

1:02:41

here listening, uh, to twit

1:02:43

and watching our shows. Our audience raises

1:02:46

the bar for us and our partners. And

1:02:49

that really explains why our network continues to stay

1:02:51

at the top for delivering, uh, the,

1:02:53

the tech news that we do every single

1:02:55

day. We do it here on all about

1:02:57

Android and all of our other shows and doing it reliably,

1:03:00

uh, partnering with twits.

1:03:03

If you work at a company that,

1:03:04

you know, is interested in partnering with twit,

1:03:06

that basically means you're going to get the gold standard in

1:03:09

podcast advertising. You get

1:03:11

a ton of services. You don't just get me

1:03:13

or Leo or Micah or ant

1:03:16

or any of our network hosts reading

1:03:18

an ad that's certainly part of it, you know,

1:03:21

getting out that brand message. You get full service

1:03:23

continuity teams. So we have a whole team

1:03:26

that supports everything that we do

1:03:29

on an ads basis here from copywriting to

1:03:31

graphic design. It's the whole, the whole deal.

1:03:34

You get embedded ads that are actually unique

1:03:37

every single time. We always, uh,

1:03:39

over deliver on impressions in fact.

1:03:42

So that's pretty awesome. Onboarding services,

1:03:45

ad tech with pod sites, which is free for

1:03:47

direct clients and detailed reporting. You

1:03:50

get courtesy commercials. Those are actually

1:03:52

shareable across social media and landing pages.

1:03:55

So that's a little value add

1:03:57

there and you get other free goodies. Uh,

1:04:00

like mentions in our weekly newsletter that are sent

1:04:02

to, we have thousands of fans

1:04:04

subscribed to that, bonus ads, social media

1:04:07

promotion. Basically, we want

1:04:09

long-term partners that want to grow with

1:04:11

us. We've had so many partners grow with

1:04:13

us over the years. If you've been a fan of

1:04:15

the Twit network, you know some

1:04:18

of these partners. In fact, we've got a couple of

1:04:20

testimonials here. Tim Broome, the

1:04:22

founder of ITProTV, they've

1:04:25

advertised on our network for 10 years now, still

1:04:28

with us, I might

1:04:29

add. And actually, Tim said

1:04:32

we would not be where we are today without

1:04:34

the Twit network. And that is true. Mark

1:04:36

McCreary, the CEO of Authentic,

1:04:39

who's partnered with Twit for 16 years,

1:04:41

said the feedback from many advertisers over 16 years

1:04:43

across a range of product categories is

1:04:46

that if ads and podcasts are going to

1:04:48

work for a brand, they're going to

1:04:50

work on Twitch shows. That

1:04:52

just illustrates how effective

1:04:55

what we do here is. So

1:04:58

this is really just a message to

1:05:00

tell you if you have a business, you want

1:05:03

to elevate your brand, you

1:05:05

should reach out to us. At least

1:05:07

hit off an email and we can talk to you about

1:05:10

what we can do to work with you on

1:05:12

this. It's advertise at twit.tv.

1:05:15

And yeah, you

1:05:17

can get to work with twit.tv's

1:05:20

world-class audience. That's advertise at

1:05:22

twit.tv. We love

1:05:24

what we do here. We love

1:05:26

being

1:05:29

in a position to tell people about

1:05:31

the really incredible technology and

1:05:33

advancements happening out there. We'd

1:05:36

love to do that for you too. So advertise

1:05:38

at twit.tv. And thank you for

1:05:41

that. All right.

1:05:43

And now we've got some app news.

1:05:45

Let's jump in.

1:05:54

All right.

1:05:55

I can still

1:05:57

hear that little jingle, even though we can't

1:05:59

hear.

1:06:00

I'm all the

1:06:02

jingles in my head. Oh,

1:06:05

Jeff Cosmicky. He's doing well.

1:06:07

Yeah. Jeff at a show in Brooklyn

1:06:10

once. Yeah. That was fun. That's right. That's a good dude.

1:06:13

All right. If I hear anything more

1:06:16

about check marks, my God.

1:06:17

Well, I'm sorry. I'm sorry, Ron. You're

1:06:19

going to do. So I mean, does anybody, did anybody

1:06:21

have a blue check mark before the check mark apocalypse

1:06:24

on the bird's eye? Nope. Okay. Never did. Would

1:06:26

you like to have one? I mean, because if

1:06:29

you don't want to go to the bird's eye and deal with all that

1:06:31

nonsense, Gmail is actually adding

1:06:33

a blue check mark to signal

1:06:36

verified sender. So this is building on

1:06:38

a system that they implemented in 2021,

1:06:41

which was for verified brand logos using

1:06:43

the B I M I

1:06:45

BIMI, the brand indicators for message indication

1:06:48

standards. So now they're going

1:06:50

to add on top of that, a kind of check

1:06:52

to make sure that, you know, basically

1:06:55

the person that is sending you an email

1:06:57

from a particular domain is actually the

1:06:59

owner of that domain. So this

1:07:02

is going to be based on strong on the authentication

1:07:05

with domain based message authentication

1:07:07

reporting and conformists conformments.

1:07:10

Oh wow. That's a

1:07:11

D Mark. We'll call it D Mark because when can't actually

1:07:13

say the whole

1:07:14

conformance

1:07:17

conformance conformance conforming

1:07:20

not conformists conformance

1:07:22

conformance. Yeah, that is kind of

1:07:24

hard to say conformance

1:07:25

and a logo

1:07:28

verification with a VMC issued

1:07:30

by certificate authorities, such as interest or did you

1:07:32

start? So basically this is

1:07:34

what we kind of all had hoped blue checks would be. And

1:07:37

basically allowing you to distinguish

1:07:39

when you're getting email from an actual verified

1:07:41

sender rather than someone who is impersonating, you

1:07:43

know, someone sending an email

1:07:44

from a certain domain. That is me. I

1:07:46

do find this really interesting despite the blue checkmark

1:07:49

aspect of it, which, which is like, come on, just be

1:07:51

a little more creative and come up with something else. But

1:07:53

still, um, I just recently

1:07:55

went down like a major D Mark rabbit hole

1:07:57

with my own server because, um,

1:07:59

something happened and like the email setup

1:08:02

and stuff like that and we were getting folks

1:08:04

sending from our domain for

1:08:06

one of my companies was getting rejected

1:08:09

and getting sent back because the DMARC profile

1:08:11

wasn't clear. So if it was sending to somebody

1:08:13

at a Gmail account, it was bouncing back and saying, hey,

1:08:15

we can't verify you are who you say you

1:08:17

are, so we're gonna bounce back. So I had to go to, I had

1:08:19

to figure out the DMARC and the DKIM

1:08:22

and like SPF and like all this like deep

1:08:24

IT, like I was in

1:08:27

the Google help things figuring it all out, but

1:08:29

like once I got into it and figured it out, it's

1:08:31

a bunch of stuff you put in on your

1:08:33

DNS, on your mail server

1:08:36

stuff, you know, kind of that validate

1:08:38

and there's a key that matches, I use

1:08:40

Google workspace, it's a key that matches it, so now

1:08:42

someone getting an email from my domain knows

1:08:44

it is truly coming from someone on my domain and

1:08:47

having a visual kind of

1:08:49

cue to that, I think is a good thing to do, just

1:08:51

don't make it a blue check mark, that's all. So it's

1:08:53

a very cool technology, like the whole DMARC

1:08:56

stuff is like, I got into it for a

1:08:58

bit, I'm like, oh, this is really cool.

1:08:59

Yeah, why is it a particular blue

1:09:02

seal with a white check mark in the middle

1:09:04

is how we've agreed, why are we agreeing

1:09:06

that that's

1:09:06

conformance? It's conformance. Yeah,

1:09:08

it's conformance. Conformance, yeah. Yeah,

1:09:11

so it started rolling out as of May

1:09:13

3rd and will be available over the coming days and weeks,

1:09:16

it's available to all Google space customers

1:09:18

as well as legacy G Suite basic and business

1:09:20

customers and will be available to

1:09:22

the rest of us with personal Google accounts, so.

1:09:24

Why check mark,

1:09:26

why not have like a little hot dog guy or

1:09:29

like something, like just something to

1:09:31

like that, make it all look cool, this is a legit thing. Nothing

1:09:34

says authentic business

1:09:35

email, like a hot dog guy.

1:09:38

Let's all go to the lobby. But

1:09:41

I don't know, cousin of John Chats says green

1:09:44

bubble. Yeah, that's what it means. Could be a green bubble.

1:09:46

Green bubble or green check mark or like a safe, like

1:09:48

a lock, some sort of like secure,

1:09:51

you know, like something, I don't

1:09:52

know. Like clashes SS, wow, see, I,

1:09:55

has this. They're getting rid of that icon though. Yeah. Oh,

1:09:57

so can they take it? Like, we'll just. That

1:10:00

won't be confusing. Although that

1:10:02

would be confusing and that's why

1:10:04

I'm actually surprised they didn't do that. Exactly.

1:10:06

Or what about like a posted stamp in a safe or

1:10:09

like something to just like this, I don't know,

1:10:11

I'd envelope. Because we all know what a check mark means.

1:10:14

A check mark means good or you know what

1:10:16

I mean or okay. Well you're doing the happy

1:10:18

hot dog guys. Because I don't have a check mark as a phone.

1:10:22

So I don't know.

1:10:24

Well. I'm trying to do a check mark with my hand

1:10:26

but it's just not working. So just do

1:10:28

the Asian heart

1:10:30

which is just like that. It's just that. It's

1:10:33

a heart. It's like Korean and Korean called. You

1:10:35

do that. Oh okay. Your heart instead

1:10:37

of this. Anyway. Yeah anyway. All right

1:10:39

well. All right well we were talking earlier in the show about AI

1:10:43

and if you're looking for some cool AI-ness

1:10:45

stuff to come to your Google world. Google

1:10:47

messages or Android messages will start. We'll

1:10:50

soon get a new AI powered feature called Magic

1:10:52

Compose. And

1:10:55

actually if we're taking bets on what might

1:10:58

appear tomorrow at Google I.O. this could show up

1:11:00

in the presentation. We'll see. And

1:11:02

basically this will give you a little assistance

1:11:04

in writing your

1:11:05

messages. And

1:11:07

so like tone or style. So you can

1:11:09

have a formal message versus informal. To

1:11:12

delightful where you can get across excited. Feeling

1:11:15

excited. You can also use the

1:11:18

music notes emoji for lyrical responses

1:11:20

for kind of musical stuff. And

1:11:22

each of these will take what you've written and offer

1:11:24

suggestions on how they can be rewritten in

1:11:27

those styles. So if I want to tell Jason

1:11:29

you know can't wait to be there tomorrow. And I say

1:11:31

oh I want it to be more excited. It'll

1:11:33

make the response that much more excited.

1:11:35

Yeah. So. Woo.

1:11:38

It seems like a lot of work for text messages. Yes it does. So okay

1:11:40

so one of these. I want them to get the message and then propose

1:11:42

like here's your response yes or no. Like. Right.

1:11:46

You know like write it for me in advance. Don't juj up what

1:11:48

I've done.

1:11:49

So 9to5 Google has the example.

1:11:51

It's a response to a text

1:11:53

thread.

1:11:56

Where the response is okay

1:11:58

I'll move the van.

1:11:59

And they triggered the lyrical

1:12:03

suggestion, which actually wrote like a poem.

1:12:05

Nice. So it took, okay, I'll move

1:12:07

the van to, sure,

1:12:10

I'll move the van. I'll do it right away.

1:12:13

I'll get it out of the way so you can

1:12:15

have your space. It's

1:12:17

a really horrible poem. That's

1:12:19

really not good poem. But

1:12:22

okay. It's

1:12:24

a strange

1:12:27

example, I guess, is where I wrote it. Could you imagine

1:12:29

you're just in an urgent situation

1:12:32

where you just need to communicate with someone, you accidentally

1:12:34

hit the zhuzh it up

1:12:36

to be like a haiku or something. I don't understand

1:12:38

what this guy's saying. What is going

1:12:39

on? What is his first name? But I do

1:12:42

think the term magic composed could be used

1:12:44

for like, you send me a message, it's like, hey,

1:12:47

you got this message, here's a response. Is this

1:12:49

what you were going to say? Like anticipate what my

1:12:51

response is going to be. Well, that was kind of the promise

1:12:53

of smart reply, right? What

1:12:56

we've realized in using smart reply is it's

1:12:58

very specific to a few very

1:13:00

canned things. It

1:13:04

doesn't have a wider context to it outside

1:13:06

of communication. Amongst humans is very difficult

1:13:08

for machines to understand.

1:13:09

This is what we're learning. I

1:13:12

actually

1:13:12

have a very funny story with smart reply. I

1:13:15

was messaging my husband for something in the kitchen. I

1:13:18

sent him, baby, can you help

1:13:20

me? And apparently smart reply only gave

1:13:22

him the response. No. That

1:13:26

was it. I was like,

1:13:28

and then he just sent me a screenshot of that and then eventually

1:13:30

came up and helped me after

1:13:31

he stopped. To your point, sometimes

1:13:34

the machines don't understand context, but I do

1:13:36

like that. It's a pretty succinct answer. If

1:13:38

you just need to get the point across, like I cannot

1:13:41

and I only have one word and the amount of time to hit

1:13:43

that button. But that is true. And that's what that's

1:13:45

what will be the failing or not the failing, but the challenge

1:13:47

with all this AI stuff and chat, GBT and bar

1:13:49

and all this sort of stuff. And it goes back to the conversations

1:13:51

I've had with social media vendors,

1:13:55

like applications that do sentiment tracking

1:13:58

or sentiment in social media and the.

1:13:59

I always give when I'm talking these vendors because I'm trying to

1:14:02

use them for work is like it's very helpful to

1:14:04

get to Get a sense of hey, we put this out there. Do

1:14:06

people like it or don't like it, right? And generally

1:14:09

Everyone I see you get like a third

1:14:11

like it a third don't like it in the middle Undetermined

1:14:14

because the because the algorithms don't understand

1:14:16

the nuance of language and especially in

1:14:18

our kind of geek world You get a lot of people saying oh

1:14:20

my god. This is the s right?

1:14:22

I don't want to say I don't say the curse on air,

1:14:24

but like this is the the right and They

1:14:27

will see the curse and assume it's negative Even

1:14:30

though that line is a very positive sentiment

1:14:32

that I see right And that's just an example

1:14:35

of how much nuance in English language there is

1:14:37

and why it's nearly impossible for AI to figure

1:14:39

that stuff out So and there's

1:14:40

always gonna be a gap because it's learning based

1:14:43

on you know data from us So, you know

1:14:45

if human culture moves forward, it's still gonna take a while for

1:14:47

that. It's

1:14:48

always playing. Yeah, it's always claimed catch-up. So So

1:14:52

fascinating stuff Interesting

1:14:54

what could be one of many AI announcements

1:14:57

happening Google IO

1:14:59

All right over to you

1:15:01

Michelle because It's

1:15:04

just a kind of a joke take it away Michelle Some

1:15:06

people are seeing ads in their play store. I checked

1:15:09

my play store search. I did not see an

1:15:11

ad I have seen ads in my play store search

1:15:13

So you do a so you open up play store

1:15:15

you tap into your search field and it just

1:15:18

showed you some ads Like like little

1:15:20

like app ads basically

1:15:22

right there. Oh you are I didn't even type

1:15:24

anything and it's giving me a calm Yeah,

1:15:27

actually so for the past couple of months I think

1:15:29

in November there was a test being spotted

1:15:31

where you would have when you just

1:15:33

open this open Google Play Store Tap the search

1:15:36

bar you would see a suggestion For

1:15:38

like a recommended app

1:15:39

even though you haven't really typed anything. So how is that recommending

1:15:42

you something? I mean ironic that my recommendation

1:15:44

is calm the meditation app by the way, which

1:15:46

is Sam Apparently got

1:15:48

one mines moonly app moon phases and signs.

1:15:50

Yeah, what is it saying about us? That's what

1:15:52

I want to know But now more

1:15:54

and more people have started to see the you know,

1:15:56

those suggestions in their search page

1:15:59

and also

1:15:59

Some of those suggestions are marked ad. So

1:16:03

we previously didn't

1:16:04

used to see ads in the search

1:16:07

page, but now some users are starting to see ads actually

1:16:09

appear

1:16:10

in that page.

1:16:11

So that's making us

1:16:14

think, is Google starting to roll out more

1:16:16

services in the Play Store to show

1:16:18

ads on? I wouldn't really be opposed

1:16:20

to it, because it's their storefront. They

1:16:23

can do what they want.

1:16:24

But it's kind of interesting to see this kind

1:16:26

of just pop up. And then it got

1:16:29

silently announced on the

1:16:31

what's new in Google system updates page.

1:16:33

So they actually had a little snippet where

1:16:35

they said this was rolling out to users

1:16:38

on the latest version of the Google Play Store. But

1:16:41

there hasn't been any formal blog post,

1:16:44

hey, we're doing this. Here's our developers and opt

1:16:46

in or whatnot. It's just been kind

1:16:48

of a slow, quiet rollout for now.

1:16:50

I mean, if that ad wasn't there

1:16:53

and I didn't have a whole list

1:16:55

of like previously searched for items,

1:16:58

it would be a blank page. So I guess it's

1:17:01

another screen

1:17:03

to throw ads into. I mean, it

1:17:05

really is a shot in the dark that I'm going to open

1:17:08

this up to search for something and Shazam's going to be

1:17:10

there. And I'm going to go, oh, okay. Oh, fresh Shazam.

1:17:12

Oh, I did want to meditate. Thank you for

1:17:15

the calm. I forgot what I was going to search for.

1:17:17

I'm going to install the Shazam app, you

1:17:19

know, like, but hey.

1:17:22

I can't blame Google for wanting to put

1:17:24

an ad on a screen like that. If it's what they do. It's

1:17:26

their mission statement. Yeah. All

1:17:30

right. Thank you, Michelle, for all of the

1:17:32

news. And now we get to

1:17:34

thank JRR.

1:17:36

We do because our very own JRR

1:17:38

Rayfield has a little tip for us. If

1:17:40

you find that your notifications need to be a little

1:17:42

more

1:17:43

flashy,

1:17:45

but you got first JRR.

1:17:48

Well, hello there. Happy

1:17:50

IO week to one and all. While

1:17:53

we're waiting for Google to give us the good stuff, I

1:17:55

thought it'd be a fine time to think about

1:17:57

an Android 14 edition.

1:17:59

that we're expecting to see take

1:18:02

shape soon. And more important

1:18:04

to think about how you can bring that very same superpower

1:18:07

onto your own phone this minute, no

1:18:10

matter what Android version it's running.

1:18:12

The feature in question is a nifty

1:18:15

new set of options around notifications,

1:18:18

spotted by our dear mutual

1:18:20

pal, Michelle Raman. The

1:18:22

options are all about making notifications more

1:18:25

useful by making sure you never miss

1:18:27

the most important of them.

1:18:29

To that end, they let you tell your phone to flash

1:18:31

a custom colored LED

1:18:33

like light on your screen anytime

1:18:36

a new alert arrives. Or if you

1:18:38

really want to get fancy to have it flash your phone's

1:18:40

back facing camera light to catch your

1:18:43

attention and or give

1:18:45

you an impressively affordable way

1:18:47

to create an on demand rave.

1:18:50

Ether approach could absolutely be

1:18:52

helpful in the right situation. And here's

1:18:54

the really cool part. You don't even need Android 14

1:18:57

to make any of that happen. In fact, you can

1:18:59

create an even more advanced and

1:19:02

customizable version of that exact

1:19:04

same concept on any Android

1:19:06

device this minute,

1:19:08

if you know where to look. We'll start

1:19:10

with the screen flashing because that part's

1:19:12

really easy. The key there is a handy

1:19:14

little app called AOD

1:19:16

Notify. It's one of my favorite Android

1:19:19

enhancing tools and something I rely on

1:19:21

constantly on my own personal devices.

1:19:24

You'll have to make sure you get the right version because

1:19:26

AOD has different apps for different types

1:19:28

of Android phones. But once you get the

1:19:31

right one for your specific phone and

1:19:33

get through the initial setup, you'll be able

1:19:35

to have your screen light up in all sorts

1:19:37

of different ways for different notifications. You

1:19:40

can have incoming notifications from

1:19:42

certain apps create a ring of light around

1:19:45

the camera cut out at the top of your screen, for

1:19:47

instance. Or you can have a small LED

1:19:49

style dot show up in your screen's corner.

1:19:52

You can even set up an unmissable full

1:19:54

screen outline light in any color

1:19:56

and style you like for certain,

1:19:59

especially important.

1:19:59

notifications. Plus,

1:20:02

unlike Android 14's equivalent,

1:20:04

you can actually specify which specific

1:20:07

apps will cause any of those effects to happen.

1:20:10

So for instance, you could have the heavy-duty flashing

1:20:12

happen with something important like Slack or Gmail,

1:20:15

but not with every other alert you get.

1:20:18

And you can pick which color is used for your on-screen

1:20:21

notification lights too, and even let

1:20:23

AOD notify automatically pull

1:20:25

the primary color associated with

1:20:27

each app, so it's super easy

1:20:29

to know at a glance what type of alert

1:20:32

is involved.

1:20:33

Next, if you really want to make sure something

1:20:35

important catches your eye, an app

1:20:37

called Mist Call Reminder

1:20:40

is exactly what you need. It

1:20:42

lets you have your phone's camera flash light

1:20:44

up for incoming notifications. And

1:20:47

not just those from Mist Calls either, despite

1:20:49

what his name implies. Just like

1:20:52

our first tool, this one has tons of options

1:20:54

and customization potential that go

1:20:56

way beyond what Google's got cooking

1:20:59

in Android 14.

1:21:01

So there you have it, a couple of great Android

1:21:03

14-like features to hold you

1:21:05

over while we wait for all

1:21:07

the new Google goodies to land. If

1:21:10

you want even more awesome new stuff

1:21:12

to make your life easier, make sure you're not missing

1:21:15

out on my Android Intelligence newsletter.

1:21:17

It brings you three new things to try every single

1:21:20

Friday, and I'll send you a trio of special

1:21:22

bonus tips as soon as you sign up too.

1:21:24

Just head over to Androidintel.net

1:21:26

slash twit to get in on the action.

1:21:29

That's Androidintel.net slash

1:21:31

twit. A very happy

1:21:34

I-O week to everyone. It's

1:21:36

gonna be an interesting one. I'll

1:21:38

see you soon.

1:21:40

JR, we'll miss seeing

1:21:42

you there. I was just thinking we were kind of, we

1:21:44

were, yes, we were listening because we love the

1:21:47

apps. We were also talking a little bit

1:21:49

about your shirt, which was, which is always a

1:21:51

hot topic. Every time JR,

1:21:53

every time he wears a shirt.

1:21:59

For audio listeners, it was a Google I.O. 2015. Which

1:22:03

was the last I.O. I attended, I believe. Yeah, last

1:22:05

at Moscone Center before Shoreline 2016.

1:22:10

And I'm pretty sure I hung out with JR

1:22:12

at 2015. He probably did

1:22:14

too. You probably wore that shirt on purpose for that very reason.

1:22:17

Yeah, I know. I know. And

1:22:19

just so you know, this was the year where Google's

1:22:21

cardboard, the foldable cardboard,

1:22:24

they got work for phablets on

1:22:26

that. So like, you know, larger phones, I suppose.

1:22:29

The maps

1:22:29

got offline turn by turn navigation.

1:22:32

Ooh, big gear. That was a big

1:22:34

one. Android M Doze mode. I remember Doze mode being

1:22:37

pretty big news. I thought

1:22:39

that was pretty cool back then.

1:22:42

Also during JR's

1:22:45

tip, Burke came in and threw more glitter at us, despite

1:22:47

me saying no. Which could have seen it. Yeah.

1:22:51

I thought it was interesting that he waited for when the show

1:22:53

wasn't happening. Right, yeah. Yeah,

1:22:55

so. Yeah. Anyway, good

1:22:57

times. All right, cool. Oh,

1:23:00

oh, Google preparing to launch Android

1:23:02

Pay and API for seamless tap to

1:23:05

pay transactions. And then only to change the name.

1:23:07

A billion times. And then change the name.

1:23:10

Anyways, that was 2015. JR

1:23:12

Rayfield,

1:23:12

Android Intel dot net, Android

1:23:14

intelligence newsletter, subscribe, JR.

1:23:17

We're going to miss you at Google IO. But thank

1:23:20

you for doing what you do. All

1:23:22

right. We have a couple of items

1:23:24

of feedback coming up next.

1:23:26

Hi, I'm Neil Apeto. I'm the editor in chief

1:23:29

of The Verge and host of Decoder podcast

1:23:31

about big ideas and other problems.

1:23:35

On Decoder, I spend time with major decision makers about

1:23:37

what keeps them up at night, the future of their

1:23:39

companies and my favorite question of

1:23:41

all, what does their org chart look like? Do

1:23:44

you use the word weird for our structure?

1:23:46

I think I would say pretty unique, special.

1:23:49

I'd be more. Yeah, I'd

1:23:51

put a little more positive judgment. This

1:23:54

is a very fun topic for

1:23:56

me because I've studied a lot of organizational

1:23:58

structures. That was New York.

1:23:59

I'm CEO Meredith Copit-Levian and Airbnb

1:24:02

CEO Brian Chesky. My theory is

1:24:04

that you can get a CEO to talk about their org

1:24:06

charts. You can get them to talk about anything. And

1:24:09

so far it's worked. You can

1:24:11

listen to Decoder and Apple Podcasts, Spotify,

1:24:13

or wherever you listen to podcasts. All

1:24:18

right. AAA at twit.tv, three,

1:24:20

four, seven show AAA. Ron, you've got the first

1:24:22

one. Yes, our first email comes from Hilton

1:24:24

Young from Virginia, good old Hilton, who

1:24:28

wants to see if they can get me to say, Holy cow,

1:24:30

Aptra, smiley emoji. There

1:24:33

you go. I'm not your monkey. I'm not here to perform

1:24:35

for you. He would never say those four words. I would never

1:24:37

say, Holy cow, Aptra. Twice.

1:24:40

Twice, there you go. Anyway,

1:24:43

that's gonna follow me to my grave. So

1:24:46

his actual email says, anyway, your discussion

1:24:48

on Android tablets is interesting. My

1:24:50

first tablet was the Nexus 10 that I got for free

1:24:52

by winning a contest. Oh, that's a good gift.

1:24:55

I used it mostly in a case to watch Twitch

1:24:57

podcasts. There you go. When it died,

1:24:59

I considered buying an iPad, but they were so expensive,

1:25:01

it didn't do everything I wanted it to do. So eventually

1:25:03

I got a Surface Pro, best of both worlds. At

1:25:07

the time, not every video streaming service had apps. It

1:25:09

was simple to just go to the webpage

1:25:11

in the browser. Prior to that, I had an HP

1:25:13

touchpad for years with Android on it. Best $50

1:25:15

tablet ever. Look forward

1:25:18

to hearing how the OnePlus tablet and Pixel tablet

1:25:20

are. Longtime fan from the Eileen Rivera days.

1:25:22

Keep it up. Nice. I

1:25:25

too, I'm

1:25:26

curious how the Pixel tablet is. You

1:25:29

didn't get the OnePlus tablet, did you? No, I

1:25:31

didn't. I mean, if I had gotten

1:25:33

it, you better believe I would have brought it on your show.

1:25:35

I'd be showing it to you. It would be really funny. It's like, no,

1:25:37

yeah, it's all for my desk. It's just sitting in a box. Did

1:25:40

you guys

1:25:40

want to see that? I'm sorry, it's in my back

1:25:42

pocket. I know. At

1:25:44

the end of the show, that would be such a mic drop moment. That

1:25:47

would be great. For long time listeners and viewers

1:25:49

of the show, you might remember that I used to measure how

1:25:51

good a tablet was by whether it could fit in my

1:25:54

pocket. That's all the total. The

1:25:56

Nexus 7 was perfectly. Was the only one that actually

1:25:58

qualified. It was perfect.

1:25:59

I believe I got up on camera and like put it

1:26:02

in my back pocket. You can't

1:26:04

do that with the pixel 10, but yeah, I know I'm very curious to you.

1:26:06

And, and, and that's the thing is that like

1:26:08

tablets tend to be media,

1:26:10

media device seems to be the most

1:26:13

common usage of tablet. You know,

1:26:15

like, back in the day, I used to take my tablet

1:26:17

to the gym to watch TV while I was on the elliptical or running

1:26:19

it without, right? You know, and like, or I honestly,

1:26:21

like last night I was on the plane to California

1:26:24

and I brought my tablet to watch the latest episode of succession,

1:26:26

you know, like, meanwhile planes

1:26:28

now have tablets embedded in the bigger

1:26:31

screen. Movies

1:26:33

to watch and everything. But, uh, but yeah, we'll cure

1:26:36

see the pixel tablet can change the game or not. So

1:26:38

I'm very curious about that. And,

1:26:40

and kind

1:26:40

of curious, hopefully, uh,

1:26:42

sometime soon. Hopefully while I have

1:26:44

the pixel tablet, I will also have

1:26:46

the one plus and do a nice side by side comparison.

1:26:50

I know I'm getting the one plus pad sometime in the

1:26:52

next week. So there's that. Will I

1:26:54

get a pixel tablet the next week? I

1:26:56

don't know. Look under your chair tomorrow.

1:26:59

See what's there. JJ

1:27:03

also was it JJ who said this

1:27:05

someone, uh, well, hey, JJ, first

1:27:07

of all, someone in chat said, um, that

1:27:10

the 2015 IO was the last hardware

1:27:12

giveaway year. Is

1:27:15

that true? Wait, what did we get? I think, I think

1:27:17

they've given away like pixel A's pixel

1:27:19

A phones. Yeah. I feel like there

1:27:21

has been some hardware since

1:27:24

then, but though, but those were

1:27:26

the days of hardware extravaganza giveaway.

1:27:29

It was like you, you went and you knew you were

1:27:31

getting like a gift basket full of like

1:27:33

things

1:27:34

and that has really tapered off. So yeah,

1:27:36

I think maybe that was the last year they gave everyone

1:27:39

something, but I know in subsequent years they gave like all

1:27:41

the press you went there like right. Right.

1:27:44

Yeah. Yeah. Because I remember the shoreline 2012 was

1:27:46

the, the skydiving.

1:27:48

Yeah.

1:27:50

You're press, right? You're now

1:27:52

I am. I sorta guess. There

1:27:54

you go. There you go.

1:27:56

I bet you're wrong in my career. You off. I've gone

1:27:58

like the press ride. I would have gotten.

1:29:59

Yes.

1:30:01

I have a Galaxy Tab S5 that

1:30:03

I installed Android Automotive onto

1:30:06

and then I also got the Android Auto

1:30:08

receiver app. So now in my car,

1:30:11

I use Android Auto for my phone on my

1:30:13

tablet. So wirelessly

1:30:15

too. So I don't have a

1:30:18

car with a head unit, Android Automotive head

1:30:20

unit built in, but I have a tablet that runs Android

1:30:23

Automotive and I use that. I'm starting

1:30:25

to get images of those photos of

1:30:27

car drivers in Korea with like the, with

1:30:30

all the tablets and the 15

1:30:32

screens on their other

1:30:34

dash. Wow. So there's

1:30:36

a couple more options for the emailer.

1:30:38

Who wants to do it? I think it was last week, right? Yeah.

1:30:42

It was, um, gotta

1:30:43

get the name in there. Steve.

1:30:46

Steve. Yes. So

1:30:48

there you go, Steve.

1:30:50

Some tips from Tommy and

1:30:52

Michelle.

1:30:54

Don't do what I did. It's not worth it. It's

1:30:56

too complicated.

1:30:58

I mean, I was sold. I was like,

1:31:00

well, I guess if you, you know, if you take

1:31:02

the time to set it all up, it might be worth

1:31:04

it. But it was fun to learn, but it's definitely not

1:31:06

worth it over just buying like one of those

1:31:08

suction cup Android auto things. That's

1:31:11

funny. I mean,

1:31:13

so I did.

1:31:16

So Tommy, I did wear for you, uh,

1:31:18

video viewers can see I'm actually wearing a kettlebell t-shirt

1:31:20

because I did see Tommy's email and I said, I appreciate

1:31:22

that very much. So yeah, I have my Android sweatshirt

1:31:24

and my kettlebell shirt. So these are my, these are the two

1:31:26

halves of my life's like working out and Android

1:31:28

or earlier when, when God here

1:31:31

and when we're like sizing each other

1:31:33

up, they were like, all right,

1:31:35

come on. No, I felt very,

1:31:38

uh, and super fit. So,

1:31:40

but

1:31:40

yeah, and

1:31:43

it's like my, like, we're like workout co

1:31:45

co co cheerleaders or yeah. Co

1:31:47

cheerleaders on Instagram.

1:31:48

So yeah, that's awesome. Meanwhile,

1:31:50

I'll have another bowl of pasta, please. Pass

1:31:53

is important part. You got to fuel

1:31:55

up. We're going to get a car

1:31:57

blow before I start the runner though. I can't

1:31:59

run. I don't run well,

1:32:02

just cause I run, doesn't it? I can't

1:32:04

run at all. I mean, you move your legs and you go places. Yes,

1:32:07

I run multiple half marathons, so

1:32:09

like I've done that. That's great on set. Yeah, I would die,

1:32:11

so you know. I've never done that. You've got that

1:32:13

on us, Ron. Totally. I'm just reading through

1:32:15

all the title recommendations and chats, I'm going to be pretty

1:32:17

good. Yeah.

1:32:19

I think that was- Thank you

1:32:22

all. I'm actually not logged into chat. Dang it.

1:32:24

I couldn't get logged in today. So I'm going to have to have chat

1:32:27

like

1:32:29

re-list them for us after the show is done.

1:32:31

I promise you we'll come up with a good title. You already know the

1:32:33

title, cause you're watching and listening to the show and you saw it

1:32:36

in your podcast. So we downloaded it. See, so you're one

1:32:38

step ahead of me. Close out,

1:32:40

close out. Close out. Okay. The

1:32:42

email.

1:32:43

Yeah, so Tommy for wishing

1:32:45

us a good past, present and future IO,

1:32:48

for giving us a solution to last

1:32:50

week's tablet via

1:32:53

phone casting solution, and for also

1:32:55

just being very kind and calling out my

1:32:57

jacketness. That does not sound right. That

1:33:00

is why Tommy on this very, very

1:33:03

extra special Google IO week with all of us

1:33:05

in studio, that is why you are the email

1:33:08

of- Ta-da-da-da. Ta-da-da-da. Ta-da-da.

1:33:10

Ta-da-da. Excellent. And

1:33:13

with

1:33:13

that, ladies, gentlemen

1:33:16

and germs, we are done. Google

1:33:19

IO has been previewed. Yeah.

1:33:22

Google IO has been briefly previewed.

1:33:24

And many other news items that may or may not have

1:33:27

something to do with Google IO have also been talked

1:33:29

about. Emails have been answered,

1:33:31

and Confetti has been spread

1:33:34

around. What a fun time we've had. Happy

1:33:37

birthday. Thank you. Happy birthday.

1:33:39

Happy birthday to Flo. Wish the Flo

1:33:41

could be here so we can wish her happy birthday in person,

1:33:43

but we will all see her tomorrow. Yep.

1:33:46

And- The birthday celebration doesn't stop after

1:33:48

one day. That's what we learned. Yeah. No. When

1:33:51

your birthday is on the same week as Google

1:33:53

IO. I'm really looking forward to them wishing us both

1:33:55

a happy birthday from the keynote. Like Sundar's

1:33:58

gonna get out there and go before we get started.

1:34:00

We had a couple of birthdays in the audience. Yeah.

1:34:02

You think we don't watch. Who

1:34:05

hears word of all about it? Right. I'm

1:34:09

not overstating it by the way. The audience

1:34:11

would go crazy right now. Right? Yeah,

1:34:13

we'll be good. Right? Totally. Right. Okay,

1:34:17

anyways. All

1:34:19

right. So we are very excited for Google I.O. We

1:34:21

have more to come. Obviously next

1:34:24

week we will be doing a kind of a post-show wrap-up.

1:34:26

Actually as we

1:34:29

have done as a tradition for a very very long

1:34:31

time. Michael Wolfson

1:34:32

will be joining us to do the post

1:34:34

I.O. often he's been on pre-I.O.

1:34:37

but that's because he would be going to I.O. He

1:34:39

says this is the first I.O. He's missed. He's

1:34:41

missing in many years and he

1:34:43

said he's okay with it. He's good. He's accepted

1:34:46

it. So he's going to join us for the post-show

1:34:48

wrap-up

1:34:49

and then again reminder

1:34:52

that we're going to be interviewing Dave

1:34:54

Burke and Samir Samat from the Android

1:34:57

team at Google I.O. tomorrow,

1:34:59

but you will not get that in this all about Android

1:35:01

feed. You will get it in our twit news feed. So go to

1:35:03

twit.tv slash news. That

1:35:05

is our kind of like our breaking news channel

1:35:08

news interviews that sort of stuff subscribe

1:35:10

there or just go there. I guess tomorrow

1:35:13

evening or Thursday morning and

1:35:15

you'll see our interview with them

1:35:17

and we've got more to come. We've got more Googlers

1:35:19

that are going to join in a couple of weeks

1:35:22

for more more kind of context

1:35:24

around a lot of the news that you're going to

1:35:26

hear about tomorrow. So Michelle,

1:35:30

thank you for being here. What do you want to leave people

1:35:32

with? Where should people go to follow all

1:35:34

the crazy news that you're breaking? If

1:35:37

you like every single day you break a bunch of

1:35:39

things. So yeah,

1:35:41

so if you're if you're going to follow Google

1:35:44

I.O. News, I'll be all over it on Twitter

1:35:46

at Michelle Roman. You know, if you're

1:35:48

listening to this before

1:35:49

I.O. obviously or if you're listening to this after

1:35:52

I.O. you can still stop by my Twitter feed where

1:35:54

I'll be covering everything I can

1:35:56

live from the show just like

1:35:59

Ron.

1:36:00

Jason and Wynn.

1:36:01

Yeah, do it our best. Thank you,

1:36:03

Michelle. What about

1:36:06

you? Yeah, I

1:36:08

usually am an Android dev. You can find most

1:36:10

of my technical content usually on

1:36:13

randomlytyping.com. You can find me

1:36:15

on the interwebs at QueenCodeMonkey if you're

1:36:17

interested in like the fitness stuff

1:36:19

mentioned. I post a lot of stuff on Instagram.com

1:36:23

slash QueenCodeMonkey where I get

1:36:26

coached by my dude AJ, Docs Fitness

1:36:28

in New Jersey. Hello. Okay. And

1:36:30

yeah, just find me there and so

1:36:33

happy to be in studio.

1:36:34

I know. It's awesome. It's

1:36:36

a whole different dynamic

1:36:38

when we're in studio. It's also

1:36:40

weird to see like, because I know it's

1:36:42

weird because like you're there. I have to remember I'm looking

1:36:45

at you and you're here. So

1:36:49

you could follow me on Twitter and on Instagram.

1:36:52

I'm still at RonXO. I'm not

1:36:54

breaking anything. I'm like, Michelle. So

1:36:57

everything is still in one piece on my Twitter.

1:37:00

But no, I'm actually super busy and

1:37:02

chasing toddlers. So I don't

1:37:04

post as much, but I will be posting from Google I.O.

1:37:06

So go check out, see what I thought of it tomorrow.

1:37:08

Excellent. Thank you, Ron. Happy birthday.

1:37:11

Happy birthday to Victor

1:37:13

behind the board here in a couple of days anyways.

1:37:16

The man. And

1:37:19

not a happy birthday to Bert because I don't know what his birthday

1:37:21

is, but it's definitely not. Even if it was his birthday, he wouldn't get

1:37:23

a happy birthday. You're absolutely right.

1:37:26

But thank you, Bert. Nonetheless, thanks

1:37:28

to everyone. We had this room filled with

1:37:31

folks here from Twit. You know, how they set up

1:37:33

cameras and Anthony tie.

1:37:36

I mean, who

1:37:38

else?

1:37:38

My mid Lisa was in here for a while. It was quite

1:37:41

the spectacle. It was quite the spectacle.

1:37:44

And I'm sure there will be photos posted to our website

1:37:46

as a result of it. So thanks for everybody for

1:37:49

making us feel super special. Jerry

1:37:51

feel Android Intel dot net slash Twit.

1:37:54

Definitely check that out. Me just

1:37:57

I guess like I'm thinking about like.

1:37:59

How am I going to like, I don't tweet

1:38:02

much anymore. I don't really,

1:38:04

but maybe I will tomorrow tomorrow. Yeah.

1:38:06

Or maybe the discord. There you

1:38:08

go. And you can get in the discord.

1:38:10

Yeah, that's right. Okay. I like where

1:38:13

you're headed here, Ron. Okay. twit.tv

1:38:17

slash club twit. When you go there,

1:38:19

yes, you get access to all of our

1:38:21

shows. No ads. Yes. You get access

1:38:23

to bonus content that we don't

1:38:25

release to people outside of the club. Things like

1:38:27

pre and post show banter, uh, hands

1:38:29

on windows, hands on Mac. Uh,

1:38:32

what is it? Uh, home theater geeks and other are

1:38:34

untitled Linux show. Lots of things. But

1:38:36

what you really want is the members

1:38:39

only discord, because if

1:38:40

you do that, then tomorrow while we're at Google

1:38:43

IO,

1:38:44

I'm going to be in the all about Android channel. I'm

1:38:46

going to be live, live discarding. What

1:38:48

is that called? Discord live posting,

1:38:50

live blogging, live blogging and discord. I

1:38:52

think that's a fantastic idea. So anyways,

1:38:54

uh, that's what I'll be doing from

1:38:57

there. And, uh, twit.tv slash club,

1:38:59

twit join $7 a month. We

1:39:01

would love to have you. Uh, it helps keep

1:39:03

the lights on after all. Thank

1:39:05

you so much for watching and listening

1:39:07

and putting up with us and our crazy antics

1:39:10

as we are all in studio for one, possibly

1:39:13

one time ever.

1:39:14

All four of us in the studio together. Um,

1:39:17

twit.tv slash a A is where you can go

1:39:19

to subscribe to this show, everything you need

1:39:21

to know. And I guarantee you that header image is going to

1:39:23

be changed out after today. Uh,

1:39:25

so, you know, check back and see what it turns into,

1:39:28

but subscribe and you'll get all of our

1:39:30

episodes and, uh, we thank

1:39:32

you for watching and listening. We'll see you next time on

1:39:34

all about Android. Bye buddy. Google IO.

1:39:42

And hooray.

1:39:42

Okay. Hey there,

1:39:45

Scott Wilkinson here. In case you hadn't

1:39:47

heard home theater geeks is back

1:39:50

each week. I bring you the latest audio

1:39:52

video news, tips and tricks

1:39:54

to get the most out of your AV system, product

1:39:57

reviews, and more.

1:39:59

You can enjoy Home Theater Geeks only

1:40:02

if you're a member of Club Twit, which

1:40:04

costs $7 a month. Or you

1:40:07

can subscribe to Home Theater Geeks by

1:40:09

itself for only $2.99 a month. I

1:40:12

hope you'll join me for a weekly dose

1:40:14

of Home Theater Geekadoo.

1:40:20

Android.