Description:
FIELD OF THE INVENTION
[001] The present invention relates to the field of computer engineering, and more particularly, the present invention relates to the Android application (app) distribution from website basis device processors.

BACKGROUND FOR THE INVENTION:
[002] The following paragraphs delve into the background of the invention and are intended to facilitate a simplified understanding of the present invention. However, it should be appreciated that the simplification of the present invention, is not and cannot be construed to be an acknowledgment or admission, that any of the material referred to herein, was published, known, or part of the common general knowledge in any jurisdiction as on the priority date of this application. If the details provided herein or parts thereof, inadvertently belong to any earlier publication, then it is clarified that such references have been incorporated herein only as a reference for describing the real world problems and are used merely as general terminologies used in common parlance, or well-known principles of science and technology.
[003] Currently, there are no means or methodology to install APK (Android Application Package) files based on processor information on user devices from websites. This results in the download of a single large-size APK file onto a user device or, alternatively, a single 32-bit base APK installed on all types of devices, irrespective of device properties. Both approaches have their specific problems, as below:
1. Downloading a single large-size APK - It will be generally twice (or more) the size of a normal APK, which include all types of processor-based code in the APK resulting in a bigger APK disk size. Larger file size requires more network bandwidth for download & device storage for usage on the device.
2. Download a 32-bit-based APK - This will include only files supported by 32-bit processors. This may result in a situation where devices which don’t support 32-bit will not be able to use this APK file. This leads to a potential loss of users, due to the extended user experience.
[004] The Applicant has conducted a worldwide prior art patent search in order to elucidate the distinguishing features of the present invention. Some of the closest relevant prior art documents are:
[005] EP4044022A1 discloses a system integrating a mobile device application creation, editing, and distribution system with a website design system. The system includes a website building system (WBS) to enable a user to build a website, and host the website, a database to store website data that includes at least a structure of the website, an application generator repository to store at least several per-vertical base apps, where each per-vertical base app is a template app for one type of business, and an application generator to determine the website type of business, to generate an initial extended application content file (XACF) at least from an associated per-vertical base app for the type of business, to analyze the structure of the website to generate a graph of elements of the website and to use the graph to modify the associated per-vertical base app into a XACF defining the mobile application.
[006] CN105117222A discloses a method and apparatus for providing Android package (APK) customization service. The method comprises: making a universal APK framework, wherein the APK framework contains a browser kernel; receives a website address provided by a user; adds the website address provided by the user into the APK framework, and packaging the APK framework into an APK customized by the user; and returning the APK customized by the user to the user. The method has the beneficial effect of simply and quickly generating the APK, and meanwhile is universal; for the user who does not understand an APK programming technology, the user is only required to provide the website address for generating the APK required for the user; and the problem that an APK programming technician is required to specially write the APK when the user hopes to customize the APK without a very complicated function is solved, so that the APK development time is greatly shortened, and time advantage and technical convenience are provided for the user to promote and use the APK.
[007] In light of the foregoing, it is established that the present invention is novel and there is a need for the Android app distribution from website basis device processor that overcomes problems prevalent in the prior art(s).

OBJECTS OF THE INVENTION:
[008] Some of the objects of the present disclosure, which satisfies, at the very least one embodiment herein, are as follows.
[009] The principal object of the present invention is to overcome the disadvantages of the prior art by providing the Android app distribution from a website basis device processor.
[010] An object of the present invention is to provide the Android app distribution from a website basis device processor that provides a technology flow/enhancement to download Android applications from websites.
[011] An object of the present invention is to provide the Android app distribution from a website basis device processor that distributes the Android application based on the specifications of the user device processor.
[012] An object of the present invention is to provide the Android app distribution from a website basis device processor that results in a better user experience.
[013] An object of the present invention is to provide the Android app distribution from a website basis device processor that reduces file download size, and usage of less disk space for installation.
[014] An object of the present invention is to provide the Android app distribution from a website basis device processor that enhances the overall better performance of the application.
[015] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.

SUMMARY OF THE INVENTION:
[016] The present invention provides an Android app distribution from a website basis device processor.
[017] In one aspect of the present invention, the process includes 3 stages such as a build phase, downloading and installing stage, and a post-installation stage. 3 different APKs are generated and created post-installation resource files that are used after the application is installed on devices.
[018] The resources are required to make an application work on the device but are not required to be part of the APK itself. The resources are then uploaded to cloud storage where they can be downloaded by the application at a later stage.
[019] The respective device properties like Make, Model, Android version, and processor details are collected from the browser for identifying and ascertaining which APK needs to be installed onto these devices. Accordingly, the corresponding APK files are pushed to users' devices for download.
[020] The device processor architecture is identified and downloaded the relevant files which are generated at Stage-1 from the cloud.

BRIEF DESCRIPTION OF DRAWINGS:
[021] Reference will be made to embodiments of the invention, examples of which may be illustrated in accompanying figures. These figures are intended to be illustrative, without limiting the actual scope and/or functions envisage for the present invention. Although the invention is generally described in the context of these embodiments, it should be understood that it is not intended to limit the scope of the invention to these particular embodiments.
[022] Figure 1 provides a flow chart showing a build process in accordance with the present invention;
[023] Figure 2 provides a flow chart showing a process flow in accordance with the present invention.

DETAILED DESCRIPTION OF DRAWINGS:
[024] While the present invention is described herein by way of example using embodiments and illustrative drawings, those skilled in the art will recognize that the invention is not limited to the embodiments of drawing or drawings described and are not intended to represent the scale of the various components. Further, some components that may form a part of the invention may not be illustrated in certain figures, for ease of illustration, and such omissions do not limit the embodiments outlined in any way. It should be understood that the drawings and the detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the invention is to cover all modifications, equivalents, and alternatives falling within the scope of the present invention as defined by the appended claim.
[025] As used throughout this description, the word "may" is used in a permissive sense (i.e. meaning having the potential to), rather than the mandatory sense, (i.e. meaning must). Further, the words "a" or "an" mean "at least one” and the word “plurality” means “one or more” unless otherwise mentioned. Furthermore, the terminology and phraseology used herein are solely used for descriptive purposes and should not be construed as limiting in scope. Language such as "including," "comprising," "having," "containing," or "involving," and variations thereof, is intended to be broad and encompass the subject matter listed thereafter, equivalents, and additional subject matter not recited, and is not intended to exclude other additives, components, integers, or steps. Likewise, the term "comprising" is considered synonymous with the terms "including" or "containing" for applicable legal purposes. Any discussion of documents, acts, materials, devices, articles, and the like are included in the specification solely for the purpose of providing a context for the present invention. It is not suggested or represented that any or all these matters form part of the prior art base or were common general knowledge in the field relevant to the present invention.
[026] In this disclosure, whenever a composition or an element or a group of elements is preceded with the transitional phrase “comprising”, it is understood that we also contemplate the same composition, element, or group of elements with transitional phrases “consisting of”, “consisting”, “selected from the group of consisting of, “including”, or “is” preceding the recitation of the composition, element or group of elements and vice versa.
[027] The present invention is described hereinafter by various embodiments with reference to the accompanying drawing, wherein reference numerals used in the accompanying drawing correspond to the like elements throughout the description. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiment set forth herein. Rather, the embodiment is provided so that this disclosure will be thorough and complete and will fully convey the scope of the invention to those skilled in the art. In the following detailed description, numeric values and ranges are provided for various aspects of the implementations described. These values and ranges are to be treated as examples only and are not intended to limit the scope of the claims. In addition, several materials are identified as suitable for various facets of the implementations. These materials are to be treated as exemplary and are not intended to limit the scope of the invention.
[028] The present invention provides an Android app distribution from a website basis device processor. This invention is a new technology flow/enhancement to download Android applications from websites. With this technology, the system can distribute Android application based on the specifications of the user device processor, which will result in a better user experience, reduced file download size, usage of less disk space for installation, and overall better performance of the application.
[029] The process includes 3 stages:
Stage-1: Build phase:
[030] In this stage, the system modified the android build process which generated 3 different APKs and created post-installation resource files. An APK file (Android Package Kit file format) is the file format for applications used on the Android operating system (OS). An APK file contains all the data an app needs, including all of the software program's code, assets, and resources. All Android apps, including those downloaded from the Google Play Store or downloaded manually, use APK files. The APKs can be downloaded from the website of the applicant. These APKs are based on device architecture as below:
- A. 64-bit supported APK - This build only includes resources that support only 64-bit-based device processors.
- B. 32-bit supported APK – This build only includes resources that support only 32-bit-based device processors.
- C. Universal APK – This build includes resources that support both 32-bit & 64-bit device processors. The size of this APK is generally twice or more than other types of APKs.
[031] While building these APKs the system extracted other resources which can be used after the application is installed on devices. These resources are dependent on device processors and other factors. These resources are required to make an application work on the device but are not required to be part of the APK itself. the system uploaded these resources to cloud storage where they can be downloaded by the application at a later stage. (Refer to Figure 1)
Stage-2: Downloading and Installing:
[032] In this stage, when users start downloading flow from website, the system collect the respective device properties like Make, Model, Android version, and processor details from the browser. Based on these data points, the system identifies and ascertain which APK needs to be installed onto these devices. Accordingly, the system pushes the corresponding APK files to users' devices for download. (Refer to Figure 2)
Stage-3: Post Installations
[033] Once the user installed the respective APK build, the system identifies the device processor architecture and download the relevant files which were generated at Stage-1 from the cloud.
[034] The system takes care of the same flow when the user updates his app from the universal APK. In that case, the system update applications with 64-bit or 32-bit APK based on the device properties.
[035] The disclosure has been described with reference to the accompanying embodiments herein and the various features and advantageous details thereof are explained with reference to the non-limiting embodiments in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein.
[036] The foregoing description of the specific embodiments so fully revealed the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should be, and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.
, Claims:We Claim:
1) An Android app distribution from a website basis device processor, the process comprises stages of:
- a build phase (stage-1) that generates 3 different APKs and creates post-installation resource files;
- a downloading and installing (stage-2) that starts downloading flow from website, and collects the respective device properties like Make, Model, Android version, and processor details from the browser; and
- a post installation (stage-3) that identifies the device processor architecture and download the relevant files which were generated at Stage-1 from a cloud.
2) The process as claimed in claim 1, wherein the APK file (Android Package Kit file format) is the file format for applications used on the Android operating system (OS).
3) The process as claimed in claim 1, wherein the APK file contains all the data an app needs, including all of the software program's code, assets, and resources.
4) The process as claimed in claim 1, wherein the APKs are based on the device architecture as below:
- A. 64-bit supported APK that includes resources supporting only 64-bit-based device processors;
- B. 32-bit supported APK that includes resources supporting only 32-bit-based device processors; and
- C. Universal APK that includes resources supporting both 32-bit & 64-bit device processors.
5) The process as claimed in claim 1, wherein the universal APK is generally twice or more than other types of APKs.
6) The process as claimed in claim 1, wherein the APKs installed are based on other resources dependent on device processors and other factors.
7) The process as claimed in claim 6, wherein the other resources are not required to be part of the APK itself.
8) The process as claimed in claim 6, wherein the resources are uploaded to cloud storage where resources get downloaded by the application the stage-3.
9) The process as claimed in claim 1, wherein the system identifies and ascertains which APK needs to be installed onto the devices and accordingly push the corresponding APK files to users' devices for download.