Google Assistant

google-lays-off-“hundreds”-more-employees,-strips-google-assistant-features

Google lays off “hundreds” more employees, strips Google Assistant features

Hey Google, it’s been nice knowing you —

Google’s layoffs hit hardware, the Google Assistant, and even the AR division.

Google is looking pretty dilapidated these days.

Enlarge / Google is looking pretty dilapidated these days.

Aurich Lawson

Google’s cost-cutters are still working overtime, with more layoffs this week and cuts to Google Assistant functionality.

First up, The New York Times reports Google laid off “hundreds” of workers in “several divisions” on Wednesday. Core engineering, the Google Assistant, and the hardware division all lost people. The report says that “Google said that most of the hardware cuts affected a team working on augmented reality.” AR cuts are eyebrow-raising since that’s quickly going to be one of the highest-profile teams at the company this year, as Google, Samsung, and Qualcomm team up to battle the Apple Vision Pro. FitBit was apparently also a big loser, with 9to5Google reporting that Fitbit co-founders James Park and Eric Friedman and “other Fitbit leaders” have left Google.

Over the years, Google has rarely laid off workers, but since January of last year, a new focus on cost-cutting has made layoffs a regular occurrence at Google. The purge started with an announcement of 12,000 layoffs in January, which took until at least March to complete. Then there were more layoffs at Alphabet companies Waymo and Everyday Robots in March, Waze layoffs in June, recruiting layoffs in September, Google News cuts in October, and now these layoffs in January. There are rumors of more layoffs happening this month, too, focusing on the ad sales division.

Next up is a Google blog post titled “Changes we’re making to Google Assistant,” which details 17 features that are being removed from Google’s struggling voice assistant. Google says these “underutilized” features will be “no longer supported” at some point in the future, with shutdown warnings coming on January 26.

The Google Search bar, which (depending on your local anti-trust laws) is contractually obligated to be on the front of an Android phone, will no longer bring up the Google Assistant.

The Google Search bar, which (depending on your local anti-trust laws) is contractually obligated to be on the front of an Android phone, will no longer bring up the Google Assistant.

Ron Amadeo

The full list of cut features—it’s a big list—is here. The biggest and most ominous news is that the Google Assistant is losing its premium, default spot on the homepage of all Android devices. The microphone button in the Google Search bar used to bring up the Assistant, but now it will only send your voice input directly to Google Search. You’ll still be able to bring up the Assistant using what are basically secret, invisible shortcuts, like saying “Hey Google” or long-pressing on the home button (if you have gesture navigation turned off), but this is a massive change that means the Assistant will no longer be front-and-center on Android phones.

The Assistant is from the Google Search division and was once considered the future of the company and the future of Google Search. If the Assistant couldn’t answer a question, it would just forward you to Google Search, so this change makes the microphone button a lot less useful. It also highlights the ongoing death of the Google Assistant, which has fallen out of favor at the company. (Android users unhappy about this should download the Google Assistant shortcut app.) Here are some of the features being removed:

  • The Google Assistant’s messaging feature, where voice messages would be sent to any phones and tablets in your family group, is dead. Audio messages will still play on local network speakers, but Google is no longer sending notifications across the Internet to Android and iOS.
  • Google Play Books voice support sounds like it will be totally gone. You can still use generic audio-cast features from another device, but you can’t ask the Assistant to play an audiobook anymore.
  • Setting music alarms—not regular alarms—is dead. Controlling a stopwatch—not normal timer support—is also gone.
  • The death of Fitbit under Google continues with the removal of voice-control activities for the Fitbit Sense and Versa 3. A wrist-based Google Assistant is exclusive to the Pixel Watch in Google’s lineup, though that probably won’t last long either.

One problem with all voice assistants is that there’s no good way to communicate the hundreds of possible voice commands to users, so there’s a good chance you didn’t know most of these exist. Figuring out whether any given Google Assistant feature is available on a phone, speaker, smart display, car, TV, or headphones is also an impossible task. Some cut features I have personally never heard of include “managing your cookbook”—apparently there is a “Google Cookbook” of saved recipes available on smart displays and nowhere else. Google says it was somehow previously possible to “send a payment, make a reservation, or post to social media” by voice on some platforms. When I ask the Google Assistant to do any of those things right now, it says “I don’t know, but I found these results on search.” I’m not even sure where you would enter payment details for the Assistant to have access to (was this some iteration of Google Pay?), or how you would connect social media accounts.

It increasingly sounds like it’s time to pick out a nice plot of land in the Google Graveyard for the Assistant. On one hand, Google seems to want to shut this one down in exchange for “Pixie,” a voice assistant that will be exclusive to Pixel devices, starting with the Pixel 9. On the other hand, just in October, Google promised the Assistant would be getting Bard generative-AI integration, so none of this lines up perfectly. It’s odd to be removing the Assistant from Android home screens, stripping it of features, planning a big revamp, and also planning a direct competitor.

Google lays off “hundreds” more employees, strips Google Assistant features Read More »

android-users-could-soon-replace-google-assistant-with-chatgpt

Android users could soon replace Google Assistant with ChatGPT

Who’s going to make a ChatGPT speaker? —

The Android ChatGPT app is working on support for Android’s assistant APIs.

Android users could soon replace Google Assistant with ChatGPT

Aurich Lawson | Getty Images

Hey Android users, are you tired of Google’s neglect of Google Assistant? Well, one of Google’s biggest rivals, OpenAI’s ChatGPT, is apparently coming for the premium phone space occupied by Google’s voice assistant. Mishaal Rahman at Android Authority found that the ChatGPT app is working on support for Android’s voice assistant APIs and a system-wide overlay UI. If the company rolls out this feature, users could set the ChatGPT app as the system-wide assistant app, allowing it to pop up anywhere in Android and respond to user questions. ChatGPT started as a text-only generative AI but received voice and image input capabilities in September.

Usually, it’s the Google Assistant with system-wide availability in Android, but that’s not special home cooking from Google—it all happens via public APIs that technically any app can plug into. You can only have one app enabled as the system-wide “Default Assistant App,” and beyond the initial setting, the user always has to change it manually. The assistant APIs are designed to be powerful, keeping some parts of the app running 24/7 no matter where you are. Being the default Assistant app enables launching the app via the power button or a gesture, and the assist app can read the current screen text and images for processing.

The Default Assistant App settings.

Enlarge / The Default Assistant App settings.

Ron Amadeo

If some Android manufacturer signed a deal with ChatGPT and included it as a bundled system application, ChatGPT could even use an always-on voice hotword, where saying something like “Hey, ChatGPT” would launch the app even when the screen is off. System apps get more permissions than normal apps, though, and an always-on hotword is locked behind these system app permissions, so ChatGPT would need to sign a distribution deal with some Android manufacturer. Given the red-hot popularity of ChatGPT, though, I’m sure a few would sign up if it were offered.

Rahman found that ChatGPT version 1.2023.352, released last month, included a new activity named “com.openai.voice.assistant.AssistantActivity.” He managed to turn on the normally disabled feature that revealed ChatGPT’s new overlay API. This is the usual semi-transparent spinning orb UI that voice assistants use, although Rahman couldn’t get it to respond to a voice command just yet. This is all half-broken and under development, so it might never see a final release, but companies usually release the features they’re working on.

Of course, the problem with any of these third-party voice assistant apps as a Google Assistant replacement is that they don’t run a serious app ecosystem. As with Bixby and Alexa, there are no good apps to host your notes, reminders, calendar entries, shopping list items, or any other input-based functions you might want to do. As a replacement for Google Search, though, where you ask it a question and get an answer, it would probably be a decent alternative.

Google has neglected Google Assistant for years, but with the rise of generative AI, it’s working on revamping Assistant with some Google Bard smarts. It’s also reportedly working on a different assistant, “Pixie,” which would apparently launch with the Pixel 9, but that will be near the end of 2024.

Android users could soon replace Google Assistant with ChatGPT Read More »

the-pixel-9-might-come-with-exclusive-“pixie”-ai-assistant

The Pixel 9 might come with exclusive “Pixie” AI assistant

Things are looking dark for Google Assistant —

What will happen to the Google Assistant when the new AI assistant comes out?

The Pixel 9 might come with exclusive “Pixie” AI assistant

Move over Google Assistant, Google is apparently working on a new AI. The Information reports that Google is working on a new “Pixie” AI assistant that will be exclusive to Pixel devices. Pixie will reportedly be powered by Google’s new “Gemini” AI model. The report says Pixie would launch first on the Pixel 9: “Eventually, Google wants to bring the features to its lower-end phones and devices like its watch.”

So far, Google and Amazon reportedly have plans to reboot their voice assistants with the new wave of large language models. Both are only at the rumor stage, so neither company has promoted how a large language model will help a voice assistant. Today, the typical complaints are usually around voice recognition accuracy and response time, which a language model doesn’t seem like it would help with. Presumably, large language models would help allow longer-form, more in-depth responses to questions, but whether consumers want to hear a synthetic robot voice read out a paragraph-long response is something the market will figure out.

Another feature listed in the report is that Google might build “glasses that could make use of the AI’s ability to recognize the objects a wearer is seeing.” Between Google Glass and Project Iris, Google has started and stopped a lot of eyewear projects.

The move shows how Google has changed its thinking around AI assistants over the past decade. It used to view Google Assistant as the future of Google Search, so it wanted Assistant to be available everywhere. Google Assistant was a good product for a time, available on all Android phones, on iOS via the Google app, and via lots of purpose-built hardware like the Google Home/Nest Audio speakers and smart displays. Google Assistant never made any money, though. The hardware was all sold at cost, the software was given away to partners, and the ongoing costs of voice processing piled up. There was never any additional revenue to pay for the Google Assistant in the form of ads. Amazon is in the same boat with its Alexa: No one has figured out how to make voice assistants profitable.

Since Google Assistant is a money pit, The Information previously reported that Google plans to “invest less in developing its Google Assistant voice-assisted search for cars and for devices not made by Google, including TVs, headphones, smart-home speakers, smart glasses and smartwatches that use Google’s Wear.” The idea is for Google to double down on its own hardware, which, according to the previous report, is what Google thinks will provide the best protection against regulators threatening the company’s search deals on the iPhone and Android partner devices. “We’re going to take on the iPhone” is apparently the hard-to-believe mindset at Google right now, according to this report.

Making the next-gen Assistant exclusive to the Pixel 9 would fall into this category. Presumably, the ongoing money problem would then be solved, or at least accounted for, in the sales of phone hardware. The current Google Assistant was originally exclusive to the first Pixel and spread out to Google’s partners, but The Information’s reporting makes it seem like that isn’t the plan this time (though that could always change). No one knows what will happen to Google AI assistant No. 1 (Google Assistant) when AI assistant No. 2 launches, but killing it off sounds like a likely outcome. It would also be a way to cut costs and get Google Assistant off people’s devices.

The problem with doubling down on hardware is that Google Hardware is a small division that has previously been unable to support this kind of ambition. Going back to that quote about third-party devices, there are no Google cars, TVs, or smart glasses (the report says smart glasses are being worked on, though). Some years, Google’s existing hardware isn’t necessarily very good. In other years, long times will go by when Google doesn’t update some product lines, leaving them for dead (laptops, tablets). Google Hardware is also usually only available in about 13 countries, which is a tiny sliver of the world. Being on third-party devices protects you from all this. Previously, Google’s strength was the availability of its ecosystem, and you give that up if you make everything exclusive to your hardware.

The Pixel 9 might come with exclusive “Pixie” AI assistant Read More »

google-is-sending-out-mysterious-emails-warning-of-a-problem-with-the-google-assistant

Google is sending out mysterious emails warning of a problem with the Google Assistant

internal/modules/cjs/loader.js: 905 throw err; ^ Error: Cannot find module ‘puppeteer’ Require stack: – /home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js: 902: 15) at Function.Module._load (internal/modules/cjs/loader.js: 746: 27) at Module.require (internal/modules/cjs/loader.js: 974: 19) at require (internal/modules/cjs/helpers.js: 101: 18) at Object. (/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js:2: 19) at Module._compile (internal/modules/cjs/loader.js: 1085: 14) at Object.Module._extensions..js (internal/modules/cjs/loader.js: 1114: 10) at Module.load (internal/modules/cjs/loader.js: 950: 32) at Function.Module._load (internal/modules/cjs/loader.js: 790: 12) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js: 75: 12) code: ‘MODULE_NOT_FOUND’, requireStack: [ ‘/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js’ ]

Google is sending out mysterious emails warning of a problem with the Google Assistant Read More »

20-types-of-android-apps-you-can-replace-with-the-google-app

20 Types of Android Apps You Can Replace With the Google App

internal/modules/cjs/loader.js: 905 throw err; ^ Error: Cannot find module ‘puppeteer’ Require stack: – /home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js: 902: 15) at Function.Module._load (internal/modules/cjs/loader.js: 746: 27) at Module.require (internal/modules/cjs/loader.js: 974: 19) at require (internal/modules/cjs/helpers.js: 101: 18) at Object. (/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js:2: 19) at Module._compile (internal/modules/cjs/loader.js: 1085: 14) at Object.Module._extensions..js (internal/modules/cjs/loader.js: 1114: 10) at Module.load (internal/modules/cjs/loader.js: 950: 32) at Function.Module._load (internal/modules/cjs/loader.js: 790: 12) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js: 75: 12) code: ‘MODULE_NOT_FOUND’, requireStack: [ ‘/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js’ ]

20 Types of Android Apps You Can Replace With the Google App Read More »

google-is-done-with-duplex-on-the-web

Google is done with Duplex on the Web

internal/modules/cjs/loader.js: 905 throw err; ^ Error: Cannot find module ‘puppeteer’ Require stack: – /home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js: 902: 15) at Function.Module._load (internal/modules/cjs/loader.js: 746: 27) at Module.require (internal/modules/cjs/loader.js: 974: 19) at require (internal/modules/cjs/helpers.js: 101: 18) at Object. (/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js:2: 19) at Module._compile (internal/modules/cjs/loader.js: 1085: 14) at Object.Module._extensions..js (internal/modules/cjs/loader.js: 1114: 10) at Module.load (internal/modules/cjs/loader.js: 950: 32) at Function.Module._load (internal/modules/cjs/loader.js: 790: 12) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js: 75: 12) code: ‘MODULE_NOT_FOUND’, requireStack: [ ‘/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js’ ]

Google is done with Duplex on the Web Read More »