Getting started

⚠️ Update OTA(Over the Air) only works on HTML, CSS, JS changes. When you update native code (capacitor plugin), you must resubmit to the app store.
In auto mode, part of logic is handled by the Native code, updates are decided server side, this is more secure and allow fine grain update Partial deploy to one device or group and more.
In manual mode, all the logic is handled by the JS, that some good and some bad in both scenario.
In V4 you can use Capgo cloud with manual

Good ✅
Bad 🥲

Good ✅
Bad 🥲

The roadmap is handle in GitHub
Roadmap

The plugin and the back-end are open source and under the LGPL-3.0 License for the plugin and AGPL-3.0 License for the back-end.
💡 LGPL-3.0 mean if someone modify the code of the project, it’s mandatory to publish it, in open-source with same licensing. If you use the code without modification, that doesn’t concern you. See issue below for more details : https://github.com/Cap-go/capacitor-updater/issues/7

  • When you develop, if you use the Ionic live reload feature from the CLI, it will override the plugin, so you will never see your update.
  • Same issue with Quasar live reload
  • Big app update (> 20mb) will have a big percentage of user who doesn't get the last version. Users need to keep the app open until download is done.

If you use this tool for free, take time to support my work with GitHub sponsor.
I made a bet to open source all the code I built here.
I could have kept it for myself and put a high ticket price.
Instead, I want to make it an open and transparent business.
I do think it would make our world a better place by opening instead of fighting and hiding.
To make it possible, it is necessary for all of us to do our part, including you 🥹.
If Capgo cloud offer can't suit you, back a bootstrapped Maker HERE on your own terms.
Last modified 5d ago
Copy link
Edit on GitHub
On this page
Join Discord Community
Choose between Auto and Manual
Auto
Manual
Roadmap
Open source
Know issues
Last words