Profile

Cover photo
Wayne Piekarski
Works at Google
Attended University of South Australia
Lives in San Jose, CA
2,496 followers|1,108,875 views
AboutPostsCollectionsPhotosYouTube+1'sReviews

Stream

Wayne Piekarski

Shared publicly  - 
 
Speedbird 1 Cleared For Takeoff

This amazing video from British Airways reflects on the history of commercial aviation, and the people who risked their lives to be pioneers in the sky. I've always been inspired by flying ... humans have always dreamed of it. Now we can go explore the sky and beyond!

Along with the inspiring story, the sound track for this video is perfect, a song called "The Aviators" by Helen Jane Long. http://www.helenjanelong.com/

This is one of my favorite videos ...
https://www.youtube.com/watch?v=XozHLoqwp_4

Enjoy!
3
2
Add a comment...

Wayne Piekarski

Shared publicly  - 
 
I've noticed that a few developers are publishing Android TV apps that require ACCESS_WIFI_STATE permission. This works fine on Android TV devices that are WiFi based, but there are also many Android TV devices that only have Ethernet, and more are coming soon. An app requiring ACCESS_WIFI_STATE will not be available for install to an Ethernet-only device, and you will be losing users by requiring this permission.

Most developers don't need access to WiFi specifics, so you should consider not including this in your AndroidManifest.xml. You can verify your final APK permissions with a command like this, and look for any mention of uses-permission:

aapt dump --values xmltree <your_apk_file> AndroidManifest.xml

You can also see the permissions summarized on Google Play with this URL:
https://play.google.com/store/apps/details?id=<your_package_name>

In general, you should review all the permissions used by your app, and make sure you have a legitimate need for each of them. In some cases, 3rd party libraries can add these during the build process. The less permissions you need, the less friction there is finding compatible devices and getting users to install it. Make sure you think about all devices in the Android ecosystem (phone, tablet, TV, wear) and the different hardware each has or does not have. Remember, a TV typically doesn't provide a GPS, camera, or microphone like a phone.

If you really need a permission, but still want to run on devices that do not support it, you can use this in the manifest and check the result of any API calls:

<uses-feature android:name="android.hardware.wifi" android:required="false" />

See the uses-feature documentation for more information:
https://developer.android.com/guide/topics/manifest/uses-feature-element.html
26
6
Add a comment...

Wayne Piekarski
owner

Discussion  - 
 
I've noticed that a few developers are publishing Android TV apps that require ACCESS_WIFI_STATE permission. This works fine on Android TV devices that are WiFi based, but there are also many Android TV devices that only have Ethernet, and more are coming soon. An app requiring ACCESS_WIFI_STATE will not be available for install to an Ethernet-only device, and you will be losing users by requiring this permission.

Most developers don't need access to WiFi specifics, so you should consider not including this in your AndroidManifest.xml. You can verify your final APK permissions with a command like this, and look for any mention of uses-permission:

aapt dump --values xmltree <your_apk_file> AndroidManifest.xml

You can also see the permissions summarized on Google Play with this URL:
https://play.google.com/store/apps/details?id=<your_package_name>

In general, you should review all the permissions used by your app, and make sure you have a legitimate need for each of them. In some cases, 3rd party libraries can add these during the build process. The less permissions you need, the less friction there is finding compatible devices and getting users to install it. Make sure you think about all devices in the Android ecosystem (phone, tablet, TV, wear) and the different hardware each has or does not have. Remember, a TV typically doesn't provide a GPS, camera, or microphone like a phone.

If you really need a permission, but still want to run on devices that do not support it, you can use this in the manifest and check the result of any API calls:

<uses-feature android:name="android.hardware.wifi" android:required="false" />

See the uses-feature documentation for more information:
https://developer.android.com/guide/topics/manifest/uses-feature-element.html
9
1
Manuel Paunet's profile photoIan Lake's profile photoWayne Piekarski's profile photo
4 comments
 
I'll add these links into the post ...
Add a comment...

Wayne Piekarski
owner

Discussion  - 
 
If you develop an Android TV app that requires a login, you definitely should be considering using Smart Lock. When a user logs in with your app on the phone, the credentials are saved, so when the same user runs your app on Android TV, there is no need to get them to enter the password again. Remember that Android TV devices don't have a keyboard by default, and users are encouraged to have long and complex passwords. So avoiding entering a password is a big win!

According to our case study https://developers.google.com/identity/casestudies/netflix-smartlock-casestudy.pdf, Netflix was able to implement Smart Lock in just a few days, and saw 20% reductions in support volume from members who had sign in problems.

So please visit https://developers.google.com/identity/smartlock-passwords/android/ to learn more, and make your Android TV user's experience so much faster and easier!
Programmatically save and retrieve credentials, and automatically sign users in across devices and websites in Chrome.
16
1
Add a comment...

Wayne Piekarski
owner

Discussion  - 
 
Our developer relations team at Google is responsible for creating the Android TV samples, such as those listed here: https://github.com/googlesamples/?query=androidtv-
https://github.com/googlesamples/?query=leanback-

We are in the process of planning for the creation of new samples that help to show best practices on Android TV. Rather than try to guess what developers need, I'd like to hear from you directly. If you could have any sample created by us, what would it be? Ideally the sample would be generic enough to be used to solve a wide variety of use cases by many developers.

So please share your ideas here, and comment on other ideas, and we will look to see what is popular, and I'll then propose it to the team. We look forward to hearing from you!
18
1
Adam Tentis's profile photoGil Larios's profile photoWayne Piekarski's profile photoPavel Repkin (YoWindow)'s profile photo
16 comments
 
Settings interface and focus management
Add a comment...

Wayne Piekarski
moderator

Design Checklist  - 
 
We just created an updated video so you can learn more about the guidelines and best practices for enabling Google Cast in your app. This video walks through live examples to demonstrate specific concepts for enabling exciting multi-screen and audio experiences.
 
Learn more about guidelines and best practices for enabling Google Cast for your app. In this updated video, we will walk through live examples to demonstrate specific concepts for enabling exciting multi-screen and audio experiences.

Join the discussion in our Google Cast G+ Community: https://g.co/googlecastdev

#GoogleCast
2 comments on original post
3
Add a comment...

Wayne Piekarski
moderator

Announcements  - 
 
Today we are releasing the second developer preview for Android Wear 2.0, and it is available for testing on the official Android emulator, the LG Watch Urbane 2nd Edition LTE, and the Huawei Watch.

The second developer preview includes an update to API level 24, Wearable Drawer enhancements and wrist gestures, as well fixes for a number of bugs you helped us identify. We plan to release additional updates, so please send us your feedback early and often.

We look forward to your feedback on the new Wear 2.0 developer preview. Enjoy!

http://goo.gl/2FQBiU

#AndroidWear
 
New Android Wear Developer Preview 2

Today we are releasing the second developer preview for Android Wear 2.0, which includes new functionality such as API level 24, Wearable Drawer enhancements and wrist gestures, as well fixes for a number of bugs you helped us identify. Throughout the summer, we plan to release additional updates, so please send us your feedback early and often.

http://goo.gl/2FQBiU

#AndroidWear
6 comments on original post
13
Ernest Karchmit's profile photoDavid's profile photoThye Chean Lim's profile photo
14 comments
 
For Android Wear 2, there is a complication for background image. The question is: how do you upload the image to the watch? If not, is there plan to do so in Android Wear app on phone? I am asking this because if there is a plan for uploading image, then I won't spent too much time developing my own solution.
Add a comment...
In their circles
1,192 people
Have them in circles
2,496 people
Michael Meidl's profile photo
HARD RESET's profile photo
Hüseyin Karagöz's profile photo
ryan cheng's profile photo
anselmo maculane's profile photo
Kaarlo Lahtela's profile photo
Libby Chang's profile photo
Barrister Chris's profile photo
Jason Grout's profile photo

Wayne Piekarski

Shared publicly  - 
 
IoT devices are becoming more and more popular, and many are provisioned using a local WiFi access point that does not provide an internet connection. This blog post from +Rich Hyndman explains the various Android APIs that are available to allow your app to control exactly where connections are routed, so you can communicate with your local device while still using the internet.
 
Connecting your App to a Wi-Fi Device

Connecting Android applications to Wi-Fi enabled devices is becoming more and more common with the IoT and the APIs have enhanced over the last couple of Android versions.

http://goo.gl/mfocAa
5 comments on original post
13
3
Add a comment...

Wayne Piekarski

Shared publicly  - 
 
At Google I/O 2016, the ATAP team showed a great demo of Project Ara and their ejectable modules.

Ok Google, Eject The Camera
https://youtu.be/8LO59eN9om4?t=38m12s

These modules will open up all kinds of cool possibilities for future phone accessories!

If you are interested in developing hardware modules for Ara, you should check out their developer page to sign up to express interest: https://atap.google.com/ara/
9
Add a comment...

Wayne Piekarski

Shared publicly  - 
 
I've seen a few postings from Android Wear developers asking about problems with some users having devices where Google Play Services on the Android Wear device is out of date (typically version 8.x instead of 9.x).

You can determine your version on Android Wear by going to Settings ... About ... Versions ... Google Play Services. It should start with a 9, and not 7 or 8. If it is 7 or 8 you have a stuck device.

I'm trying to understand what the cause of this problem is, so we can get it fixed. Most developers don't have the problem on their own devices, but occasionally they are being contacted by users of their apps who are reporting problems. If you hear from a user with a problem, I would like to get a bug report from them so we can analyze and then help fix it.

We need bug reports captured from both the phone and wearable side. So if you have a USB cable and watch cradle, you can run "adb bugreport > phone.txt" with the phone plugged in, and "adb bugreport > wear.txt" with the wearable plugged in. There is also a bug report mechanism which can work over Bluetooth, outlined here: http://www.androidpolice.com/2014/08/27/android-wear-app-update-adds-a-confusing-way-to-report-bugs-to-app-developers-support-for-ambient-light-sensors/

Once you have a bug report, please send them to me directly, do not share them in public since they might have private information in them. Ping me on hangouts and I'll send you my email address. The quicker I get reports, the quicker I can work on getting a solution for this. Thanks!
13
6
Jose Azua (FlyingRhinoCMG)'s profile photoWayne Piekarski's profile photoDirk Vranckaert's profile photoCraig Jarratt's profile photo
5 comments
 
I've been instructing people to press the play services version, seems to work for some even if it takes a day. Also had reports services only updating related to battery. Someone who reset their watch 3 times and on the third it was plugged in which worked. Another says it needed to be over 75% battery.

Others who've had this in the past with older play services have ended up clearing play services cache and uninstalling android wear to get it to updated. Hard to know what was actually sorting it.
Add a comment...

Wayne Piekarski
moderator

Discussion  - 
 
I've seen a few postings from developers here asking about problems with some users having devices where Google Play Services on the Android Wear device is out of date (typically version 8.x instead of 9.x).

You can determine your version on Android Wear by going to Settings ... About ... Versions ... Google Play Services. It should start with a 9, and not 7 or 8. If it is 7 or 8 you have a stuck device.

I'm trying to understand what the cause of this problem is, so we can get it fixed. Most developers don't have the problem on their own devices, but occasionally they are being contacted by users of their apps who are reporting problems. If you hear from a user with a problem, I would like to get a bug report from them so we can analyze and then help fix it.

We need bug reports captured from both the phone and wearable side. So if you have a USB cable and watch cradle, you can run "adb bugreport > phone.txt" with the phone plugged in, and "adb bugreport > wear.txt" with the wearable plugged in. There is also a bug report mechanism which can work over Bluetooth, outlined here: http://www.androidpolice.com/2014/08/27/android-wear-app-update-adds-a-confusing-way-to-report-bugs-to-app-developers-support-for-ambient-light-sensors/

Once you have a bug report, please send them to me directly, do not share them in public since they might have private information in them. Ping me on hangouts and I'll send you my email address. The quicker I get reports, the quicker I can work on getting a solution for this. Thanks!
12
1
Marcin Stepien's profile photoUlrich Schonhardt's profile photoWayne Piekarski's profile photoSaid Tahsin Dane's profile photo
8 comments
 
Although Play Services be available in older watches, it will definitely hard to support all.
Basic networking works through Data API in Wear 1.0
Now that v2.0 can access network directly, using Data API to access network is discouraged.
It is even harder to support both.
Add a comment...

Wayne Piekarski

Shared publicly  - 
 
NASA is developing a robot mission to land on an asteroid, capture a boulder, test if it can be used to redirect the asteroid, and then keep the boulder in an orbit around the moon for astronauts to explore and take a piece home. https://www.nasa.gov/content/what-is-nasa-s-asteroid-redirect-mission

There is an amazing concept video, which has a great soundtrack to inspire you even more:
https://www.youtube.com/watch?v=3UkEximY6lc
8
1
Add a comment...
Wayne's Collections
People
In their circles
1,192 people
Have them in circles
2,496 people
Michael Meidl's profile photo
HARD RESET's profile photo
Hüseyin Karagöz's profile photo
ryan cheng's profile photo
anselmo maculane's profile photo
Kaarlo Lahtela's profile photo
Libby Chang's profile photo
Barrister Chris's profile photo
Jason Grout's profile photo
Work
Occupation
Senior Developer Advocate at Google
Skills
Mobile computing, augmented reality, virtual reality, 3D user interfaces, software development
Employment
  • Google
    Senior Developer Advocate, 2014 - present
  • Qualcomm
    Staff Engineer, 2010 - 2014
  • WorldViz
    Development Manager, 2007 - 2010
  • University of South Australia
    Senior Lecturer and Co-Director of the Wearable Computer Lab, 1999 - 2007
  • SE Network Access
    Manager of Research and Development, 1996 - 2001
  • University of North Carolina at Chapel Hill
    Visiting Researcher, 1999 - 1999
Places
Map of the places this user has livedMap of the places this user has livedMap of the places this user has lived
Currently
San Jose, CA
Story
Tagline
Developer Advocate at Google
Introduction
Wayne Piekarski is a Developer Advocate at Google, focusing on Android, Wear, the Internet of Things, and the Living Room. He has worked for 15 years in academia and industry in the areas of wearable computing, outdoor augmented reality, 3D user interfaces, and mobile devices, with a PhD from the University of South Australia. Wayne works to get developers excited about new mobile and wearable technologies, through conferences, social media, and training materials. He also works to advocate for developers within Google, ensuring developers have the right tools and information to support their work.
Bragging rights
Authority on Chicken Fried Steak and Biscuits & Gravy
Collections Wayne is following
Education
  • University of South Australia
    PhD, 1999 - 2004
  • University of South Australia
    Computer Systems Engineering, 1995 - 1998
Wayne Piekarski's +1's are the things they like, agree with, or want to recommend.
Wifi Analyzer - Android Apps on Google Play
market.android.com

Turns your android phone into a Wi-Fi analyzer!! Shows the Wi-Fi channels around you. Helps you to find a less crowded channel for your wire

Email
market.android.com

Приложение Email предустановлено на устройствах Nexus и некоторых устройствах серии Google Play Edition. В нем можно читать и отправлять пис

Android Wear
market.android.com

Information that moves with you. The Android Wear app is the link to Android wearables. Control voice action preferences, adjust notificatio

Google Authenticator
market.android.com

Google Authenticator generuje v telefonu kódy pro dvoufázové ověření.Aktivací dvoufázového ověření přidáte do účtu další úroveň zabezpečení

Recherche Google
market.android.com

Application Recherche Google pour Android : le moyen le plus facile et le plus rapide de trouver ce dont vous avez besoin sur le Web et sur