Google, please fix Android's slow, bloated share UI
androidpolice.com
androidpolice.com
I feel like they're trying to do something extremely sophisticated and it's coming out far far worse than if they were doing something extremely simple.
Even just basic user testing of such a fundamental part of a project--sending data between apps--would reveal what an obvious gap this is.
But maybe with all of these “smart” solutions to problems I’m attributing to malice what can be explained by incompetence and the people building them don’t even realize they’re terrible.
Or maybe they do realize it’s bad but they all say “Yeah it sucks now, but once we figure out how to make it work it’s gonna be great.”
This sums up my experience with a huge portion of the Google ecosystem. It's not just Google, of course, but Google particularly sticks out.
It feels like Google really likes to be clever, and just never had anyone take them aside and explain that clever solutions are usually bad. Sometimes I wonder if that extends to their codebases as well as their products; I'd love to be a fly on the wall and hear the conversations that are leading to some of the decisions they make.
much like the android stuff in the original article, it's just broken, and is a poor experience.
Google employees are mostly interested in building new stuff, not fixing broken old stuff.
There's also no central design authority for Google's Android. Each team implements the same thing in multiple different way.
Which is a shame, because there are plenty of people who would happily fix the bugs in the open source version of Android - but Google doesn't accept patches.
is this true that google won't accept public patches? are there any examples?
You'll be hard-pressed to find any recent patches from the public. There are some from hardware manufacturers and other organisations like that.
By contrast supportlib, which has a _much_ lower barrier to entry, sees considerably more patches (opened & merged) from non-Google and non-major organizations: https://android-review.googlesource.com/q/project:platform/f...
Even though this issue has been acknowledged internally but the above strategy is still the most promising when it comes to moving up the ladder.
Outside of the UI consistency issue, simply caching the share link index would largely fix the problem...
The UI consistency problem is the harder problem to solve and a common issue across Android apps, although not anywhere near as bad as it used to be. Maybe Google should publish some guidelines around share button placement? But I'm not sure how that would work exactly... but Google should definitely lead the way here (Youtube using a completely different icon is a great example).
This makes it seem like it is an amateur design issue, where callbacks are perhaps being called much more often than they are needed. How often does your 'most contacted' list need to change anyway?
They just need to implement some intent caching with invalidation callbacks that active apps can call (or push updates to).
Seems so childishly simple from all the way up here, wonder why they haven't done it already.
You need to launch flashy products and APIs to have the promo committee look at your packet properly. Unsurprisingly, promo driven development ensues.
Whether or not they'd see the light of day is another question, but it's surprising that stupid issues like this aren't tackled more by the people suffering.
Here's my favorite iOS sharing frustration. Often I want to copy a link from Safari. Click the share icon, select copy from the share widget, switch to different app (or another Safari tab), tap paste. There's about a 50% chance that what gets pasted is the URL vs what was previously on the clipboard. I usually perform the share/copy step twice now before trying to paste but that only seems to improve the odds. This bug has existed since at least iOS 9 and occurs for me on multiple devices.
You're suggesting that they want to fix it at all, rather than build new, shiny things.
There has been a workaround for this with where you can customize the menu by redirecting all share intents to a specific app. There are cases where apps don't use the standard api for share intents, but in most cases this app works as expected.
I agree Android should have a built in function that provides this level of customization at the OS level. Google should also provide a uniform experience with all apps however I don't mind the fragmentation because it merely a side effect of backwards compatability. Specifically with Youtube, Google shows that they have share intents in mind and are simply experimenting ways to increase user engagement.
https://play.google.com/store/apps/details?id=com.andmadesof...
-----
I am not the author nor affiliated with the app in any way.
I would pay money for a good share adapter.
Andmade Share is a wee bit more configurable, tho. For example, Firefox adds two share targets for some reason: "Firefox" and "Add to Firefox". With Andmade Share I can enable only one of them; with Fliktu, it's either both or none as you can hide an entire app from the share menu but not just some of its static "sub-targets".
That being said, I prefer Fliktu.
And please, a headphone jack on the next pixel. Usb-c is awesome, keep that, but everything from airplanes to cheap karaoke machines in China still will forever use 1/8" jacks.
Sometimes I leave it for several seconds, no share dialog, so press it again, but low and behold it was just taking a really long time. Othertimes I wait and wait and wait and eventually conclude it isn't coming up after all.
After years of training you get better at sharing, very firm clear tap on share and then wait 10 seconds. But then someone else uses my phone and I tell them to share it for me and it goes horribly wrong and they can't quite believe how bad it is, just as I get used to it.
Currently on a Samsung Galaxy S6 but I have had this issue on all Android phones.
The order thing is insane, I wondered if this was all just my phone, maybe a rogue app or bad firmware update, so relieving to hear this happens to others.
also fix the fact that it moves and changes the order of things all the bloody time. that drives me nuts!
1) quite suboptimal
2) becomes bloated with time
But this is also not only Google's issue. If you direct share to a contact in Messenger, instead of just sharing whatever you wanted to, Messenger opens the share interface where you can select other people to share to. This is even though you wanted to share to just one.
I like to watch YouTube on Kodi, there's an Android app which can be used as a remote control, and load URLs into the playlist. In binge mode I see the related videos and think "Oh that also looks interesting", so I "share" a lot of videos within a few seconds. Video 1, hit share, look for the remote control app icon, press it, done. Second video, hit share, hunt for the icon because it has moved... Same thing every time! Luckily my phone is quick enough that the share menu doesn't take forever to load, and I've accepted that the icons move around, only quietly swearing "Stupid programmers" every time, but it's still stupid.