Web apps are (arguably) the most efficient way of transferring knowledge. Right now, most of the information in the world can be obtained from websites - be it an online course, news or other types of media. So one can alternatively think of web apps as conduits of knowledge. If web apps have such an important responsibility, then their structure matters. Let’s stop for a second to look at how web app architecture trends have progressed over time.
The architecture of web apps has changed significantly since the day modern browsers started to gain traction. From Java applets, through to .NET, JSP, and other templating technologies. These set the scene for jQuery, Knockout which led to the modern world of Angular and React. It took time and effort to achieve the state of the art that we have now. Most of the technologies above fall under the umbrella of monolithic architectures - one piece web apps.
More recently, the web developer community has started to care more about decentralized architectures. We went back to basics and began to think a lot more about components. HTML itself is designed as a set of elements, so it is a natural habitat for modular web components. Libraries like React, Polymer or frameworks like Angular 2.0 allow us to build separate components and combine them into websites. This fundamental idea can result in powerful results and outcomes.
Websites are expected to become a combination of components that can also be accessed separately. That gives others an opportunity to include those separate app components into their websites. Hence the visitors of that second website can benefit from the information that the integrated element visualizes. An excellent example of this type of component would be Google Maps. Many of us would have used the standalone application, but we see it even more frequently embedded in the contact or location pages of websites. Going back to the interpretation of websites as knowledge bearers, the componentized architecture, therefore, allows a simple but effective knowledge sharing mechanism across the web.
Web Components within the Altocloud Dashboard: Outcome Probabilities
Businesses are craving more context about their customers. The information allows them to engage better with their customers without having to repeat questions, therefore making the engagement more productive and less stressful for the customer. The latter is an essential ingredient for business success.
At Altocloud our goal is to help businesses achieve that contextual synergy. It has inspired us to compose our web apps from components that can be accessed independently as well as in a full web app. Therefore any combination of our knowledge-bearing contextual elements can be rendered on any third party website or webapp that our customers wish. We endeavor to deliver customer context for businesses in the most flexible way possible.
Knowledge is power.
If you would like to hear more about our customer journey analytics and digital engagement tools, talk to our customer team today or book a demo here.