RU2786200C1 - System and method for installing a personalised application on a mobile device - Google Patents

Abstract

FIELD: computing technology.

SUBSTANCE: invention is intended for installing an application on mobile devices. The technical result is achieved using the method for installing a personalised application on a mobile device, wherein the application distribution source is determined by analysing the parameters of the operating system of the mobile device modified as a result of receiving the application from the application distribution source; application resources corresponding to the determined application distribution source are selected from the resource base; a personalised application is generated by converting the application received from the application distribution source based on the selected resources, and the generated personalised application is installed on the mobile device.

EFFECT: ensured installation of a personalised application on a mobile device.

20 cl, 3 dwg

Description

Technical field

The invention relates to the field of creating and distributing software for mobile devices, and more specifically to systems and methods for installing a personalized application on a mobile device.

State of the art

The rapid development of computer technology in the last decade, as well as the widespread use of various computing devices (personal computers, laptops, tablets, smartphones, etc.) have become a powerful incentive for the use of these devices in various fields of activity and for a huge number of tasks (from the Internet to surfing to bank transfers and electronic document management). In parallel with the growth in the number of computing devices, the amount of software running on these devices has also grown.

A paradoxical situation has arisen when different computing devices (or different users, different categories of users) often use almost the same programs from the same manufacturer for different tasks, differing only in minor, “cosmetic” details. For example, two different distributors can distribute the same application with different logos or interface elements, designed to work on computing devices of different categories of users.

This situation has led to difficulties in creating and distributing software. On the one hand, you have to spend additional resources (both temporary and human) on creating a large number of modifications of the same application, on the other hand, you have to spend additional resources on placing the created modifications on various distribution sources of applications (for example, in application stores similar to App Store or Google Play, various cloud services, etc.).

Currently, the described problem is solved in various ways. One way, for example, is to create large distributions that already contain all the necessary application modifications, the resources required by each modification, and allow you to install on users' computing devices only the application modifications necessary for these users. Another example is an approach where some universal applications are updated with only required application components or resources.

US8631456B2 describes a hypermedia navigation technique (Nelson, T. H. (1965). "Complex Information Processing: A File Structure for the Complex, the Changing and the Indeterminate" in ACM '65. Proceedings of the 1965 20th National Conference: 84-100 , Cleveland, Ohio, USA: ACM DOI:10.1145/800197.806036 Nelson:1965:CIP:800197.806036) using multiple synchronized I/O device sets. The disclosed systems and methods allow a user and/or application owner to control which device resources are presented on which set of devices (whether they are integrated or not) and provide for coordination of browsing activities such that such a user interface can be used across multiple devices. independent systems.

Yet another publication, US10409862B2, describes a technology for delivering content (including applications) on a mobile media platform providing automated tag processing and content delivery to a mobile device, where content delivery is based at least in part on automated tag processing.

Each of the described solutions has both its advantages and disadvantages, which are especially pronounced when it comes to mobile applications, that is, applications installed on mobile devices.

The present invention solves the problem of installing a personalized application on a user's mobile device.

Disclosure of invention

The invention is intended for installing an application on mobile devices.

The technical result of the present invention is to install on a mobile device, depending on the source of its distribution.

The technical result of the present invention is to personalize the application when it is installed on a mobile device.

This result is achieved by using a system for installing a personalized application on a mobile device, which contains: a source determination tool designed to determine the source of distribution of the application by analyzing the parameters of the operating system of the mobile device that have changed as a result of receiving the application from the source of distribution of the application; a resource handler for fetching from the resource base those application resources that correspond to the application's distribution source determined by the source determiner; generating means for generating a personalized application by converting the application obtained from the application distribution source based on the resources selected by the resource working means; an installer for installing the personalized application generated by the generating means on a mobile device.

In another particular case of the system implementation, the content of the clipboard acts as one of the parameters of the operating system.

In another particular case, system implementations change the operating system parameters through the use of an external reference to the application.

In another particular case of system implementation, an external link to a mobile application is preliminarily generated through an intermediate service, which additionally redirects to the application distribution source.

In another particular case of the system implementation, the intermediate service provides data on the application distribution source through at least: an API provided by the application store; the clipboard of the user's device on which the corresponding application will be installed.

In another particular case of the system implementation, the resources characterize at least: the elements of the multimedia application, the functionality of the application.

In another particular case of system implementation, at least the following are used as a resource: multimedia data; text lines; licenses; scripts describing the functionality of the application; modules that provide the functionality of the application.

In another particular case of the system implementation, if there are no resources in the resource base corresponding to a certain application distribution source, resources corresponding to the standard assembly of the application are selected from the resource base.

In another particular case of the system implementation, the resource base is part of the application distribution package obtained from the application distribution source.

In another particular implementation of the system, the resource base is a remote service, wherein resources are selected by at least: updating an application obtained from an application distribution source; direct download.

This result is achieved by using the installation of a personalized application on a mobile device, while the method contains steps that are implemented using tools from the system for installing a personalized application on a mobile device and in which: determine the source of distribution of the application by analyzing the parameters of the operating system of the mobile device, changed in the result of obtaining an application from an application distribution source; select from the resource base those application resources that correspond to a certain application distribution source; generating a personalized application by transforming the application obtained from the application distribution source based on the selected resources; install the generated personalized application on the mobile device.

In another particular case of the implementation of the method, the content of the clipboard acts as one of the parameters of the operating system.

In another particular case, the implementation of the method changes the parameters of the operating system through the use of an external link to the application.

In another particular case of the implementation of the method, an external link to the mobile application is pre-formed through an intermediate service, which additionally redirects to the application distribution source.

In another particular case of the implementation of the method, the intermediate service provides data on the distribution source of the application through at least: an API provided by the application store; the clipboard of the user's device on which the corresponding application will be installed.

In another particular case of the implementation of the method, the resources characterize at least: the multimedia elements of the application, the functionality of the application.

In another particular case of the implementation of the method as a resource are at least: multimedia data; text lines; licenses; scripts describing the functionality of the application; modules that provide the functionality of the application.

In another particular case of implementing the method, if there are no resources in the resource base corresponding to a certain application distribution source, resources corresponding to the standard assembly of the application are selected from the resource base.

In another particular case of implementing the method, the resource base is part of the application distribution package obtained from the application distribution source.

In another particular implementation of the method, the resource base is a remote service, wherein resources are selected by at least: updating an application obtained from an application distribution source; direct download.

Brief description of the drawings

Fig. 1 is a block diagram of a system for installing a personalized application on a mobile device.

Fig. 2 is a flow diagram of a method for installing a personalized application on a mobile device.

Fig. 3 represents an example of a general purpose computer system, a personal computer or a server.

Although the invention may have various modifications and alternative forms, the characteristic features shown by way of example in the drawings will be described in detail. It should be understood, however, that the purpose of the description is not to limit the invention to a particular embodiment thereof. On the contrary, the purpose of the description is to cover all changes, modifications included in the scope of this invention, as defined in the attached claims.

Description of embodiments of the invention

The objects and features of the present invention, methods for achieving these objects and features will become apparent by reference to exemplary embodiments. However, the present invention is not limited to the exemplary embodiments disclosed below, but may be embodied in various forms. The gist of the description is nothing but the specific details necessary to assist a person skilled in the art in a thorough understanding of the invention, and the present invention is defined within the scope of the appended claims.

Let us introduce a number of definitions and concepts that will be used in describing embodiments of the invention.

Application personalization (can also be understood as application customization) is the individualization of products for the orders of specific consumers by making structural or design changes (usually at the final stages of the production cycle). An example of personalization is changing the interface of an application depending on the target group to which the user of the application belongs (for example, an application for a target group that has chosen a trial version of the application or for a target group that has chosen a paid version of the application that includes more complete functionality or has more personalization options to choose from). applications).

Personalized application (customized application) - an application on which personalization (customization) has been performed, i.e. an application formed for the orders of a particular consumer by making structural, design or functional changes.

Application Distribution Source - a service or data storage that provides, upon request, the selected application to the user's mobile device. And in a particular case, providing an application to a user's mobile device includes installing the application on the user's mobile device from an installer file or assembling the application on the user's mobile device from intermediate modules. One example of an app distribution source is app stores like Google Play apps, App Store, etc.

Installing an application on a mobile device - a set of actions that includes at least placing an application on a mobile device (in particular, by downloading an application to a mobile device or building an application from elements provided by other applications, for example, an application installer or an application distribution kit), setting up operating system settings for the operation of the specified application on the mobile device.

Fig. 1 is a block diagram of a system for installing a personalized application on a mobile device.

The block diagram of the system for installing a personalized application on a mobile device consists of an application distribution source 100 , an application 101 , a source determiner 110 , a resource worker 120 , a resource base 121 , a generator 130 , a personalized application 131 , an installer 140 .

These means run on a processor using memory and may be implemented as elements of a computer system or collection of computer systems, described in more detail in FIG. 3 .

The distribution source of application 100 is at least:

• storage directly on the mobile device itself, while the application 101 can also be the application distribution package;

• a server containing an application 101 to be downloaded to a mobile device 100 , where the server is granted access through an application store, where the application store may provide an infrastructure including an application running on the mobile device and interacting with an external service;

• the server hosting the site from which the application 101 is downloaded to the mobile device.

For example, the app store could be the App Store for apps for iPhone mobile devices and Google Play for apps for Android mobile devices.

In one embodiment, the distribution source of the application 100 is the site, which is only an intermediate node between the user's mobile device, on which the personalized application 131 will be installed, and the server that stores the application 101 (or the service that provides the application 101 ), from which a personalized application 131 will subsequently be formed. At the same time, the specified site is additionally intended for changing the parameters of the operating system of the mobile device (see below).

Application 101 is a mobile application, and said application may be intended for different categories of users, which in turn may require said application to provide different functionality or appearance (including a different interface).

The source determiner 110 is designed to determine the distribution source of the application 100 by analyzing the operating system parameters of the mobile device changed as a result of receiving the application 101 from the application distribution source 100 .

That is, in the process of downloading and/or installing the application 101 on a mobile device, the parameters of the operating system of the mobile device change, and such changes depend on the distribution source of the application 100 .

The operating system parameters that can be changed are at least:

• contents of the operating system's clipboard;

• the amount of used RAM or the amount of free RAM;

• data on services launched on the mobile device;

• Settings that describe your Internet connection and how your browser works (which includes things like your home page URL, favorites, bookmarks, cookies, security settings, phone connections, and proxy settings).

Changing the operating system parameters depending on the distribution source of the application 100 is carried out at least:

• when installing application 101 (for example, using a special installer application);

• due to the peculiarities of the operation of applications (for example, the browser) in the operating system, when downloading the application 101 , the operating system parameters are changed (for example, the address of the last download is recorded in the browser history).

For example, when installing an application from Google Play, the corresponding installer application indicates to the operating system that it is downloading and installing the application. In this way, the application 101 and the distribution source of the application 100 can be unambiguously linked.

In one embodiment, one of the operating system parameters is the contents of the clipboard.

For example, when placing application 101 on a mobile device using a special installer program or using a browser (if application 101 was placed on a mobile device by downloading application 101 from the site), information characterizing the distribution source of application 100 and representing at least:

• application distribution source ID 100 ;

• resources needed to create a personalized application 131 .

After the application 101 is placed on the mobile device and launched, said application 101 reads the information from the clipboard and generates the personalized application 131 . In this case, the resource manager 120 , the builder 130 , and the installer 140 can be considered to partially implement the functionality of said application 101 .

In another implementation, the operating system parameters are changed through the use of an external link to the application 101 . To implement this functionality, an intermediate site is used between the mobile device and the application distribution source 100 . In this case, the application 101 is directly located on the distribution source of the application 100 (which may be another site or other remote service), and the download and installation of the application is carried out by clicking on the link to the above intermediate site in the browser. The specified intermediate site redirects the request to download the application 101 to the distribution source of the application 100 (in this case, such redirection is not transparent to the user), and additionally, for example, by executing a javascript script, changes the parameters of the operating system of the mobile device on which the specified application 101 is downloaded , for example, writes to the clipboard information characterizing the distribution source of the application 100 .

In another implementation, an external link to a mobile application is pre-formed through an intermediate service, which additionally redirects to the application source.

That is, if the application is not distributed through the application store and is not installed on a mobile device using specialized applications, it can be distributed through regular sites in the form of links. In this case, the application 101 can be hosted on one site, and links to the specified application 101 can be both direct and through other sites (that is, when the link leads to a third-party site, from which the user is then redirected via a direct link to the site, which is not transparent to the user). , on which the specified application 101 is located).

With this implementation of the distribution of the application 101 , the specified application downloaded from different sites will be considered different applications, and different personalized applications 131 will be generated.

In yet another implementation, the intermediate service provides information about the distribution source of the application 100 through at least:

• API (from the English application programming interface - application programming interface), provided by the application store;

• the clipboard of the user's device, on which the respective application 101 will be installed.

The resource handler 120 is designed to retrieve from the resource base 121 application resources corresponding to the application distribution source 100 determined by the source determiner 110 , where the resources are at least:

• correspond to the multimedia elements of the application 131 ,

• set (ie describe what functions, how and when should be performed during the operation of the application and the interaction of the application with the user or other applications, services, etc.) the functionality of the application 131 .

In one implementation, the resource is at least:

• multimedia data (eg graphic themes for applications);

• words, tokens, text blocks (for example, in the form of text strings);

• licenses (in the form of files, raw-data, etc.);

• scenarios describing the functionality of the application 131 ;

• modules that provide the functionality of the application 131 .

For example, the multimedia data may be images used to form the interface of the application 131 .

In another example, the scripts describing the functionality of the application 131 can be the rules for user interaction with the interface of the application 131 .

In another implementation, if there are no resources in the resource base 121 that correspond to a certain distribution source of the application 100 , resources corresponding to the standard assembly of the application are selected from the resource base 121 using the resource tool 120 .

For example, the resource base 121 may contain graphic themes for the application 131 - unique themes for applications distributed by multiple partners, and a generic theme for an application received by users from other sources.

In yet another implementation, the resources that the resource base 121 works with are stored directly in the application distribution obtained from the application distribution source 100 .

For example, resource base 121 is itself a resource (eg, a packaged data archive) that is contained within application 101 .

In yet another example, resource base 121 may contain an image resource of application interface elements 131 that is contained within application 101 and from which images are selected by resource manager 120 depending on the distribution source of application 100 .

In yet another implementation, the resource base 121 is a server providing a remote service, with the resource engine 120 selecting resources through at least one of:

• by updating the application 101 obtained from the distribution source of the application 100 ;

• via direct download.

Creator 130 is designed to generate a personalized application 131 by converting the application 101 received from the distribution source of the application 100 based on the resources selected by the resource handler 120 .

In this case, obtaining the application 101 from the distribution source of the application 100 consists of at least:

• downloading and subsequent installation of application 101 ;

• receiving an update to an application 101 or a personalized application 131 (including an update to the resource base 121 );

• downloading and subsequent execution of the distribution kit of the personalized application 131 .

Moreover, the transformation of the application 101 with the formation of a personalized application 131 as a result is, in a particular case, an assembly of a personalized application 131 using modules (components) and resources of the application 101 .

For example, a custom application assembly 131 may be:

• formation of a personalized application 131 using the application distribution 101 , in this case the application distribution 101 contains modules that the specified distribution kit installs on the mobile device and forms links between them, thus compiling the specified personalized application 131 ;

• recompilation of the application 101 to obtain a personalized application 131 with the disconnection or connection of the models of the specified application.

In one of the implementation options, the formation of a personalized application 131 is carried out by generating the resources of the application 101 to which the specified application has access.

For example, as the formation of application resources 101 can be:

• generation of resources based on other resources (for example, generation of some images from other images, selection of images from other images (the so-called "slicing");

• allocation of resources from other resources (for example, if the application resource 101 is an archive containing the resources of a personalized application 131 ).

In another embodiment, the formation of a personalized application 131 is carried out by assembling the specified application from the components of the application 101 .

In another embodiment, the formation of a personalized application 131 is carried out at the distribution source of the application 100 . In this case, builder 130 runs on application distribution source 100 .

For example, the formation of a personalized application 131 distributed through the Google Play application store can be carried out on the side of the specified service using the provided SDK (from the English software development kit - “software development kit”).

In yet another embodiment, the generation of the personalized application 131 is carried out after installation on the mobile device and the first launch of the application 101 , which includes at least a resource manager 120 and a generator 130 .

In this case, after the first launch of the installed application 101 , the generating tool 130 , based on information about the distribution source of the application 100 , generates available resources and configures the functionality, thus generating a personalized application 131 .

The installer 140 is intended for installing the personalized application 131 generated by the generating tool 130 on a mobile device.

In one of the implementation options, the installation of a personalized application is understood as a set of actions leading to:

• placing the personalized application 131 on a mobile device, ie. the location of the files necessary for work on the mobile device;

• initial configuration of the hosted personalized application 131 so that it can perform the declared functionality after launch;

• installation or modification of operating system parameters that will be used by the personalized application 131 in the course of its work.

Thus, it is possible that the personalized application 131 is already hosted on the mobile device, running, but not configured yet (the setting may be performed after the first launch of the personalized application 131 ). In this case, it is considered that the installation of the personalized application 131 (final installation) has not yet been made.

During the process of setting up a first-time launched personalized application 131 , at least:

• formation of personalized application resources 131 ;

• update of the personalized application 131 ;

• changing operating system settings.

Thus, in a particular implementation, the personalized application 131 may be an application 101 that has been customized after it was placed on the mobile device and launched for the first time.

Fig. 2 is a flow diagram of a method for installing a personalized application on a mobile device.

The block diagram of the method for installing a personalized application on a mobile device includes step 210 where the distribution source of the application is determined, step 220 where application resources are selected, step 230 where the personalized application is generated, step 240 where the personalized application is installed.

A more detailed description of the means by which the steps indicated above are implemented is disclosed in the description of FIG. 1 .

In step 210 , the source determiner 110 determines the distribution source of the application by analyzing the operating system settings of the mobile device that have changed as a result of receiving the application from the distribution source.

In one of the embodiments of the method, the content of the clipboard acts as one of the parameters of the operating system.

In another embodiment of the method, the operating system parameters are changed through the use of an external link to the application.

In another embodiment of the method, an external link to the mobile application is pre-formed through an intermediate service, which additionally redirects to the application distribution source 100 .

In another embodiment of the method, the intermediate service provides data on the source of distribution of the application through at least:

• API provided by the app store;

• the clipboard of the user's device on which the corresponding application will be installed.

At step 220 , using the resource manager 120 , application resources are selected from the resource base 121 corresponding to the distribution source determined at step 210 , where the resources characterize at least:

• elements of the multimedia application,

• application functionality.

In one of the embodiments of the method, at least:

• multimedia data;

• text strings;

• licenses;

• scripts describing the functionality of the application;

• modules providing application functionality.

In another embodiment of the method, if the resource base 121 does not contain resources corresponding to a certain distribution source of the application 100 , resources corresponding to the standard assembly of the application are selected from the resource base 121 .

At block 230 , the builder 130 generates a personalized application by converting the application obtained from the application distribution source based on the resources selected at block 220 .

In one embodiment of the method, the resource base 121 is part of an application distribution obtained from an application distribution source 101 .

In yet another embodiment of the method, the resource base 121 is a remote service, wherein the resources are selected by at least:

• updates to the application 101 obtained from the distribution source of the application 100 ;

• direct download.

At step 240 , using the installer 140 , the personalized application generated at step 230 is installed on the mobile device.

Fig. 3 shows an example of a general purpose computer system, personal computer, mobile device, or server 20 ', comprising a central processing unit 21 ', system memory 22 ', and a system bus 23 ', which contains various system components, including memory associated with the central processing unit 21 '. The system bus 23 is implemented as any bus structure known in the art, in turn comprising a bus memory or bus memory controller, a peripheral bus, and a local bus capable of interfacing with any other bus architecture. The system memory contains read-only memory (ROM) 24 , random access memory (RAM) 25 . The main input/output system (BIOS) 26 contains the basic procedures that ensure the transfer of information between the elements of a personal computer 20 , for example, at the time of booting the operating system using ROM 24 .

The personal computer 20 may in turn comprise a hard disk 27 for reading and writing data, a magnetic disk drive 28 for reading and writing to removable magnetic disks 29 , and an optical drive 30 for reading and writing to removable optical disks 31 such as CD-ROM, DVD-ROM and other optical storage media. The hard disk 27 , the magnetic disk drive 28 , the optical drive 30 are connected to the system bus 23 via the hard disk interface 32 , the magnetic disk interface 33 , and the optical drive interface 34 , respectively. Drives and related computer storage media are non-volatile means of storing computer instructions, data structures, program modules, and other personal computer data 20 .

The present description discloses an implementation of a system that uses a hard disk 27 , a removable magnetic disk 29 and a removable optical disk 31 , but it should be understood that other types of computer storage media 56 that are capable of storing data in a computer-readable form (solid-state drives, flash memory cards, digital disks, random access memory (RAM), etc.), which are connected to the system bus 23 through the controller 55 .

The computer 20 has a file system 36 that stores the recorded operating system 35 as well as additional software applications 37 , other program modules 38 and program data 39 . The user has the ability to enter commands and information into the personal computer 20 through input devices (keyboard 40 , mouse 42 ). Other input devices (not shown) may be used: microphone, joystick, game console, scanner, etc. Such input devices are typically connected to the computer system 20 through a serial port 46 which is in turn connected to the system bus, but may be connected in other ways, such as through a parallel port, game port, or universal serial bus (USB). A monitor 47 or other type of display device is also connected to the system bus 23 via an interface such as a video adapter 48 '. In addition to the monitor 47 , the personal computer may be equipped with other peripheral output devices (not shown), such as speakers, a printer, etc.

The personal computer 20 is capable of operating in a networked environment using a network connection to another or more remote computers 49 . The remote computer (or computers) 49 are the same personal computers or servers that have most or all of the elements mentioned earlier in the description of the nature of the personal computer 20 shown in FIG. 3 . Other devices may also be present in the computer network, such as routers, network stations, peer-to-peer devices, or other network nodes.

The network connections may form a local area network (LAN) 50 and a wide area network (WAN). Such networks are used in corporate computer networks, internal networks of companies and, as a rule, have access to the Internet. In LAN or WAN networks, the personal computer 20 is connected to the local network 50 via a network adapter or network interface 51 . When using networks, personal computer 20 may use a modem 54 or other means to communicate with a wide area network, such as the Internet. Modem 54 , which is an internal or external device, is connected to system bus 23 via serial port 46 . It should be clarified that network connections are only exemplary and are not required to represent the exact configuration of the network, that is, in fact, there are other ways to establish a connection by technical means of communication from one computer to another.

In conclusion, it should be noted that the information given in the description are examples that do not limit the scope of the present invention defined by the formula.

Claims (50)

1. A system for installing a personalized application on a mobile device, which contains: a source determination means for determining the distribution source of the application by analyzing the operating system parameters of the mobile device changed as a result of obtaining the application from the application distribution source; a resource handler for fetching from the resource base those application resources that correspond to the application's distribution source determined by the source determiner; generating means for generating a personalized application by converting the application obtained from the application distribution source based on the resources selected by the resource working means; an installer for installing the personalized application generated by the generating means on a mobile device. 2. The system according to claim 1, in which one of the parameters of the operating system is the contents of the clipboard. 3. The system according to claim 1, in which these means are implemented using the processor of the mobile device. 4. The system according to claim 1, in which the parameters of the operating system are changed through the use of an external link to the application, while the external link to the mobile application is pre-formed through an intermediate service, which additionally redirects to the application distribution source. 5. The system according to claim 4, in which the intermediate service provides data about the distribution source of the application through at least: API provided by the app store; the clipboard of the user's device on which the corresponding application will be installed. 6. The system according to claim 1, in which the resources characterize at least: multimedia application elements, application functionality. 7. The system of claim 1, wherein the resource is at least: multimedia data; text lines; licenses; scripts describing the functionality of the application; modules that provide the functionality of the application. 8. The system according to claim 1, in which if there are no resources in the resource base corresponding to a certain source of distribution of the application, resources corresponding to the standard assembly of the application are selected from the resource base. 9. The system of claim 1, wherein the resource base is part of an application distribution obtained from an application distribution source. 10. The system of claim 1, wherein the resource base is a remote service, wherein the resources are selected by at least: updates to an application obtained from an application distribution source; direct download. 11. A method for installing a personalized application on a mobile device, the method comprising steps that are implemented using tools from the system according to claim 1 and in which: determining the source of distribution of the application by analyzing the parameters of the operating system of the mobile device, changed as a result of receiving the application from the source of distribution of the application; select from the resource base those application resources that correspond to a certain application distribution source; generating a personalized application by transforming the application obtained from the application distribution source based on the selected resources; install the generated personalized application on the mobile device. 12. The method according to claim 11, wherein one of the operating system parameters is the contents of the clipboard. 13. The method according to claim 11, according to which the parameters of the operating system are changed through the use of an external link to the application. 14. The method according to claim 13, whereby the external link to the mobile application is pre-formed through an intermediate service, which additionally redirects to the application distribution source. 15. The method of claim 14, wherein the intermediate service provides data about the distribution source of the application through at least: API provided by the app store; the clipboard of the user's device on which the corresponding application will be installed. 16. The method according to claim 11, in which the resources characterize at least: multimedia application elements, application functionality. 17. The method of claim 11, wherein the resource is at least: multimedia data; text lines; licenses; scripts describing the functionality of the application; modules that provide the functionality of the application. 18. The method according to claim 11, according to which, if there are no resources in the resource base corresponding to a certain application distribution source, resources corresponding to the standard assembly of the application are selected from the resource base. 19. The method of claim 11, wherein the resource base is part of an application distribution obtained from an application distribution source. 20. The method of claim 11, wherein the resource base is a remote service, wherein the resources are selected by at least: updates to an application obtained from an application distribution source; direct download.

Images