On this episode, we seek insight on Wear OS, formerly known as Android Wear. As with any other operating system Google has its hands in, there are some unique challenges that developers have had to deal with. Add to that the general malaise the software has experienced over the past several years and you could say that this ship needed to turn around. What does Wear OS 3.0 do to help with that?
We're joined by https://twitter.com/Deadman_Android (Sean Hoyt), an Android developer who worked on the https://www.kickstarter.com/projects/2106691934/blocks-the-worlds-first-modular-smartwatch (BLOCKS) and https://github.com/OpenWatchProject (Open Watch) smartwatch concepts, and https://www.reddit.com/user/DYNAlogix (Greg Viczian), a Wear OS app developer best known for his https://bubble.dynalogix.eu/ (Bubble Cloud launcher).
01:42 - How did Android Wear get its start? What was using it like?
08:36 - What made it challenging for third-party devs to work on Android Wear/Wear OS?
17:27 - What happens when you try to cram a full version of Android onto a smartwatch?
24:58 - What is the app development experience for Wear OS?
32:30 - What does Wear OS 3.0 bring and what does Samsung have to do with all of it?
41:57 - What does the future hold for the success or failure of Wear OS?
Android Bytes is hosted by Mishaal Rahman, Senior Technical Editor, and David Ruddock, Editor in Chief, of Esper.
https://twitter.com/MishaalRahman (Mishaal's Twitter)
https://twitter.com/RDRv3 (David's Twitter)
For more about Esper, visit us.
https://blog.esper.io/ (Esper Blog)
https://www.esper.io/ (Official Esper site)
https://www.esper.io/book-demo (Book an Esper Demo)
Our music is "https://home96.bandcamp.com/track/19 (19)" by https://twitter.com/RNDYGFFE (HOME) and is licensed under https://creativecommons.org/licenses/by/3.0/ (CC BY 3.0).