First of all, thanks for checking out NativeScript, and also for providing this feedback on our forum
Those numbers look about right for the out-of-the-box experience, but there are two things you can do to optimize that app fairly significantly.
webpack: Our webpack plugin greatly reduces startup time by bundling your app’s files together, which means there’s a whole lot less file I/O going on when your app starts up. Make sure to use the
--uglify flag as that’ll add some tree-shaking optimizations that will take your app size down a bit too.
With these two optimizations your startup times should be under well under two seconds for simple applications on decent devices.
The reason we don’t have these optimizations on by default is because they slow down your build times fairly considerably, so we recommend only using these workflows for benchmarking and release builds. That being said, I do think we need to be better about telling our users that these optimizations are available... somehow.
I’m actually working on a documentation articled tentatively called “How to Build NativeScript Apps That Start Up Fast”, which will theoretically put all of these tips into a single easy-to-follow guide. But even once that exists we still have to come up with ways to help people find that article when they’re looking for these sorts of benchmarks. Any suggestion you have would be great.
And also feel free to follow up here if you have any other questions or thoughts. Since I’m actively writing documentation on this topic I’m especially curious about what you think here.