In this episode of Adventures in Angular the panel is Ward Bell, Alyssa Nicoll, Joe Eames, and Charles Max Wood. The panel talks to special guest Mike Hartington about Ionic. Tune in to learn more!

Mike is a developer for the Ionic framework. He helps people succeed on Mobile.

Ionic is currently going through an investigative phase. They are moving things to a vanilla JavaScript state and web component based architecture.

Throughout all different frameworks (such as Angular, React, Ember) and libraries have a similar concept of a reusable thing. It is a custom element they can ship, which becomes limiting. It only works in their specific framework because the API capability isn’t there. Ionic wants to make something that works in all frameworks.

No, talking about the web standard itself.

When implementing these experiments in new releases, it shouldn’t change for people who are currently using Ionic and Angular; everything pretty much stays the same. There is a slightly smaller payload, but that’s it.

More or less. There would have a single Ionic Angular package. Everything it needs to have the web components talk to Angular would already be including as soon as you started the entire app.

Yes, that’s the vision. It was the idea when we first started Ionic. It is easier to implement now than when Ionic first started.

Can still create something new within Ionic and have something more custom to your needs.

It shouldn’t. The code would not be heavy; it would be vanilla JavaScript. It would run outside of your framework. It could run faster because they are default APIs. It allows for an extra layer and everything Angular can do will still work with a web component.

Generally. The building time of an app is APIs Makes sense for application development but not controls.

Becomes more useful because web components uses browsers own APIs. Overall payload ends up being smaller. Smaller network area users can take advantage and it can be faster if a large desktop application is used.

Ionic understands hybrid technology is going to be around. Some people want distribution through an app and some just want a website. Ionic is catering to both parties. At the end, browser will implement APIs that native devices have.

Just released the numbers from a developer survey we sent out. There is a healthy mix between people who want a native binary and progressive web apps.

Ionic will continue pushing for progressive web apps.

He doesn’t know. Has seen a few people that has a HoloLens. In the future, Ionic could possibly use augmented reality.

Will speak about Ionic components across multitude of frameworks. How to take advantage of tools that Ionic has to use to create own custom components that work across all frameworks.

Alyssa:

Joe:

Charles:

Mike:

 

 

 

 

 

 

Special Guest: Mike Hartington.