Duration 39:57
16+
Play
Video

The future of apps on Android and Google Play: modular, instant, and dynamic

Kobi Glick
Senior Product Manager at Google
+ 4 speakers
  • Video
  • Table of contents
  • Video
2018 Google I/O
May 8, 2018, Mountain View, USA
2018 Google I/O
Video
The future of apps on Android and Google Play: modular, instant, and dynamic
Available
In cart
Free
Free
Free
Free
Free
Free
Add to favorites
24.36 K
I like 0
I dislike 0
Available
In cart
Free
Free
Free
Free
Free
Free
  • Description
  • Transcript
  • Discussion

About speakers

Kobi Glick
Senior Product Manager at Google
Matt Henderson
Director of Product Management at Google
Jonathan Karmel
Product Lead at Google
Karen Ng
Product Manager at Google
Milena Nikolic
Engineering Director at Google

Kobi is a product manager leading app distribution on Google Play. Kobi is focused on helping developers build leaner apps, deliver excellent experiences to different devices and form-factors, and launch & grow on Google Play.

View the profile

Matt leads product management for the Google Play Console, building publishing, distribution and analytics tools for apps and games developers. He previously managed the product team for AdWords features, bidding systems and analytics for Shopping Ads. Matt was the founder and CEO of Rangespan, the retail analytics company acquired by Google in 2014. He previously worked at Amazon.com, most recently as product director for Amazon's seller marketplace.

View the profile

Jonathan is the product lead for Google Play Instant. Previously, Jonathan was the product lead for Analytics, Data Science, and CRM at Google Play. Jonathan holds a Bachelor of Science in Statistics and Finance and an MBA in Customer Analytics, both from the Wharton School at the University of Pennsylvania.

View the profile

Karen is a group product manager working on Android Studio and making mobile development easier and faster than ever before. Prior to joining Google, Karen was at Microsoft working on DevOps tooling and cloud services, programming languages like C#, and designing productive IDE tooling in Visual Studio. She has a masters degree from the Massachusetts Institute of Technology.

View the profile

Milena is an engineering manager leading app distribution and developer success efforts on Google Play. She's based in London, and has been at Google for 10 years working on a number of different products. Milena enjoys building happy and productive engineering organizations, exciting products and powerful technology.

View the profile

About the talk

Android development is becoming modular, app experiences are becoming instant, and delivery of apps and features is becoming dynamic. The Android App Bundle enables you to deliver leaner, fresher apps with optional features loaded on-demand. Google Play's Dynamic Delivery takes care of device configurations for you, only sending each device what it needs, so you don't have to manage multiple APKs. You'll also soon be able to “instant-enable” your Android App Bundle, so that users can open modules instantly, from any link, without installation.

Share

The hello everybody as the video shows things get better over time technology helps things get better. It helps things get smaller faster easier. Much much better, but how about apps how will the architecture of apps get better? We're here to tell you more about our vision for the future of Android app development Discovery and distribution. Android's first 10 years have centered around the app download. It works like this developers build a lodge app with only features in it. People find apps on Google Play and install the ones they want and then I weigh while play

Cynthia to their device. And it's been a great 10 years. There are now over 2 billion active Android devices around the world and play installed close to 100 billion apps and games in the last year 100 billion. But I laugh model can get even better. So what to improve well during development building and Publishing four different device types is still hot. In the discovery stage new users. I put off by long wait times for the download. And off to distribution large tap sizes, these large apps are much more likely to get uninstalled.

Set a future of apps will address these problems development will be more modular. Discovery will be more instant and distribution will be more dynamic. I'll first step in this direction has been instant apps and you'll have more today about how it's removing install friction and helping to improve discovery. We made instant apps available to game developers at GDC this year. You can simply tap the try now button to jump into game experiences like this one King's Candy

Crush Saga. Developers of seeing that instant apps drives Anchorman who installs users that would have otherwise abandoned at this page. I'm trying to experience the clicking try now and then the proceeding to install Today we're revealing our related ethics on development and distribution. In the developer keynote, you heard a little bit about what we working on in these areas and we're going to talk much more about them now to tell you more about what we've been working on. Let me invite out Milana

engineering manager for Play app distribution and Coby product manager for play at distribution. Thanks math. The Android ecosystem has evolved since the humble G1 was introduced 10 years ago. With over 2 billion devices. There are new form factors in thousands of your device models every year. This is great for user Choice. There is a device for everyone but thinking about all these devices is made development complex. Some of you use multi APK to optimize the size of your app. This is costly and complicated instead of focusing on making your app unique you end up focusing on trying to Target

the right devices. With multi APK did dimensions of device configurations on android multiplayer really quickly. So if you try to optimize by CPU architecture in screen densities, you will end up with many apks. In the number of apks Woodrow really really quickly, especially when you start targeting 64-bit. And each one of those apks has its own unique version code. All of them is part of the same after lease. This is painful for developers. There must be a better way.

To avoid the hassle of multi APK some apps simply ship everything to everyone all stream densities ocp architectures or languages. The results are really really big apps. This is painful for users. There must be a better way. Supporting all the different devices while also adding new features has also contributed to apps becoming a larger over time. Since March 2012 the average APK size has grown by five times. This is bad for users because mobile data and device storage or both of our premium and you just don't want to have to wait

forever to start using an app for a game. We can't wait for this point enough APK size is a very real effect on conversion and successful downloads of your app shows you the correlation between using conversion in the play store listing and the size of an 88 clearly the heavier your app the less likely a user will download it. You may have read about this in one of our meeting posted this topic for every 6 megabytes of an increase. The conversion rate goes down by 1% This is a material loss conversion rates, which can

be recovered by focusing on the APK size, but that's not all. Bloated ABS can also be bad for Innovation something over there having to choose between adding new features and keeping their athlean for example flip guard is leading Ecommerce player in India where their costs are still high. So it's important for them to keep their app download size small. They're looking for solutions to keep their initial install as small as possible while being able to provide Rich experiences for their users in the long run. So

we've been thinking about this. How can we decrease APK size without affecting development and distribution complexity? Well, let's look at what's in today's APK many languages most of which are user never needs. Duplicative CPU information for arm and x86 and sometimes even 32-bit and 64-bit. it includes resources in five or six different screen densities and probably includes Niche or experimental features, which only a percentage of the audience will ever be exposed to this stuff make my sent a far better solution

would would be the only delivered the code and resources that a particular device needs and to deliver leaner. I have experience where you download additional features on demand. Sore vision for solving the same point in development is a new app format. I'm happy to announce that they were launching the Android up bundle. The Android app bundle is the new publishing format for Android. It is open source and Backward Compatible. It will help your users benefit from smaller apps and you will not need to build multi APK

to optimize the size of your apps anymore Yes. You heard that right? Multi APK is finally going away. Thank you. With your bundle you only build one thing and you don't need to refactor your code to start using it. In addition it enables modular app development, which we'll talk about later in this session. So how does this work on Google Play Friend users to benefit from the out bundle. We're doing some of the heavy lifting behind the scene on the distribution site launching today Dynamic delivery. With Dynamic

delivery play will take care of bundle and generate apks that are specific to a device with only the code and resources needed by. Device these means much smaller apps for your users, which is great news for the billions of New Year's is coming online. So let's take a look at the Android app bundle in a little bit more detail. So here is an Android a bundle. Similar to APK files resources asset Cincinnati libraries with one difference. You can see include more than one module in this particular

example base food and Bar. Important for a polarity which we'll get to talk about soon. Another thing you can see either the format includes a few metadata files where you can provide to play with different instructions on how to process the bumble. Now, Google Play use this format to create the light wave binary. We use an Android platform feature launch the lollipop called split atk's think about Android that bundle is a publishing format are the serving for a month and what eventually ends up being installed on user devices. When you upload your bundle to play

Wheel throws assets to generate split. We do this with a fool we have very originally named bundle tool. This school will be open source. So you can use it to perform the same processing that we do for off play testing and distribution purposes. Bulbasaur facilitates all the necessary conversions between a bungalow floor mats and split apks for example generating all the splits for densities architectures. Any language is selecting specific splits needed by a particular device installing split on a connected device and for devices on

Android versions older than lollipop. It's a silly face fusing of splits into monolithic device optimize APK There are many more options available with a Bumble and Bumble hole in the next session is stage 2 at 6 p.m. Our engineering team will provide us technical Deep dive about the band perform at the bundle tool and all the options that enables. Okay, so you mentioned site savings tell me a little bit more about how it happens. Sure. Yep here has the base APK with X-Files and the corresponding density Avi and language list. We Dynamic delivery play will only deliver at the

density and Avi splits required by a particular device making the apps smaller for users in addition label start handling Mission languages. Bungle, you will be able to supply all the languages and Flavel only sent two users the splits for language. Is there typically using In the rare case where user switches to a new language that we weren't aware of before play will dynamically deliver relevant splits to their device for some apps language splits alone introduced massive size savings. So we've been texting you with we've been testing

this with your developers. Probably some of your in the audience right now. For example Twitter is one of our Early Access partner by splitting over languages in screen densities. They are saving 35% of their outsides. This is huge. And this is not everything you're a few more examples text plus with 26% size savings Blue Apron with 27% size Savings in jail Mo with 15% size savings. And that's not all we have more here a few more examples of our early access Partners oldest Partners to

build the bundle published it to play and were able to make their apps significantly smaller. Look at the results ABA English Airbnb LinkedIn memorize very G Pluto TV and RV appstudios him all saved between 11 and 64% of their app size. And that's how I enter the bundle and school plays Dynamic delivery work. Once you publish and build your bundle Google Play will deliver. Just what specific device needs now. Let me by Karen who leads Android Studio product into the

stage to tell me a little bit more about how you build a bundle. Face - I am Karen and I work on the sun is ended really bad. So you've now seen the concept of an app bundle. What I want to do is tip at directions and show you a bit about the tools that you're going to use to build a bundle in Android Studio 3 to Canary in 4 hours ago. So go download it. There's full support inside studio and Gretel to build a bundle format. Fiat Punto contain everything you're at need all your languages support for every device screen every

Hardware architecture and will automatically build those into configurations those configuration into apks for you. If you're using Android studio to build a bundle, the flow will feel very similar to an ATK working with an APK today. What weed introduced in the build menu is a new option to build a bundle. If you're using a continuous integration system. All the Gradle build tasks have also been updated to build a bundle. So replacing a single option rebuilding your project as a bundle means that's all you need to do to take advantage of the APK size saving you'll also be able to

take advantage of Google Play's Dynamic delivery. The only the bits that are needed are downloaded to the device. The Android app bundle is your new publishing format for the store? Testing and deploying your bundle will again feel very similar to it. What it does today in Android Studio. You're just working with Apk What we've also done is updated a new run configuration dialogue so you can choose the bundle and select your deployment Target and deploy directly to a device or to an emulator greater will build a bundle and then deploy only the atk's that are needed by the device.

Disability to test and deploy your bundle will simulate exactly with a place for a does. If you're just passing your app functionality though, you can go ahead and use an ATK like you did before it work the same way and it actually going to be faster to deploy to device. To upload the bundle into the Play Store you'll need to sign the bundle with a signing key for all existing apps. You need to provide Google play with your signing key. So play can process that key and then re-sign your bundle the same key. For new apps play will just generate that APK for you or that sexy for you.

If you recall animal 2 apk world, you used to have to upload every APK manually yourself to that store in a bundle world. We do all the heavy lifting for you. You only have to upload one thing. Once you build a bundle you can upload and publish it through the play console. You will use the same release flow. You're familiar with with an APK. In addition in order to test your Rapunzel with your testers, you can use our new internal testing track. It allows you to distribute your app to your testers

within less than a minute. When you publish an app bundle to to the play console, we provide you a new way to look at your a bundle and understand the size of the device specific apks that played generates and delivers to your users. We called you Snoop age the bundle Explorer here. You can see what is the size of all those device specific apks that plays generates for every device configuration. For example, you can see what is the size of the apks if they will deliver to an RM xhdpi device. You can also use this page to download the device specific

APK is generated by play to any device model that is listed in our device catalog. We showed you how the Android app bundle and dynamic delivery will benefit you in a number of ways for developers. You really no longer have to manage the multi APK world for your users were really hoping that they won't have to pay the cost of that giant up front install. So what does it all mean in practice? We work with a number of developers in the Early Access program ecobee mentioned earlier. It's been fun. Twitter has told us what they like about the new flow with the Android

app bundle. They upload one binary with one version code and dynamic delivery handles ATI density and language split for Twitter to have done this themselves. It would have required the maintenance of 580 case. That's not a small feat. They describe their build and release process is more streamlined with the size of their app has significantly decrease for their users. So you've now seen how building an app on Dell results in smaller app and it note edit also means that you no longer have to manage multiple APK II big change of the app bundle enables is more

modular app. So today we're releasing a preview of the ability to deliver features on demand. Justice building a bundle automatically build split such as language screen density and Hardware. You can create a split for additional feature. We call these features Dynamic feature. And they are installed on demand each apple then have a base teacher and N number of dynamic features. Begin with the latest version of Android Studio you can start reading apps today with Dynamic features. If you want to polish that out into the

PlayStore, however, we're still in beta so you'll need to join the beta program on the Play store apps won't need any effort to treat a bundle and support Dynamic delivery treating these modular apps with on-demand features. We do expect will feel longer-term progression and it works fast as you re architect your apps over time. Show me to give an example of what it means for not to have Dynamic features in this particular example. We have a camera Depot app. It's just a simple e-commerce app. There's four features to pay attention to the first feature is just to be able to browse Goods

the second one to be able to see what offers you have 3rd theme to buy items in the forcing of the South. You can imagine that from our app usage that we see that less than 1% of people ever use the cell feature and it's only by people in a particular region or primarily. Every person who downloaded your app have to pay the price of installing all the features. In this case, we should make a cell feature a dynamic feature. So if a user clicks on the sell button, you'll see a small user front that the feature is downloading and then it's dynamically

delivered to the device. So how did you sign a make features that relate to a bundle and Ecommerce app the main browser application today with what we would call a face teacher you can then extend your face feature was delivered to your users on demand an Android Studio. We've added a new plug-in called Dynamic teacher. You can extend your application in Android Studio by adding multiple Dynamic features to it. So let's take another example imagine that you have a video chat app the app and the main out with your face feature. You can then carve out a special

teacher like augmented reality stickers and delivered on demand to users only with devices with the right camera to support that teacher. If you build a new app, you should design your office modular from the start thinking carefully about a lightweight face. And then how you would extend that out within on the future. If you have an existing app, we're expecting to see people take advantage of dynamic features, but car about specific features overtime. So once you created your Dynamic features, you can choose an employee only a set of them to the device as

you can see here in Android Studio. What we've done is also updated how you deploy the box your shows you three Dynamic features by offers in South you have full control over which features used to play so that you can mix and match them and the base teacher is always deployed. So this framework will help large apps become smaller and smaller apps remain small Will adding more functionality. The first step is building an Android app bundle and the next like Aaron just described. He's identifying features that can be carved out is dynamic features. After you factoring your

code to carve out those Dynamic features, you will need to integrate with a new client Library. We're releasing today. He's called the Google Play core library and it includes a set of apis allowing you to manage the delivery of those Dynamic features for your users. And in case you want to deliver a future as a response to a user request, you probably want to build a nice user experience around it. The Google Play Coeur Library provides a high degree of flexibility when you're wanted deliver a feature to your users be on delivering a future as a response to the user

request. You can also ask to pre-fish the Future when you predict the user will need it soon or you can ask play to deliver. The feature is part of the next update cycle. We called this auction deferred installation. When thinking about good use cases for dynamic features, we've identified two broad categories. The first category is what we call this thing features. These features are logically separate from the main flow of your app. For example in the e-commerce app Karen mentioned earlier. There's a buyer experience and a seller experience. The seller experience

is logically separate and therefore a great candidate for dynamic feature. The second category is what we call interrupting features those features pop up during a normal user flow in Europe. For example, if you have a photography app, you might have an option to add additional filters during the editing process. And for those features it is typically better to use the Deferred installation option. I mention earlier to make sure users have the feature available when they ready to use it. And of course, we'll be super curious to see what use cases you come up with

is you start innovating with Dynamic features. Earlier in the stock we've mentioned how developers want to keep their base install the smallest possible while building Rich new user experiences Flipkart and Facebook are too early access Partners for helping us to this Dynamic features. For Flipkart is they think about building for the next 100 million users Dynamic features allow them to ship new and which user experiences there naturally size heavy like vernacular support video in feets. Facebook use Dynamic features

to improve the experience of the app for different devices while reducing its Network and resource usage. They told us that one thing they really liked about the new framework is how Dynamic teachers are updated seamlessly is part of any app update. Dynamic features enable Dynamic code loading when you deliver a feature on demand for your user. It can include code resources and assets as you know. Some play are scanned by Google Play protect and delivered security to use our devices. Dynamic features will also

be scanned by Google Play protect which means your users will benefit from all the same protections. We've been building for years on Google Play. The Android app funds will make development easier and dynamic delivery and is the future the internet model delivery will improve distribution. But what about the big thing in the middle? We've barely touched upon discovery. I want invite Jonathan Carmel who leads the instant apps team to come join me and tell me what's a little bit more about discovery.

Thanks, Karen. Last year on this stage. We announced that all app developers can now develop an Ensign app. Today we're excited to add games to the mix today all game developers can now develop an internet. So let's start with an example of one of our top game developers that are alive today roll the video, please. welcome to Google Play Ensign where you can get apps and now games instantly and as you saw on the video when you click try now you launch into a

native app experience that is instant and then you'll have an option to install and users are installing more because of because of this trying out button Let Me Explain how in the old world You'd see a store listing page like this where the user has two options install or abandon and users were abandoning because they weren't ready to commit to a hundred answer their phone without playing the game or understanding understanding the game fully. Caught in the new world and now looks like this. So if you are already coming to the

store to install you're going to continuing continue to install at the same rate you have it before and we're seeing this the CTR rate for install has not changed. But if you were starting to wander and think about leaving you now have another option you have to try now button and that was launched you into the instant experience and allow you to install. So, where do you see this instant experiences will clearly from the Play Store? Where you'll see not only try now but Collections and Banners that launched directly into an Instagram, but nothing to do with the Play

Store who is everything outside the Play Store cuz that's often where the decision is to install or abandon and that's where the biggest drop-off rates are. Let's take ads for example. In the old world I click the sad and I'd land in the store listing page with an option to install. In the new world likes like this and I land in the instant experience with an option to install in both worlds. I have to decide if I want install or not. But now I get to play the game while I SAS if this is worth it to be on my phone. And if I receive a SMS from a friend that

says try out this new TV show I can start watching that TV show immediately and then decide if I want to install the app. And if I'm looking for a new home on Google search, I can actually find a Homeland in the experience. Look at the images accessify. I like the property and then determine if I uninstall the app the real estate app that got me all that information. Now, this is great. It's a consumer first experience. It's great for the user. What is it good for developers. The answer is yes. We're seeing installs conversions and engagement go up. So

start with in sauce Mighty battles on 19% increase in installs just from the try not to run. Now. This is one of the higher data points that we've seen what we have seen incremental installs across the board and as a developer as you expand beyond the Play Store and start thinking about all the traffic sources. I showed him the other slide you'll start noticing that your new customer acquisition channel is instant apps. Take them a meal. For example, if she's sitting right over here. They're seeing 15% of their installs coming from Ensign X and n o s a news app is seeing

30% of their installs coming from in synapse. This is their new customer acquisition Channel. Sorenson apps just driving users to install now. They're also having great experiences for the user within the internet. We go a travel outfits in 27% increase in conversions within the travel app where you get you paid leads from the internet. And Vicki a TV show app is seeing monetizable watch time increase by 5 x. So be it if you're trying to drive it stalls or you want to make sure that the user has a great experience within the internet internet search. Now I

know what you're wondering. We just talked about Android app bundle. We talked about in synapse and now you're worried that you're going to have double the work. You're going to go home and have to work on both things where you can have to choose one or the other absolutely not this is part of the same effort and instant is just a mode of the Android app bundle. So what I'm going to do is take you from an Android app on Google and migrated to an instant enabled Android a bundle. And then I'm also going to start with a nap and show you how you get to the internet bundle.

all right, so Toby came up here instead you take her if you can you get to an Android app on though and also mention that you're going to start carving out code and start modularizing you're at so as you go through this process you might notice that one of your features makes a great entry point and you would love that your users actually instantly jump into your app that way so if your bass module and your. Maisel are small enough you can just make those incident able For all that is in a stalled out that you're not ready to have part of your

insta. Now you're going to wrap that is a dynamic feature module and you're just going to make it available to install time. And there you have it one binary that is both an instant app and install them. Now, let's see what this looks like. If you're one of the Ensign app developers that I seen the audience today, so you probably have something that looks like this you have a zip file. It has both a base feature module potentially another feature module. And you're going to take it and you did all this hard work to decrease the binary to modularize that work is not wasted. You're just going to

take that same code and you're just going to make it part of the Android app bundle. And for all that code that's in your installed app. That's not in your instant app. Again. You're going to wrap it as a dynamic feature module and just make sure it's available and install time. There you are. I got you have one binary. That's both an instant app and installed out. So now he's going to talk about what this looks like an Android studio and the tooling that is coming soon to help you do just that. Thanks, Jonathan. So let's take a safe to use app on the

that we saw earlier are related and internet and related to an Android Android app bundle. What would that look like those Jonathan mentioned at this point you already have a pretty modular app built using the existing Android Studio plugin. You have a base teacher and a set of feature module. It relates really nicely to the Android app bundle. The only difference is that your face teacher is now comdot Android application and that your feature modules are just using the Cradle plug-in comdot Android. Damn it then I'm a future in the future will be releasing tooling to support full

unification of these to format your Android app bundle will simply be in Centennial hills. So regardless of where you start from if it is moving to an Android or an Android app bundle that wants to be instant enabled you're going to be covered. So as I mentioned earlier Dynamic features, you can fill them today in Android Studio building apps that Dynamic features, but if you do want to publish them to production, they're still available as preview need to join the beta program on the Play Store. At the same time that we're releasing Dynamic features and making

them fully available will also be working on the tooling to instant enable your app bundle. Let me invite not back up here talk more about the future. Thanks. It was talked about big changes coming today. Firstly much leaner apsa possible and his normal multi multi APK and secondly Dynamic features are out as a beta now. I'd like to encourage you to imagine how you use these capabilities in the future and make you sit in for your own app. As you've heard using the Android app bundle

and Google Play Dynamic delivery, you'll be able to create highly configurable modularized apps that can be adapted to different users and different use cases. So your preliminary experience can be lean and instant. With additional features provided to users on the mine as they need it which of your features are only used by a fraction of your users. The capabilities will allow you to create different versions of your of the same feature to different device types such as low memory and high memory

devices. It will also enable you to do live experimentation with different versions of the same functionality without making your app bigger and you can find out which variant works the best Infuse your success what's sensitive user Journeys and you're at like a check out path could benefit from that sort of experimentation. We're moving away from the world of giant installs to World of modular app development. Instant app experiences and dynamic delivery apps will be richer

yet that we smaller. and more efficient both on disc and Over The Wire we encourage you to stop thinking about how you use these capabilities to improve your install conversion. Stop thinking about how you use these capabilities to lower your uninstall rights and stop thinking about how you use them to build Richard experiences that helped you to improve engagement with your app. Android apps are evolving and we're excited to see what you can build with these capabilities

and we stopped today old developers can now build Android app bundles in the latest Canary the release of Android Studio 3.2 and upload them to the play console. You don't need to refactor your app to get started. You can get started on the web at G. Co / Android app bundle and you can get started with modularization and dynamic features in the canary to those who are ready to stop publishing apps with Dynamic features can apply to join the beta on the website to find out more attend the session right after this one on stage to wear out engineering team

going to share some technical Deep dive about building the bundle and using the new client Library enabling Dynamic delivery. Thanks and have a great day.

Cackle comments for the website

Buy this talk

Access to the talk “The future of apps on Android and Google Play: modular, instant, and dynamic ”
Available
In cart
Free
Free
Free
Free
Free
Free

Access to all the recordings of the event

Get access to all videos “2018 Google I/O”
Available
In cart
Free
Free
Free
Free
Free
Free
Ticket

Interested in topic “Software development”?

You might be interested in videos from this event

September 28, 2018
Moscow
16
159
app store, apps, development, google play, mobile, soft

Similar talks

Raj Ajrawat
Global Product Specialist Lead at Google
+ 3 speakers
Ignacio Blanco
Engineering Lead at Google
+ 3 speakers
Shobana Ravi
Software Engineer at Google
+ 3 speakers
Prafulla Rawal
Product Manager at Google
+ 3 speakers
Available
In cart
Free
Free
Free
Free
Free
Free
Alberto Medina
Developer Advocate at Google
+ 1 speaker
Thierry Muller
Engineering - Developer Relations Program Manager at Google
+ 1 speaker
Available
In cart
Free
Free
Free
Free
Free
Free
Ibrahim Karahan
Partner developer advocate at Google
+ 2 speakers
Pierre Lecesne
Senior Software Engineer at Google
+ 2 speakers
Anthony Morris
Software Engineer at Google
+ 2 speakers
Available
In cart
Free
Free
Free
Free
Free
Free

Buy this video

Video

Access to the talk “The future of apps on Android and Google Play: modular, instant, and dynamic ”
Available
In cart
Free
Free
Free
Free
Free
Free

Conference Cast

With ConferenceCast.tv, you get access to our library of the world's best conference talks.

Conference Cast
558 conferences
22059 speakers
8190 hours of content