joeruelle on Nostr: I think that's a fair argument, but on the basis of ethics or principles. Not on the ...
I think that's a fair argument, but on the basis of ethics or principles.
Not on the basis of team size or tech stack, as many of these teams don't have anything to point fingers at there.
On the tech stack side it could be their design is simply optimised for native APIs. PWAs can’t fully plug into the accelerometer, gyroscope, ambient light sensor, bluetooth, USB on and on. Geolocation on a PWA can be of by many meters more than on a native app. And so on. There are a lot of things you can only do on a native app—or you can do a very watered down version on a PWA that people at best don't find nice—and at worse hate.
These are make or break things when it comes to the business side.
Or it could be down not to native APIs but rather deep-link integration with other native apps, or just certain market dynamics when it comes to attracting foot traffic and so on.
Basically there are many reasons to have empathy for teams that would love to go all in on PWAs but don't.
Not on the basis of team size or tech stack, as many of these teams don't have anything to point fingers at there.
On the tech stack side it could be their design is simply optimised for native APIs. PWAs can’t fully plug into the accelerometer, gyroscope, ambient light sensor, bluetooth, USB on and on. Geolocation on a PWA can be of by many meters more than on a native app. And so on. There are a lot of things you can only do on a native app—or you can do a very watered down version on a PWA that people at best don't find nice—and at worse hate.
These are make or break things when it comes to the business side.
Or it could be down not to native APIs but rather deep-link integration with other native apps, or just certain market dynamics when it comes to attracting foot traffic and so on.
Basically there are many reasons to have empathy for teams that would love to go all in on PWAs but don't.