As an Android Things OEM, you are building system components that integrate with the platform at a deeper level than the typical mobile app and often without any user interaction. How should you structure your code? Should you use activities or services? Should the code be running in the foreground or the background? Do you package all the code into one APK, or split components up into modules? Find answers to all of these questions and more with best practices for building OEM-level apps.
Rate this session by signing-in on the I/O website here → https://goo.gl/fBUpN5
Watch more Android sessions from I/O '18 here → https://goo.gl/R9L42F
See all the sessions from Google I/O '18 here → https://goo.gl/q1Tr8x
Subscribe to the Android Developers channel → http://goo.gl/GEh1ds
For GoLang training courses, please contact Wojtek.