This post really shows how old I am, because I immediately thought “does anyone actually compose on a mobile device?” The experience is so bad I limit my own mobile compositions to message responses like “k” and “lol”.

I wrote this comment on my phone and it was an awful experience 🙃. But hey, at least my keyboard app suggested a silly emoji…

I’ll continue to do my “real” writing on my desktop for now. Integration apps like KDEConnect have been enough for me to get by, but they aren’t perfect either.

Bloody hell yes. I have to select text on my phone all the time and that little hovering Android context menu is utterly atrocious. How that passed any UX process is completely beyond me.

1. It hovers over text, rather than appearing in a predictable location like every other context menu in the OS does.
2. The menu just doesn’t appear sometimes. Usually when the selected text is large or near the edge of the screen or the screen is zoomed in.
3. It’s unstable. Every time you bring it up, the context sensitivity might add additional options. That context sensitivity is good, but it also means that one has to scan the menu for the desired option every single time, no matter how proficient one gets.
4. It’s uncustomisable. One of my most-used options requires me to select the text and wait for the menu, tap the three-dots to open the second layer of the tiny little context menu, scroll that tiny sub-list past a bunch of less-commonly used options to the option I use all the time, then tap on that. The menu is sorted arbitrarily, not even alphabetically, and is completely unmodifiable.
5. And what is given sort-priority over my actually used context menu items? “Share”. I can share text with two taps, which I will never do, but the action I use dozens of times a day requires three taps and a scroll to find it.