Ionic 3.0 - third time's the charm?

Ionic 2.0 vs. 3.0

It hasn't been that long since the Ionic 2.0 framework was introduced. During its use, inánáak individualásoldiersáfound minorábugs thatá led to prolongedáapplicationá development. The requirements were thusšened and tým Ionic brought a corrected butáequal new version.

Ionic 3.0 is not a completely newý framework, but the change is noticeable. The current version is built on top of the new Angular version 4.0.0. This is somewhat modified from the 3.x.x version on which Ionic 2.0 was built. This change brings&scaron& í a number of newý “features”, smaller&scaron& í size, more&scaron& í speed and stability of the application.

Move to a higheršší version

A major change is the transition to a higherší version of Typescript. Dáky version 2.2 will reduceátátheábuildá time of the application and mainly improveáená typeá control. Theále remainsává compatible with previousáversions.  

We need to continuously innovate. Gone are the days when inýarmyáers had to set allšsome application configuration in the root file. Ionic 3.0 bringsáší setá usingá the @IonicPage component on everyá pageášite. Theše becomesá clearerší and much more acceptableší. Díky téthis change makes itšeasierší to use the “lazy loading” pattern and thusé set the configuration of individualýpages.

Lazy loading

“Lazy loading” is already working in a newé version, but Ionic vývojá doesná t have enoughé answersá and ná zors from vývojá. This change has a hugeý effect not only on theé pageá but also on theé navigation in the application. A hugeé positiveá is the fact that the app dí dí té this change caná beá up to twiceá fasterší!

Theší advancement of theýwarás of Ionic will be focused on improving´ speed, stability and výcon of the application. If theýsoldierséof thisýframework succeeds, the speed of hybridýapplicationsécan&even&possibly&approach&the&nativeýspeed. Otherší steps includeé isš to´ improveš support for the desktop. Last but not least, we will not forget to fix bugs and errors that will be associated with the change of navigation in the application.