A few weeks after Google’s annual developer conference, many of us have seen a fascinating nonetheless frightening videos of Google Assistant phoning a restaurant to make a reservation.
What’s a 411 on Google I/O?
Google I/O (or simply I/O) is one of Google’s outrageous developer conferences, that brings together developers from all over a creation and gives them a initial demeanour during Google’s latest developer products and platforms. Basically, it’s usually a large festival for all things Google!
Interesting things learned
From a consumer-facing perspective, they showed off Google Duplex, whereby Google’s AI voice-generated partner creates phone calls on your behalf, practically “faking” tellurian interaction. we don’t consider it’s entirely baked yet, though positively hints during where we’re streamer in a future. It really lifted some engaging reliable questions about a inlet of AI.
From a developer perspective, and one of a categorical reasons we went, I/O addressed a few engaging topics. These enclosed a Polymer 3.0 launch, that represented elementary though critical stairs brazen for a Polymer Project (and a Web height as a whole).
There were a whole garland of talks on Progressive Web Apps (PWA), including new tooling, and engaging and divulgence information on trends with PWA. Finally, there was a lot on appurtenance learning!
Can we give a discerning appurtenance training update?
Google announced ML Kit, that fundamentally cuts opposite a whole garland of a program offerings on Android and Web. This is to try and make it easier to entrance common appurtenance training information tasks, such as picture and debate recognition, among other things. Essentially, it becomes a lot easier to do really worldly work but wanting a PhD in appurtenance learning.
All a talks were live-streamed and are accessible online. Which were some of your favourites?
I indeed have 3 that we would recommend:
1. The state of a Web union. It was really judicious to see how things fit together on a Web.
2. The Polymer 3.0 roadmap. It talked about a new Polymer and where they are, together with deliberating where they are with perplexing to expostulate a Web platform.
3. Ewa Gasperowicz and Addy Osmani articulate about a basics of Web performance. They introduced a Guess.js framework.
What was your comprehensive favourite partial of a whole event?
Easy answer. Everybody knows it is a large festival with thousands of people everywhere. While it was easy to get held adult in bigger and busier areas, a many extraordinary tools were how they put so most courtesy into tiny details. There were graffiti walls with #IO18 logos, small Android robots pushing around with selfie sticks, string candy machines in a dilemma of a pointless room and even Android sumo wrestling! There were domes showcasing things built with Google products, and my favourite was a Internet of things (IOT) one. It had robotic flowers that would follow your face as if your face was a sun, as good as flowers that altered colour formed on your facial expressions, both regulating a ‘Android Things’ appurtenance training capabilities. So, for me, it was all about a small things that could so simply go unnoticed.
Any recommendation for destiny I/O attendees?
1. For my South African friends, zero prepares we for a 27-hour moody and a jet-lag that follows!
2. When during Google’s Mountain View headquarters, don’t try and “borrow” a Google campus GBike to expostulate around. It’s for Google employees usually and we will be chased by security. But, this is, of course, what a small birdie told me; I’m innocent, we promise!