Example 2 requires the use of depth-sensing and heat-sensitive cameras to avoid trivial "show a photo of an authorized user" attacks - that's not really CPU-dependent either.
Example 2 requires the use of depth-sensing and heat-sensitive cameras to avoid trivial "show a photo of an authorized user" attacks - that's not really CPU-dependent either.
You can build basic functionality into a speech bot in Powershell ("PowerShiri, what time is it?" "PowerShiri, what is the weather?") as a weekend project: https://news.ycombinator.com/item?id=11663029
https://myactivity.google.com/item?product=29
(If the Product 29 parameter doesn't work, click on "Item View" in the left and filter by "Voice & Audio".)
Modern speech models are quite big, not so big that you couldn't load it on your desktop, but big enough that you would notice. Couple that wih the fact that search/or a service is going to happen on a server anyways, client side processing doesn't make sense beyond a few functions.
I don't know of any smartphone or similar device that would interpret voice commands locally.
The impressive amount of processing power available on many smartphones today certainly contributes to this being a practical unlock method.
I assume Google encodes the data in something like iSAC [1], requiring 32 kbit/s for good quality speech, so an hour of dictating is 3600 x 32/(8 x 1024) = 14 MB.
[1] https://en.m.wikipedia.org/wiki/Internet_Speech_Audio_Codec