How to define your install strategy
Skills:
Backend Performance60%
Key Takeaways
Discusses best practices for defining an install strategy across mobile experiences, including native app installs and progressive web apps
Full Transcript
[Music] [Applause] [Music] hi I'm Damian a well because he's thing consultant at Google in this talk you will learn how to define an install strategy across all your mobile experiences letting your users install your app is one of the best ways to keep them engaged today you can achieve that in different ways let's start with native app installs if you have a native application you might think that this might be the best platform to promote to all your users and for some of them this might be true but for some users native apps can have some disadvantages too the most common one is storage constraints making space for a new app may mean removing valuable content freeing up storage is also the number one reason users remove apps from their devices there's also the issue of available bandwidth especially for users on slow connections and expensive data plans finally moving to a store creates additional friction and delays a user action that could be performed directly in the web a great alternative to this is allowing users to install your progress he web app from the browser through another home screen prompt you can also upload your PWA to the play store using trusted web activity in this example came to under a real estate company from Brazil was able to reuse the same codebase in the world and the Play Store while offering a great experience to users let's take a look at another example all your rooms is one of the largest hospitality companies in India they have a very large user base coming from a variety of devices and networks they have built different versions of their mobile experience to satisfy the needs of all their users first I created a native application for the Play Store for the most sophisticated users this could be the best choice all you light is a progressive web app uploaded to Play Store be a trusted web activity it provides the same functionality of the nav bar well occupying only 7% of the space finally for users that visit the site directly by typing the URL or clicking on a link or offers the chance of installing the pedo directly from the home screen having all these ways to achieve app installs is great but how can you combine all these offerings to increase installation rates well I Bodi make your apps compete with each other let's discuss some strategies to combine different install offerings the first strategy is to show the different options in the same screen this is a simple approach that might just work for many users the challenge is to be able to communicate the value proposition to distinguish clearly one from the other but instead of delegating the choice completely to users we can make the life easier the idea of the following strategies is to make some inferences for example by tracking users behavior and device characteristics we call this heuristic based approaches the first one is web installed as fallback in this strategy you can start showing the native app installed prompt if the user doesn't install the app and keeps visiting to your website chances are that the web is their platform of choice after a while you can start promoting your pillow EA to these users this strategy can be implemented very easily for example by using cookies to drag user behavior the group of users that this means the abun huh keep coming several times to the side might be good candidates for a web install offering but before showing the web install call-to-action there are two more things to take into account the first one make sure that the user hasn't already installed your native app or your PDA by other means the Getty store related apps API can help you check that the second is actually a UX best practice to maximize the opt-in rate for your web install prompts you might want to use the double permission pattern in this example shows AG web install icon after capturing the before installed prompt event when the user clicks on it they trigger the standard Add to Home screen prompt if you want to learn about UX patterns for web permissions like this one check Deshea stock safe permissions for the capable web at crontab Sammy 2019 let's move now to the second strategy intuitively users on slow networks or low-end devices might be more inclined to download light apps therefore if it's possible to identify a user's device one could prioritize the light up over the heavier native app installed version you can implement this by writing a function checking for device characteristics to decide which prompt to show if it's a low-end device a light up if it's a high-end device you can offer the core native app inside the function the by signals can be obtained in two ways the first one is by using javascript api s-- like device memory hard work on currency or the network information API the second one is by using client hints which can be inferred from the header of the HTTP request to use them you need to send an asset CH gathering your response indicating the type of hints you want to receive for example device memory after that you will start receiving these hints in the header of the HCP request finally you can use this information to map to a device category and use that later to decide which prompt to show if you want to learn techniques on how to map the buy signals to device categories check out adaptive loading a talk that was given at random Sammy 2019 prepping us today you can offer different channels to users to install your model experiences for example you could offer an ad but ap delay available in the Play Store and iWeb installed from the user screen then you can define a heuristic to show the most suitable install offering to a particular user you can create a very simple one based on the user behavior on your site for example by tracking how often they come to it or you can go for a more sophisticated approach when mapping the buy signals to device categories and show different install offerings depending if the device is low mid or high end we encourage you to experiment with these techniques for example by running a be test and to reach out to us on Twitter to share your experiences I hope you continue enjoying what the Bligh's thanks for watching [Music] [Applause] [Music]
Original Description
This session covers best practices for combining different installation offerings to increase installation rates and avoid platform competition and cannibalization.
Related Playlist:
Day 2 → https://goo.gle/WDL20Day2
Subscribe to the Chrome Developers → https://goo.gle/ChromeDevs
Speaker:
Demian Renzulli
#webdevLIVE event: web.dev LIVE 2020; re_ty: Publish; fullname: Demian Renzulli; product: Chrome - General;
Watch on YouTube ↗
(saves to browser)
Sign in to unlock AI tutor explanation · ⚡30
Playlist
Uploads from Chrome for Developers · Chrome for Developers · 0 of 60
← Previous
Next →
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Polymer Performance Patterns (The Polymer Summit 2015)
Chrome for Developers
Polymer Power Tools (The Polymer Summit 2015)
Chrome for Developers
Chrome Dev Summit 2014 – Chrome Case Studies
Chrome for Developers
Web Directions Code 2015 round up
Chrome for Developers
Maintainable Code - HTTP203
Chrome for Developers
iron-ajax… wat?! -- Polycasts #26
Chrome for Developers
The Guardian - Supercharged
Chrome for Developers
ES2015 (next version of JavaScript), Totally Tooling Tips (S2 Ep1)
Chrome for Developers
#AskPolymer: Rob answers all the questions ever -- Polycasts #27
Chrome for Developers
The Future of JavaScript - HTTP203
Chrome for Developers
Data Binding 101 -- Polycasts #28
Chrome for Developers
The Guardian part 2 - Supercharged
Chrome for Developers
The Future of Web Audio: with Chris Wilson and Chris Lowis
Chrome for Developers
Chrome 46: New motion-path animations, client hints and service worker improvements
Chrome for Developers
Sublime Snippets, Totally Tooling Tips (S2 Ep2)
Chrome for Developers
#AskPolymer: How do you make the show? -- Polycasts #29
Chrome for Developers
Critical Path CSS, Totally Tooling Tips (S2 Mini Tip #1)
Chrome for Developers
Binding to Objects -- Polycasts #30
Chrome for Developers
Player FM - Supercharged
Chrome for Developers
Where’s the Designer? #AskPolymer -- Polycasts #31
Chrome for Developers
Jake Beats Wikipedia - HTTP203
Chrome for Developers
Supercharged Observers! -- Polycasts #32
Chrome for Developers
Jai's Web blog - Supercharged
Chrome for Developers
Windows Command-line Tooling, Totally Tooling Tips (S2, Ep4)
Chrome for Developers
What about internationalization? #AskPolymer -- Polycasts #33
Chrome for Developers
Developing for Billions (Chrome Dev Summit 2015)
Chrome for Developers
Google+ Performance Improvement Comparison
Chrome for Developers
Deploying HTTPS: The Green Lock and Beyond (Chrome Dev Summit 2015)
Chrome for Developers
Progressive Web Apps (Chrome Dev Summit 2015)
Chrome for Developers
Instant Loading with Service Workers (Chrome Dev Summit 2015)
Chrome for Developers
Increase Engagement with Web Push Notifications (Chrome Dev Summit 2015)
Chrome for Developers
Engaging with the Real World: Web Bluetooth and Physical Web (Chrome Dev Summit 2015)
Chrome for Developers
Asking for Permission: respectful, opinionated UI (Chrome Dev Summit 2015)
Chrome for Developers
Polymer - State of the Union (Chrome Dev Summit 2015)
Chrome for Developers
Building Progressive Web Apps with Polymer (Chrome Dev Summit 2015)
Chrome for Developers
Introduction to RAIL (Chrome Dev Summit 2015)
Chrome for Developers
DevTools in 2015: Authoring to the max (Chrome Dev Summit 2015)
Chrome for Developers
RAIL in the real world (Chrome Dev Summit 2015)
Chrome for Developers
#ChromeDevSummit talks are up - W00T! -- Polycast #34
Chrome for Developers
V8 Performance from the Driver's Seat (Chrome Dev Summit 2015)
Chrome for Developers
Quantify and improve real-world RAIL (Chrome Dev Summit 2015)
Chrome for Developers
Owning your performance: RAIL (Chrome Dev Summit 2015)
Chrome for Developers
HTTP/2 101 (Chrome Dev Summit 2015)
Chrome for Developers
Leadership Panel (Chrome Dev Summit 2015)
Chrome for Developers
Build Processes, Totally Tooling Tips (S2, Ep 5)
Chrome for Developers
Accessibility (Chrome Dev Summit 2015)
Chrome for Developers
Binding to Arrays -- Polycasts #35
Chrome for Developers
HTTP2 - HTTP203
Chrome for Developers
Chrome 47: Splash Screens, requestIdleCallback and better desktop notifications (New in Chrome)
Chrome for Developers
Call For Submissions - Supercharged
Chrome for Developers
Cross Device Testing, Totally Tooling Tips (S2 Ep6)
Chrome for Developers
Testing AJAX with Web Component Tester -- Polycasts #37
Chrome for Developers
Slack: Extended Xmas Special - Supercharged
Chrome for Developers
Browser testing with Travis & Sauce Labs -- Polycasts #38
Chrome for Developers
Optimize for production with Vulcanize -- Polycasts #39
Chrome for Developers
Highlights from Chrome Dev Summit 2015
Chrome for Developers
Chrome 48: Custom buttons in notifications, DevTools Security panel, and Presentation mode
Chrome for Developers
Crisper: Protecting your Polymer app with CSP -- Polycasts #40
Chrome for Developers
How do I use Sass with Polymer? #AskPolymer -- Polycasts #41
Chrome for Developers
Colors – DevTools Tonight #0 (Pilot)
Chrome for Developers
More on: Backend Performance
View skill →Related Reads
📰
📰
📰
📰
Swift typealias — What It Is, What It Does, and Why It Matters
Medium · Programming
s3fifo 1.0: Zero-Allocation S3-FIFO Cache for Node.js is Ready for Production
Dev.to · JeongSeop Byeon
Node.js Error Handling Patterns for Production Queue Systems
Dev.to · Faisal Nadeem
Make Your CLI Config Write Survive Ctrl-C Without Leaving Truncated JSON
Dev.to · Sam Rivera
🎓
Tutor Explanation
DeepCamp AI