Part of this is because the UI paradigms for a good touch UI and for a good desktop UI for mouse/keyboard are completely and totally different.
A smaller part is that Android basically requires Java or an oddball Java-derivative (Kotlin) unless using hacks to try and make applications originally targeted at X/wayland kinda sorta work on a tablet like this Andronix thing, and most desktop Linux applications are NOT done in java
Yes, that would be theoretically nice. Maybe at least, from an image management / organizational viewpoint.
But for me, a mobile device ā even a tablet ā is at best a temporary stand-in for a desktop or laptop. I find touch-UIs and small(er) screens are OK when Iām away from my computer, but thereās no way I would choose to work via them if a better UX is available (i.e., if Iām not limited to them, being on the road). Tablets and phones are vastly better than nothing, but far inferior to an actual computer. For that matter, I donāt even care for touch screens on computers. Of course, thatās personal preference.
Now, if an Android tablet could be used to replace my cheap Wacom, with the image being edited visible on the tablet and on my monitor, then I might be interested. But for me itās painful to try and do Actual Work on a mobile device.
Iām having a hard time wrapping my head around OSMand being considered FLOSS. Maybe it was less restrictive, but currently it is crippleware of the worst kind.
You get 7 downloads of maps. Period. Whether they are updates or not, then you have to pay.
Doesnāt fit my concept of FLOSS.
If a dev wants to provide a paid version with extended capabilities, I can wrap my arms around that. But crippleware, never ever.