Framework for the declarative implementation of native mobile applications

Abstract

The development of connected mobile applications for a broad audience is a complex task due to the existing device diversity. In order to soothe this situation, device-independent approaches are aimed at implementing platform-independent applications, hiding the differences among the diverse families and models of mobile devices. Most of the existing approaches are based on the imperative definition of applications, which are either compiled to a native application, or executed in a Web browser. The client and server sides of applications are implemented separately, using different mechanisms for data synchronization. In this paper we propose DIMAG, a framework for defining native device-independent client-server applications based on the declarative specification of application workflow, state and data synchronization, user interface, and data queries. We have designed DIMAG considering the dynamic addition of new types of devices, and facilitating the generation of applications for new target platforms. DIMAG has been implemented taking advantage of existing standards.

Can We Rely on Smartphone Applications?

“…According to the preceding section, and as an answer to the first research question raised in the abstract, it can be concluded that the most successful reliability models [9] failed to account for the failure data and to predict the reliability of mobile applications. This failure can be traced back to the following main reasons: (1) Operational Environment and Usage Profiles of Smartphones Applications, (2) Hardware and Software Limitations [10]. Assuming all of these uncertainties, at a second stage, and in order to answer the second research question, we collected data from many users in different regions of the world, sorted them by application versions, and grouped them in different time periods (days, weeks, and months).…”

Mobile accessibility expense analysis of the agrarian WWW portal

“…Alongside the expenses for personnel (Table 3; only main tester and UX specialist included, not additional testers), there were the costs associated with obtaining the Xamarin development environment which cost 999 USD (Xamarin 2015) per year, and the MS Visual Studio which cost 1286.65 EUR (Visual Studio 2015). Higher monetary and time expenses can be also expected when maintaining the resulting applications and keeping them updated (Xanthopoulos and Xinogalos 2013;Miravet et al 2014;Chang and Oh 2015).…”

“…Thanks to optimization, the platform specific applications are usually very fast, but they are commonly plagued with problems in the implementation pro- Source: Author and CSO (2015) doi: 10.17221/313/2015-AGRICECON cess (Miravet et al 2014). One of the approaches of developing native applications in the cross platform environment involves using the shared code base, but that cannot be done in every situation and scenario (Klima and Selinger 2013).…”

Improving University services using mobile web applications based on PHP/JSON-RPC technology

“…Uzimajući u obzir sve ove podatke može se zaključiti da će upotreba mobilnih uređaja u budućnosti biti sve veća i veća a samim tim i razvoj Web aplikacija za mobilne platforme će biti u porastu. Ova Web aplikacija je prilagođena za rad na svim operativnim sistemima koji podržavaju HTML/ JAVASCRIPT/ CSS3 i PHP/JSON-RPC tehnologiju [1,2], tu se pre svega misli na Symbian, Windows mobile, Palm OS, Android i iPhone OS za Apple uređaje i na sve pretraživače koje navedeni operativni sistemi koriste.…”