I was wondering lately on what is, as of today, the main issue with using nativescript + angular. My company is working with this awesome framework since the alphas of ns+ng, and we’re glad of the way it went.
As we are developpers, we tends to struggle to take a step back and see what are the main issues on our apps (bugs appart !) for the user point of view. I’m creating this topic to have an open discussion on the issue of startup time.
As far as I see it, startup time is the main issue for us. Why ?
- For our customers, first launch (fresh install) is long enough to trigger a “the app is not responding” - which is wrong and can be ignored by the user, but still.
- app launch is too long ! Seriously, this is a big deal. I’ve read a very promising thread from the nativescript blog about AOT compiling with webpack. I’ve not been able to make it work properly, and I’ve allocated an entire day to it. This raises to me one question, why is this not more documented ? A blog post is not enough on that, even if it’s a good start.
- Startup time is a big deal for us, because we experience a lot of “hard reboot” of the app when resuming the app (I guess it’s the default behavior when the resume sequence fails). Therefore, the startup time directly impacts the application lifetime, and is not experienced “just once” in the best case.
- Default package JSON imports the nativescript android snapshot (tns create xx --ng), which is responsible of a direct crash of the app when building signed APK. I’m raising this in that topic because this one is supposed to speed up startup time. weird.
Well, in a nutshell, I’m dropping this out to get things better !
I think that telerik’s goal is to have real apps running wiith ns, and I wanted to raise this up !