Capgo
OTA update system for capacitor mobile app
Building a Capacitor app should not mean maintaining macOS runners, Android toolchains, signing scripts, provisioning profiles, and store upload steps by hand.
Capgo Native Build lets you build signed iOS and Android apps from any machine with one command.
You can run it locally, from CI, or from a teammate’s laptop. Capgo handles the native build job, streams live logs, signs the artifact, and can submit the build to App Store Connect or Google Play after a clean build.
The goal is simple: keep control of your code, CI, and release process, but remove the painful native build maintenance.
Built for Capacitor teams who want reliable mobile releases without babysitting Xcode, Android Studio, or custom CI runners.
Try it here: capgo.app/native-build
1 500 euro of recurrent income with Capgo.
I will soon earn as much as my first dev salary, almost 10 years ago.
It's not much, but at the same time it's huge, I've learned so much, entrepreneurship is a really efficient way to grow, especially when you're building by yourself, there's nobody else to blame but yourself.
If I were smarter, I'd probably do double or more already.
But that's ok, I learn each job one by one, marketing, design, sales, support.
My goal is to be average at everything, then automate as much as possible.
When you choose to stay alone in your business, automation is the key.
Next step, 5k revenue!
Few months ago Pieter Level adding Stripe climate to all of this project, I was inspired to do the same, not only for the better conversion but also because I believe in this kind of actions.
Since 4 years I do buy only clothes who have taken in account the ecologic impact,
I'm personally a shareholder of Time for the planet https://www.join-time.com/en
Capgo donate 5% of his revenue to Stripe climate and will become Shareholder of Time for the planet when I reach my goal of 3k revenue.
I also built the architecture to not consume many resources, all is serverless.
The only always up system is the database.
After talking a bit of Capgo in GitHub, Twitter and Reddit, I got some people to start trying the plugin.
I got so much feedback on the discord community, and it helped me to improve the documentation and remove tons of bug!
I even got people complaining about the price, who was impossible to find.
Yea, I wasn't confident enough to put a price from 0.
so, I let them register and use it for free, I just wrote in the documentation somewhere the paid plan is coming, with some price idea.
After some feedbacks from users, as I expected the main issue with capacitor-updater was the need of backend to store ZIP where the new code source is, and have a trustable process, currently if you load a broken version then your user is stuck with a broken app.
To resolve this issue, I started to build the auto-update feature with my own version server, I decided again to go for open source.
So, the backend function are host in Netlify and the database on Supabase.
It took me 1 week to make this work, it was easier since the base function were already working.
It took 4 weeks, but I'm finally done building the minimum viable product for Capgo. I worked mostly during Christmas and weekends, and I coded the whole thing in swift and java, it was still new to me and I couldn't do it without the help of some nice people from internet.
I made the most simple feature I could, nothing automatic, you have to save your update package somewhere and load it from the JS bridge, but that allow me to start speaking about it.
And got some GitHub stars, yes I have chosen to build it open source.
It's been since years i use ionic to make my apps.
From years, they provide a super solution to update your app without the hassle of app store review.
It's allowed by Apple only for JavaScript and HTML, not native.
That unfair advantage hybrids app have over native, but no one knows it because the only solution made is 2500$ mininum.
Ionic is an awesome company but they make business with big corpo, not makers !
1 Comment
This is a strong expansion because it moves Capgo from “OTA updates” into a much more painful part of the mobile release pipeline.
The positioning I’d lean into is not just “build from any machine.” It is reliable mobile release infrastructure without forcing teams to maintain fragile native build systems. That speaks directly to the real pain: Xcode runners, signing, provisioning, CI drift, logs, and store submission all becoming operational overhead.
One thing I’d pressure-test is the brand frame as this expands. Capgo works well around Capacitor updates, but Native Build sounds like a bigger infrastructure layer than the original OTA story. If this becomes the release system teams rely on for signed builds, logs, artifacts, and store delivery, the brand needs to carry more trust than a utility.
Davoq .com would fit that harder infrastructure direction better if you ever decide to separate or reframe the native build product as its own serious release platform. The product itself already feels like infrastructure; the name should help teams read it that way before they compare it to another build tool.
This feels especially worth thinking through now because release infrastructure gets sticky fast once teams put it into CI and store workflows.