Google I/O may be a wrap. The session celebrated product and platform innovations at Google. As a part of the Google Developer, Expert program gaggle folks traveled to I/O and enjoyed learning together, here we would like to share a number of our top moments and sessions from the event.
This is just a snippet of what went on at Google I/O 2019, you'll find a playlist of all the 177 sessions!
What’s New with Android for Cars
Paul Blundell (Android GDE @ Novoda)
Google I/O has three sorts of talks; hands on coding, developer deep dive and merchandise sales pitches. This was the merchandise sales talk type. Most of the time that’s a nasty thing (when you only want to understand the way to code the thing) but they’re specialized talks for once you are exploring a replacement area and what to understand the high-level product concepts. This talk explained how the Google Assistant is coming to the car interface, hinting that it’ll likely consume Android Auto because it currently stands, and also explaining how original car manufacturers are beginning to use Android for his or her infotainment systems.
This was interesting because it explained how car manufacturers are embracing a version of Android AOSP to run the infotainment in their cars. If you're conversant in Android Auto and the way it's locked right down to a selected subset of apps, Android Auto OS is not any different – however each manufacturer can plan to share key information about the car. this is often the cool thing! It’s the door opening to the unlocking of potential around showing climate controls, car speed and other information.
Watch this space, Google is on a mission for mass-market share within the car space, they know the car manufacturers are screaming for a standardized platform to run infotainment, and if Google manages to tug it off, each carmaker might be running Android. If you're curious about this space (like me), it’s an honest bet to start out to find out more about AOSP, building your own Android fork, and learning the subtleties of custom ROMS. (And a stimulating side note, forking AOSP is strictly what the Android JetPack compose team are asking you to try to if you would like a sneak peek of what they're up to…)
I really enjoyed the ‘community lounge’ at Google IO, this was an area for all the various collaborations Google gets involved in, to satisfy up and talk (GDG’s, GDE’s, Meetups, Udacity, etc). I noticed that they had feedback posts, and having a peek inside they were raspberry pi’s and chatting with some Googlers there, they run AndroidThings, maybe there's hope for the platform yet. 😉
Customisable Delivery with the App Bundle and straightforward Sharing of Test Builds
Edward Woollard (Android Engineer @ Monzo Bank)
Google has continually been performing on improving the Google Play Store in recent years and thereupon work, we’ve been brought some lovely new features to assist us with delivering our app builds to users. We now have in-app updates, conditional delivery, on-demand delivery and asset delivery. I’ll explain more about what each of those is and the way exactly they will benefit you, with a selected example per feature. Since asset delivery is for games, I’ll specialize in the primary three for now.
One thing to notice is that each one of those new features repose on using app bundles which you ought to definitely inspect if you haven’t already. they're now the official standard for a way to ship Android apps through Google Play, but the essential difference is that Google now can handle APK generation and sign for you…you just provide the code.
First off we’ve now been blessed in-app updates. have you ever ever had a time where you’ve had to critically fix a bug and need to make sure all users have this latest app version or even you’d wish to retire an old version but are aware of leaving those users within the lurch? Previously we’ve had to believe users installing updates, whether that be manually or expecting automatic updates to roll out, but the most issue still remains…we cannot guarantee that the user has that latest version before using the app during a particular session. Now we have a primary party solution to simply tell if there’s a replacement app version available, and if we so wish, require that remake is installed before the user can continue using the app, all without even visiting the Google Play Store. What’s more, is that the answer I’ve just described is understood as ‘immediate in-app updates’ but they’ve also provided ‘flexible’ ones too if you would like to permit the user to update to the newest version inside the app whilst still having the ability to hold out other actions. Obviously, during a lot of cases this is often a nicer solution but inevitably results in more work to supply a stunning experience for your users.
Next within the line up is conditional delivery. many apps grow to some extent where they begin aiming at users from either different markets or even they need two separate user use cases, like Deliveroo riders and Deliveroo orders. you would possibly quickly find that there are some features you don’t want to be shipped to a particular market or a selected portion of your users needs a feature from your app et al. don’t. we will now ship this feature to particular users if they meet certain criteria that we will define.
Third we've on-demand delivery. Although almost like conditional delivery, on-demand delivery allows us to feature and take away features of the app as and once we got to, instead of just provide or not provide them initially when the app is first installed. this enables us to not bulk the initial download of the app if we all know that there's an outsized feature that the majority users don’t use regularly, if ever.
If you want to get professional training in Android Applications, you can join Alhuda I.T Institute and Software House Multan. For further information contact us.
This is just a snippet of what went on at Google I/O 2019, you'll find a playlist of all the 177 sessions!
What’s New with Android for Cars
Paul Blundell (Android GDE @ Novoda)
Google I/O has three sorts of talks; hands on coding, developer deep dive and merchandise sales pitches. This was the merchandise sales talk type. Most of the time that’s a nasty thing (when you only want to understand the way to code the thing) but they’re specialized talks for once you are exploring a replacement area and what to understand the high-level product concepts. This talk explained how the Google Assistant is coming to the car interface, hinting that it’ll likely consume Android Auto because it currently stands, and also explaining how original car manufacturers are beginning to use Android for his or her infotainment systems.
This was interesting because it explained how car manufacturers are embracing a version of Android AOSP to run the infotainment in their cars. If you're conversant in Android Auto and the way it's locked right down to a selected subset of apps, Android Auto OS is not any different – however each manufacturer can plan to share key information about the car. this is often the cool thing! It’s the door opening to the unlocking of potential around showing climate controls, car speed and other information.
Watch this space, Google is on a mission for mass-market share within the car space, they know the car manufacturers are screaming for a standardized platform to run infotainment, and if Google manages to tug it off, each carmaker might be running Android. If you're curious about this space (like me), it’s an honest bet to start out to find out more about AOSP, building your own Android fork, and learning the subtleties of custom ROMS. (And a stimulating side note, forking AOSP is strictly what the Android JetPack compose team are asking you to try to if you would like a sneak peek of what they're up to…)
I really enjoyed the ‘community lounge’ at Google IO, this was an area for all the various collaborations Google gets involved in, to satisfy up and talk (GDG’s, GDE’s, Meetups, Udacity, etc). I noticed that they had feedback posts, and having a peek inside they were raspberry pi’s and chatting with some Googlers there, they run AndroidThings, maybe there's hope for the platform yet. 😉
Customisable Delivery with the App Bundle and straightforward Sharing of Test Builds
Edward Woollard (Android Engineer @ Monzo Bank)
Google has continually been performing on improving the Google Play Store in recent years and thereupon work, we’ve been brought some lovely new features to assist us with delivering our app builds to users. We now have in-app updates, conditional delivery, on-demand delivery and asset delivery. I’ll explain more about what each of those is and the way exactly they will benefit you, with a selected example per feature. Since asset delivery is for games, I’ll specialize in the primary three for now.
One thing to notice is that each one of those new features repose on using app bundles which you ought to definitely inspect if you haven’t already. they're now the official standard for a way to ship Android apps through Google Play, but the essential difference is that Google now can handle APK generation and sign for you…you just provide the code.
First off we’ve now been blessed in-app updates. have you ever ever had a time where you’ve had to critically fix a bug and need to make sure all users have this latest app version or even you’d wish to retire an old version but are aware of leaving those users within the lurch? Previously we’ve had to believe users installing updates, whether that be manually or expecting automatic updates to roll out, but the most issue still remains…we cannot guarantee that the user has that latest version before using the app during a particular session. Now we have a primary party solution to simply tell if there’s a replacement app version available, and if we so wish, require that remake is installed before the user can continue using the app, all without even visiting the Google Play Store. What’s more, is that the answer I’ve just described is understood as ‘immediate in-app updates’ but they’ve also provided ‘flexible’ ones too if you would like to permit the user to update to the newest version inside the app whilst still having the ability to hold out other actions. Obviously, during a lot of cases this is often a nicer solution but inevitably results in more work to supply a stunning experience for your users.
Next within the line up is conditional delivery. many apps grow to some extent where they begin aiming at users from either different markets or even they need two separate user use cases, like Deliveroo riders and Deliveroo orders. you would possibly quickly find that there are some features you don’t want to be shipped to a particular market or a selected portion of your users needs a feature from your app et al. don’t. we will now ship this feature to particular users if they meet certain criteria that we will define.
Third we've on-demand delivery. Although almost like conditional delivery, on-demand delivery allows us to feature and take away features of the app as and once we got to, instead of just provide or not provide them initially when the app is first installed. this enables us to not bulk the initial download of the app if we all know that there's an outsized feature that the majority users don’t use regularly, if ever.
If you want to get professional training in Android Applications, you can join Alhuda I.T Institute and Software House Multan. For further information contact us.