- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
“Google is constantly optimizing and tweaking its apps through various A/B tests, and the latest one for the Play Store has us scratching our heads quite a bit. We’ve noticed that the familiar and handy install button is disappearing for some in the Play Store’s search results, which means that you actually have to tap through to the full app listing to install an app. This behavior isn’t in place for all results and apps, though, making the tweak feel arbitrary and random…”
You must log in or register to comment.
Google’s constant A/B testing is really tiring and confusing. One day a feature is there, next day it’s nowhere to be found
For about a month, my Google Hone app swapped between a new interface and the old one about once every couple days. I was never sure what I was going to get.
Of all companies out there, I’d expect Google to be able to run an a/b test right. You don’t learn anything of value by constantly pulling the rug out from underneath people.
they probably are doing it ‘right’, at least by their own definition. a/b testing for a company like google is more about what generates the most revenue, not what pleases the product… err, users… most.
Even still, without a consistent experience over a reasonable amount of time, all you’re really monitoring is novelty or discombobulation. You’re not learning which interface generates more money.
This only makes sense if discombobulation makes the most money.
I personally dislike that the notifications icon in the Play Store app shows me ads instead of app updates.
The problem with this kind of testing is that they do not ask you whether or not you want to be a part of this particular form of testing, and by default opt you into it.
There’s a need for this kind of testing to be uninformed and unbiased. I think better implementation would be to stay consistent and have a longer span of data collection instead of changing it under a week…
Then suggest it. Ask the user if they want to test it.
It’s not like the average user, after finding an issue, is gonna go and review it on the Play Store. More often than not, they will just be pissed off that it changes so often.
My grandmother HATES the new Phone Call chip. She liked the bubble, and I agree. And the number of times Google has pushed the update and rolled it back for her and everyone else in my family is extremely annoying.
I like to beta test apps. They don’t give a fuck.
And Google has the beta testing opt in feature in the Play Store. It’s ALREADY A FEATURE! Why would you not respect your own rules?? Wtf Google?!
The experiment isn’t really valid with optgin data, but that doesn’t mean there’s a need for it. That’s entirely contingent on whether the experiment is needed at all, and most of the time these things are about squeezing one last drop of blood out of a dead corpse. And I’d argue that that’s not something that’s needed.
Few corporations will do that, real purpose is to understand user behaviour and test which flow is the fastest and easiest to understand for users .
True, and I wish they were at least transparent-ish about it. Show me that I just got something enabled. Or disabled.
deleted by creator
Plus, this way at least people have to navigate to the result page before being able to install trash on their phones. It increases the chances of users figuring out they’re looking at malware marginally, but every little bit helps.
Wake me when we discover Google charging app developers a premium to put an install button in search results.
It seems that this is a safeguard:
When you search for an app’s specific name, you likely already know what you want to get, and you probably just want a quick way to install it without going through any hassles. However, if you have a more generic term or if you’ve confused one app for another, it might make sense to first take a proper look at the detailed listing in order to avoid installing the wrong app or, worse, a phishing or scamming app (some will always slip through Google’s malware and abuse scanners). In those cases, Google likely wants to enforce this extra tap to make sure to at least give you the chance to read up on the app, its description, and its reviews before you tap that install button.
I guess it makes sense. Aurora Store (a FOSS frontend for the Play Store) doesn’t have install buttons in the search results at all, and F-Droid only has install buttons in the search results for apps without “anti-features” (i.e., potentially worrisome privacy practices, etc.).
I have the update and it makes sense to me. I don’t want to accidentally click install while scrolling through search results. The arrow functions as a drop down preview of the app for easy comparison. The install button is still there on the main app screen.
Do apps really install the moment you press the button on Android? On iPhone you have to confirm through Face ID or by entering your passcode first.
Yes, in my experience.
Installation is just the same as getting an app on desktop and telling it that yes, you do want to run it. (I know that sometimes requires a password, but sometimes it doesn’t and I’m not sure why but that’s how Android Play Store installations work).
It depends on whether or not your account is setup to request authorization each time.
Aurora users unaffected
I think that’s already the default behaviour on Aurora!
Google playing catch-up 😔
