NATIVE, HYBRID AND CROSS-PLATFORM APPLICATIONS

1. Native Applications

Definition:
Native applications are mobile applications developed specifically for a single platform such
as Android or iOS. They are built using platform-specific programming languages and tools
provided by the platform vendors. Native apps are directly installed on the device and can
access all the features of the operating system and hardware.

Examples:

• Instagram

• WhatsApp

• Spotify

• Snapchat

Technologies / Components used:

• For Android: Java, Kotlin, Android Studio

• For iOS: Swift, Objective-C, Xcode

• Native SDKs (Software Development Kits)

• Access to APIs for camera, GPS, storage, sensors, notifications, etc.

Advantages:

1. High Performance – They are optimized for a specific platform, so they run faster and
more smoothly.

2. Full Access to Device Features – Can directly use hardware like camera, GPS,
Bluetooth, and sensors.

3. Better User Experience – UI follows platform design guidelines, which gives a

consistent look and feel.

4. More Secure – Built using official tools and have stricter security standards.

Disadvantages:

1. High Development Cost – Separate apps need to be developed for Android and iOS.

2. Longer Development Time – Because developers need to write different codebases

for each platform.
 3. Requires Specialized Skills – Developers must know platform-specific languages and
tools.

4. Maintenance is Difficult – Fixes and updates must be done separately on each

platform.

2. Hybrid Applications

Definition:
Hybrid applications are mobile apps developed using web technologies like HTML, CSS, and
JavaScript. They are wrapped inside a native container using a WebView. The same code
runs on multiple platforms, but the app is packaged like a native app and distributed through
app stores.

Examples:

• Uber

• Evernote

• Instagram Lite

• Ionic View apps

Technologies / Components used:

• Apache Cordova / PhoneGap

• Ionic framework

• Web technologies (HTML, CSS, JavaScript)

• WebView (embedded browser component inside a native shell)

• Plugins to access device features like camera or GPS

Advantages:

1. Single Codebase – One code can run on multiple platforms.

2. Faster Development – Less time needed to build and deploy apps.

3. Lower Development Cost – Same developers can build for both Android and iOS.

4. Easy to Maintain – Updates are made in one place and reflected on all platforms.

Disadvantages:

1. Lower Performance – Web-based content inside a native shell may run slower.
 2. Limited Device Access – Some hardware features may not work well or require extra
plugins.

3. Poor User Experience – May not feel as smooth or native to the platform.

4. Compatibility Issues – Might behave differently on different devices or OS versions.

3. Cross-platform Applications

Definition:
Cross-platform applications are built using frameworks that allow developers to write code
once and deploy it on multiple platforms. Unlike hybrid apps (which run inside WebView),
cross-platform frameworks compile the code into native-like code, providing better
performance and closer integration with the device.

Examples:

• Facebook

• Airbnb

• Skype

• Microsoft Teams

Technologies / Components used:

• Flutter (uses Dart)

• React Native (uses JavaScript)

• Xamarin (uses C#)

• Shared UI and business logic

• Platform-specific bridges to access native device APIs

Advantages:

1. Code Reusability – A large part of the code can be reused across platforms.

2. Faster Development – Only one main codebase reduces development time.

3. Lower Cost – Fewer resources and developers are needed.

4. Near-native Performance – Faster than hybrid apps and closer to native apps.

Disadvantages:

1. Not Fully Native – Some platform-specific features might still need separate coding.
 2. Slightly Lower Performance – May not match 100% of native speed.

3. Framework Limitations – Some device APIs or new features may not be supported
immediately.

4. Larger App Size – Cross-platform frameworks can increase app file size.

4. Comparison Table

Feature Native Apps Hybrid Apps Cross-platform Apps

Separate for each Single (compiled to

Codebase Single (web-based)
platform native)

Java, Kotlin, Swift, HTML, CSS,

Languages Dart, JavaScript, C#
Objective-C JavaScript

Performance Very High Low to Medium High

Access to Device Limited (via Good (via native

Full
APIs plugins) bridges)

Development Cost High Low Medium

Time to Market Long Fast Medium

User Experience Excellent Average Good

Difficult (multiple Easy (single

Maintenance Easy (single codebase)
codebases) codebase)

5. Conclusion

• Native apps give the best performance, security, and user experience but require
more time, cost, and effort as they need separate development for each platform.

• Hybrid apps are quick and inexpensive to build but compromise on speed, device
access, and user experience.

• Cross-platform apps try to combine the advantages of both — offering good

performance with code reusability, but may still face limitations in using platform-
specific features.

The choice depends on the project requirements, target audience, time availability, and
budget.
Web Applications vs Mobile Applications

1. Comparison

Feature Web Applications Mobile Applications

Runs in a browser, so slightly

slower due to network Runs directly on the device hardware →
Performance
dependency and browser faster and smoother performance.
overhead.

Accessible on any device via a web Requires installation from an app store
Accessibility browser and internet connection. (Google Play Store / Apple App Store).
No installation needed. Limited to supported platforms.

Consistent across devices, but less Provides rich, interactive UI and full
User
interactive and limited in access to access to device features like camera,
Experience
hardware features. GPS, sensors.

Instant updates (just refresh Updates must be downloaded and

Updates
browser). installed by users.

Offline Requires internet connection Can work offline using local storage or
Support (unless using offline caching). databases.

2. Fundamentals of Web Application Development

Definition:
Web applications are programs that run in a web browser using internet technologies. They
are platform-independent and do not require installation on the device.

Core Technologies / Components:

• Frontend: HTML (structure), CSS (styling), JavaScript (interactivity)

• Backend: PHP, Python, Java, [Link]

• Database: MySQL, MongoDB

• Web Server: Apache, Nginx

• Browsers: Google Chrome, Mozilla Firefox, etc.

Examples:

• Gmail Web
 • YouTube Web

• Facebook Web

• Amazon Website

Development Process:

1. Design UI using HTML, CSS

2. Add interactivity with JavaScript

3. Build server-side logic and APIs

4. Connect to databases for data storage

5. Deploy on a web server

3. Fundamentals of Mobile Application Development

Definition:
Mobile applications are software programs developed to run on mobile devices like
smartphones and tablets. They are platform-specific (native) or platform-independent
(cross-platform or hybrid).

Types of Mobile Apps:

• Native Apps: Built for specific OS like Android or iOS

• Hybrid Apps: Built using web tech inside a native shell

• Cross-platform Apps: Single code compiled for multiple platforms

Core Technologies / Components:

• Android: Java, Kotlin using Android Studio

• iOS: Swift, Objective-C using Xcode

• Cross-platform frameworks: React Native, Flutter, Xamarin

• Device APIs: Camera, GPS, Sensors, Notifications, Storage

Examples:

• WhatsApp

• Instagram

• Swiggy

• Paytm
Development Process:

1. Decide platform (Android, iOS, or both)

2. Design UI and navigation

3. Write platform-specific or cross-platform code

4. Test on simulators and real devices

5. Publish on app stores

4. Conclusion

• Web applications are best for wide accessibility, lower development cost, and instant
updates, but they depend on internet and browser performance.

• Mobile applications give better performance, offline support, and user experience
but require installation, higher development effort, and periodic updates.

Choosing between them depends on target users, required features, budget, and
performance needs.

Architecture of a Healthcare Mobile Application Combining Native Features and PWA

Capabilities

1. Introduction

A healthcare mobile application can be designed as a hybrid system that uses both:

• Native features (like GPS, camera, biometric sensors) for accessing device hardware,
and

• Progressive Web App (PWA) capabilities (like offline access, push notifications,
background sync) for web-like flexibility.

This approach combines the high performance of native apps with the wide reach and low
data dependency of PWAs.

2. Architecture Overview

Layers of the Architecture:

+------------------------------------------------------------+
| User Interface Layer |

| - Built using HTML, CSS, JavaScript (PWA UI) |

| - Native UI components (Android/iOS) for critical screens |

+------------------------------------------------------------+

| Application Layer |

| - Business logic written in JS (PWA part) |

| - Native modules (Kotlin/Swift) for GPS, camera, sensors |

| - API integration with hospital/clinic servers |

+------------------------------------------------------------+

| Service Layer |

| - Service Workers (for offline cache & push notifications)|

| - Background Sync APIs |

| - Secure authentication (OAuth/Token based) |

+------------------------------------------------------------+

| Data Layer |

| - Local Database (:contentReference[oaicite:1]{index=1} /

:contentReference[oaicite:2]{index=2}) for offline storage |

| - Cloud Database (:contentReference[oaicite:3]{index=3} /

:contentReference[oaicite:4]{index=4}) for central data |

+------------------------------------------------------------+

| Device Layer |

| - Native device APIs (Camera, GPS, Bluetooth, Sensors) |

| - OS specific SDKs (:contentReference[oaicite:5]{index=5} /

:contentReference[oaicite:6]{index=6}) |

+------------------------------------------------------------+

Working Flow:

1. User Interface is built mainly as a PWA (responsive and browser-based).

2. Service workers enable offline mode and push notifications.

 3. When a user needs device features (GPS to locate nearby hospitals or camera to
upload reports), the app switches to native modules.

4. Data is stored locally when offline and syncs with cloud servers when internet is
available.

3. Benefits of Such Integration

1. Offline Access:

o Service workers cache data so users can access medical history and
prescriptions even without internet.

2. Push Notifications:

o Reminders for appointments, medication alerts, and health tips are sent even
when the app is closed.

3. Access to Native Features:

o Camera to upload medical documents or scans.

o GPS to locate nearby clinics, ambulances, or pharmacies.

4. Improved Performance & Experience:

o Native modules give smooth, fast operations.

o PWA UI gives quick loading and lightweight design.

5. Cross-Platform Reach:

o Runs on browsers as a web app and can be installed like a native app.

6. Lower Data Usage:

o PWA reduces the need to download large updates.

4. Challenges of Such Integration

1. Complex Architecture:

o Managing both native and PWA layers increases development complexity.

2. Compatibility Issues:

o Some device features may not be fully accessible via PWA on all platforms.

3. Security Concerns:
 o Handling sensitive healthcare data requires strong encryption and secure
offline storage.

4. App Store Restrictions:

o PWAs may not fully comply with Apple App Store or Google Play Store
policies.

5. Maintenance Overhead:

o Need to update both native modules and PWA components.

6. Performance Gaps:

o PWA parts may be slightly slower than fully native components.

5. Conclusion

A healthcare app that integrates native features and PWA capabilities offers the best of
both worlds — rich functionality, offline support, cross-platform reach, and enhanced user
engagement.
However, developers must handle complex design, security, and compatibility carefully to
ensure reliability and data safety in the sensitive healthcare domain.

2m

1. Define Mobile Application Development

Mobile Application Development is the process of creating software applications that run on
mobile devices like smartphones and tablets, using platforms such as Android Studio or
Xcode.

2. What is a Native App? Give an example

A Native App is an application developed specifically for a particular mobile operating

system using its native programming language.
Example: Instagram on Android or iOS.

3. State any two benefits of Responsive Web Design

• Provides a consistent user experience across different devices.

• Improves accessibility by adapting the layout to various screen sizes.

4. Differentiate between Web App and Mobile App

• Web App: Runs in a browser and requires internet access (e.g., Gmail web version).

• Mobile App: Installed directly on a device and can work offline (e.g., WhatsApp).

5. Define a Cross-platform application

A Cross-platform application is an app developed using a single codebase that can run on
multiple operating systems like Android and iOS.

6. What is a Hybrid Application?

A Hybrid Application is a type of app built using web technologies (HTML, CSS, JavaScript)
but wrapped inside a native container to run on mobile devices.