The problem, imo, is that Google dropped the ball, and nobody really picked it up. And by dropping the ball i mean the gradual rolling back of distinctiveness

The problem, imo, is that Google dropped the ball, and nobody really picked it up. And by dropping the ball i mean the gradual rolling back of distinctiveness between Android tablets and Android phones. With 3.0/honeycomb, Android tablets got a distinctive interface with a single system bar, aimed at using tablets primarily in the landscape orientation. Alongside this the first generation of Android tablets often shipped with a full size USB A port, to allow connecting things like storage and input devices (3.0 also introduced basic HID support to Android). But come 3.1, Google did the inexplicable move of introducing a new set of storage permissions distinct from the "external" RW permission that had existed since Android 1.0. There were "media" RW permission, specifically set up to cover removable storage. The real problem was that by default the write half of the permission set was exclusive to system apps, meaning apps bundled with the device. End result was that Android went from being a potential production platform to being a straight media consumption platform. Then as 4.x rolled on, more and more of the tablet UI was rolled back, replaced with a variation of the 4.0 phone UI. This culminating in 4.3-4.4 where the single bar was fully removed on all sizes of tablets, replaced with a dual bar setup where the bottom bar would move to always be at the bottom (on phones it sticks to the portrait "bottom"). And while MS seemed poised to pick this up with Windows 8/10, they largely fumbled. For example UWP apps are not allowed to access anything but the users home area, unless they make a specific request and the user approves. But the approval has to happen via the age old win32 file picker dialog, that is a right pain to operate using fingers. This then leaves us with the equally old file explorer to handle file management. And not only is it still a win32 program, though now outfitted with a ribbons UI, but it is the same process as is operating the overall Windows UI! Similarly win32 programs still have a close button everpresent on screen, making it easy to close those by grabbing the device by upper right corner. Never mind that the Windows 10 tablet UI has sprouted a Android-like back button, but that do not interact with win32 programs except to send them to the background. Nor is there a good indication that something is running. You have to basically tap the switcher button (same one used to handle multiple desktops in desktop mode), and see if anything pops up. All this result in the best option for using Windows "tablets" is to prop them on some surface and attach enough devices to use them as ad-hoc desktops.