Pre-loading of user applications including skipping of selected launch actions
A user device includes a memory and one or more processors. The memory is configured to store one or more user applications installed in the user device. The one or more processors are configured to select one or more operations, which are to be performed in normal launching of a user application but not in background pre-loading of the user application, to pre-load the user application before the user application is accessed by a user, including skipping the one or more selected operations, and to complete the one or more skipped operations in response to the user accessing the user application.
1. A user device, comprising:
a memory, configured to store one or more user applications installed in the user device; and
one or more processors, configured to:
select one or more operations, which are to be performed in normal launching of a user application but not in background pre-loading of the user application;
provide to the user application an Application Programming Interface (API), which enables the user application to distinguish between launching due to user access and launching due to background pre-loading;
upon determining that the user application is launched due to user access, launch the user application using the normal launching; and
upon determining that the user application is launched due to background pre-loading, pre-load the user application before the user application is accessed by a user, including skipping the one or more selected operations, and complete the one or more skipped operations in response to the user accessing the user application.
2. The user device according to claim 1 , wherein the one or more operations comprise at least one of:
an update of data analytics;
generation of an advertisement impression; and
a user-interface element that differs depending on whether or not it was already presented to the user.
3. The user device according to claim 1 , wherein the one or more processors are configured to track a pre-load status of the user application, and, in response to the user accessing the user application, to complete the one or more skipped operations based on the tracked pre-loading status.
4. The user device according to claim 1 , wherein the one or more processors are configured to pre-load the user application within an Operating System (OS) of the user device.
5. The user device according to claim 1 , wherein the one or more processors are configured to emulate a click of the user so as to trigger one or more of:
pre-loading of the user application;
refreshing of the user application;
pre-loading of in-app content of the user application; and
refreshing of in-app content the user application.
6. The user device according to claim 1 , wherein the one or more processors are configured to receive, from the user application, pre-loading program code that skips the one or more selected operations, and to pre-load the user application by executing the pre-loading program code.
7. A method in a user device, the method comprising:
selecting one or more operations, which are to be performed in normal launching of a user application but not in background pre-loading of the user application;
providing to the user application an Application Programming Interface (API), which enables the user application to distinguish between launching due to user access and launching due to background pre-loading;
upon determining that the user application is launched due to user access, launching the user application using the normal launching; and
upon determining that the user application is launched due to background pre-loading, pre-loading the user application before the user application is accessed by a user, including skipping the one or more selected operations, and completing the one or more skipped operations in response to the user accessing the user application.
8. The method according to claim 7 , wherein the one or more operations comprise at least one of:
an update of data analytics;
generation of an advertisement impression; and
a user-interface element that differs depending on whether or not it was already presented to the user.
9. The method according to claim 7 , wherein pre-loading the user application comprises tracking a pre-load status of the user application, and wherein completing the skipped operations comprises completing the one or more skipped operations based on the tracked pre-loading status.
10. The method according to claim 7 , wherein pre-loading the user application is performed within an Operating System (OS) of the user device.
11. The method according to claim 7 , and comprising emulating a click of the user so as to trigger one or more of:
pre-loading of the user application;
refreshing of the user application;
pre-loading of in-app content of the user application; and
refreshing of in-app content the user application.
12. The method according to claim 7 , wherein pre-loading the user application comprises receiving, from the user application, pre-loading program code that skips the one or more selected operations, and pre-loading the user application by executing the pre-loading program code.