I am not familiar with the hybrid approach, I will make some researches about it.
However, as soon as we bring in natives apps (iOS/Android) wouldn't we lose some of the PWAs benefits in terms of reusing the same developers and reduce the time to market (skipping the store approval)?
However, as soon as we bring in natives apps (iOS/Android) wouldn't we lose some of the PWAs benefits in terms of reusing the same developers and reduce the time to market (skipping the store approval)?
I'm not the resident expert on the apps but the thing is they don't subtract anything from the PWA, you can still use that as it is. The goal is to be able to enhance it with native APIs in a limited set, this way you can get the best of both worlds without too much effort.
Thanks! What do you think about the hybrid approach?
DEV's iOS and Android app are written with that approach, basically creating a shell around the web app:
Why Not React Native? Why Not Flutter? Why Not Meteor? Why Not NativeScript?
Ben Halpern ・ Oct 26 '18 ・ 2 min read
ps. the link to pwastats.com is broken :)
Thanks for the hint about the link, fixed now 👍!
I am not familiar with the hybrid approach, I will make some researches about it.
However, as soon as we bring in natives apps (iOS/Android) wouldn't we lose some of the PWAs benefits in terms of reusing the same developers and reduce the time to market (skipping the store approval)?
I'm not the resident expert on the apps but the thing is they don't subtract anything from the PWA, you can still use that as it is. The goal is to be able to enhance it with native APIs in a limited set, this way you can get the best of both worlds without too much effort.
But yeah, it's more work than just having the PWA
Sounds good. I will look deeper into it. Thanks for giving the hint!!