In contrast Google's AI plans give you at least three seperate pools of token usage limits: Gemini App + Antigravity/Other Code Assist tools like Android Studio + AI Studio free usage limits.

Google limit the context of where you can use their tokens but in exchange they give you substantially more.

Odd choice since it strongly undermines the stated purpose of the rebrand in the first place: to break it away from the Tensorflow brand and emphasise it being model/framework agnostic. Working with ".tflite" files more or less immortalises what they're trying to get away from.

Would've made more sense to bite the bullet and launch with a ".litert" format which is identical to ".tflite", but continue to work with the later. That would remove the conceptual integrity issue without breaking any compatibility.

Dart has survived this long so that doesn't seem on the cards.

In a slight shift from how Inbox was characterized at launch, Bank says it now amounts to an experimental test bed for future Gmail features. “Inbox is the next-gen, early adopter version, whereas Gmail is the flagship that will eventually get the best new features,” according to Bank.

https://www.theverge.com/2018/4/25/17277360/gmail-redesign-l...

There's "Voice Search", typing into the Google search box with your voice.

VS Assistant, a Google's chatbot interface.

Probably completely unrelated since Nest doesn't even support Google's Brillo/Weave. They're going forward with their own "Nest Weave" which despite the name is a completely separate platform/ecosystem from Google's stuff.

Wouldn't be surprised if Homekit support is actually on the cards but it's stuck in their super slow release cycle.

I think it's because "Google" aren't involved at all. Google has it's own approach to IOT called Brillo/Weave that they're focused on. Nest is doing its own isolated thing.

This backfired because what people made the natural inference that the purpose of the former was to force use of the later when the opposite was what Google was aiming for. The purpose of the social network was to promote the unified login, but instead it poisoned the well.

New way: Concept of a "Google+ account" has been folded into the main Google Account as a new cross-service "About Me" account https://aboutme.google.com/ . Google+ (Social Network) is now just a client of the former, so the G+ website is shedding all the features related to its old dual system integrator role.

That's what I can make out, anyway.

Doesn't seem correct: https://source.android.com/devices/tech/security/overview/ke...

Going by how closely this matches the leaks, I think the onHub actually is running Brillo. They've just chosen not to mention it just yet.

We may also use personal information for internal purposes such as auditing, data analysis, and research to improve Apple’s products, services, and customer communications.

https://www.apple.com/legal/privacy/en-ww/

No time limit specified = No time limit

"Google Wallet stores your credit and debit cards on secure servers and encrypts your payment information with industry-standard SSL (secure socket layer) technology. Your full credit and debit card information is never shown in the app and won't be shared with the merchant. In addition, access to Google Wallet is protected by password or PIN. We also recommend locking your phone with a passcode for additional security."

"Your actual credit card number is not stored. Only the Google Wallet Virtual Card is stored, and Android's native access policies prevent malicious applications from obtaining the data. Even if the data is compromised, Wallet uses dynamically rotating credentials that change with each transaction and are usable for a single payment only. Finally, all transactions are monitored in real-time with Google’s risk and fraud detection systems."

https://www.google.com/wallet/faq.html#tab=faq-security

Keep in mind "Tokenization" has existed in the NFC industry for years, the only thing which changed last year is that the EMV standards body agreed and released a standardized way to do it in March 2014. Apple Pay is a branded solution over that.

So what it really boils down to is whether or not you take Google's word for it that their independent solution is secure. If not, you owe it to yourself to not be using a Google Android phone in the first place.

I think its more nuanced: In-line maps are a better search result to location queries than a plain blue link, but to some degree the only way to offer that UX is to control that functionality from the ground up. Explicit integration comes with reliability/speed/technical costs while implicit integration comes with fair use/scraping costs.

While search boosts the integrated properties (Maps, News, Finance etc) much of the value to Google may actually be the reverse: integrated verticals give people less reason to switch away from Google's generalized Search to more specialized, domain-specific search engine.

There's an argument to be made that there's utility in a Jack-of-all trades engine.

It doesn't have to feel abandoned just because its niche.