我拥有一个大约30万用户的Android应用程序。
该应用最初是一个Android应用程序,仅我转换为扑朔迷离以发布iOS版本。
当我发布使用Flutter开发的第一个更新时,我只部署了5%,然后更新为10%,以确保此新版本没有重大问题。
然后,我更新到部署至100%。
现在,我已经根据Flutter发布了我的第三个新应用程序,将所有国家 /地区的部署设置为100%。
但是,在大约3周后,我只看到大约10%的用户在播放控制台中更新该应用程序。
我知道Flutter与X86手机不兼容,但这些X86仅占Android手机的1%。我还必须将Minsdkversion从19个更新为20,但这再次不应影响太多的用户。
我还阅读了应用程序尺寸可能会影响安装和更新,但是使用颤动降低了尺寸。
我不明白为什么我的应用程序仅在更新后3周将所有用户中的10%更新。我在游戏机中看到约90%的用户仍在使用上一个应用程序版本,并且我仔细检查了所有国家 /地区的部署均设置为100%。
感谢您的任何提示,您可以为我提供。
I own an Android app with about 300K users.
This app was initially an Android app only that I converted to flutter in order to release an iOS version as well.
When I released the first update developed using Flutter, I deployed only 5%, then updated to 10%, to be sure there was no major issue with this new version.
I then updated to deployment to 100%.
I have now released my third version of this new app based on flutter, setting a deployment of 100%, available in all countries.
But I only see about 10% of the users updating the app in the play console, after about 3 weeks.
I know flutter is not compatible with x86 phones, but those x86 represents only 1% of the Android phones. I also had to update the minSdkVersion from 19 to 20, but again this should not impact so much users.
I also read the app size could impact installations and updates, but the size was reduced using flutter.
I do not understand why my app is updated by only 10% of all users more than 3 weeks after the update. I'm seeing about 90% of my users in the play console still using the previous app version, and I double checked the deployment was set to 100% in all countries.
Thanks for any tip you can provide me.
发布评论
评论(1)
因此,有一些原因我可以指出为什么会发生这种情况:
为避免这些问题,您可以做一些事情
请确保拥有a 检查最新版本,然后提示用户,如果 版本!=最新_version&&版本<最新_version 。
将FCM发送给用户,其中 版本<最新_version 。
尝试在同一版本(0.1.1至0.1.2)中发布另一个次要更新,然后检查其统计信息(可能是更新统计数据的最佳方法)。
希望它有帮助,让我知道。
so there are a few reason i can point out why this is happening :
To Avoid these issues , u can do a few things
Make sure to have a version check inside app that checks for latest version and then prompts users if version!=latest_version && version< latest_version.
Send a fcm to users where version < latest_version .
try publishing another minor update within same version (0.1.1 to 0.1.2) and check it's stats (its probably the best way to update stats).
Hope it helps , let me know.