Meet the Capacitor Team
The Capacitor team maintains the core Capacitor runtime, its plugins, and the tooling that supports them. If you’ve opened an issue, reviewed a pull request, or followed a release, you’ve already seen this team’s work in action.
Alongside our open-source responsibilities, we’re also one of several teams that enable mobile development within the OutSystems suite, helping ensure Capacitor and plugins integrate cleanly into the broader platform.
If you follow Capacitor closely, some of these names or GitHub handles may already be familiar. Here’s a closer look at the people behind them.
Eric Horodyski
GitHub: @eric-horodyski
Favorite Language: TypeScript
Engineering Manager for the Capacitor team. Former Ionic Solutions Architect.
Pedro Gomes
GitHub: N/A
Favorite Language: N/A
Product Manager for the Capacitor team.
Pedro Bilro
GitHub: @OS-pedrogustavobilro
Favorite Language: Kotlin
Software engineer focusing on Android.
Rui Mendes
GitHub: @OS-ruimoreiramendes
Favorite Language: TypeScript
Software engineer focusing on iOS.
Chace Daniels
GitHub: @ItsChaceD
Fun Fact: I love working with Web3; my current favorite JS framework is Astro.
Started coding in high school, now focused on making Capacitor the best cross-platform framework and ecosystem.
Alex Jacinto
GitHub: @alexgerardojacinto
Favorite Language: Kotlin
Software engineer with focus on mobile development and Android.
André Destro
GitHub: @andredestro
Favorite Language: Swift
Software engineer focusing on iOS.
Joesph Pender
GitHub: @theproducer
Favorite Language: Swift/C++
Software engineer with a background in graphic design, web, and iOS development.
Mark Anderson
GitHub: @markemer
Fun Fact: I’ve worked with Swift since the Xcode 6 beta, integrating it on release day—essentially as early as possible in production.
Done everything from handcrafting transistors, to chip design, to (mostly) iOS mobile programming in the last 15 years or so.
Much of the work behind Capacitor happens in the open, alongside a wide community of contributors and maintainers. We’re grateful for the care, collaboration, and feedback that help keep the project moving forward — both from the people on this team and from the community that works with us every day.
