This session was an open Q&A among the viewers (which includes an viewers queried prior to the party) and the Android platform team, which incorporated engineers from the Android framework, runtime, media, graphics, and other teams. A issue with the microphones prompted some of the first concerns from the viewers to be inaudible in the recording. These concerns are transcribed here, along with the times at which these concerns had been asked.
4:55 – For people that are setting up with Android, do you advocate them to use Kotlin or Java?
six:57 – We’ve heard a ton at I/O about options like the new Assistant and very similar that call for turning on location heritage and search heritage and a ton of other info collections, what are the alternatives or possibilities for people that want all those capabilities that want to retain their privateness and not report a ton of heritage?
eight:fifteen – Could you explain to what you might be undertaking at a significant level [with Treble] to guarantee that the implementation from some of the OEM companions you should not crack, both intentionally or not, some of the factors you might be likely to do in bringing forth new versions of the OS?
thirteen:31 – When you use your Android cell phone, what do you truly despise and why have not you fastened it however?
fourteen:55 – Recognizing what you know now, and in particular with some of the alterations in Android O, would you even now implement the identical four software interfaces, this sort of as Things to do, Support, and Intents, in a new working program?
fifteen:55 – My query is to do with the blocking of broadcast receivers declared in manifests in O. In a session this afternoon, Dan mentioned that person preference is the essence of Android, so why will never you permit users whitelist applications?
21:19 – Like every person else, I’m truly excited to have the support and encouragement for software progress in Kotlin. I’m pondering if that identical encouragement will lengthen to Gradle Script Kotlin when it’s unveiled, in all probability later in the yr.
21:51 – For third occasion frameworks, are you likely to need to have to incorporate just about anything like a bridging header, as you do in Swift to Aim-C to support Java initiatives in Kotlin initiatives and the other way all over? Are we likely to need to have to incorporate any bridging in an Android task to use a Java third-occasion framework?
22:36 – So Tim [Murray] confirmed us how to use Systrace to profile our applications and in Tor’s session right now we noticed CPU monitoring. I might like to know how these evaluate and contrast, and what are the values of each?
Check out more Android talks at I/O ’17 here:
See all the talks from Google I/O ’17 here:
Subscribe to the Android channel:
#io17 #GoogleIO #GoogleIO2017