ARM has some distinct problems for consumer use: 1. Historical tight coupling of components (necessary for SoCs in embedded products such as Smartphones) means

ARM has some distinct problems for consumer use: 1. Historical tight coupling of components (necessary for SoCs in embedded products such as Smartphones) means there is no standard to build an ARM PC. This means vendor lock-in, difficulties upgrading, and even more proprietary blobs than you get with PCs. 2. No desire by vendors to change #1. PCs being customizable and piece meal upgradable is something that vendors would like to go away. Samsung and Apple would love it if ARM desktops took over, they make their own ARM chips, they would sell you a computer with 16GB of soldered on memory, 256GB of storage built in, and if you wanted to change that you'd have to buy a new machine. Want a new graphics card? New machine. Imagine all the nightmares of laptops, except that every computer is like that. For corporate, professional, and enthusiast users, this is very bad. A lot of the scenarios you talk about are actually possible today, indeed demos of those scenarios have been floating around for ages. The CPU architecture is not the hard part, both Google and Microsoft's app stores have packages that run on both x86/x64 and ARM just fine. Real problems are things like real time syncing and collaboration, real time migration of entire app state from one device to another, and creating a good user experience around this. Making a cool demo where one app transitions from a smartphone to a PC screen is not that hard, and you can see many tech demos of that uploaded to YouTube. Making that work across all apps, in general, and making an app UI that works just as well on Mobile as on Desktop and maybe also on Tablet, that gets harder.