ywoski

Oh geez, that's an entirely different can of worms that isn't related to the monorepo.

Most products at Google are not dropped because the monorepo makes it difficult for them to support - and I'm not sure how it would or how you got to that association. Also, plenty of products that are killed are not in the monorepo.

They are usually dropped due to a mix of things, but a big part is just better product management.

Almost. We had a UI library on Android that was stuck on an alpha version of the library for three or so years after the library had shipped.

Upgrading the library broke many tests across the org, and no one wanted to own going in and getting each team to fix it. Eventually, the library had a v2 release, and people started to care about being able to use it.

Ultimately, they just forked the current release and appended a v2 to the package name.

Not the norm, but it happens. The monorepo works for Google, but I wouldn't recommend it for most organizations; we have a ton of custom tooling and headcount to keep things running smoothly.

From the mobile side, it makes it super easy for us to share code across the 50+ apps we have, manage vulnerabilities quicker, and collaborate easily across teams.

TikTok is the name of Google's internal (and convoluted) framework for first party Android apps.

They have some internal libraries developers are supposed to use when handling intents that prevent common mistakes developers might make.

Hi Nicholas , Long time!

Yeah Cruise definitely seems to be moving with safety in mind. Props to the team for this milestone!

Listing 5 items and having vs between them clearly puts them against each other.

And that seems more like a marketing issue, under the hood there actually are differences between macOS and iOS. Catalyst hopes to fix this but it's still pretty rocky imho. Google also did something similar with running Android apps on chromeOS.

iPadOS, iOS and watchOS would be the same for Android phones, tablets and watches. So it doesn't seem like a fair comparison here.

I don't see Apple being big in the web space as much so Google really wanting to push PWAs vs Apple's stance is different. Although Apple seems to be fine with PWAs to a degree, so it would be the same for them too.

Apple really doesn't seem to care to support things outside their ecosystem (it doesn't benefit them like it does Google.) So you probably aren't going to see a multiplatform library from them.

I like this design but I wonder how many apps will actually adopt this. I don't see Facebook, Instagram, Pinterest, Snapchat, etc rushing to adopt this (it largely conflicts with their own design language.)

Also a lot of smaller companies rarely update theming for apps so I don't see them doing it either (I doubt my banking app cares.) I have a feeling few apps will actually update to this leading to fragmentation. Anyways we will see.

Eh kind of but you are mixing the OS with the application framework to make it look like more things exist.

PWA for ChromeOS, Flutter for Fuchsia (but yes it is multi-platform), JetPack Compose for Android (but does have some multi-platform stuff coming out).

So really it's three.

PWAs, Flutter, and Jetpack Compose.

Of which I think PWAs rightly exist alongside a native solution.

Flutter is sort of the odd one out and not sure where it will be long term. Although it's becoming more clear Fuchsia is probably going to be for IoT devices, so I could see Flutter being used as an application framework for them (which IMHO makes a lot of sense.)