|
|
|
|
|
by tennis_80
1065 days ago
|
|
This doesn’t surprise me. A user has a need - in this case a food diet app. They find this app, think it looks good, and registers their interest. Good. Launch day comes around, they’re nowhere to be seen - why? Well, they may have found another app, or decided they don’t need the app after all - say they lost interest in the diet / health kick. I feel like app registrations would only work for “special” apps that don’t have close competitors or have a particular buzz - e.g. Threads, ChatGPT etc EDIT: I’ve misunderstood - the app was supposed to auto-download on launch day. It didn’t. This story makes a lot more sense now! I assumed it just sent a push notification / email. |
|
In the docs it makes it clear that there are a bunch of caveats to the auto installation. Reading through these caveats, they are all there for good UX reasons, essentially to ensure that what gets advertised is what gets installed (no bait-and-switch), and that users are going to be ok with the auto-installation (doesn't eat all their data or battery life). There is advice on how to improve eligibility, it's not clear if the author followed this or not.
The eligibility factors will vary from user to user, and may between user bases as well. For example if you have an app that is popular with users on devices with less storage space, there are likely to be more who can't install it because they don't have enough space.
One or more of these factors may not have been met for the author/publisher of this app, and it's also possible that their target market also doesn't meet the conditions for auto-install as much.