Assessing the feasibility of Micro frontend architecture in native mobile app development

Objectives: This research study provides an analysis model which is used to analyze the requirements of mobile native apps contextually under any domain. Methods/Statistical Analysis: Based on the background study, the research process have taken three research approaches and also have identified various activities which are performed among a native mobile app user and mobile native apps and formed them into questionnaires which are sent to different mobile native app developers of different software industries. This research process has determined the requirements based on four contexts in mobile domain such as device context, mobility contexts, user context and social contexts. Findings: These activities are mapped into attributes and contexts for modeling the requirements under mobile domain and for developing the sub models of the analysis model. Finally the analysis model is built and composed of four sub models. These sub models are content analysis model, interaction analysis model, functional analysis model and configuration analysis model. Application/Improvements: This research study provides the analysis model where the requirements are analyzed in a mobile native app under any domain such as agriculture, learning or healthcare applications. This analysis model is significant as it determines the contexts and models the contexts which are not specified in any frameworks or process models. Keywords: Configuration Analysis, Content Analysis, Functional Analysis, Interaction Analysis

Multiple Sclerosis (MS) is a chronic neurodegenerative disorder. People living with MS (plwMS) require long-term, multidisciplinary care in both clinical and community settings. MS-specific mHealth interventions have advanced in the form of clinical treatments, rehabilitation, disease monitoring and self-management of disease. However, mHealth interventions for plwMS appear to have limited proof of clinical efficacy. As native mobile apps target specific mobile operating systems, they tend to have better interactive designs leveraging platform-specific guidelines. Thus, to improve such efficacy, it is pivotal to explore the design characteristics of native mobile apps used for plwMS. This study aimed to explore the design characteristics of native mobile apps used for adults living with MS in academic settings. A scoping review of studies was conducted. A literature search was performed through PubMed, CINAHL, MEDLINE and Cochrane Library. Per native mobile apps, characteristics, persuasive technology elements and evaluations were summarized. A total of 14 native mobile apps were identified and 43% of the identified apps were used for data collection (n=6). Approximately 70% of the included apps involved users (plwMS) whilst developing (n=10). A total of three apps utilized embedded sensors. Videos or photos were used for physical activity interventions (n=2) and gamification principles were applied for cognitive and/or motor rehabilitation interventions (n=3). Behavior change theories were integrated into the design of the apps for fatigue management and physical activity. Regarding persuasive technology, the design principles of primary support were applied across all identified apps. The elements of dialogue support and social support were the least applied. The methods for evaluating the identified apps were varied. The findings suggest that the identified apps were in the early stages of development and had a user-centered design. By applying the persuasive systems design model, interaction design qualities and features of the identified mobile apps in academic settings were systematically evaluated at a deeper level. Identifying the digital functionality and interface design of mobile apps for plwMS will help researchers to better understand interactive design and how to incorporate these concepts in mHealth interventions for improvement of clinical efficacy.

The proposed system uses Natural Language Processing (NLP) and Deep Learning (DL) techniques to extract voice data and translate it to text during medical consultations. Iterative model was adopted in the design of the system and the user interfaces was implemented by using NLP techniques, especially speech recognition and natural language understanding. Deep learning algorithm shows a great ability to build clinical decision support systems by extracting various information for medical diagnosis and produce result is few seconds. The result form the system testing shows that the installation size of the Progressive Web App (104 KB) is 42 times smaller than the native Android app (4.37 MB). In terms of render-speeds, the PWA rendered different results. The native app will launch the Android activity after 1408 ms after app icon tap (launch), while the progressive web app launches the application in 230 ms. The advent of cross-platform application development frame-works have made it much easier to create applications for multiple platforms for mobile devices. In spite of reduced learning effort, usually lower costs, and a faster time-to-market cross-platform methods always do not prevail in most cases. Although there are normal exclusions – like graphic-intensive games, which should to be programmed with the native software development kits (SDKS), choice between native apps, cross-platform generated ones, and Web apps can remain delicate. Whereas many diverse efforts have been made with respect to how cross-platform development frameworks ought to work, no technology is deemed unequivocally superior than the others. But a cross-platform mobile app has got an edge over native app development. It also recommends that developers adopt this technology of mobile app development due to its huge gains.

Smartphone apps support people to adopt healthy lifestyles. Therefore, it is useful to understand the persuasive design strategies involved in hybrid mobile applications that facilitate behavior changes. The aim of our research is to show the ease of use of hybrid mobile applications compared to Web and Native applications. Hybrid mobile apps combine the features of Web apps and Native mobile apps. Like web applications, they are implemented in portable, platform-independent languages such as HTML and JavaScript. They directly access local device resources such as native apps. Transition to hybrid applications has been increasing in recent years with the rapid progress of technology. Although it has performance disadvantages compared to native applications, it is more preferred by software developers due to its ease of use. From the results, it has been determined that the user interface for hybrid applications is simpler to develop with its dynamic structure and it uses mobile device features better in terms of performance when used in hybrid applications.

The global expansion of smartphones and tablets has created a huge industry of mobile applications. The cloud computing together with the mobile cloud apps, have been both gaining importance against native apps in the last years. This paper aims to perform a comparative study about the features of native and mobile cloud apps for health care. With that purpose, we have developed an academic and non-academic review of features, advantages and disadvantages of both types of apps and we have applied these features in three different health care scenarios: an Electronic Health Records (EHRs) administration app in a wide region, a heart rate monitoring app in a rural area, and a diabetes management app. It was concluded that although the mobile cloud apps offer significant advantages, which overcome the ones of native apps in some scenarios, there are other cases where native apps are the only solution. Hence, both types need to coexist for a while. As users seem to prefer native apps, a possible solution can be the use of hybrid apps, mobile cloud apps with a native container, since they get advantages from both types.

We can notice that security problems of inappropriate integration of native and web technologies in hybrid mobile applications (apps) have been covered in the related state-of-the-art research. However, analyzing hybrid mobile apps' unique behaviors has been seldom addressed. In this paper, we explore the influence of native and web technologies integration in hybrid mobile apps on the generated profile of mobile applications. Specifically, we analyze the type of Security Sensitive APIs (SS-APIs) exposed to web content and identify the corresponding usage patterns by systematically tracking function-call-graphs of a large number of hybrid and native mobile apps. Our investigations indicate that the generated profiles for hybrid and native mobile apps are considerably different. Using our proposed tool, called Hybrid-scanner, for tracking and analyzing internal behaviors of hybrid mobile apps, we show that there is more trace of API calling for triggering a specific SS-API in a hybrid mobile app in comparison with Android native mobile apps. In addition, we have found that almost 40% of SS-APIs in hybrid mobile apps are invoked by third-party libraries, e.g. advertisement libraries. This knowledge, however, is crucial for designing appropriate malware detection or vulnerability mitigation strategies. Based on our results, we discuss two main approaches in Android malware analysis field and enumerate some suggestions which should be considered in order to successfully detect malicious behaviors in such new type of apps.

Given the monopoly over native mobile market for certain kind of apps, a cheaper and an easier to make alternative is necessary. One such alternative are the progressive web apps which solve some of the issues related to the native mobile apps. The goal of the work is to analyse the pros of progressive web apps and native mobile apps and estimate why and at which scenarios the progressive web apps can outcompete native mobile apps in terms of the pros.

Aims and objectivesTo review the available literature regarding the use of prostate cancer-related mobile phone applications (PCA).Materials and methodsThe search was for English language articles between inceptions of databases to June 2019. Medline, EMBASE, Cochrane Library, CINAHL and Web of Science were searched. Full-text articles were reviewed, and the following data were extracted to aid with app analysis: name of application, developer, platform (Apple App Store or Google Play Store) and factors assessed by the article.ResultsThe search yielded 1825 results of which 13 studies were included in the final review. 44 PCAs were identified from the data collected of which 59% of the PCAs had an educational focus. 11 apps were inactive and 5 weren’t updated within the last year. Five studies focused on the development and testing of apps (MyHealthAvatar, CPC, Rotterdam, Interaktor, NED). Two studies evaluated the readability of PCAs. Most PCAs had a reading level greater than that of the average patient. Two studies evaluated the quality and accuracy of apps. Majority of PCAs were accurate with a wide range of information. The study reported most PCAs to have deficient or insufficient scores for data protection. Two studies evaluated the accuracy of Rotterdam, CORAL and CPC risk calculators. Rotterdam was the best performer.ConclusionsPCAs are currently in its infancy and do require further development before widespread integration into existing clinical practise. There are concerns with data protection, high readability standards and lack of information update in current PCAs. If developed appropriately with responsible governance, they do have the potential to play important roles in modern-day prostate cancer management

With the vigorous development of the modern science and technology, mobile phone APP in such aspects as enterprise, education, medical treatment is getting more and more attention. The development and application of mobile phone APP facilitates the daily life of people. The development and application of medical APP, has gradually become the trend of the 21st century in medical domain. Health educational APP, as a new type of health educational mobile phone application software, gets the favor of people. Health educational APP has the advantage that the pertinence, initiative and timeliness, but in terms of the current health educational APP, which defects such as patient information disclosure and unreliable. Therefore, we need to strengthen the market management of health educational APP, audit the authenticity of information content and make it more professional. In the future, health educational APP can truly helm our health. Key words: Health education; Application; Development

Mobile apps have found wide acceptance in today’s world which heavily depend on smart technology to access data over wide location. The apps are mostly of native type which can be used for accessing data even without the internet availability. In this paper the development of mobile native applications requires the assimilation of various analytical contexts depending on the requirement of users. We have done an empirical study of various papers based on ubiquitous systems and mobile apps for finding out the contexts in building mobile native apps and the mobile contexts are such as device context, user context, mobility context and social context. We have found that the overall weight of each mobile context is an empirical study. We have taken various activities which are performed among a user and mobile native apps and formed them into questionnaires which are sent to different mobile native app developers of different software industries. The mapping is done among these activities with the attributes and their associated mobile contexts. We have identified and obtained four contexts as main requirements for developing mobile native apps under any domain. The analysis of requirements is done modeling the contexts and their attributes through OWLDL language. We have determined from the empirical study that the overall weight of device context is more than the other contexts. Hence it is clear that the device context with its numerous features have a great impact on developing mobile native apps under any domain.

prevalent smartphones have become the major entrance to accessing services on the Internet. On smartphones, users can have two options as the clients, i.e., native apps and Web apps. There have been several debates about native apps and Web apps. However, major service providers such as Google, Amazon, and Facebook provide both native apps and Web apps to end-users. Essentially, the performance differences between these two types of apps haven't been addressed. Indeed, the performance differences make non-trivial impacts on apps development, deployment, and distribution. In this article, we conduct a measurement study on the performance of native apps and Web apps on Android smartphones. Specifically, we want to explore given the same functionalities, do Web apps always perform poorly compared to native apps. We select 328 services from some popular providers, covering various domains such as e-commerce, map, social networking, and entertainment. With HTTP-level trace analysis, we demystify the workflows on how native apps and Web apps deliver services on mobile devices, respectively. Then, we characterize the performance differences between native apps and Web apps with the metrics including the number of requests, response time, data drain, and energy consumption. We find that the performance of Web apps is better than native apps in more than 31 percent cases. Our derived knowledge can suggest some recommendations to improve the performance for mobile apps.

A process-oriented modeling approach for graphical development of mobile business apps

BackgroundGiven the effective role of a mobile applications in disease management, disease monitoring, and self-care in patients with COVID-19 disease, we aimed to design, development and evaluation of a self-care Mobile app for COVID-19 patients not requiring hospitalization.MethodsThe design, development and evaluation the usability of the self-care and education mobile app for patients with COVID-19 disease were conducted in two main phases at 2021 in Northwest of IRAN; (1) Determine the features and capabilities and (2) Design, development and evaluation of self-care mobile App. JAVA programming languages and Android Operating System were used and selected to design and development of a mobile app. There were 25 participants who conducted evaluations of the mobile app’s usability and impact using the mobile health app usability a Questionnaire of User Interface Satisfaction was administered to assess the usability of the developed application. The results were analyzed via Excel 2013.ResultsThe model of developing a mobile app as an Information System was the Waterfall model. The smartphone application based on a set of capabilities and features was designed and consists of two main parts: the login screen for user registration, and the main home menu. The user interface includes three main pages or activities; (a) Main Menu for quick access to all of the pages, (b) Symptom management and monitoring to monitor the signs and symptoms during the illness, and (c) Set Reminders and Alarms to notify patients. The users’ mean score of the application usability was calculated as 7.91 out of 9 indicating a good level of satisfaction.ConclusionThis app can be a guideline and a useful tools for managing and monitoring symptoms, reminding medications, and implementing self-care instructions in outpatients. The authors suggest evaluating the efficacy and functionality test of mobile-based applications for COVID-19 in clinical trial studies.

Recent developments in mobile technology have enabled mobile phones to work as mobile Web servers. However, the composition of mobile phone applications and Web resources to form new mashup applications requires mobile programming knowledge ranging from how to create user interfaces, network connections and access to Web resources. Furthermore, the unique capabilities of mobile phone applications such as access to camera inputs or sensor data are often limited to local use only. To address these problems, we present a description-based approach and an Integration Model for the composition of mobile mashup applications combining Web applications, Web services and mobile phone applications (i.e., generic components). The compositions appear to require less native mobile programming knowledge. In the current work, to leverage access to these services and applications, an Interface Wrapper was used to transform generic components into mashup components. Composers were able to transform and reuse form-based query results from Web applications and integrate them with wrapped output from users' interaction with mobile phone applications, and other Web services. The final applications can be configured to work two ways: 1) as native mobile phone applications or 2) as a Web application accessible externally via a mobile Web server application.

A large number of web applications are written using server-side scripting languages. Although web browsers allow clients to run these applications, it is often cumbersome to depend on desktops for the services provided by the applications. Given the popularity and convenience of mobile devices, there is a clear need to have native mobile apps driving the applications along with web browsers. In this paper, we present a solution to re-engineer web applications developed using server-side scripting languages, into native mobile apps. The solution takes source code of the web application along with its test suite as input and produces corresponding cross-platform mobile apps. The entire re-engineering process is fully automatic requiring no manual intervention at any stage. Our solution is generic enough not only to handle popular server-side scripting languages, but also to output mobile apps that support diverse popular platforms including Android, iOS, and Windows Mobile. To showcase the capability and generality of our solution, we have developed a prototype tool KIRKE to handle applications developed using JSP, PHP, and ASP.NET. We present three case studies based on real-life codebases to evaluate the correctness, coverage, usability, and performance of our solution. The results indicate that KIRKE is capable of generating a mobile app that preserves the functionality of original web application and uses resources more efficiently when compared to the web application running on a mobile browser.