Liquid computing: Difference between revisions

Revision as of 06:07, 29 January 2025

Revision as of 11:57, 11 April 2025

Line 9:

A limitation of current liquid computing implementations is that they are confined to specific vendors' platforms, such as within Apple's iOS and OS X pair or within Google's Android and ChromeOS pair. That means workflows can't flow across different vendors' devices, such as from an Apple [[iPad]] to a Microsoft Windows [[Personal computer|PC]]. That is not a technical limitation of the liquid computing concept but a vendor decision to encourage adoption of its product ecosystem. Both Apple and Google, for example, make liquid computing capabilities available to developers through a set of [[API]]s that theoretically could be made available to competing platforms, but currently are not. To address this problem, the liquid computing concept can be applied to Web applications running across different Web-enabled devices.<ref>{{cite web|last1=Mikkonen|first1=Tommi|last2=Systa|first2=Kari|last3=Pautasso|first3=Cesare|title=Towards Liquid Web Applications (ICWE2015)|url=http://design.inf.usi.ch/publications/2015/icwe/liquid-web-app/|website=liquid.inf.usi.ch/|publisher=Springer}}</ref>

== Liquidity as a Quality Attribute ==

More in general, liquid software features flexible redeployment in response to changes to the software and to its execution environment.<ref>{{cite web|last1=Pautasso|first1=Cesare|title=A Brief History of Liquid Software (iEDGE)|url=https://ieeexplore.ieee.org/document/10234252|publisher=IEEE}}</ref> As the software is updated, the new version is seamlessly redeployed, replacing the previous one without any user disruption. As the devices on which it runs change (as in the above user workflow scenario), the software smoothly follows the user attention focus from one device to the next. Overall, within the [[List of system quality attributes], liquidity can be defined as the combination of deployability with flexibility.

== Related technologies ==