Updating Android applications is likely to become a much more convenient process for end users and developers at some point in a not-so-distant future thanks to the new application-updating API introduced at this year's Android Dev Summit hosted on Google. Set to begin accelerating "soon", the new API has already been tested with early access partners and fundamentally changes the way in which Android applications are updated. Namely, the company asks that the updates are the real "background" process that occurs in the application, even if the end user still uses the application in question. There are two possible ways that can be implemented, and Google refers either to "immediate" app updates or to "flexible" updates in the app.
For the first of these, the current updates in the application, the programmer can install new software all at once, pushing users to a short message on the entire screen that must wait until the installation occurs. However, under another option called "flexible update", programmers can effectively use hot-swap while using the application, which leads to a more natural update of the flow in which changes are installed without interruption. In any case, when the installation is completed, the application is automatically launched in a way that is much more similar to updating pages from reset, whereby users place the application exactly where they stood.
Background: In addition to the obvious advantages, the change will help developers build up the fixes so that the process becomes part of their application in a much more integral way. However, this is not the only new development that Android Dev Summit has brought to the table in terms of allowing developers to make things more of their own. On the hardware side of things, Google recently announced that it will help move borders forward with system-level changes that are designed to support the expected incoming wave of flexible or foldable smartphones. In short, Android OS will support two types of switching phones. This will include those with two or more screens and those with one panel that can be bent directly.
In particular, Samsung's developer development program works together with Google and this company has already revealed its Infiniti Flek screens. As the two companies worked on new user interfaces and other API modifications, Samsung will probably be one of the first, but not the only manufacturer to use in the future. In any case, publishing means at least one other area in which Google works to help developers across the whole society to create diversity in Android, while at the same time still keeping everything consistent.
Influence: In the meantime, there is no immediate indication as to how the new API can affect traditional installations. All installations will likely continue to be processed through the Google Play Store to continue the company's policy using its threat scanning tools and Google Play Protect. Moreover, major changes may require more traditional updates. Bearing this in mind, from a user perspective, the changes will undoubtedly look much greater than when developers begin to implement the API for application updates. The change will allow updates that almost feel flawlessly simply because they do not require users to leave the application and return to a completely new launch of applications just to get new features or view UI tweaks. In this sense, more will act as updates on the server. At the same time, instead of making Google Play Store install updates in the background, unseen and often unnoticed, developers will be able to bring end-users attention to the first fact that the update is installed.