We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

An introduction of Android Auto

00:00

Formale Metadaten

Titel
An introduction of Android Auto
Serientitel
Anzahl der Teile
46
Autor
Lizenz
CC-Namensnennung 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
It has been a lot going on since the first version of Android in 2008! After thousands of devices and even after Android Wear in 2014 it's now time for Android Auto! Connected cars are going the be future and Android Auto will play a big role in this scenario. This is where this session comes in: It'll give you a brief overview and introduction of the brand new Android Auto SDK and it's APIs. You want to get started with Android Auto? - Then you should definitely attend this session! The four main points in this talk are about the initial question: What is Android Auto - and why should I start developing for it? Followed by some neat facts and informations about the special Designing Guidelines in Android Auto, starting with your first Code and of course with some practical thoughts about scenarios and usecases of Android Auto. Why not be part of the future? And start with Android Auto - Right now!
Humanoider RoboterBitfehlerhäufigkeitHumanoider RoboterVorlesung/Konferenz
SoftwareentwicklerHumanoider RoboterZweiRechenschieberWurzel <Mathematik>Metropolitan area networkEinfacher RingTypentheorieGruppenoperationHumanoider RoboterSoftwareentwicklerPlastikkarteMaschinenschreibenNegative ZahlPerspektiveFormation <Mathematik>CodeAdressraumSoftware Development KitVorlesung/KonferenzBesprechung/Interview
GruppenkeimStellenringProzess <Informatik>GruppenoperationFlächeninhaltComputeranimation
MaschinenschreibenPhysikalisches SystemGamecontrollerVorlesung/Konferenz
SmartphoneTablet PCGoogolHumanoider RoboterPlastikkarteBesprechung/Interview
QuaderNotebook-ComputerHumanoider RoboterVorlesung/Konferenz
Ordnung <Mathematik>MaßerweiterungHumanoider RoboterSichtenkonzeptSystemplattformFramework <Informatik>App <Programm>Vorlesung/Konferenz
BitfehlerhäufigkeitApp <Programm>Humanoider RoboterMultiplikationsoperatorGebäude <Mathematik>MaßerweiterungRechenwerkVorlesung/Konferenz
SoftwareentwicklerApp <Programm>Humanoider RoboterMultiplikationsoperatorSmartphoneNichtlineares ZuordnungsproblemWort <Informatik>Vorlesung/Konferenz
Formation <Mathematik>FacebookPunktPhysikalisches SystemMessage-PassingAdressraumInfotainmentFront-End <Software>
Humanoider RoboterVorlesung/Konferenz
Offene MengeHumanoider RoboterSoftwareentwicklerGrenzschichtablösungOrdnung <Mathematik>GoogolOffene MengeVorlesung/Konferenz
Humanoider RoboterKonfiguration <Informatik>BildschirmsymbolE-MailSoftwareentwicklerApp <Programm>GoogolMultiplikationsoperatorComputersimulationVorlesung/KonferenzBesprechung/Interview
BitfehlerhäufigkeitSimulationDivisionDokumentenserverProgrammbibliothekSoftware Development KitMessage-PassingHumanoider RoboterComputersimulationFormation <Mathematik>EmulatorARM <Computerarchitektur>DatenverwaltungCASE <Informatik>FlächeninhaltComputeranimation
Humanoider RoboterGoogolHumanoider RoboterApp <Programm>CASE <Informatik>Elektronische PublikationGeradeVorlesung/KonferenzBesprechung/Interview
KontrollstrukturInterface <Schaltung>Message-PassingDivisionHumanoider RoboterDifferenteMessage-PassingHypermediaDienst <Informatik>RechenschieberBrowserFormation <Mathematik>BroadcastingverfahrenTypentheorieProgrammbibliothekHumanoider RoboterCodeGüte der AnpassungComputeranimationVorlesung/Konferenz
ATMPrognoseverfahrenApp <Programm>TeilbarkeitKontrast <Statistik>TouchscreenPunktCASE <Informatik>Treiber <Programm>Humanoider RoboterComputeranimationVorlesung/Konferenz
DualitätstheorieSoftwaretestHumanoider RoboterSimulationChecklisteEin-AusgabeApp <Programm>InformationsspeicherungTreiber <Programm>ProgrammschleifePerspektiveHumanoider RoboterSichtenkonzeptE-MailComputersicherheitWärmeausdehnungMomentenproblemGoogolÄhnlichkeitsgeometrieKontextbezogenes SystemOnline-KatalogXMLBesprechung/Interview
App <Programm>InfotainmentBitfehlerhäufigkeitApp <Programm>MultiplikationsoperatorPunktEinfach zusammenhängender RaumInformationVorlesung/Konferenz
SoftwarewartungGüte der AnpassungCASE <Informatik>Humanoider RoboterTreiber <Programm>App <Programm>ComputersicherheitTeilbarkeitVorlesung/KonferenzBesprechung/Interview
Humanoider RoboterSystemplattformApp <Programm>Wiederkehrender ZustandHumanoider RoboterEndliche ModelltheorieMereologieCodeGeradeSystemplattformCoxeter-GruppeSoftwareentwicklerPunktNichtlineares ZuordnungsproblemVorlesung/Konferenz
Humanoider RoboterApp <Programm>MereologieBesprechung/Interview
Vorlesung/Konferenz
Transkript: Englisch(automatisch erzeugt)
Thanks for attending my session, today I'm going to give you a small overview about Android Auto. And I want to start with a scenario. So imagine you want to visit a friend, you're going to take your car, and you get into your car, first thing you probably do is type in this address and navigation
and maybe in your car without touch and whatever, so it's not very intuitive. Then before starting you probably want to turn on your music, but man, you forget your CDs, SD card, maybe your cable for your phone and whatever, you just turn on the radio.
You probably then start driving and while you're driving your car is ringing, so it's ringing and ringing and you don't have a hands-free kit, can't do anything, and even if it starts ringing you can't even answer with texting or something, because we all know driving and texting is pretty bad, and that's a really bad scenario. But I mean it's just one out of hundreds and I think it's kind of annoying, it's not
really smart, things are going to change, things are going to change with Android Auto. Yeah, let's get it started. So I'm not a big man of introductions and ag agendas, so here's mine.
At first I want to give you a brief overview what Android Auto is for the consumer and for the developer side, the second is some dev stuff, I mean we're developers so let's get some code, and the third is about some perspectives, some future scenarios, what could be in connected cars and how can we make our cars even smarter.
So first things first, introduction slide about me. I'm an Android developer for like seven years now, currently I'm working for Groupon, I did some freelance stuff, and I really love cars and I love Android, and I think Android Auto is a perfect topic for me and I'm really excited what's coming
up in the future, so as I'm working for Groupon, you probably know this company, so currently we're looking for some skilled engineers in the mobile area, so if you want to have a great job at a great company we should have a talk, and yeah, as I said I love cars, there's something that really grinds my gears but it's really annoying,
it's that every car manufacturer has its own system, its own smart system, and I think putting in all those stuff without touch controls, with a different UI, it's not very intuitive and it really sucks. I have my smartphone with me every day, all day long, so why can't I just use my smartphone
the way I want it, and that's something that's going to change in the future with Android Auto, and before we come to this topic, let's start with a small story. Years ago, I mean really really a decade ago nearly, there was a company, the company was called Android, and Google bought it, and since then we got our beautiful Android smartphones
and everyone was pretty happy about it, and years later they gave us tablets and people were even more happy and excited about it, and after that I mean, you know when that came, we got like setup boxes, TVs, notebooks, we even got smartwatches on our wrists,
and now comes the next step, after years, finally, Android got hit by a car, literally, so it's something new what's coming up to us, but now we come to the real big question, what exactly is Android Auto, and Android Auto is not like being dressed up as an Android and driving in your car,
I mean that would be pretty funny, but it's not, so Android Auto is not a new platform, it's just an extension of the existing Android framework, so you can use all your features and all your apps you already love, and furthermore because of that, it just needs a small extension
to make your app extendable for Android Auto, some people already did that, unfortunately only a few, so these apps are currently extended for Android Auto, the only problem is that there aren't so many cars out yet with Android Auto, I think there's this Hyundai Sonata 2015, they have Android Auto inbuilt with Apple CarPlay,
and to extend your app for Android Auto, it's pretty simple, I'll come back to that later, and I think because there are only a few apps out there yet, it's really the time for us developers to start developing for Android Auto,
and that comes to the next question, what do I need to get started with Android Auto? Just pretty simple, as a consumer you only need three things, you need your smartphone, lollipop and upwards, you need a cable, and you need a car, so you just connect them, you install the app for that, and everything works fine,
so okay, smart clue on this one is, you put on your phone into your car, so you got all your addresses, all your contacts, all your Facebook messages, you even got your music with you, and everything is processed on your phone, so your car and your infotainment system is just a front-end for that, and the next point would be,
okay, I don't have an Android Auto car, and I don't want to buy a new car, so do I have to? No, fortunately you don't have to, there are some aftermarket devices you can buy, currently there are like three out there from Pioneer, ranging from 700 to 1.5k, you can just install them in nearly every car, and have the Android Auto experience in your car,
and to make Android Auto successful, to make it the next great big thing, this is Open Automotive Alliance, it consists of several car manufacturers, tech partners like Nvidia and Intel,
all backing up Google to support them doing Android Auto, and making Android Auto the next big thing, and yeah, it's pretty awesome. So, we're developers, let's come to the developer stuff. At first you want to download the Android Auto app from the Google Play, looks like this.
You just started, and when you started it you can connect it to your car and use it as consumer, but I mean we're developers, so just enable the developer options first. In this header where these icons are, just click them like seven times, and you can enable the developer options, I mean we already know that clicking something a couple of times, that's the first step.
The second step would be to get the simulators, currently there are two APIs out there, the messaging API and the music API, and to simulate those car behaviours you need those APKs, those simulators. So, you start with your SDK manager, Android Studio, Eclipse, whatever, and download them,
download the simulators as you download your SDKs. After that, you can access those two APKs in this path, and install them on your device, or on your emulator, or whatever. So, that said, the next big question would be, okay, what's under the hood, what do I need to do to enable my Android Auto app?
It's roughly like two lines, you start a new manifest, saying okay, I want to have my app extended for Android Auto, it's pretty simple, and this manifest entry refers to another XML file, and this XML file itself just describes what kind of APIs you want to use for your Android Auto app, in this case it's Meteor.
So, that's nearly everything, you just have to then to support your new layouts and assets and stuff, but that's nothing. So, and as I said, there are currently two APIs out there, these are the two APIs, it's audio and messaging. So, messaging is quite a little bit different from what we know, because when you're driving a car,
you can't just type text or something, so it heavily relies on voice commands, just like a dialogue with your car, you're telling them compose a message, that's my message, I want to send it and stuff. Furthermore, this messaging API relies heavily on broadcast receivers and intents, so it's a pretty good design, and I have an example in the next slide,
and also there's these audio commands, and the audio API, it's just like a media browser that gives you a media session with your media service to browse your music, to enable Android Auto, and to design your own custom music player in your car. As I said,
the messaging API, you will start by importing your support library to enable Android Auto messaging features, and then to have some broadcast receivers in your manifest, and to read and reply to messages just about to intents, and that's nearly it,
so it's a pretty good design, it's very the Android way, and it's pretty cool. Okay. Beside code, there's another really important key factor, it's design. I mean, okay, app design and UX design is pretty important for Android developers, sure, but we're talking about apps in your car. You don't want to distract your driver
while he's driving, you want to have an intuitive UI, you want to have clear contrasts, you don't want him to do unnecessary stuff. So in this case, in these three screens, you can see that there are clear fonts, not so many buttons,
everything is very, very pure and very clear with good contrast, so that's one of the key points. And the thing is, to ensure that you're following a good design, that you don't distract your drivers, just something pretty new in Android Auto. It's the quality criteria. So this quality criteria
is something like, I don't know, maybe you have already developed some iOS apps, it's like when you upload your app in the store, it takes a couple of days, two weeks, until it gets checked, and we don't have that in Android yet, but in Android Auto, we will have something similar, because security and awareness for your driver is pretty important, so if you upload your new release,
with your new Android Auto extension, it'll take days to maybe a couple of weeks until your app gets then published in the store. If it's not published, you get an email with the reasons what you have to improve on your app, and to have a peak overview, what you can do, there are at the moment two catalogs from Google
telling you what is important, what you should keep an eye on, and what you should do to make your app compatible to Android Auto. Okay, let's think of the future, I mean, it's all about a perspective, right? So currently, it's just two APIs, it's not much out there, not so many cars, devices, whatever,
but time by time, it grows and grows. So let's think maybe of car infos. You could probably in the future access your car infos like wheel speed, tire pressure, all temperature and all this stuff, and compute that in your app. You could also do some connected car stuff, I don't know who of you knows Waze,
it's a crowdsourcing navigation, and the more people use this app, the better it gets, because they're sharing information to each other. Another point would be companion apps, you could check your car status via your smartphone and via your home and stuff. Another key factor would be security,
you could use the park sensors or maintenance intervals to remind your driver via your app. And at least ecology, especially in this case, you can think of gamification stuff. You can reward your driver if he's driving eco-friendly, if he has a good fuel consumption, or if he's driving safe.
So it's fun for him to drive safe and eco-friendly. So that said, let's come to a small conclusion. As a consumer, Android Auto is nothing special, nothing new, it's just extending the existing Android platform. There are only a few cars and apps out there,
as far as I know, Volkswagen wants to release a new model at the end of this year using Android Auto. Also, you can upgrade your car using aftermarket devices, and to use Android Auto, it's just about an app, a cable, and your car. And as a developer, it's nothing more, it's just that you need two lines of code roughly,
there are two APIs out yet, you really have to focus on a good, clear design, because elsewhere, and that's the next point, you get rejected because of this quality criteria. And that said, and especially when I started the presentation, we, as a developer, can be part of the future, we can change the way people are using their cars,
using apps in their cars. So I think we all should be part of that. And as you now know what it takes to start with Android Auto, I want you to get there, get out there, and start with Android Auto today. Thank you.