Drael646464
New member
- Apr 2, 2017
- 2,219
- 0
- 0
Re: Microsoft admits Windows Phone is a dead platform... 
Meh, I mean something like a browser can surely be made to scale easily, running full win32. It's literally just a matter of re-arranging a little at the top and bottom for smaller screens. Certainly web apps run via html5 can scale. Fruity loops scales for a tablet, that's a win32.
I've seen games that are win32 run on small screens play fine.
I don't personally see win32 as fundamentally unscalable.
I see no reason why say, adobe illustrator, fruity loops, or movie editing or other power win32 software on windows can't be converted to scalable, and run on windows on arm on a smaller screen.
They don't specifically have to be coded as UWAs if mobile can run win32. Already programs can be made to run on both console and desktop/tablet without being coded as anything but win32. They can include touch without being anything but win32. Witcher 3, and several other win32 games are touch compatible. Extend that to mobile, and like with tablets, there is then motive to include touch and scaling.
Obviously some apps will always be appropriate for certain screen sizes. An app written specifically for a watch, might not have been coded to scale for a fifty inch screen and vice versa, but by and large the goal is to move everyone towards scaling.
Having apps that only work on small screens or big screens means you can never get real deep benefit out of simple things like miracast, VR, streaming things to your smaller device, and other convertible products.
Sure all those legacy apps might not scale well on a small screen. But that doesn't stop currently revising software and new released from being both win32 and touch friendly on a small screen. For some things their might be motive to do that rather than write UWPs. Such as games. Or pre-existing code that is harder to convert.

Seems simple to me, with the new devices it will run windows 10 mobile for appearance. Windows on arm for continuum, so use that feature and you get full windows on the desktop experience. That would surely be the way to go and how I think they will go. To abandon continuum which is what a5cent is suggesting for only w10arm is contrary to virtually everything we have had from Satya on mobile (which isn't much granted). That's the way I see it going, win32 apps surely not running in a 5 inch screen that would be horrid! But using continuum that 5 inch arm device could easily be powering full windows 10 on another device.
That's how I imagine they would want to take this, that is a truly cellular pc in my opinion, to dismiss the mobile element of that equation would be a foolish move on microsofts part.
Meh, I mean something like a browser can surely be made to scale easily, running full win32. It's literally just a matter of re-arranging a little at the top and bottom for smaller screens. Certainly web apps run via html5 can scale. Fruity loops scales for a tablet, that's a win32.
I've seen games that are win32 run on small screens play fine.
I don't personally see win32 as fundamentally unscalable.
I see no reason why say, adobe illustrator, fruity loops, or movie editing or other power win32 software on windows can't be converted to scalable, and run on windows on arm on a smaller screen.
They don't specifically have to be coded as UWAs if mobile can run win32. Already programs can be made to run on both console and desktop/tablet without being coded as anything but win32. They can include touch without being anything but win32. Witcher 3, and several other win32 games are touch compatible. Extend that to mobile, and like with tablets, there is then motive to include touch and scaling.
Obviously some apps will always be appropriate for certain screen sizes. An app written specifically for a watch, might not have been coded to scale for a fifty inch screen and vice versa, but by and large the goal is to move everyone towards scaling.
Having apps that only work on small screens or big screens means you can never get real deep benefit out of simple things like miracast, VR, streaming things to your smaller device, and other convertible products.
Sure all those legacy apps might not scale well on a small screen. But that doesn't stop currently revising software and new released from being both win32 and touch friendly on a small screen. For some things their might be motive to do that rather than write UWPs. Such as games. Or pre-existing code that is harder to convert.
Last edited: