The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,638 other followers

Archive for the ‘Google AI’ Category

Quick Intro Into Actions on Google | Grokking Android

Posted by jpluimers on 2019/01/30

Hopefully by now the Google Assistant and Google Home have made their way into the Dutch language. If so, then it’s time for me

[WayBackQuick Intro Into Actions on Google | Grokking Android: Find out which options exist to develop apps for the Google Assistant with Actions on Google and to bring the Assistant to devices with the Assistant SDK.

–jeroen

 

Posted in Android, Android Devices, Development, Google, Google AI, Google Assistant, GoogleHome, Mobile Development, Software Development | Leave a Comment »

AI in Voice Assistants: I’m not impressed

Posted by jpluimers on 2017/10/06

I started thinking about writing this post way before [WayBack] When +Google Assistant gets a mind of their own… – Jeroen Wiert Pluimers – Google+.

Though I’ll focus on Google Assistant, the competition (Alexa, Cortana, Siri) have about the same level of incompetence.

Though living in The Netherlands, I use the English version of Google Assistant as it won’t be available in the foreseeable future: [WayBack] Google Assistant in het Nederlands voorlopig toekomstmuziek.

This means that I cannot use Dutch words for destinations, but find English ones.

  • This fails: navigate to Schiphol trainstation
  • This works: navigate to Amsterdam Airport Arrivals

The odd thing is that after switching phones, the latter wants to perform this navigation by public traffic, whereas my former phone it would default to navigation for driving by car.

Basically the only interactions that work sort of OK are calling persons and navigating to places.

Appointments

  • what's my next appointment succeeds
  • what's my current appointment (in case you are late, for instance because of traffic conditions) fails

Calling persons

This allows for aliases to persons like my wife, my brother and my mother. But often it:

  • forgets about an alias asking who that alias is for
  • asks for confirmation of an alias
  • totally misses the alias (so when asking to call my wife mobile, it sometimes presents search results, for instance on “How to spy on my wife’s calls tracking for free”)

After defining these aliases, these actions usually work OK:

  • call my brother mobile
  • call my mother at home

Navigation to places

Contrary to calling, where you can define many aliases, you can only define 2 navigation aliases: home and work. Which means these all fail:

  • navigate to my brother at work
  • navigate to my mother at home

Heck, even the simple variations fail:

  • navigate to my brother
  • navigate to my mother

A cool feature would be navigate to my next appointment, but that fails too. No surprise though, as the simpler navigation commands fail.

The best way I found to navigate is to – just before you leave – search on Google Maps in your browser for the route, then open Navigation on your phone (this presumes they use the same account).

Also, since switching phones, I have to indicate how I want to navigate:

  • navigate home by car
  • navigate to Amsterdam Airport Arrivals by car

Stuff that hardly works

Starting applications is a pain.

Examples that work

  • start pokemon go

These work unreliably:

  • start navigation sometimes opens the map, but at other times asks where to navigate to

These fail at all:

  • start dialer (opens a Google search, but fails to start the stock Android Dialer App)
  • start ex-dialer (my dialer of choice: ExDialer)
  • start player FM (fails to locate Player.FM)

Conclusion so far

It is far from intuitive what kinds of phrases will work, sometimes work or will fail.

I could do a search for how to better phrase my requests, but average users won’t

The Google Voice Assistant still has a long way to go to become useable.

–jeroen

Posted in Google, Google AI, Power User | 2 Comments »

Cool Google stuff: Trivia Template for the Google Assistant

Posted by jpluimers on 2017/07/11

This is soo cool: [Archive.isTrivia Template to make Google Assistant trivia questionaires.

It reminds me of a project a few years back where we did a similar thing to create automated interviews.

The trivia template tool lets you build apps for the Google Assistant without writing a single line of code.

Source: [WayBackGoogle Assistant Trivia Template – Leon Nicholls – Medium

Via: [WayBack] Trivia Template: Nandini Stocker and I just launched a template tool to create trivia games for the Google Assistant. The template turns your questions and answers from a spreadsheet into a fully functioning game without writing any code… – Leon Nicholls – Google+

–jeroen

Posted in Development, Google, Google AI, Power User, Software Development | Leave a Comment »

Google drawing AI – My first “Quick, Draw!” attempt – Jeroen Wiert Pluimers – Google+

Posted by jpluimers on 2016/11/28

Not your grandma’s QuickDraw, but a one of the new Google AI experiments by their AI research team:

Can a neural network learn to recognize doodles? See how well it does with your drawings and help teach it, just by playing.

Source: Quick, Draw!

On the right is my first “Quick, Draw!” attempt.
Too bad the canoe didn’t work out; parrot and firetruck are pretty hard with either a mouse or a trackpad.

Source: [WayBackMy first Quick Draw attempt – Jeroen Wiert Pluimers – Google+

Other A.I. Experiments (g.co/aiexperiments):

–jeroen

Via:

Posted in Draw!, Google, Google AI, LifeHacker, Power User, Quick | Leave a Comment »

 
%d bloggers like this: