According to 9to5 Google, in a few hours on March 23, a large number of Android users encountered a number of Android applications flash back, some people found that uninstall android WebView can stop the flash back. Now, Google has released a permanent fix for the app crash issue, which involves updating the Android System WebView and Chrome version 89.0.4389.105.
In fact, Android fragmentation has been a problem since its inception, and there doesn’t seem to be a good solution. There are also differences in browser kernels among different systems and vendors, leading to endless compatibility problems that make many Android developers feel uneasy.
In order to solve and control these problems thoroughly, mPaaS integrates an independent UC browser kernel, so that problems such as flashback and lag caused by WebView can be effectively converged and managed in a unified manner. At the same time, according to the applications and tests of many services, when the UC browser kernel is used, browser-related blink back and Application Not Respond (ANR) decline significantly.
In addition, mPaaS can fix and release **[1]** as soon as possible any security issues surrounding a WebView, far more efficiently than vendor upgrades.
In addition to UC WebView kernel, mPaaS also inherits container and offline package technology of Alipay deep application [2].
Normally, when an online page is launched in an App, there is usually a blank screen where the browser needs to download HTML resources from the server. Due to the limitation of mobile network, the resource loading time is not controllable. It usually takes more than 300ms to practice, and users will see a blank screen during this period.
In order to optimize user experience and reduce blank screen time, Alipay introduced offline package technology inside the container. An offline package is a ZIP package that contains HTML, CSS, JS, and images required by the front-end page. After it is built into the client, the container directly obtains resources from the offline package when opening the offline package page. This process takes milliseconds and eliminates the problem of a blank screen when the page starts.
Currently, THE mPaaS container solution supports HTML5 and applets. With the offline package capability, static resources such as rendering, logic and configuration can be preset easily, eliminating the influence of network environment on page loading and improving user experience.
At the same time, with the help of mPaaS dynamic publishing service, for new product/business requirements, can achieve rapid development, and can be completed through the mPaaS console release; The container SDK integrated in the end user client will automatically pull the latest offline packages. This release and update process eliminates app store approval and maximizes business iteration efficiency.
Reference documentation
[1]mPaaS dynamic release of product documentation: help.aliyun.com/document_de…
[2]mPaaS H5 Container and Offline package Product Documentation: help.aliyun.com/document_de…
– END –
