Snark aside, if you have a native mobile app it is a much, much nicer experience to have native animations integrated rather than trying to mash an HTML view into the app just for some animations.
*Because programmers are the worst kind of pedants: Yes I know sometimes you can't afford to write native apps, sometimes a partial solution is better than no solution, etc. Just don't lie and tell me a web app is as good as (or better than) a native app, or that Cordova is a great way to write mobile apps. Those are compromises. Sometimes you make compromises to get shit done. It doesn't magically transform a compromise into an ideal solution.
That's another approach which has it's own pros and cons. The approach from the article is obviously good if you have Affect Effects experts on hand. I'm not understanding why this isn't interesting to programmers who on a daily basis have to weigh up the pros and cons of different technology/library choices.
Perhaps I'm showing my age, but this feels like this problem was solved a long time ago, forgotten or unused to a large extent and now re-invented. Flash was the clever web version back in the day but I can't see anything really new in this.
I could absolutely be missing the point though. I never count that out.