Refine
Year of publication
- 2021 (12) (remove)
Document Type
- Part of a Book (12) (remove)
Language
- English (12) (remove)
Keywords
- robotic process automation (2)
- Central receiver power plant (1)
- Coefficient of ocular rigidity (1)
- Concentrated systems (1)
- Concentrating solar power (1)
- Corneo-scleral shell (1)
- Cross-platform (1)
- Differential tonometry (1)
- Evaluation (1)
- Eyeball (1)
- Fresnel power plant (1)
- Gas turbine (1)
- Mobile web (1)
- PWA (1)
- Pressure-volume relationship (1)
- Progressive Web App (1)
- Robotic process automation (1)
- applications (1)
- artificial intelligence (1)
- business process automation (1)
Intelligent autonomous software robots replacing human activities and performing administrative processes are reality in today’s corporate world. This includes, for example, decisions about invoice payments, identification of customers for a marketing campaign, and answering customer complaints. What happens if such a software robot causes a damage? Due to the complete absence of human activities, the question is not trivial. It could even happen that no one is liable for a damage towards a third party, which could create an uncalculatable legal risk for business partners. Furthermore, the implementation and operation of those software robots involves various stakeholders, which result in the unsolvable endeavor of identifying the originator of a damage. Overall it is advisable to all involved parties to carefully consider the legal situation. This chapter discusses the liability of software robots from an interdisciplinary perspective. Based on different technical scenarios the legal aspects of liability are discussed.
The existence of several mobile operating systems, such as Android and iOS, is a challenge for developers because the individual platforms are not compatible with each other and require separate app developments. For this reason, cross-platform approaches have become popular but lack in cloning the native behavior of the different operating systems. Out of the plenty cross-platform approaches, the progressive web app (PWA) approach is perceived as promising but needs further investigation. Therefore, the paper at hand aims at investigating whether PWAs are a suitable alternative for native apps by developing a PWA clone of an existing app. Two surveys are conducted in which potential users test and evaluate the PWA prototype with regard to its usability. The survey results indicate that PWAs have great potential, but cannot be treated as a general alternative to native apps. For guiding developers when and how to use PWAs, four design guidelines for the development of PWA-based apps are derived based on the results.