Mobile Application Development I

Author(s):  
Lei-da Chen ◽  
Gordon W. Skelton

Microsoft Embedded Visual Tools were designed to develop applications that run on Windows CE devices (e.g., Pocket PC and Handheld PC 2000). It is a free software product that can be downloaded at the www.microsoft.com Web site. Two programming languages are supported by Microsoft Embedded Visual Tools: Embedded Visual Basic (eVB) and Embedded Visual C++ (eVC). These two programming languages are versions of Visual Basic and Visual C++ with limited capabilities, respectively. Therefore, developers with Visual Basic or Visual C++ experience can easily leverage their existing expertise to develop mobile or wireless applications. Since many developers are familiar with Visual Basic, we will explore the techniques of using eVB to develop applications for wireless devices in this chapter.

Author(s):  
Lei-da Chen ◽  
Gordon W. Skelton

n the previous chapter on mobile application development, we developed an order placement system (OPS) using Microsoft Embedded Visual Basic (EVB). Although EVB provides developers with the basic tools for developing mobile applications, it has many limitations. Microsoft Visual Studio .NET 2003 addresses these limitations by including tools for developing smart device applications. Using these tools, developers can create mobile applications for PocketPCs or other Windows CE devices with relative ease and flexibility. Similar to EVB, Visual Studio .NET uses a form-based approach to build applications and provides developers with WYSIWYG tools for user interface development, but as you will find in this chapter, it not only provides many new tools to enrich the application but also simplifies many tasks that are cumbersome in EVB (i.e., creating menus and interacting with databases). Furthermore, Visual Studio .NET allows developers to use a number of different programming languages including Visual Basic and C# to develop applications so that developers can leverage their existing programming skill sets. To illustrate how Visual Studio .NET can be deployed to develop mobile applications, we will develop an upgraded version of the OPS in this chapter. In order to provide a better comparison between Visual Studio .NET and EVB, we will use Visual Basic as the programming language in this project.


2021 ◽  
Vol 21 (1) ◽  
pp. 1-24
Author(s):  
Paolo Modesti

Mobile applications are extremely popular with many higher education institutions offering courses to prepare new developers sought by the software industry. However, teaching and assessing mobile application development poses specific challenges due to the complexity of real-world programming languages and environments. In this work, we present a script-based approach for teaching and assessing Android application development that addresses shortcomings of existing tools that impact negatively on the learning experience. Our evaluation, which covers pedagogical and technical aspects, provides possible evidence that the scripts have been beneficial in helping students to work more efficiently and achieve better results. Additionally, the scripts have been effective in streamlining the grading process and keeping the tutorial material up to date with the evolution of the Android platform.


2016 ◽  
Vol 14 (39) ◽  
pp. 29-40
Author(s):  
Sharon D. Sánchez Santana ◽  
José Ignacio Estévez ◽  
Sergio B. Sepúlveda Mora ◽  
Byron Medina Delgado

A native Android application and a multi-platform web application to monitor solar radiation and the output power of a photovoltaic system were developed, in order to establish which is more efficient using the mobile device resources. The methodology for Mobile Application Development [MAD] was adopted and free software tools –Android Studio and HTML5– were used. CPU consumption, response time in sending data and memory usage for the execution of the applications, were compared; also, the user experience was evaluated through the 6Ms survey. The transfer time of a data from the server to the mobile application executed in Chrome was 0.887 seconds, the native application transfers a data in 0.853 seconds –both times are within the acceptable ranges, since the acquisition system stores one data every 5 minutes; the average memory usage was 182 Mb for executing the application in the Chrome browser, while the native application achieved a reduction of 65%, therefore it can be concluded that the native application requires less memory usage for its execution. 


Author(s):  
Imaobong Chinedozi ◽  
Karen E. Schetzina ◽  
Gayatri Jaishankar ◽  
Robin Fisher ◽  
Jill Fair

Sign in / Sign up

Export Citation Format

Share Document