// the find
ionic-team/ionic-framework
A powerful cross-platform UI toolkit for building native-quality iOS, Android, and Progressive Web Apps with HTML, CSS, and JavaScript.
Ionic is a Web Components-based UI toolkit for building mobile apps that run on iOS, Android, and the web from one codebase. It wraps native-feeling components (built with Stencil) with Angular, React, and Vue bindings. The target is teams who want mobile app distribution without writing Swift or Kotlin.
The Stencil-based core compiles to actual web components, so the framework bindings are thin wrappers rather than reimplementations — when a bug is fixed in core, all three framework packages get it. The screenshot-diff test suite (Playwright, per-component, per-mode, per-direction) is unusually thorough for a UI library; pixel regressions get caught before release. The iOS/MD dual-mode design is genuinely useful — you get platform-appropriate styling without maintaining two separate component sets. Migration guides are maintained across every major version going back to v3, which matters because Ionic has a long history of breaking changes and users actually need them.
The Capacitor dependency for real native features is a separate project with its own release cadence; when Capacitor lags behind a native OS update, your Ionic app is blocked until they catch up — you don't control that timeline. Stencil as the compilation layer adds a build-time dependency that most teams don't understand well enough to debug when it misbehaves, and Stencil itself is maintained by the same small team as Ionic. The CSS custom properties theming system works but becomes unwieldy at scale — you end up with hundreds of undocumented variables and no tooling to find which ones actually affect which component. Performance on lower-end Android devices remains a known gap versus truly native; the web component layer adds overhead that shows up in scroll jank on older hardware.