There There are two ways to prompt user to save your app, both use technique called - Custom Saving Prompt.
Table of Contents |
---|
- The INSTANT app saving, which appears right when a user first logs in into the link with your app, which is enough for most cases
...
2. The MANAGED app saving, which is much more complicated, but allows much more granular app saving, if necessary
The INSTANT app saving prompt
This is the prompt, which works for users on for every link you get from a Access Info tab. So if you use any of those links, thats the app saving you get - instant, right when a user access the app's link for the first time.
...
In any case make it short and make it meaningful, you only got 140 symbols.
Anchor | ||||
---|---|---|---|---|
|
This way you can have granular settings, like delays and condition to pop, as well as to decide with prompt pop up first - App Saving or Push request. You can For example, you might need to allow users browse your mobile website for say 10 seconds, before offering them to save the app.
Info |
---|
This managed and flexible prompt is prompts are ONLY available for ONE kind of link to your app - xxxxxxxxx.mobsted.com/pwa/NN?appid=NN Note, that the only thing you need to do to your long app link, at Access Info tab is to copy the APPID, which you see for the app, and insert it between the /pwa/ and ?appid= This way users will be routed to a managed app saving prompts. |
...
Info |
---|
The two app saving prompts have no infuence on each other, so you can use send users both kinds of link for different user experience. of links, depending on your exact needs in each moment of time. |
Related articles
Content by Label | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...