VJC Chapter 23 Web Applications Principles

VJC/H2Computing/9569 Chapter 23 Web Applications Principles Contents 1 Native applications 2 Web applications 3 Native Applications vs Web Applications 4 Usability Principles in the Design of Web Applications 4.1 Visibility of system status 4.2 Match between system and the real world 4.3 User control and freedom 4.4 Consistency and standards 4.5 Error prevention 4.6 Recognition rather than recall 4.7 Flexibility and efficiency of use 4.8 Aesthetic and minimalist design 4.9 Help users recognize, diagnose, and recover from errors 4.10 Help and documentation 5 ASCII 6 Unicode Annex 1 – “Newer” Types of application Annex 2 – Web application vs Website Syllabus Learning Outcomes 4.2 Web Applications Understand the concepts and techniques for developing web applications. 4.2.1 Describe the differences between web applications and native applications. 4.2.2 State and apply usability principles in the design of web applications. 3.2 Character Encoding Understand the use of ASCII code and Unicode to represent characters. 3.2.1 Give examples of where or how Unicode is used. 3.2.2 Use ASCII code in programs. 1

VJC/H2Computing/9569 1 Native Applications Native applications are installed directly on the device that can work with no internet connection depending on the nature of the application. They are developed specifically for a particular platform or operating system such as Apple iOS, Android or Windows. They can also be designed to take advantage of the device features such as the power of the processor, specific hardware such as GPS and other components of the system such as the notification system and gestures. These apps have more safety and security than web apps, as native apps must be approved by the App Store Examples: Calculator, Mobile games 2 Web Applications Web application is a software application accessed and used through a web browser. A Browser is an application that is used to browse the internet. Users don't need to download and install web applications on their devices. Web applications can be accessed from any device with a web browser and an internet connection, regardless of the operating system. They are typically developed as web pages in HTML and CSS while the interactive components of the applications are developed in programming languages such as JQuery and JavaScript. Examples: LuminPDF, Google Docs 3 Native Applications vs Web Applications Deployment and maintenance (updates) for a web-based application require deployment on a single set of server machines. However, for native applications, the deployment and any maintenance/patch has to be done on individual client machines separately. Web applications can also be accessed from anywhere (most locations), so there is no location constraint. However, as native applications are confined to a standalone machine, they can only be accessed from the machines they are deployed in. Web applications thus, rely heavily on internet connectivity, for their operations. And thus, developers need to account for network reliability before deciding to embark on such projects. Native applications, on the other hand, don’t require the internet for their operations. Some applications just require internet connectivity at the time of update. Web applications are also often platform-independent, i.e. they can work on different types of platforms with the only requirement being the provision of a web browser. Native applications, on the other hand, need to be developed separately for different platform machines. (Windows, Linux, Unix, Mac etc) Web applications lend themselves to higher security risks as they are inherently designed to increase accessibility. This is a trade off that developers must take note and circumvent accordingly with the latest technologies and cyber security intelligence. Native applications, on 2

VJC/H2Computing/9569 the other hand, have better authorisation and administrators have better control, hence they are more secure. Web apps lack consistency in user experience due to their heavy dependency on browsers. Certain features or images may look different on different browsers. Buttons and menu bar features may be challenging to access from mobile browsers. Browser window resizing may impact the look, feel, and functionality of the web application. Users tend to have a better experience on native mobile apps. For instance, the native app fills the screen and takes control of the entire device. Users get more out of the native app because they are comfortable with the interactions. The native app can also send push notifications to users and get them to re-engage. The table below shows a summary of the above points of difference. Native Applications Web Applications Developed for a specific operating system or platform. As native apps are confined to a standalone machine, they can only be accessed from the machines they are deployed in. Developed to be accessed via the device’s internet browser. Web applications can be accessed from anywhere (most locations), so there is no location constraint. Need to be installed in the device to function. Native applications need to be developed separately for different platform machines. (Windows, Linux, Unix, Mac etc) No need to be downloaded or installed. Web applications are platform-independent, they can work on different types of platforms with the only requirement of a web browser. Have access to system resources such as GPS, camera etc. No access to system resources such as GPS, camera etc. May be able to work offline. Native applications don’t require the internet for their operations. Some applications just require internet connectivity at the time of update. Need an active internet connection to work. Web applications rely heavily on internet connectivity, for their operation. Comparatively faster. Comparatively slower, depending on the internet connection. Relatively safer and more secure. Relatively less secure. 3

VJC/H2Computing/9569 Native applications, on the other hand, have better authorization and administrators have better control, hence more secure. Web applications are at higher security risks as they are inherently designed to increase accessibility. May incur maintenance and update costs. Deployment and any maintenance/patch are done on individual client machines separately. Updated automatically. Deployment and maintenance (updates) for a web-based application require deployment on a single set of server machines. Tend to give better user experience. Native app fills the screen and takes control of the entire dev