Any statement?

Sorry for the delayed response.

Your concern related to the startup time of Android app created using Crosslight has been forwarded to Crosslight development team. The report is filed under CROS-1130.

I'll keep this thread updated with any news I heard from the team regarding the progress of CROS-1130.

Any news about CROS-1130?

What about CROS-1130?

Hello Yudi,

is there already a schedule for CROS-1130?

It should be "high priority" on your list because the startup performance is quite poor at the moment.

Thanks,

Thomas

When will this be fixed? When will there be a new stable version of Crosslight?

@all

Thomas and I investigated the issue further by comparing the start-up time of plain Xamarin app and Crosslight app. Two projects are created, they are:

• project(1): Xamarin Android Blank app with splash screen;
• project(2): Crosslight project created using Crosslight Blank App project template.

By using these projects, we are going to compare the Android start-up time. Following is the start-up time measurement method:

1. Deploy each app in test device.
2. Use AZ Screen Recorder app (Third party application used to record Android screen. This app is available in Play Store. Can use other/similar application.) to record the screen.
3. Run the app on device.
4. Inspect the video (recorded by AZ Screen Recorder) using Camtasia Studio (Third party desktop application to edit video. Can use other/similar application.). Start-up time is measured right where user start to press the app icon and finish just before the splash screen is replaced with fragment.

Following are the results:

project(1): Xamarin Android Blank app with splash screen
Start-up time: 3.16 second.

project(2): Crosslight project created using Crosslight Blank App project template
Start-up time: 5.03 second.

project(2): Crosslight project created using Crosslight Blank App project template with SplashScreenLatency = 1
Start-up time: 4.11 second.

project(2): Crosslight project created using Crosslight Blank App project template with SplashScreenLatency = 0
Start-up time: 4.07 second.

Based on these result, set the SplashScreenLatency to 0 or 1 will improves the start-up time by 1 second. We consider this as normal (compared to Xamarin app start-up time) since Xamarin also needs to initialize Crosslight assemblies.

Anyway, considering your results it seems that Xamarin is the bottleneck and I guess you won’t or can’t do anything to speed up things.

Thank you very much, Thomas. Have a nice day.