Cordova support waning, Capacitor is more popular?

mobile
21

Unfortunately, yes. Browser OS bugs, parity between browser capabilities to native functionalities, and performance are limiting factors of PWA. That’s where Capacitor comes in. (I don’t hope of coming back to Cordova since we dropped it in favor of PWA).

There is hope that Chrome/Google is pushing for that functional parity for Android. Hope in ios seems to rely on how far EU (and the US?) can force Apple. Performance seems like a limitation on the language/engine level (although even Capacitor has that limitation).

22

I haven’t heard anything official from Meteor about switching from Cordova to Capacitor yet, but with the trend, it could happen eventually. Keep an eye on the roadmap for updates!

23

It’s official as it’s listed in Candidate items

24

One limitation - I think - for PWA apps is that they don’t have access to Apple & Google’s store purchases infrastructure.

Mine is a consumer app and I think I would be at a big disadvantage if I couldn’t use app store-managed subscriptions.

25

And since you are using RevenueCat

2 Likes
26

Thanks.

Regards the In-App Purchases for PWA, I see this in the headline:

how we wrangled Swift to integrate in-app purchases in iOS PWAs

I’m not in a position where I can afford to do any “wrangling” to get basic things like purchases to work. It just works in Capacitor and Cordova. That’s what developers are expecting.

If Meteor want to go PWA instead of Capacitor, that’s fine by me. I just hope it properly supports everything mobile apps need.

The RevenueCat Web SDK uses Stripe, not in-app purchases, so it’s not a substitute.

27

FYI: I created a new feature request for this at Replace Cordova with Capacitor (or similar) · meteor/meteor · Discussion #13562 · GitHub

1 Like