Home > Blogs > Application design for the changing context
Mass customization in application design is the concept and act of designing interfaces that make every user believe that a particular interface is designed exclusively for them. Personalization at scale is the key driver for mass customization. Any task or activity, persona regardless, spans various stages such as interaction, operation and business process. In most of the cases, it cuts across multiple application boundaries as well. Personalization should span all these dimensions of interaction, operation and business. Context plays the biggest role in determining personalized behavior.
Key elements required for context include:
Please note, the above list is not exhaustive.
All dimensions of context are essential for an interface designed for personalization. In this article, we look at one of the dimensions – “where” – and explore it to figure out if there exists a pattern.
Access phase which followed automation phase in the banking industry focused on enabling the customers to carry out banking transactions using digital interfaces like ATM, online banking and mobile banking. All the controls and personalization were designed around these consumption points or touch points which are “Technical” in nature like ATM, browser, mobile, kiosk etc. For example, banks can setup different limits (which can be personalized) for browser, mobile and ATM.
During the next wave, banking services were made accessible through social media applications like Twitter and Facebook. Now, Facebook can be accessed using a browser on a desktop or through a mobile application. Hence “Application” provides context, with design controls for suitable behavior to drive personalization. In this wave, “Technical context” was immaterial. Hence the controls and personalization are around “application context” irrespective of their access points like browser or mobile.
During the next wave banking services were made accessible through third-party application through open banking APIs. This is a very interesting aspect since the provider of the banking services is neither aware of the technical context (can be browser or mobile) nor aware of the application in which banking service would be consumed. Here the context would be “Third party”.
This changing context is captured with examples in this table:
Channel | Supported By | Application | Technicality | Context to be considered |
Online Banking | Bank’s own channel | Online Banking | Browser | Technical |
Mobile banking | Bank’s own channel | Mobile Banking | Mobile | Technical |
ATM | Bank’s own channel | ATM banking | ATM | Technical |
Managed by 3rd party | Application | |||
Managed by 3rd party | Application | |||
AISP | Third party | Managed by 3rd party | Managed by 3rd party | Third Party |
PISP | Third party | Managed by 3rd party | Managed by 3rd party | Third Party |
Banks should recognize the various dimensions to provide personalized experiences amid changing context, and make sure that the right applications, advice, and assistance are made available. Designing such as experience cuts across interaction, operation and business layers.
In these increasingly digital times, interactions will originate on different channels and will also be influenced on these channels. And many of these channels will not be owned by banks. Context at all times, irrespective of the channel, will be the cornerstone of personalization in this digital future.
Narasimha Nagaraj
Head, Product Engineering & Digital Channels, Infosys Finacle
More blogs from Narasimha Nagaraj >