BBVA API Market
Google’s two latest projects refer to the websites of the future and are mostly focused on content loading speed and user experience. These two issues have become an obsession for Google, not only in terms of the media but also as referents to the whole World Wide Web. Accelerated Mobile Pages (AMP) and Progressive Web Apps (PWA) seek to offer a fast and satisfactory reading experience where friction and frustration are reduced to the minimum and user engagement skyrockets.
AMP is a new way of developing static content web pages so that, when they are rendered by a browser, the loading speed is as fast as possible.
An AMP web page consists of three simple elements:
1. HTML AMP, a traditional HTML document with some restrictions. In the end, these restrictions allow the web page to load at full speed (the enriched content is always handled through extensions).
3. The AMP cache, which makes it possible for the browser to render an AMP cache (this typical web page element speeds up content loading even more).
PWA aims to add to the quick-loading web page some of the features that ensure the power of native mobile applications, such as push notifications and high availability using a desktop icon, besides always rendering under a secure HTTPs protocol domain.
Google’s idea is to facilitate the load of content always instantaneously, even when the connectivity is not good; ensure quick response to the user’s interactions with smooth animations; and guarantee greater user engagement through an immersive ecosystem.
At the start of this year, Google has made some interesting changes to the AMP roadmap. Google has improved some of the project’s major elements, e.g. it has polished some of the interactive formats such as the galleries, carousels or modules with small images (for example, the forms). Additionally, it has improved the optimization of advertising loading in AMP web pages. And lastly, it has improved analytics, particularly for pages with steppers and forms such as e-commerce (improves data gathering when processes are stringed within a website).
2017 changes to PWA
Until now, the service worker returned the result of a request to the browser when requested but this always happened after launching. Under normal conditions, a service worker takes 50 ms on average to launch and serve content the browser is able to render. In mobile devices, this may go up to 250 ms in the fastest models and 500 ms in the slowest models. Even though the service worker stays active in the background between browser requests, sometimes there are requests for a different website or from a different tab.
To correct this situation, Google has changed its approach: instead of beginning to load the request to send it to the browser after the service worker launches, these two actions take place in parallel: the request is the object of a sort of pre-load without having to wait for the service worker. The request could never be served before the service worker launches but this parallel action reduces the times.
Real-time payments have become one of the most noteworthy innovations in the financial industry. Their growth in recent years has been significant thanks to the possibilities they offer companies, especially in customer relations.
Open finance has become one of the main drivers of digital financial change worldwide. Its implications go far beyond those of open banking and may serve to change the current financial paradigm in some regions such as Latin America or Africa.
Lack of confidence in the payment platform and slow processing are the two factors that most influence the abandonment of purchases from ecommerce. Two problems that can be solved thanks to APIs.