What are the differences among the various loading strategies available in the settings option of vDesigner?

vDesigner 2.0
1

I’m planning to create a new build, so what criteria should I use to select one of these loading strategies?

2

Hi @Harshit, when creating an embedded configuration build with a deployment check for environments other than sandbox—like UAT or production—it’s best to follow this strategy.

Here’s a brief overview of the other build loading strategies:

  • Eager: With the Eager loading strategy, all configurations load simultaneously when you initiate the build. This approach works well for smaller builds.
  • Lazy: In the Lazy loading strategy, configurations load gradually, page by page. This method is ideal for larger builds.
3 Likes
3

Hi @Ved. Can you explain more on this?

4

@Harshit

The lazy Build Loading Strategy depicts a scenario in which you log in to an application’s dashboard. Then, only the Configurations of Dashboard will load which results in less buffering time and efficient working of the build on the other hand in the Eager Build Loading Strategy, all the configurations of the application will load at once when you log in to the Dashboard Page, that’s why this strategy is only suitable for the small size builds only.

2 Likes
5

Thank you @AnushkaGupta for explaining.

2 Likes
6

There are two additional strategies available, both of which are crucial for production apps:

  1. Embed Configuration Only:
    In this approach, all the application’s configuration is embedded within the app during the build process via the internal CI/CD pipeline. This eliminates the need for an API call to fetch configurations at runtime. However, it won’t contact the server to retrieve updated configurations. If you need to update any configuration, a new version of the app must be distributed. This method is particularly beneficial when the app is distributed through app stores like the Google Play Store.
  2. Embed Configuration with Deployment Check:
    Similar to the “Embed Configuration Only” strategy, this approach minimizes API calls by embedding the initial configuration within the app. However, it includes an additional deployment check. If a new configuration has been synced on the server, the app will fetch only the updated or differential configuration from the server. This balances reducing API calls with ensuring the app remains updated when changes occur.
2 Likes