< IMG SRC = "/Uploads/Blogs/84/0e/IB-FR9P7JJJ4R_2715237c.jpg" Alt = "Google goes to a fully closed Android design mode: what does it mean to users"/> ~ ~ ~ ~ < p >
< p _ngcontent-serverApp-c88For many years, Android has been designed in such a way that the public could look into the work process almost live. This is now changing because Google says that from next week will start developing the operating system completely closed in its internal unit.
~ ~ < p >
< h2 class = "News-Subtitle CKE-MarkUp" > that will change
< P > Android Open Source Project or AOSP & NDash; This is a project that provides the initial code of the Android operating system. It means that anyone can download this code at any time, change it and create their own versions of Android. The main idea of AOSP & mdash; It is the provision of a basic platform that can be used to develop your own operating systems or devices, modifying it with your own design and features. The AOSP development process has always been public. Now everything will change, but it is early to worry, because there is a positive moment, reports & nbsp; 24 channel & nbsp; with reference to & nbsp; Android authority.
~ ~ ~ > 62 > 62 > < p >
< P > Open Elementary Code Project is issued under the Apache 2.0 license that allows anyone to use, distribute or modify AOSP operating systems without the need to pay any licensing payments or publish their modified code. This Licensing Structure & nbsp; < strong > contributed to the widespread distribution of AOSP, which led to the creation of customized pods , such as one ui from Samsung or p'more ~ 62. < P > Like many other open code projects, AOSP accepts code contributions from third -party developers. However, Google conducts most of the development on its own, as it considers the project not as a collective heritage, but its own product. Therefore, & nbsp; < strng >Google has a decisive word as to which code can be implemented & nbsp; in AOSP at native level.
< P > To balance the open nature of AOSP and product development strategy, & nbsp; < strong > Google supports two main branches of Android : public branch of the development and internal branch. AOSP branch is available to anyone, whereas Google's internal compartment is limited to companies with a license agreement.
< P > But here's the problem: As long as Google adds new features and corrections to its internal version and gives it access to individual companies under license, & nbsp; < strong > AOSP version of the AOSP solidifies at the last update < p > If you follow the development process, you may notice that & nbsp; < strong > Company for some time develops most parts of Android behind closed doors in their “inner branches” Android frameworks (including Bluetooth, nucleus and some other major components).
< p > now Google has confirmed that “all Android development will take place in the internal units of” Company. As the main parts of Android are developed privately, the public branch of AOSP is often far behind. This difference is obvious when comparing the availability of functions and API in the AOSP assembly and in the last beta android 16, which was collected from the inner branch.
The discrepancy makes Google spend time and effort to plot AOSP to a new version from the inner branch. Due to how different the branches, conflicts often occur, which further inhibits the process. < P > Moving everything into its inner development branch, Google does not change the speed with which new buildings appear. Rather, it will potentially streamline the process and prevent conflicts with fusion of branches. Now all developers will wait for the release of a stable assembly from Google at the moment when a certain portion of changes will be made to the next beta-version of the OS.
< p > It is important to note that & nbsp; < strng > This does not mean that Google makes Android a platform with a closed initial code . On the contrary, the code will still be open to all and free, and the only change is how the developers will access it.
< h2 class = "News-Subtitle CKE-MarkUp" > What does this mean to users
< p > in short, then for users it probably will not play any role. Manufacturers of their smartphones will still access each next assembly in the same time frame. The only change is that they could work with AOSP before, as Google is working on their version, and now they will expect a stable company release instead of AOSP at any time. This may be a slightly slowing study of new functions and adaptation to them, but it should be borne in mind that even with access to AOSP, all smartphone manufacturers were waiting for the final stable version.