Common use of Standardization Clause in Contracts

Standardization. The Pressure to Go Multiplatform When looking at the development of home banking, the transfer from the early adoption phase to the expansion phase was driven by the need for more users to use home banking. This is different from the transfer of the expansion phase to the exploitation phase, which seems to be driven more by banks to reduce costs and increase client- side interoperability. The perceptions that have the most influence on embracing home banking were positive in the expansion phase, and stayed positive after the transfer to the exploitation phase. For mobile banking, the changes between phases were quite similar. The changes made during the transfer from the early adoption phase to the expansion phase were also due to the need for an increase in user acceptance. Unlike home banking, it seems that an exploitation phase (characterized by the use of open (web) technologies) has not been reached yet for mobile banking. Browser-independent mobile banking sites actually exist, but they are not offered by as many banks as mobile client-side applications. While we do not know the exact reasons used to rationalize the choice to offer mobile banking applications over mobile sites, we understand that there are enough possible arguments from many different perspectives for why applications are preferred. A technical reason for this might be that applications have a better integration with the underlying operating system and hardware, through which banks can gain more information (such as data from sensors, biometrics, etc.) compared to mobile browsers. As noted earlier, aesthetics are an important factor in the acceptance of mobile banking. A functional reason might be that an application integrates visually better with the operating system, creating a more consistent user experience. A usable security reason might be that it is not required to provide a client-side application with information (e.g., a URL) to reach the bank, which is both user friendly and which reduces the risk of visiting a wrong (and possibly fraudulent) website. Of course, the risk still exists that a user accidentally installs a malicious application instead of ACM Computing Surveys, Vol. 49, No. 4, Article 61, Publication date: December 2016.