Creado el 18 Jun. 2018

Open banking, APIs and Banking as a Service are increasingly common concepts in the financial world, partly due to the promotion of the new PSD2 European directive that establishes new rules of the game in which financial institutions must open their data to third parties so that the customer benefits from greater competition and better services.

BBVA has been working for a long time to lead open banking. Ricardo Segoviano, Head of BBVA API_Market, explained that long-term commitment recently at Open Expo, which is a conference for professionals of free software and open technologies that was held at the beginning of June in Madrid.

Segoviano explained that BBVA has been launching various initiatives since 2013 to innovate and adapt to the environment that it has been forming. But probably the most important step has been the creation of its Open APIs platform, launched commercially in May 2017.

That commitment to open banking had a lot of work behind it. "In the pilot phase, we invited around 200 companies to try use cases and solutions. We wanted to experiment and learn, and several lessons were learnt from the experience," explained Segoviano.

Segoviano summarizes everything learned in these years of work in six conclusions. 

  1. Open banking is not just a matter ofAPIs. You have to have a global vision, and financial institutions must take into account not only the customer's user experience, but also the developer's.
  2. To move forward in this new environment, banks need the direct support of top management, since it is a total transformation of the bank, from all points of view.
  3. The APIs market has still to be consolidated. "Demand is there, supply remains limited and prices have yet to be set in the market," Segoviano explained.
  4. The possible business models and their concrete formulation have also to be outlined. "There are many possibilities, but they are not obvious. When you collaborate with people who have different perspectives, you arrive at ideas that you had not even considered," Segoviano said.
  5. Although it gives the impression that the PSD2 is open banking's main engine, the paradigm shift in the banking business is much deeper.
  6. There is a lot of commercial education left to do. "The end customer will still take time to assimilate what is happening and allow access to their finances, and younger customers will entail a lot of work," predicted Segoviano. 

While the market consolidates and grows, BBVA already has a leading position in Open APIs, with 10 solutions inBBVA_API_Market. Segoviano considered the PayStats case of use in particular, which offers retailers detailed information on consumption patterns by retail areas, with which they can, for example, optimize their advertising campaigns and choose the best location, with data, for their stores.

They are examples of economic transformations that are already here thanks to APIs, but Segoviano closed his talk with an overview of open banking. "All this is here to stay, and banks should opt for collaboration models. We have to change our way of thinking and create opportunities for our customers."



Creado el 14 Jun. 2018

There’s no better platform than Twitter for keeping up with developments, advances and changes in a number professional fields. The network's capacity for microblogging to create a constant flow of information is considered by most people to be priceless. The development world, specifically that of the APIs, is a good example. You can find multiple profiles to follow on the Twittersphere to get good information either directly or through retweets.

1.- @w3c

W3C, the initials of the World Wide Web Consortium, is a work group formed by professionals from institutions and companies who are charged with developing technologies, specifications and protocols to guide the open web and its component parts.

This account provides updated content featuring new ideas and the most recent news on the development of standards and the APIs that will make them possible.

2.- @Mashape

One of the most popular services for finding points of connection between APIs also has one of the most interesting Twitter profiles. By following Mashape you can not only learn everything about their services but you can also get links to in-depth documentation on APIs and microservices.

3.- @ProgrammableWeb

This is undeniably the world's most popular news website on APIs, standards and protocols. If you follow this Twitter account you can stay up to date with information on the APIs you already know as well as discovering many others with which to expand your horizons as a developer.

An API is only as powerful as the set of other APIs with which it can interconnect, and on ProgrammableWeb you can always learn something that will help you come up with new ideas and ways of doing projects.

4.- @3Scale is a platform that allows API providers to manage their services conveniently. It's incredibly useful. On their Twitter account, in addition to discussing improvements in the platform and resolving queries, you can find more information about the most interesting technologies on the market, information about conferences, and links to new science and research articles.

5.- @BankInnovation

We don't need to explain that financial technology is the future, and much less that financial APIs are at the center of the revolution. The Twitter account of Bank Innovation, a fintech startup accelerator, offers an incredible amount of information on the banking and technology market.

If you work in finance or the IT sector, you'll find it very useful to stay informed about the most buoyant IT markets.

6.- @OpenApiSpec

Like W3C, OAI is a work group focusing on the standardization and promotion of neutral APIs capable of interconnecting in an open and simple way.

Following this account –supported by industry big-hitters such as IBM and Microsoft– will add vital information to your timeline every day: conferences, best practices and new APIs to discover and adopt.

7.- @ApiAcademy

One of the sites with the best learning resources to ensure your knowledge stays fresh. Methods, protocols, practices and new programming styles to discover, and resources to improve what you already know. A must.

8.- @ApiWorld

The largest international conference focused exclusively on the integrated economy has a Twitter account that's active all year round. In addition to keeping up with all the news and new methods, you'll find out when tickets go on sale for the next conference in September and –if you're quick off the mark– get them at a good price. This is a great way of continuing your professional training and meeting interesting people in the sector.

9.- @Fabric

Now part of the Google ecosystem, Fabric was a set of tools created by Twitter to make life easier for developers. With Fabric you'll get advance notice of all the new tools, automation and integration possible for your apps.

10.- @TwitterAPI

Twitter's API is definitely one of the most complete, widely used and useful in the world. Its official account announces changes and improvements, and distributes links to libraries and frameworks so you can take maximum advantage of them.

There are numerous ideas for using this API, and numerous possibilities for integration with your platforms and businesses.

Bonus: @BBVAApiMarket

BBVA's Market API Twitter account offers resources, links, interviews, documentation and articles on the financial sector in Spanish and English for IT and fintech professionals, so you can make sure you miss nothing.

What's more, you'll always be the first to know when BBVA's financial APIs are updated or receive new methods. This is essential if you work in the technology or financial information sector.

Creado el 13 Jun. 2018

The range of available APIs for developers is ever expanding. Turning to an external service that provides the tools that otherwise would have had to be built from scratch not only saves time but also resources.

Therefore, in order for those who turn to your API to be happy with the results, there is no need to provide them with all possible options; instead, it is important to make sure that your service is working properly and that there are no bumps on the road. The only way to fulfil this premise is to monitor its performance and consider possible changes to make it compatible with the software of third parties. Undoubtedly, the work becomes more difficult as complexity increases as well as the number of dependencies (components that the applications can use) of the API.

Thus, the key to assess the success of your API is to monitor traffic (incoming calls), the developers and applications that use it, the quality of service offered (this includes error rate, code failures and efficiency of responses) and the income provided by its use by third parties.

Resources: APImetrics, Visual Studio Application Insights and APIscience

Fortunately, there are different tools to keep an eye on your API and swiftly detect possible failures and solve them fast. One is APImetrics, a sort of scorecard from which to analyse different parameters of the programming interface.

This software solution allows measuring the time the API takes to respond to requests from apps, the effectiveness of its response and the reaction capability it presents for each dependency or type of call. Thus, it offers a holistic view of the performance of the service.

Another monitoring tool is Visual Studio Application Insights, available in the Microsoft Azure service. In this case, analysis includes checking data bases, HTTP calls, Java and databases, as well as the evaluation in real time of interactions between the API’s and the external interfaces.

It is worth noticing that the program facilitates the analysis of the response produced by a particular type of call, so that it is possible to evaluate if the versions of the API interface and those of third parties are compatible. On the other hand, faults and exceptions are detailed in the reports provided by the tool.


Turning to the past to understand the present

Unlike the previous ones, the kind of analysis provided by APIscience is staggered; it first evaluates the integration of external APIs with its own, and then assesses the results of their interactions. It serves to monitor, among other styles of software architecture, REST, JSON and OAuth APIs.

One of the main advantages of this tool is that it allows to compare previous versions of the programming interfaces with the current one, a comparison used to detect errors, slow responses and integration problems.

The tool is based on a system that monitors variations in the functioning of the API as well as its performance on the basis of time. Next, it represents the data by means of useful dynamic graphics. These reports help developers to analyse the code of the programming interface in search of possible errors.

Meanwhile, AlertSite offers a three-for-one solution, allowing to monitor the performance of the API along with that of websites and applications. For the first, the solution is called SmartBear, a complete manager of the status and health of programming interfaces. It is based on a network of nodes to monitor the speed of interactions and responses at a global level (it includes a map in the report of results), subsequently relating this flows to the degree of performance exhibited in each case.

Another useful feature of the AlertSite solution is that it offers different types of analysis adapted to third-party APIs, public APIs and those of partners, as each of them presents different problems. SmartBear also accepts scripts, so that internal assessment tools, such as Ready! API and SoapUI, are integrated into the service. Thus, developers can then execute these other services from the same product.

Ideally, a combination of tools

Although the existing tools and solutions are varied, the choice of one over the other should depend on the needs of each case. If only global assessments apply, and there is no need to look too much into the detail of the functionalities of the API, this latter may seem perfectly functional with respect to third-party applications despite being an outdated or obsolete version.

On the other hand, checking only the basic elements of the API, without considering the overall picture, it is also a partial approach. The best is to combine both strategies to achieve complete monitoring.

Are you interested in financial APIs?  Discover all the options offered by BBVA

Creado el 04 Jun. 2018

Some of the most sought-after professions are data analysts, database administrators, data science experts, data architects, database managers and Big Data engineers.

Snapshot of a data analyst

  • Analysts are much more than Excel experts: “Big Data is not everything that's analyzed on an Excel sheet, and an analyst is not just someone who knows how to draw graphs on it”, says Julia Díaz, director of Health and Energy Predictive Innovation at IIC (Instituto de Ingeniería del Conocimiento).
  • Profiles with a background in mathematics and computer science: according to Miren Gutiérrez, head of the expert program entitled ‘Data analysis, research and communication’ at Deusto University: “It's possible for one person to master several skills, but a large project can ultimately only be tackled in a group where everyone deploys their special skills and experience at the service of the others”.
  • They must be able to work in a team: whether you're a government employee who needs to convey information to the public, a data journalist or the campaign manager for an NGO, the most effective method is to bring together different fields so that the data analysis has greater validity.
  • There are also analysts from the humanities: the best analysts do not have to be computer experts, mathematicians or specialists in statistics, as long as they can find a story in the data.
  • They must be embedded in the social context and pursue a social utility: data have to be analyzed with a target in mind and based on a social, technological, economic and scientific framework.
  • They must be deeply curious and have the ability to think outside the box.
  • They work for civil society: they mobilize and empower people.

Today there are several training programs at both the national and international level to learn how to be an analyst in any of several different categories. There are also a large number of courses and tutorials, in addition to open programs available on the Internet for anyone who wants to learn on their own.

The Financial Times estimates that over 50,000 jobs related to the sector will be created every year until 2020.

A research work by the consulting company Robert Walters indicates that almost half of all employers plan to increase the number of workers in this sector. According to forecasts by Midsize Insider on Big Data, the United States will create a demand for almost 200,000 Big Data experts by 2018.

But there will not only be more jobs on offer. There will also be significant salary hikes. The rise in salaries is a partial result of the scarcity of the offer of people specialized in data. This imbalance in the Big Data labor market is a matter of great concern to the industry.

The financial sector has a particularly high demand for this type of professionals. The benefits for the sector include the fight against fraud and risk management.

The figures point to a growing awareness among companies of the various benefits that can be achieved from the management and use of data, and highlight new opportunities for future professionals.


Are you interested in financial APIs? Discover all the APIs we can offer you at BBVA

Creado el 31 May. 2018

Reducing costs, creating applications, designing predictive models, etc. There are many companies that use APIs to increase their competitiveness, explore and discover new markets and diversify their business. However, these new opportunities depend on monitoring how these APIs operate.

Mashape Analytics, Akana Envision and CA App Synthetic Monitor are three of the professionals tools used to measure the performance of application programming interfaces in real time. Thanks to these platforms, the development teams can keep track of performance at all times and act to solve errors.

1. Mashape Analytics

Mashape Analytics has been created internally by Mashape with the aim of controlling and measuring the performance of over 13,000 APIs used by Mashape itself to develop its microservices infrastructure, and by other companies such as Amazon, Citibank, Accenture, DHL and NASA.

Mashape claims that this tool was created to fill a gap in the market: monitoring the performance of microservices infrastructures and APIs for modern development teams. This analysis solution offers the following features:

- Real-time data: Analysis of the performance, consumption and use of an API in real time. It also measures the average latency time of the activity or errors, both on the customer's and the server's sides. In the final phase, the platform provides this information in a drill-down by points. 


- Custom dashboards: Development teams can create dashboards to prepare reports and create filters among other options. This tool could be called the "Google Analytics of APIs".

- API logs: Everything that happens in a microservices infrastructure can be logged. Development teams can access these logs as they arrive and, consequently, debug errors more easily. 

- Alerts: Systems that sends real-time notifications to the technical team regarding the overload or mismanagement of infrastructure resources, or notifications about the actual API status. These alerts are sent via email or push notifications.

- Request for repetition: A second identical request can be raised to check that the performance response for the first log meets the predefined goal.

2. Akana Envision

Akana's platform provides companies with the ability to reach conclusions based on information from their APIs and data about the performance of these interfaces, with the aim of managing and exchanging data among the APIs. Envision is a scalable and customizable tool. It can be used as the main platform to analyze complex data and how the APIs work, or integrated into an existing tool to avoid duplicates in the IT infrastructure.

With Envision, a group of developers can:

- Track product trends.

- Identify new business ideas and opportunities.

- Discover the best available APIs for each type of application, platform, channel or monetization outlook.

- Analyze whether or not the infrastructure responds to requests from devices and locations correctly, and whether or not it reacts to the type of requests correctly.

- Manage APIs. For example, troubleshooting. 


Some of its main features include:

- Data lake: Storage of raw data for future use or analysis.

- Data enrichment with Map Reduce, R Analytics or fully customized plug-ins.

- Data import from external sources.

- Data export to external sources for analysis.

- Creation of custom dashboards.

3. CA App Synthetic Monitor

This tool allows you to monitor APIs and web services in the cloud. The platform simulates the complete workflow of an API and reproduces it from any of the measurement and monitoring stations in the CA App Synthetic Monitor. The tool aims to replicate the end user experience to determine the status and availability of every application and identify possible errors


Its main features are as follows:

- Replicate transactions by actual users from 94 monitoring stations in six continents so as to provide real-time, minute-by-minute API performance control and measurement.

- Performance monitoring of the company's APIs and third party APIs. Performance monitoring of web services, including users.

- Alerts to react to problems involving API performance as soon as possible. These alerts contain all the necessary information: a timestamp, the script name, the type of API error, etc. Alert notifications can be set up in the tool's console and sent via email, SMS, XMPP/Jabber, MSN, RSS or SNMP, or sent to a webpage (API). There is a log of when these alerts are received.

- Creation of customer reports: Statistics by time, day, week, month and year regarding availability and response times. All reports can be downloaded as a PDF or Excel file or using the API and sent via email, either manually or automatically. Real-time views (also available in interactive flash format) can also be downloaded as PNG. 

- Data availability is variable: 30 days for non-processed data, 48 hours for analysis data about the root cause, and 4 months for statistical data.

- Monitoring of APIs and web services in the cloud is compatible with any type of API: REST, SOAP, oAuth, JSON, XML, RSS, openID…

Configuration of dashboards from the CA App Synthetic Monitor's console. The default dashboard includes historical data and the latest alerts. All this is real-time information. Aggregate script results can also be displayed in the monitoring dashboard. 

More information on APIs here.

Follow us on @BBVAAPIMarket


Creado el 25 May. 2018

Alaska Airlines needed to compete with other major airlines like American Airlines and Delta, and given its lack of marketing budget, decided to place the emphasis on innovation.

Thanks to this change of course it became one of the first airlines to allow the introduction of electronic devices on its planes and offer its users a new way of enjoying their journey. It also pioneered the online check-in process, a move which made the airline company an electronic innovation leader.

The goal was to improve the user experience

Alaska Airlines was one of the first to develop an iPhone app to enable users to access their boarding passes, a system that has today been copied by many airlines. But this app was very limited at the start, and the user experience left much to be desired.

The executives at Alaska Airlines realized the app alone was not sufficient and decided to incorporate an API, as part of an initiative they called “Innovation at the Edge”. Their aim was to develop apps that offered their users and employees added value.

To achieve their goal, the company needed a API proxy that would carry out the work of security and management, both to receive incoming requests and to guarantee the operation of its back-end services. The API they used was CA API Gateway, because it offers flexibility and good integration between the development and test environment.

How has it improved?

Using this API they managed to create an app that has streamlined the boarding process while enabling passengers to check their flight status in real-time. This API has also allowed the Alaska Airlines partners to develop other apps to improve their customers’ experience:

  • Users can send an SMS with their dispatch number using Alaska Mobile Track to see the current status of their package.
  • And FlyingSocial enables Facebook users to access all current Alaska Airlines offers.

By implementing an API, Alaska Airlines has been able to securely showcase itself to others, thereby increasing its commercial activity.

Are you interested in financial APIs? Discover all the APIs we can offer you at BBVA

See other success stories with APIs





Creado el 24 May. 2018

Developers often forget that creating, organizing and maintaining a set of APIs also means working hard on managing the user experience. After all, your APIs will be used by other developers.

An API is only as powerful as the applications and programs it connects; and if developers find it hard to incorporate an API, this may affect its end performance. You can never go wrong if you create APIs you would like to use yourself.

It's not complicated at all to create an API with good user/development experience. To do so, you can follow a list of rules that are somewhat abstract but that you must bear in mind at all times; otherwise, your end product will not be consistent or easy to understand by an external developer.


Understandable and intuitive

In other words, an API whose documentation is secondary reading. And whose methods clearly say what they do, how this is requested and what data are returned. Naturally, all documents must be read but doing it once should be enough.

It's not only a matter of creating a constant naming system that follows industry standards. Developers must also be able to intuitively anticipate the returned content.

How not to do it: design methods with generic names and numeric variables based on external IDs that cannot be recognized at first glance:


Recommendation: use descriptive methods in your names for methods and arguments.




By definition, an API does not exist on its own in a digital haven, living independently from all other applications. APIs are extended, changed and refactored over time based on the feedback of other developers or the project's own needs. Extensibility is essential in two ways:

•       API's own extensibility: the API must be able to grow with new methods in the future so as to maintain the principles of intuition and clarity we mentioned above.

•       Extensibility of others: the API must be designed to help other developers create better applications; it must go beyond offering a connection between two points.

In user experience, the second type of extensibility is largely achieved through callbacks, which define the execution of data returned by the API.

Make sure that the data included in the response are enough to help design more agile user interfaces that require less code and facilitate development.

How not to do it: return few fields with unrecognizable values; need for extra calls in most cases.

{ "users": [ 2, 3, 4, 5 ] }

Recommendation: the data returned by the API must be descriptive and with the ability to extend the connected software

{ "users": [{

        "id": 2, "name":"Laura", "date_registered": "2008/09/29"},

        "id": 3, "name":"Sara", "date_registered": "2008/09/29"},

        "id": 4, "name":"Ramón", "date_registered": "2008/09/30"}




Do not reinvent the wheel. More experienced developers with more free time will have created some kind of "good practices" for user experience in practically all fields of software; your API must follow these standards. Find out about them, learn them and enforce them.

Ask for comments from other designers and developers during the initial planning stage. It is essential to know the interface's end needs and the target experience.

If your API is going to be added to a complicated ecosystem of connections, especially in corporate settings, our two initial tips must prevail: intuitive and extensible.

If your API's UX is poor, you can ruin the underlying work of the entire organization and destroy any possible agreements because a competing API is better adapted to its functions, involves less development from third parties or is designed using known industry standards.

Are you interested in financial APIs? Discover all the APIs we can offer you at BBVA

Creado el 22 May. 2018

One of the great recent revolutions in technology is data management in the cloud. Not only for large volumes of information, what we know as Big Data, but also in relation to platforms or services for end users, such as a customer or a company’s employee. The result of this effort is embodied in hundreds of tools and features for managing information in the cloud: from office automation like Google Drive or Microsoft OneDrive to storage of personal images and videos through applications.

The greatest challenge for companies and developers is integrating their own system infrastructure with these cloud-based platforms or services, often with third-party providers, and improving the entire experience deriving from that strategic move. APIs are the real key in all this process. We have already mentioned two giants in the sector: Google and Microsoft. But there are many others, such as Amazon or Salesforce

Four possible scenarios for companies

Sometimes the IT infrastructure of companies is made up of what is known as legacy systems, in other words, outdated services or platforms that are being used and cannot be replaced easily. In order to make this decision, development teams can follow several paths, to a great extent conditioned by the services or platforms they need to integrate into their own service infrastructure, usually linked to certain providers:

  • PaaS APIs: Platform as a Service APIs provide access to the different features of a cloud-based service. For this to be possible, the service has to be integrated with the initial infrastructure's own elements. This connection is always done through APIs.
  • SaaS APIs: Software as a Service APIs facilitate the connection between cloud-based software/functionality and the entire system infrastructure underpinning the source platform. For example, a typical example is using APIs for connecting to a cloud-based CRM or CMS platform (content editor) to connect them to the entire underlying system infrastructure.
  • IaaS APIs: Infrastructure as a Service APIs enable the resources existing in the cloud-based service to be managed easily.
  • Several providers of cloud services: The most common scenario in companies today is to coexist with several providers in the cloud, where each one offers services with very varied engagement concepts, from Platform as a Service or Infrastructure as a Service to Software as a Service. APIs are the most effective way to manage increasingly complex models. They are the keys that open all the doors.

Interoperability, the essential element

As a company's services in the cloud grow and, therefore, it starts to feel the need to create a service provider network in the cloud, its need to ensure true operability grows exponentially. Otherwise, it can become too reliant on a single provider. As the different services cannot coexist, the most obvious technical solution is for a single provider to provide all the services. But this obviously has clear risks for the future of the company and for its own business.

Some market players have been making interesting moves for some time to force the entire set of cloud providers to accept a number of requirements that would ensure that the service models could always coexist and thus ensure interoperability. One example is the OpenStack Foundation, which is laying a firm foundation for using services in the private and public clouds with many providers on the market. The standardization work of the OpenStack Foundation goes in two directions:

  • Basic services that are common among cloud providers: The most obvious option is for cloud-based service providers to offer a set of basic services where interoperability between platforms and the different types of cloud is completely cross-cutting, with no specific features by provider. This, for example, would enable an application to be written once irrespective of the provider or the future service changes made by the original system infrastructure owner. In the end, OpenStack made the decision to incorporate public-domain code into its products, which in some way is forcing providers to combine own elements in the private cloud with those in the public cloud. And this results in the model called for by companies: hybrid cloud services. Some of these providers are HP, IBM, Rackspace, Red Hat, Suse and Canonical.
  • Federated identities: Federated identity is one of the solutions that makes it possible to manage users irrespective of the companies. It is ultimately a process that synchronizes the user's ID details and the entire access management process. In the case of OpenStack, the federated identity management system is called Keystone, an authentication (AuthN) and high-level authentication service (AuthZ). This user identification process at each OpenStack provider is done through its identification API. Many companies have already joined this identification mechanism interoperability project: Cisco, HP, IBM, Red Hat, Oracle, Mirantis, Stratoscale, Raclspace or Ubuntu.

Are you interested in financial APIs? Discover all the APIs we can offer you at BBVA

Creado el 21 May. 2018

Progressive Web Apps combine the best of web and native applications. They require no installation, like the latter, and are becoming more and more powerful, as they load faster and send important notifications. This explains why PWAs are gaining increasing interest from companies in several different sectors.

Currently compatible with Google Chrome but not with iOS, PWAs must fulfill four technical requisites:

1.- A site must be visited twice within a five-minute interval to qualify.

In Google Chrome, users must have visited the site hosting the PWA twice before the browser shows the message to install it.

This is not the most reliable form of verification, but it is a simple way of determining the user's interest. This parameter will probably be replaced by another better one in the future, but for the time being Google's developers are satisfied with this measure.

2.- Valid secure HTTPS connection

As the Progressive Web App has a secure connection, users can feel relatively safe about allowing it permits. As network requests are routed via a service worker script, adding https to the server helps mitigate certain vulnerabilities. This makes it possible to run heavy code in the background and to communicate with them so that one or several long tasks do not block the user interface.

Although the main thrust of this requirement could be primarily to add security, having a secure connection also contributes to create trust among users. What's more, as PWA can be indexed by search engines, it also makes sense to serve through TLS, cryptographic protocols that provide secure Internet communications, as they add a small amount of SEO benefit.

3.-Valid installed JSON manifest

When you provide a data extract in JSON format, this information can be cached with the help of the service worker. The shell app (a model or pattern when creating apps) is then used to load the CSS rules and deliver an offline version with complete user interface capabilities.

Each time a visitor loads a new page, the service worker will cache the JSON extract and store it physically in the shell app. This shell is an autonomous container with all the style sheets, scripts, images, fonts and HTML outputs necessary to enable a user to represent a complete page without loading anything else.

4.- Installed service worker

As we have said, the service worker is responsible for caching all the files, push notifications, content updates, data handling and much more.

It is important to understand that this script functions independently of any app or website already on the web server, working with events listeners and commands such as "fetch", which is similar to the HTTP commands "Get / Post / Set".

As it listens to the network requests on the server, but it is located as a .js file in the user device, the service worker will handle these requests with appropriate responses depending on whether there is an Internet connection or not, allowing customized pages offline.

Once these four requirements have been correctly implemented, users of Android phones and other compatible devices will be asked to add the PWA to their home screen, where there will be an icon similar to a regular app, which will open in a browser.

In constant development

Developers must take into account that they need to ensure that the user interface is similar to the one on the site or application, although they may prefer to develop a completely new user interface for PWA users. This freedom of choice is what has caught the attention of some developers interested in this trend.

For the time being PWAs are not available for iOs and are only compatible with Chrome on Android (and only in recent versions of the browser). This is certainly one of their great drawbacks, but in view of the fact that Android represents 85% of the cellphone market, they will continue developing and reaching more people.

On the Google page for Progressive Web Apps there are several examples of real apps, and they come with abundant documentation.

Source: Site Point

Are you interested in financial APIs? Discover all the APIs we can offer you at BBVA