App Development – Types of Apps

This post is a definition of terms for types of apps – including exam questions and tags.

In a Nutshell

• Native Apps: developed for a specific platform (Swift/Kotlin)
• Hybrid Apps: web technologies in a native container (HTML/CSS/JS + Cordova)
• Cross-Platform Apps: shared code for multiple platforms (Flutter/React Native)
• Responsive Web Apps: mobile-optimized websites in the browser

Compact Technical Description

Native Apps

Developed for a specific platform (e.g., Android in Kotlin, iOS in Swift) and utilize the full capabilities of the operating system. Highest performance, full access to device interfaces, but high development effort.

Hybrid Apps

Combine web technologies (HTML, CSS, JS) with native containers (e.g., Apache Cordova). They appear like native apps, but are essentially web applications. Cost-effective, but limited hardware integration.

Cross-Platform Apps

(e.g., with Flutter, React Native) generate native components for multiple platforms from a shared codebase. Save time and resources, performance between native and hybrid.

Responsive Web Apps

Mobile-optimized websites that dynamically adapt to screen sizes. No installation required, but no access to native hardware functions.

Exam-Relevant Key Points

• Native App: platform-dependent, high performance
• Hybrid App: web technology in native container
• Cross-Platform: shared code for iOS & Android (e.g., Flutter)
• Responsive Web: browser-based, no app store required (IHK-relevant)
• Access to sensors and APIs varies greatly (practical relevance)
• Security requirements differ (app stores vs. web security)
• Development costs and maintenance influence choice (economic viability)
• Type of app must be clearly documented and justified in the project (documentation requirement)

Core Components

1. Development environment (IDE)
2. Platform dependency
3. Programming languages (Swift, Kotlin, Dart, JS)
4. Access to native interfaces (APIs)
5. App distribution (store vs. web)
6. Performance requirements
7. Device compatibility
8. Maintenance and update capability
9. Security & data protection
10. UI/UX consistency

Practical Example

Native: App in Swift for iOS – best performance, full camera access
Hybrid: App with HTML5 and Cordova – quick to develop, limited sensor usage
Cross-Platform: Flutter app for Android and iOS – one code, good performance
Responsive Web: Mobile-friendly website with flexible CSS layouts – no installation

Advantages and Disadvantages

Native Apps

• Highest performance
• Full access to device interfaces

• High development and maintenance effort (two codebases)

Hybrid Apps

• Cost-effective, simple implementation

• Limited hardware integration, sometimes poor UI behavior

Cross-Platform Apps

• Shared code saves time and resources

• Performance between native and hybrid

Responsive Web Apps

• No installation required
• Platform-independent

• No offline access, limited functionality

Typical Exam Questions (with Short Answer)

1. Difference between native and hybrid? Native: developed platform-specific; Hybrid: web technologies in container.
2. Advantages of cross-platform? Shared source code saves time, faster deployment.
3. Responsive web app? Website that adapts to different screen sizes.
4. Why are native apps more performant? Direct system access without intermediate layer.
5. Which app types do not require an app store? Responsive web apps (accessible via browser).
6. Disadvantage of hybrid apps? Limited access to native functions.
7. App type for quick prototypes? Hybrid or responsive web app.
8. Security aspects in web apps? Protection against XSS, CSRF, HTTPS encryption.

Most Important Sources

1. https://flutter.dev/docs
2. https://reactnative.dev/docs
3. https://cordova.apache.org/docs