> (To preempt a facile counter-argument: yes, a native app can be coded very silly, do busy wait or whatever, and eat all the cpu/battery/memory. We're interest

> (To preempt a facile counter-argument: yes, a native app can be coded very silly, do busy wait or whatever, and eat all the cpu/battery/memory. We're interested about baselines and what happens "everything else being equal"). But everything else is not equal. If I don't have to develop a native app for iOS and Android, I can dedicate double the amount of resource to the PWA version (or triple, if I was planning to do it anyway), which means I can decide to make it performant (or add more functionality, if I don't care much about my customer's battery).