Opinion: Core functionality should not rely on 3rd party or community plugins #6188
livesemantics
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Capacitor has a set of "official plugins" which I think is a bit random.
On the one hand, it contains esoteric plugins like Google Maps (3K weekly downloads in npm), or "fake" plugins like Motion.
On the other hand it is missing some of the most basic core functionality needed by many apps.
For example, the ability to track screen orientation (or to dynamically lock/unlock) was always a core plugin in Cordova.
But in Capacitor, not only is it not part of Capacitor core, but it doesn't even have an official plugin (and also not a community plugin). In fact, according to Capacitor docs:
So Capacitor is basically acknowledging that many apps need it, but then refers to a plugin that hasn't been updated in over 3 years, and is broken for the past 3 months (since the release of iOS 16).
Another example is the ability to request reviews. This is probably needed by at most apps, but there's no official (nor community) plugin for it.
I think that basic functions that are an integral part of iOS / Android SDK (such as screen orientation and requesting reviews) should be included in Capacitor Core, or at least as official plugins.
Community plugins are great for 3rd party stuff (Facebook login, Admob, FCM etc) but core functionality should not be managed by the community. As much as I appreciate the good folks in open source community, the fact that every change to mobile SDK can break apps for months on end before members get around to fixing, makes any app that rely on community plugins simply unsustainable.
Beta Was this translation helpful? Give feedback.
All reactions