Introduction
Software titans, like Google are interfering with the otherwise safe and established gamers within the mobile database integration business. Beginners like Android have brought to significant structural changes on the way forward for mobile database integration by imposing their rules. This transformed atmosphere not just brings additional possibilities, but additionally adds certain constraints. Designers today, have to assess their options and discover how they may take advantage of this transformed atmosphere.
While traveling with a laptop has caught the interest of application designers, there's been hardly any work completed to check out the programming easy these technologies. Wish to consider have a look at two most broadly available mobile development conditions - Android and Home windows Mobile and explore and assess these options from the developer's perspective.
Android
Android was released by Google in 2007, as an open source platform for mobile software development for smartphones. The Android platform was released as part of the Open Handset Alliance. The primary aim of this alliance was to set up open standards for smartphones. Android is basically a Linux based, open source operating system for mobiles. As a mobile operating system it allows developers to create managed codes in Java, by using Java libraries developed by Google. Not only does Android provide a mobile operating system including a development environment, it also offers a custom virtual machine known as the Dalvik Virtual Machine for running applications as well as acts as the middleware in between the operating system and the code. When it comes to application development, Android facilitates the usage of 2D as well as 3D graphic libraries, advanced network capabilities such as 3G, Edge and WLAN and a customized SQL engine for continual storage.
Windows Mobile
Developed by Microsoft, the Window Mobile is an operating system for mobile devices. Based on the Microsoft Windows CE 5.0, Windows Mobile is used as an operating system on many smartphones, PDAs and touch screen devices. Windows Mobile facilitates the creation of custom written applications in managed as well as native codes. The Application Programming Interface (API) in Windows Mobile is extensible and has rich features along with a programmable layer. Besides that Windows Mobile also takes advantage of the capabilities provided by Microsoft.Net environment.
We will compare these platforms and closely examine their str
engths and weaknesses. The platforms will be compared on the basis of implementation and performance aspects as well as developer support. We have chosen these criteria for the comparison as they represent the most important aspects when it comes to mobile software developers.
Performance
Performance figures are essential for customers in addition to designers. The performance comparison of these two platforms is going to be completed in line with the quality. The fundamental reason for calculating quality is to buy a much better concept of the configuration along with the run time dependencies which are incorporated in packed programs.
Android programs come packed in apk (Android Package) files. The .APK file generally has several .DEX (Android program files) files, which operate just like a single application apply for usage inside the Android platform. The .APK file is essentially the compressed form of the contents within the 'Androidmanifest.xml' file.
Home windows Mobile programs take advantage of cab-files for application packaging and deployment. The initial step while creating a distributable file, involves packaging the applying inside a CAB (Cabinet) file. This CAB file could be used with other products where it may be broadened and installed. A CAB file is essentially an executable archive which consists of the applying, assets, dependencies like DLLs along with other resource files.
A comparative study of mobile development conditions was carried out by Tom Morten Gronli, Jarle Hansen and Gheorghita Ghinea, of Brunel College, London. Within this comparative study, a demo example application was produced both in the Home windows Mobile and Android development platforms to higher illustrate the deployment quality for every application. The demo example application would be a simple program which printed a type of text on screen. The end result in the code example was the following:
The deployment size the demo application within the Home windows Mobile atmosphere was 2.8 KB.
The deployment size the demo application within the Android atmosphere was 9.3 KB.
The file dimensions as denoted were with no obfuscator or shrinker software. This is actually the kind of file that the consumer would either download or get shipped after which placed on his/her device. As possible seen previously mentioned, the demo application in Home windows Mobile were built with a quality of two.8 KB while Android was roughly three occasions the dimensions at 9.3 KB. This can serve as a sign of the quantity of configuration files and runtime dependencies which should be bundled up together with each one of the client programs. If this involves the amount of lines of code, Home windows Mobile needed only 11 lines whereas Android needed 28.
Developer Support Comparison
Developer support is really a very important aspect if this involves attaining speed in addition to quality throughout the expansion process. While both mobile development platforms will have commonalities, you will find some unique variations in developer support. The variations become clearer whenever we go ahead and take integrated developer atmosphere (IDE) and also the pedaling into account.
The only real option for rise in Home windows Mobile is Visual Studio, that is again produced by Microsoft. With Visual Studio, Home windows Mobile needs Microsoft backing before it may implement and ship additional features within the IDE. The city are only able to make suggestions but does not have direct influence. However, there's an optimistic side as consistency is assured. Also, the standard approval process implemented by Microsoft while shipping new items will ensure quality.
However, you will find several pedaling choices for Android, with a number of IDEs. Android has free towns who lead to IDE development by supplying in addition to guaranteeing quality of wordpress plugin benefits for software. However, the multiple IDE atmosphere could be a challenge for maintaining consistency and quality assurance. Consistency turns into a challenge as extension features might be readily available for only one competing IDEs. Quality assurance turns into a major challenge as development completed through the community isn't controlled by a typical standard for quality needed just before making the brand new integrated developer atmosphere feature available. Quality assurance from the shipped code is important for delivering completely functional items. Both of these factors could possibly make code and application portability between conditions impossible.
Among the variations between your Android and also the Home windows Mobile development platforms so far as developer support and quality assurance is worried gets to be more apparent within the testing atmosphere. Let's take particular notice only at that throughout unit testing of both development platforms.
Unit tests are essentially an excellent assurance and validation tool for testing small areas of a pc or mobile programs. The goal would be to have each section isolated and examined individually. This helps to isolate and assure the standard from the different models from the application.
Unit testing for Android is substantially straightforward because the API uses the JUnit test framework. The JUnit framework makes sure hierarchical organization of the several test models that is a major advantage. On top of that, the JUnit pattern guarantees independence from the test models in addition to minimizes interference. This is accomplished beginning with creating after which wrecking the lately produced test atmosphere, pre and post each test technique is run. Android even takes JUnit one step further by permitting on device testing from the code. Here the exam libraries are incorporated included in the Android's standard libraries.
However, there's one issue with Android's on device testing as in comparison to Home windows Mobile may be the results' readability. Android's on device tests posess zero interface which could display the test's results. To be able to view outcomes of the exam, a handler which handles callbacks from Android's test runner needs to be implemented.
Home windows Mobile however exhibits a higher amount of readability and visibility, as the Android platform is a little difficult to use if this involves efficiency. The problem with Android is the possible lack of feedback, that is released instantly through visual tools within the integrated development atmosphere in Home windows Mobile.
Home windows Mobile implements a form of the xUnit framework. The code for test classes is stored inside a separate project, although it still stays inside one solution within the IDE. Like Android, Home windows Mobile's xUnit testing also enables on device testing. The greatest difference here, as pointed out earlier, is its test feedback. Home windows Mobile includes a more comprehensive interface that provides feedback according to each test run. This causes it to be simpler for designers to higher understand which test been successful and why a specific test unsuccessful.
Debugging support can also be essential for database integration because it is a genuine time step-by-step code execution, which will help find and connect bugs. The debugging process is going to be determined by the integrated development atmosphere to do its task. Both Home windows Mobile and Android platforms support step-by-step debugging. On top of that, both platforms likewise incorporate an on device debugging feature that allows a credit card applicatoin operate on a mobile phone while debugging runs within the IDE.
Conclusion
Both Android and Home windows Mobile have the benefit of being carefully integrated using the cell phone's operating-system. This is exactly what leads to great integration between your mobile phone and also the development atmosphere. The main strength of Home windows Mobile is within its close reference to Microsoft, like a sole vendor. This guarantees the soundness from the development atmosphere in addition to top quality assurance if this involves features enabled for application designers. Android however, has introduced a fascinating method of disbursing applications with the Android market. Because the Home windows Mobile development platform is really a product from Microsoft, it's Visual Studio based. Visual Studio also depends on the Home windows operating-system, so you haven't any choice here. For Android however, Google provides the Eclipse wordpress plugin. Designers aren't locked into Eclipse as both IntelliJ IDEA and Netbeans provide developer support. Which means that designers can pick the IDE and operating-system they need. Development ease in a variety of areas have a major affect on the option of the mobile development platform for creating assistive atmosphere programs.
Software titans, like Google are interfering with the otherwise safe and established gamers within the mobile database integration business. Beginners like Android have brought to significant structural changes on the way forward for mobile database integration by imposing their rules. This transformed atmosphere not just brings additional possibilities, but additionally adds certain constraints. Designers today, have to assess their options and discover how they may take advantage of this transformed atmosphere.
While traveling with a laptop has caught the interest of application designers, there's been hardly any work completed to check out the programming easy these technologies. Wish to consider have a look at two most broadly available mobile development conditions - Android and Home windows Mobile and explore and assess these options from the developer's perspective.
Android
Android was released by Google in 2007, as an open source platform for mobile software development for smartphones. The Android platform was released as part of the Open Handset Alliance. The primary aim of this alliance was to set up open standards for smartphones. Android is basically a Linux based, open source operating system for mobiles. As a mobile operating system it allows developers to create managed codes in Java, by using Java libraries developed by Google. Not only does Android provide a mobile operating system including a development environment, it also offers a custom virtual machine known as the Dalvik Virtual Machine for running applications as well as acts as the middleware in between the operating system and the code. When it comes to application development, Android facilitates the usage of 2D as well as 3D graphic libraries, advanced network capabilities such as 3G, Edge and WLAN and a customized SQL engine for continual storage.
Windows Mobile
Developed by Microsoft, the Window Mobile is an operating system for mobile devices. Based on the Microsoft Windows CE 5.0, Windows Mobile is used as an operating system on many smartphones, PDAs and touch screen devices. Windows Mobile facilitates the creation of custom written applications in managed as well as native codes. The Application Programming Interface (API) in Windows Mobile is extensible and has rich features along with a programmable layer. Besides that Windows Mobile also takes advantage of the capabilities provided by Microsoft.Net environment.
We will compare these platforms and closely examine their str
engths and weaknesses. The platforms will be compared on the basis of implementation and performance aspects as well as developer support. We have chosen these criteria for the comparison as they represent the most important aspects when it comes to mobile software developers.
Performance
Performance figures are essential for customers in addition to designers. The performance comparison of these two platforms is going to be completed in line with the quality. The fundamental reason for calculating quality is to buy a much better concept of the configuration along with the run time dependencies which are incorporated in packed programs.
Android programs come packed in apk (Android Package) files. The .APK file generally has several .DEX (Android program files) files, which operate just like a single application apply for usage inside the Android platform. The .APK file is essentially the compressed form of the contents within the 'Androidmanifest.xml' file.
Home windows Mobile programs take advantage of cab-files for application packaging and deployment. The initial step while creating a distributable file, involves packaging the applying inside a CAB (Cabinet) file. This CAB file could be used with other products where it may be broadened and installed. A CAB file is essentially an executable archive which consists of the applying, assets, dependencies like DLLs along with other resource files.
A comparative study of mobile development conditions was carried out by Tom Morten Gronli, Jarle Hansen and Gheorghita Ghinea, of Brunel College, London. Within this comparative study, a demo example application was produced both in the Home windows Mobile and Android development platforms to higher illustrate the deployment quality for every application. The demo example application would be a simple program which printed a type of text on screen. The end result in the code example was the following:
The deployment size the demo application within the Home windows Mobile atmosphere was 2.8 KB.
The deployment size the demo application within the Android atmosphere was 9.3 KB.
The file dimensions as denoted were with no obfuscator or shrinker software. This is actually the kind of file that the consumer would either download or get shipped after which placed on his/her device. As possible seen previously mentioned, the demo application in Home windows Mobile were built with a quality of two.8 KB while Android was roughly three occasions the dimensions at 9.3 KB. This can serve as a sign of the quantity of configuration files and runtime dependencies which should be bundled up together with each one of the client programs. If this involves the amount of lines of code, Home windows Mobile needed only 11 lines whereas Android needed 28.
Developer Support Comparison
Developer support is really a very important aspect if this involves attaining speed in addition to quality throughout the expansion process. While both mobile development platforms will have commonalities, you will find some unique variations in developer support. The variations become clearer whenever we go ahead and take integrated developer atmosphere (IDE) and also the pedaling into account.
The only real option for rise in Home windows Mobile is Visual Studio, that is again produced by Microsoft. With Visual Studio, Home windows Mobile needs Microsoft backing before it may implement and ship additional features within the IDE. The city are only able to make suggestions but does not have direct influence. However, there's an optimistic side as consistency is assured. Also, the standard approval process implemented by Microsoft while shipping new items will ensure quality.
However, you will find several pedaling choices for Android, with a number of IDEs. Android has free towns who lead to IDE development by supplying in addition to guaranteeing quality of wordpress plugin benefits for software. However, the multiple IDE atmosphere could be a challenge for maintaining consistency and quality assurance. Consistency turns into a challenge as extension features might be readily available for only one competing IDEs. Quality assurance turns into a major challenge as development completed through the community isn't controlled by a typical standard for quality needed just before making the brand new integrated developer atmosphere feature available. Quality assurance from the shipped code is important for delivering completely functional items. Both of these factors could possibly make code and application portability between conditions impossible.
Among the variations between your Android and also the Home windows Mobile development platforms so far as developer support and quality assurance is worried gets to be more apparent within the testing atmosphere. Let's take particular notice only at that throughout unit testing of both development platforms.
Unit tests are essentially an excellent assurance and validation tool for testing small areas of a pc or mobile programs. The goal would be to have each section isolated and examined individually. This helps to isolate and assure the standard from the different models from the application.
Unit testing for Android is substantially straightforward because the API uses the JUnit test framework. The JUnit framework makes sure hierarchical organization of the several test models that is a major advantage. On top of that, the JUnit pattern guarantees independence from the test models in addition to minimizes interference. This is accomplished beginning with creating after which wrecking the lately produced test atmosphere, pre and post each test technique is run. Android even takes JUnit one step further by permitting on device testing from the code. Here the exam libraries are incorporated included in the Android's standard libraries.
However, there's one issue with Android's on device testing as in comparison to Home windows Mobile may be the results' readability. Android's on device tests posess zero interface which could display the test's results. To be able to view outcomes of the exam, a handler which handles callbacks from Android's test runner needs to be implemented.
Home windows Mobile however exhibits a higher amount of readability and visibility, as the Android platform is a little difficult to use if this involves efficiency. The problem with Android is the possible lack of feedback, that is released instantly through visual tools within the integrated development atmosphere in Home windows Mobile.
Home windows Mobile implements a form of the xUnit framework. The code for test classes is stored inside a separate project, although it still stays inside one solution within the IDE. Like Android, Home windows Mobile's xUnit testing also enables on device testing. The greatest difference here, as pointed out earlier, is its test feedback. Home windows Mobile includes a more comprehensive interface that provides feedback according to each test run. This causes it to be simpler for designers to higher understand which test been successful and why a specific test unsuccessful.
Debugging support can also be essential for database integration because it is a genuine time step-by-step code execution, which will help find and connect bugs. The debugging process is going to be determined by the integrated development atmosphere to do its task. Both Home windows Mobile and Android platforms support step-by-step debugging. On top of that, both platforms likewise incorporate an on device debugging feature that allows a credit card applicatoin operate on a mobile phone while debugging runs within the IDE.
Conclusion
Both Android and Home windows Mobile have the benefit of being carefully integrated using the cell phone's operating-system. This is exactly what leads to great integration between your mobile phone and also the development atmosphere. The main strength of Home windows Mobile is within its close reference to Microsoft, like a sole vendor. This guarantees the soundness from the development atmosphere in addition to top quality assurance if this involves features enabled for application designers. Android however, has introduced a fascinating method of disbursing applications with the Android market. Because the Home windows Mobile development platform is really a product from Microsoft, it's Visual Studio based. Visual Studio also depends on the Home windows operating-system, so you haven't any choice here. For Android however, Google provides the Eclipse wordpress plugin. Designers aren't locked into Eclipse as both IntelliJ IDEA and Netbeans provide developer support. Which means that designers can pick the IDE and operating-system they need. Development ease in a variety of areas have a major affect on the option of the mobile development platform for creating assistive atmosphere programs.
