Google IO 2016 Highlights

Last month Google held it’s annual Google IO conference. Not really a surprise but it was chock full off conversation and AI based tech which is all the buzz of late.

Three bits in particular stood out for me.

The first is the demo of Allo, their new chat app. The app itself wasn’t particularly groundbreaking but the embedding of their new digital assistant tech (the Google assistant) is very interesting and it really shows where Google thinks things are going. The fact that 3rd parties will be able to hook into the Google assistant ecosystem, as shown with the Open Table integration at the end of the clip, should have organizations interested in conversational commerce buzzing.

Here is the clip:

The second demo was for Google Home, their answer to the Amazon Echo. I suspect there was a bit of hand waving going on in this video clip but having done some work with the Echo, everything they demo should be doable. The one thing that did not ring true for me was how it was identifying specific family members so that it could perform actions in the context of their data and “profile”:

The last thing that stood out for me was the new Android Instant apps tech. It basically allows a sliver of your app to be downloaded and run, which means that your users don’t have to first install your app. They demoed apps been launched from web searches and from an NFC tag scan. Really starts to blur the difference between an app and a web page. Here is the clip from the key node:

All in all, some pretty interesting tech will be hitting us shortly.

How to create a private key for signing Android apps

To create a private key to sign your Android apps with, you need to run the keytool command (installed when you install a Java development kit) as follows.

keytool -genkey -v -keystore myandroid.keystore -alias myandroidkey -keyalg RSA -keysize 2048 -validity 10000 -dname "O=Acme Ltd"

Replace Acme Ltd with your company name.

When the tool runs it will prompt you for a password and then generate a file called myandroid.keystore. You will need this file, your password and the key’s alias (myandroidkey in this example) to sign your app.

To see the details of your key use the following command:

keytool -list -v -keystore myandroid.keystore

For more information see the Link to Signing Your Application page page in the Android developer’s documentation.