Android can run on <1GB RAM devices, and I'm willing to bet WSL's port runs a lot less background services. Couple that with Hyper-V VMs being able to release memory back to the host and it probably won't be too bad. (Maybe even lighter than some Electron apps)
Are you comparing a wrapper around a native app(chromium) to an app running on an OS emulated on a VM, with non-physical connection to a physical drive?
I guess the drive bandwidth itself would punish an app enough. Random disk reads and writes are no where near native performance.
Android over vm is much worse than electron, for wide usage.
Would you say WSL2 apps are meaningfully heavier than "native"? Because I'm not sure that's the case, and this is just the same. And just like WSL2, you're running a VM with much less background services and bootstrappers.
Drive bandwidth is really no concern here, you have so many Android phones with I/O much worse than computer SSDs. Not everything is a flagship with UFS 3.0+.
I’ll give you an analogy.
Imagine an Engine directly connected to the wheels, rather than a drive train vs via axle and drive train. Even if the engine is the best or even the worst, there is a loss of energy happening when its not connected directly.
Similarly you are putting more effort on PC to get similar performance of a mid range phone by pushing the energy via drivetrain(VM). Electron is just a wrapper around a native app. Teams is based on it. Then Teams on android running on PC would be based on an entire VM.
Wsl2 apps are not heavy, but they’re limited by the performance penalty of using a drive train(vm).
And apps on android are performant on phones because, there is only one app running the UI in foreground, and many OEMS cheat by killing background services.
I see no sense it makes to run an Android native app when PC alternative is available.
If the app has ended up using flutter or react native, the would be 3 abstracted layers deep.
VM->android->js/dart vm->app
