For larger modules that can take a few seconds or longer to download and. 
For smaller modules (~10 MB or less) that can be installed very quickly,Ĭonsider indicators such as spinners or a brief “downloading content”. Want to display might depend on the size of the download: To display the download progress and install state. User decides to download the feature from Google Play, display the progress of You should inform the user when a feature is not immediately available. Where you can anticipate that a user will need a particular module.Īfter you’ve read through this guide, see these best practices in action by Further optimize the module delivery experience, especially in situations. Ensure your users are aware and feel in control of relatively larger moduleĭownloads which don't load instantly, or module install errors. 
This page describes best practices that help you do the following: Than if the module had been present at app install. That is, the experience is typically no different In the typical case where these modules are relatively small (less than 10MB),Īnd there aren't any network or other failures, users can download and use an
Very high-resolution media experiences or VR/AR features. Specific payment or checkout capabilities. Large libraries for less used functionality such as providing detailed bug. Help and support functionality when most users don't seek help, or don't. Adding a recipe in an app, where most users only browse and follow others'. Editing and uploading a video in an app where the majority of users only. The following are aįew examples for app features that would appropriate on demand modules: Needed by the majority of your users at install time. The functionality that works well as an on demand module are those that aren't
0 kommentar(er)
