Live data from Hacker News

Speech to Text on iPhone vs. Pixel

twitter.com

1–10 of 131 posts

Re: Speech to Text on iPhone vs. Pixel

#2
Latency matters a lot, and it's one of the least-appreciated aspects of UX design.

I (accidentally) dropped my desktop Linux system into pure console mode the other day and realized how much FASTER it felt just because of the improvement in keyboard latency.

Re: Speech to Text on iPhone vs. Pixel

#4
There are already some novel applications of this. It is extremely useful to use Google's screening service for unknown numbers that might be a call I'm expecting from a new number. I can't recall the last time I actually listened to a voicemail. I know that at least voicemail transcription works elsewhere, and I can't speak to how well, but I do know that on the Pixel, transcription is really quite impressively accurate.

I'm sure it's not much different than the test shown in the twitter post, but I've enjoyed calling myself from another phone and then screening the call and doing my best micro machines guy fast-talking impression just to see how well it really can transcribe conversation at real-time speeds.

Re: Speech to Text on iPhone vs. Pixel

#6

Since I got my Pixel 4, I've found myself using more and more speech to text as... it's just that quick and easy. Every so often, I try to use speech to text on my iPad Pro and I have an experience pretty similar to Poor Michael Geer over here.

+1 The Apple experience is frustrating at best and usually flat out wrong. Especially for use cases it is supposed to be good at like hands free driving where accuracy is paramount to use case's success.

Re: Speech to Text on iPhone vs. Pixel

#7

I basically can't look at my phone screen when doing TTS for full sentences, it does something to derail me and I basically cannot finish a sentence, similar to how DAF trips people up. Am I alone in this? [1] https://en.wikipedia.org/wiki/Delayed_Auditory_Feedback

I love when the "Good Mythical Morning" guys demonstrated the effect for entertainment.

https://www.youtube.com/watch?v=TB2rEddp-Oo

Re: Speech to Text on iPhone vs. Pixel

#8
I'm curious about the privacy policies behind both engines and their development.

Google's gotten an advantage in many fields by simply trampling over user's rights. Apple has been more respectful of user rights, and that's kind of made life harder for them too.

Re: Speech to Text on iPhone vs. Pixel

#9

I'm curious about the privacy policies behind both engines and their development. Google's gotten an advantage in many fields by simply trampling over user's rights. Apple has been more respectful of user rights, and that's kind of made life harder for them too.

Here's my controversial post of the day:

I'm okay with Google trampling on my rights, in exchange for the things it gives. Personalized search results, better ad hoc translation, all of these things work well only because they have my data. And for me, I like these things enough that I'm perfectly okay with the trade.

Re: Speech to Text on iPhone vs. Pixel

#10
post #9

I'm curious about the privacy policies behind both engines and their development. Google's gotten an advantage in many fields by simply trampling over user's rights. Apple has been more respectful of user rights, and that's kind of made life harder for them too.

Here's my controversial post of the day: I'm okay with Google trampling on my rights, in exchange for the things it gives. Personalized search results, better ad hoc translation, all of these things work well only because they have my data. And for me, I like these things enough that I'm perfectly okay with the trade.

In this case however the transcription is done fully offline on device - that is why it is so fast. Yes Google may have trampled on your voicemail data and 411 calls to create a model that works so amazingly well across different accents and languages - but it is forgivable in this case given how good and useful it is!
Post reply on HN