Nativescript: Initial load time too slow? Webpack not working either.

[jpmoney]

Dear friend, we, the rest of the NativeScript community really
appreciate your feedback! While we are doing all we can to take care of every
issue, sometimes we get overwhelmed. Because of that, we will consider issues
that are not constructive or problems that cannot be reproduced "dead".
Additionally, we will treat feature requests or bug reports with unanswered
questions regarding the behavior/reproduction for more than 20 days "dead". All
"dead" issues will get closed.

Please, provide the details below:

Did you verify this is a real problem by searching Stack Overflow and the other open issues in this repo?

I have done searching through and found the issue with no actual solution other than using webpack. I have not been able to have any webpack examples actually build and run on an Android device. The device I was testing with was a Samsung Tab A running Android 5.0

Tell us about the problem

Please, ensure your title is less than 63 characters long and starts with a capital
letter.

After building a brand new blank application as well as testing many of the example applications the framework performs extremely well other than the fact that the initial load time is usually ~8-10 seconds. I cannot release an app that takes 8 seconds to load. After doing some research the only solution I found was to use webpack. However none of the examples will run for me. Whether from a blank test app or from the groceries example I haven't been able to get anything using the --build command to run on an Android device. Additionally I noticed that the log always outputs that Angular 2 is running in development mode which I know having developed a traditional Angular 2 app slows down the initial load. If anyone has any suggestions that would be great because it is frustrating using such a powerful framework but putting one label with Hello World causes a 10 second load time...

Which platform(s) does your issue occur on?

iOS/Android/Both

Only tested on Android so far.

Please provide the following version numbers that your issue occurs with:

• CLI: (run tns --version to fetch it)
• Cross-platform modules: (check the 'version' attribute in the
  node_modules/tns-core-modules/package.json file in your project)
• Runtime(s): (look for the "tns-android" and "tns-ios" properties in the
  package.json file of your project)
• Plugin(s): (look for the version number in the package.json file of your
  project)

Please tell us how to recreate the issue in as much detail as possible.

tns create test-app --ng
cd test-app
tns run android

Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.

[NathanaelA]

A couple comment;

1. Release mode is considerably faster than debug mode (hint: use --release)
2. PAN (Plain Awesome NativeScript) is way faster than NAN (NativeScript ANgular)
3. Getting WebPack to work for NAN is pretty critical, makes a MAJOR speed difference. Use --bundle after getting the nativescript-webpack installed, should normally handle most the issues. But check the NS-webpack repo for issues you might have to work around...

[jpmoney]

Thanks so much for the quick response! Just wanted to clarify a couple things:

1. My understanding was that the --release flag simply supports the signing of the app for release to the Play or App Store. I was not aware that this actually affected the build performance. If that is the case than I will perform a quick test with a keystore and see if that improves anything.
2. As far as you know WebPack should be working fine with NAN? If that is the case then I can spend a little more time investigating why for some reason I can't get mine to build. Do you know of any working WebPack / NAN examples I could test against?

Thanks again

[NathanaelA]

1. In 2.4, SnapShots were defaulted on for release mode; so doing --release actually makes a big difference for startup time.
2. WebPack I can't really answer for the new version; they recently released a new version of webpack that supposedly fixes most the issues with PAN & NAN, but I haven't tried it yet. You can see the issues and how to install here: https://github.com/NativeScript/nativescript-dev-webpack -- The earlier version actual had several issues that I had to work around to make work for PAN or NAN projects. But once you got it working you were good, and it made a considerable difference in launch speed.

[jpmoney]

This gives me some stuff to work with I'll see if I can get WebPack to work thanks.

[Dutchboy]

@Nicklliev why did you close this issue while no solution to the problem was given?

We are almost living in May, I have read the same issues starting in October, and still no real solution??

[NickIliev]

@Dutchboy we have documentation article on bundling with WebPack here and at this very moment, you should be able to bundle your Andro8id application with no hassle.
Also, you can take a look at these suggestions on how to measure and improve your loading time (for both NAN and PAN apps).

Let me know if you are still experiencing issues bundling your application with webpack - and if so please provide details on your workflow so we could reproduce your caseI have closed this one here as there was no activity since January and from that time we have multiple updates on nativescript-dev-webpack and on the WebPack bundling.

[x00]

My loading is slow too

standard build ~ 15 seconds
bundle + uglify + snapshot ~ 10 seconds
release ~ 10 seconds
release + uglify + snapshot ~ 10 seconds

[x00]

I repeated this with the hello world angular app

standard build ~ 15 seconds
bundle + uglify + snapshot ~ 5 seconds
release ~ 5 seconds
release + bundle + uglify + snapshot ~ 5 seconds

this is quite long time for a simple app. I agree it is an improvement on 15 second, but with he minimum of complexity this goes up.

To put this in perceptive from a fresh start Whatsapp loads in 2 second, Chrome Canary loads in 3 second not including the last web page (which load in 1-2 seconds on my network for a yahoo/google.com)

[x00]

I think basically I need to ditch angular...

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.