Comparing the Widows Mobile and Android Development Platform

Mobile Development Platforms Comparison


Software giants such as Google disrupt the else safe and proven players in the development business of mobile applications. Newcomers like Android have brought about major systemic shifts in the creation of mobile apps by enforcing their guidelines. Not only does this changed world provide new opportunities, it also increases those restrictions. Today developers need to evaluate their choices and learn how they can take advantage of this changed environment.

While the attention of application developers has been paid to mobile computing, little work has been done to check the ease of the programming of these technologies. Here we will discuss and evaluate these choices from an evolving viewpoint, taking a look at two of the most commonly accessible mobile development environments – Android and Windows Mobile..

Android The
Google launched Android in 2007 as an open-source software development platform for cell phones. As part of the open handset alliance, the Android platform was released. The main objective of the partnership was to set open smartphone standards. Android is essentially an open source, Linux-based mobile operating system. As a mobile operating system, developers can generate controlled codes in Java using Google’s Java libraries. Android provides not only a mobile OS, and a development environment, but a custom virtual machine for running applications as well as a middleware between the operating system and code known as Dalvik’s Virtual Machine. As regards the application growth, Android makes it easier to use 2D and 3D graphical libraries as well as advanced network capabilities like 3G, Edge and WLAN and an on-the-go SQL engine.

Mobile Windows
The Window Mobile is a Microsoft-developed mobile device operating system. Windows Mobile is used as a multi-smartphone, PDAs and touch screen operating system using the Microsoft Windows CE 5.0 system. Windows Mobile enables the development of controlled and native custom written applications. The Windows Mobile Application Programming Interface (API) is expandable and features a rich programmable layer. In addition to Windows Mobile, the functions offered by Microsoft are also used. The net world. Net environment.
These platforms will be compared and their strengths and limitations closely investigated. The platforms are compared according to implementing, operating and developer support aspects. These reference requirements have been selected as they are the key aspects for mobile app designers.

For a comparison of the implementation factor, we will use continuous storage. The technology used for permanent mobile storage differs from one mobile environment to another. Both Windows Mobile and Android are able to use a device database that makes it easier to manipulate and collect data. Furthermore, both environments support extra storage space for memory cards as regards local file storage. The difference, however, is how the storage room is used. Windows Mobile allows Android to run apps on memory cards. There’s a relational database for both Android and Windows Mobile platforms. The libraries also have a range of useful continuing characteristics in both platforms. Upon initialization of the libraries, access to the database is accessible through an object-oriented interface, which developers can easily access.

Lei stung
For users and developers, performance figures are significant. The findings are compared on the basis of the size of the file. The two platforms. The basic aim of calculating file size is to obtain a better understanding of the configuration and runtime dependency of the packages.
Android apps are compiled into APK files (Android Package). There was an error. APK file typically consists of a group of . DEX (Android software files) files operating in an Android framework as one device file. There was a mistake. The APK file simply is the version of the ‘AndroidManifest.xml’ contents compressed.

Windows Mobile apps use cab-files for packaging and deployment of applications. In the first stage, the application is packaged into a cabinet file while creating a distributable file. This CAB file can be mounted on other computers to extend and instal it. Basically, a CAB file is an executable file containing the programme, tools, addictions like DLLs or other resource files.

Tom Morten Gronli, Jarle Hansen and Gheorghita Ghinea from Brunel University, London conducted a comparative study of mobile development environments. A demo example application was developed in the comparative study on Windows Mobile and Android development platforms to show the scale of the application deployments. A basic programme that printed a text line on the computer was the application for demo examples. The code example resulted in the following:

The demo application’s deployment size was 2,8 kB in Windows Mobile.The prototype application was 9.3 KB in the Android world.The denoted file sizes were without a shrinker or programme. This is the type of file that will be downloaded or sent to an end user and installed on its computer. As seen from above, the Windows Mobile demo application was 2.8 KB in file size, while Android was approximately 3 times 9.3 KB in size. This is an example of the total sum to be grouped together with each client programme in the configuration and the runtime dependencies.. As for the number of code lines, Windows Mobile only required 11 lines, while Android needed 28 lines.

Comparison of Developer Support

The help of developers is a very important feature for speed and quality in the process of development. Although both mobile platforms are identical, there are some specific developer support differences. When we consider the built-in developer environment (IDE) and instrumentation, the differences become clearer.

Visual Studio, which Microsoft built again, is the only option for the development of Windows Mobile. Windows Mobile requires Microsoft support with Visual Studio, so it can incorporate new features and ship them in the IDE. The group can make only recommendations but has no direct impact. However, as continuity is guaranteed, it has a positive side. In addition, Microsoft is able to ensure consistency through the process of approval during shipment of new goods.

On the other hand, many tooling solutions are available for Android, with several IDEs. Android has open source communities that contribute to IDE creation through providing plugin functionality for applications and ensuring quality. The various IDE environments can nevertheless be a challenge to maintain continuity and quality assurance. Consistency is a problem, since only a few competing IDEs have extension capabilities. Quality assurance is a big challenge as community development does not comply with a common quality standard until the new integrated developer environment feature becomes usable. For the supply of fully functioning goods, the guarantee of quality of the code supplied is important. These two factors will theoretically prevent code and portability of applications between environments.

In the testing environment, one of the gaps between the Android and the Windows application development systems is clearer in terms of developer support and quality assurance. Let us look at this closely as the two software platforms undergo unit testing.
Testing units are simply a method for quality assurance and validation for small device or smartphone applications to be tested. Each segment should be individually isolated and tested. This helps to separate the various units of the application and ensure their consistency.

The unit testing of Android is significantly easy as the JUnit testing system is used for the API. The JUnit system supports the hierarchical organisation of the different test units which represents a significant advantage. In addition, the JUnit pattern guarantees independence and minimises interference from test units. This is achieved before and after each test process, creating and then destroys the newly generated test environment. JUnit is even further taken by Android by enabling code testing of the software. The test libraries are included in the regular Android libraries..

However, compared with Windows Mobile, Android’s readability in application testing presents a problem. Android on mobile tests has no user interface that displays the results of the test. A handler to deal with Android test runner calls must be introduced in order to check the test results.

In comparison, Windows Mobile has a high standard of readable and visible content, while the Android platform is a little difficult to use in terms of performance. The problem with Android is that there is a lack of input automatically emitted from visual resources in the integrated Windows Mobile development environment.

The version of the xUnit platform is implemented by Windows Mobile. In a separate project, the code for test classes is maintained, but it remains within the IDE solution.. Like Android, the xUnit testing of Windows Mobile also supports d

Leave a Comment