Updating Android apps is likely to be a much easier process for end users and developers at some point in the future that is not too far away thanks to the new In-app Updates API introduced at Google's Android Dev Summit this year. Set to start launching "soon," the new API has been tested with early access partners and fundamentally changed the way Android applications are updated. Namely, the company wants to update to the process & # 39; background & # 39; what actually happens in the application even though the end user still uses the application in question. There are two possible ways that Google can refer to updates in "direct" applications or updates in "flexible" applications.
For the first of them, updates directly in the application, developers can install new software at once, encouraging users to short-screen full-screen messages that have to wait temporarily when the installation occurs. However, under other options called "flexible updates," developers can effectively hot-swap code when an application is being used, leading to a more natural stream of updates where changes are combined without interruption. In both cases, after the installation is complete, the application automatically restarts in a way that is much more similar to page refresh than reset, with users placed in the application exactly where they left off.
Background: In addition to the obvious benefits, change will help developers combine updates so that processes become part of their application in a far more integral way. However, that is not the only new development that the Android Dev Summit has brought to the table in terms of letting developers make their own things. On the hardware side, Google also recently announced that it will help push the frontline with system-level changes made to support the expected influx of smartphones that are flexible or collapsible. In short, the Android OS will support two types of folding phones. It will include them with two or more screens and those with a single panel that can be bent directly.
Exactly, the Samsung Developer Conference event itself goes hand in hand with Google and the company has revealed its own Infinity Flex display panel. Because the two companies are working on a new UI and other API changes together, Samsung is likely to be the first, but not the only, producer to use it in the future. However, the announcement marks at least one other area where Google is working to help developers across the board create diversity on Android while still keeping everything consistent.
Impact: Meanwhile, there is no direct indication of how new APIs can affect more traditional installations. All installations will likely continue to be processed through the Google Play Store to continue company policies that utilize threat scanning tools and Google Play Protect. What's more, major changes may still require more traditional updates. Given that, from a user's perspective, that change will undoubtedly appear to be far greater than that after the developer starts implementing the In-app Update API. This change will allow updates that almost feel smooth just because they don't require users to leave the application and return to the new application startup just to get new features or see UI tweaks. In this case, they will act more like server-side updates. At the same time, instead of reinstalling the Google Play Store in the background, invisible and often unnoticed, developers will be able to direct end-user attention to the fact that the update has been completely installed.