Signup for the Ionic Newsletter to get the latest news and updates!

  • Tom McLellan

    Max, it’s awesome that you’re transitioning Ionic to be a UI framework that can enhance (not replace) major frameworks like Angular, Vue, and React.

    As an iOS dev who moved to Ionic 1, I’m a huge fan of what your team has done and that you’ve given us a transition path from Ionic 3 to pure Angular. That said, I’m migrating a v3 project with 50K lines of code right now to Ionic 4 / Angular and it’s an expensive effort with so many changes.

    In the spirit of Angular 2 becoming “just Angular”, do you think Ionic 4 will be stable and final enough that it becomes “just Ionic”?

    Anyway thanks for all the ongoing builds and improvements, excited to see what’s next!

    • Max, Ionic CEO

      Hey Tom, yes, that is our goal. We don’t anticipate the core of Ionic changing much going forward. We have no reason to rebuild or redo our components or how they are used, as they are just plain web components now. The thought of that is really, really nice!

      What _could_ change is anything depending on framework stuff. For example, if we support a router for Framework X, then if that router changes that will mean breaking changes for Ionic users using Framework X. However, I think that’s fair because that would require changes for all users of Framework X and thus would be part of using that framework.

      • Tom McLellan

        Sounds good, that seems totally fair for framework bindings, appreciate the way you’re handling that with NavController.

  • Simon Grimm

    Good job on focusing again on your core values and taking a huge step with v4!

    I’m sure people will love it and the reduced maintenance/upgrade work they will have once their apps use v4. Plus of course the benefit that Ionic becomes a lot more attractive to developers of other Frameworks like React.

    Excited to see what great tools you’ll ship over the next year now that you can focus on more important aspects than framework integration again 🙂

  • SĂ©bastien BatĂ©zat

    Hey Max,

    It’s really awesome. I wish stencil will be used all around the world and tons of great WebComponents will be shared.

    However, could you please tell us more about Capacitor, which is your worldview instead of using the existing ecosystem? Will Capacitor be compatible with UWP apps?


    • Max, Ionic CEO

      We will be talking more about Capacitor soon. As for being compatible w/ UWP that’s on the roadmap but not working right now. However, we support Electron so you can get a windows app that way.

  • misha130

    But why not just use Angular to build Web Components instead of Stencil? I understand you started Stencil before Angular 6 with Web Components was released but whats the point of that now? I mean you talk about how Ionic is best in doing UI and then you go off to make a framework that is similar to Angular in a way.

    • Max, Ionic CEO

      It’s a fair question. If you look at Angular Elements it’s not yet ready when looking at size and load performance. We couldn’t do a lot of the things we did with v4 and stencil if we went that route. I’m optimistic it will improve but now we control all our tooling and there’s something to be said for that.

  • Loke Sonne

    I’ve built ionic v3 apps, but really disliked Angular’s templates and multiple declarations for every single service/component. Because I like the ionic UI components I started building React app using them. It went mostly well, but got into some trouble when using click events. I switched to StencilJS and it has just been smooth sailing. With TSX, the Stencil/Redux wrapper and ion-router everything just works. Why would I need a framework? The virtual DOM seems an unnecessary abstraction, and I already mentioned my gripes with Angular. I don’t have any experience with Vue but, for now I can’t see why I should. Keep up the good work!