PLAGIARISM SCAN REPORT

Date 2020-12-31

Words 799

6% 94% Characters 5186

Plagiarised Unique

Content Checked For Plagiarism

An analysis was performed to calculate the execution times of selected tasks in order to compare the performance of native and hybrids
generated mobile applications. Because of their greatest market share, Android and iOS systems were chosen for experiments. On 95
percent of mobile devices in the world, both systems are deployed globally[3]. In the Xamarin environment, a cross-platform application was
developed. Its high popularity and rapid growth have determined the choice of this technology. There were 4 sections of the analysis. Time
is the aspect that affects the user experience most with the use of a mobile app. Another area of API application is involved in each of the
experiments: • Numerical measurements – the test measuring period for calculating the number of decimal places from ? to ten thousand; •
Save and read from a file – test tests write and read text file times containing the result of ? from the previous test measurement. The data
to be entered in the file is estimated and processed once. The time to measure is not included in the experiment result; • Network support –
the test tests the time taken to download a large graphic file from the Internet (about 7 MB). In the analysis, the same file put on a publicly
available server is used for every application. The same Internet connection was connected via Wi-Fi to smartphones; • Location
determinations — the test measured time in the cell phone sensors for determining latitude and longitude. The positioning of the GPS
system, the BTS transmitter position or the Wi-Fi networks available can also be identified on modern mobile devices.The test on both
systems was conducted using the default device setting in the absence of the iOS position method option. The time was determined when
the application logic was first instructed. The findings did not include the upgrading of the user interface and the presentation of the result. A
separate view was established in the application for each analysis. Any test run is followed by the re-entry of the appropriate screen into the
application for simulation of conditions nearest the real one. For the study six trial applications were created: three for each system: native
cross-platform based on the Xamarin Native approach and cross-platform using the Xamarin Forms books. The results obtained from the
analysis can be compared only via the device platform because of the variations in system design and the performance of mobile
components. Every test was conducted with care for the repeatability of the conditions in order to ensure the reliability of the findings. On
the same smartphones, apps ran. It was an LG G4 for Android and a 16GB iOS for iPhone 6. The applications have been reviewed on the
latest versions of operating systems available for the equipment to use all functionality of the system. For Android this was "Marshmallow"
Android 6.0 and version 9.3.2 for iOS. Applications have been created and installed on the phone with the 'release' compiler environment.
For each device and application, each test was conducted 20 times. The network tests were conducted with the same link. Location checks
at the same location have been conducted. Results of analysis Computing performance The computational efficiency test results are shown
in Table 1. In both systems, the evaluation was done much better by native applications than the cross-platform. The disparity between
native and cross-platform app performance on Android however is much higher. The calculations were made native to the cross-platform
about five times quicker. In the case of iOS, the gap was about 60%. Table 1- Results of the computing performance study Android(s)
iOS(s) Average Computing Time Native 4.515 3.215 Xamarin forms 22.315 5.116 Xamarin native 20.804 5.121 Figure- 1 File access Table
2 explains the effects of the write and read file. The Android native app was the slowest in the reading file survey, but the results were both
worse during other testing operations. There are also some variations between application models, but the results are in milliseconds, so
these differences may not be so significant in real life. Table 2. The results of the file read performance test Android [ms] read Android [ms]
write iOS [ms] read iOS [ms] write Native 26.502 2.722 0.714 16.945 Average Time Xamarin forms 5.114 6.751 1.484 18.475 Xamarin
Native 8.256 10.309 5.614 21.246 Figure-2 Image downloading The network connection test results are shown in Table 3. Similar findings
have been obtained for all applications. There are very few variations. These are most likely due to temporary bandwidth differences that
have been used for the evaluation.The network connection test results are shown in Table 3. Similar findings have been obtained for all
applications. There are very few variations. These are most likely due to temporary bandwidth differences that have been used for the
evaluation.

Matched Source

Similarity 7%
Title: (PDF) performance analysis of native and cross-platform mobile...
table 1 shows the results of the computing performance test. in both systems, native applications coped with the test much. better than the
cross-platform ones.

https://www.researchgate.net/publication/320039474_PERFORMANCE_ANALYSIS_OF_NATIVE_AND_CROSS-
PLATFORM_MOBILE_APPLICATIONS