@daniel @chockenberry this is likely due to the requirement of ‘equal’ capabilities afforded to other browsers. I suspect this is less ‘hahaha screw them! we hate PWAs!’, and either a time-thing (didn’t get to it) or a risk thing (api to do it would be abused by 3rd party browsers to fill your home screens with crap)