Mobile Application DevelopmentUnit 16 min read
Mobile Computing: Devices, Networks, and Challenges
Unit 1 of Mobile Application Development introduces the core concepts of mobile computing, including definitions, evolution, hardware/software architectures, wireless networks, and key challenges like battery life, security, and connectivity. This note covers mobile devices, networks, applications, and real-world use c
Key Concepts and Definitions
What is Mobile Computing?
Mobile computing refers to the use of portable computing devices (smartphones, tablets, wearables) connected via wireless networks to access information, services, and applications anytime, anywhere. It combines hardware (devices), software (apps/OS), and networks (Wi-Fi, cellular, Bluetooth).
mindmap
root((Mobile Computing))
Hardware
Smartphones
Tablets
Wearables
Software
Mobile OS (Android, iOS)
Applications
Networks
Cellular (4G/5G)
Wi-Fi
Bluetooth
Challenges
Battery Life
Security
ConnectivityEvolution of Mobile Computing
Mobile computing has evolved through generations of devices and networks:
- 1G (1980s): Analog voice calls (no data).
- 2G (1990s): Digital voice + SMS (GSM).
- 3G (2000s): Mobile internet (slow data).
- 4G (2010s): High-speed data (HD video, apps).
- 5G (2020s): Ultra-low latency, IoT support.
Real-world example: eSewa uses 4G/5G for real-time transactions, while Pathao relies on GPS and 4G for ride-matching.
Mobile Devices and Their Components
Hardware Components
Mobile devices consist of:
- Processor (CPU): Handles computations (e.g., Snapdragon in smartphones).
- Memory (RAM/Storage): Temporary (RAM) and permanent (Flash) storage.
- Battery: Lithium-ion/polymer (e.g., 4000mAh in mid-range phones).
- Sensors: GPS, accelerometer, gyroscope, fingerprint scanner.
- Display: OLED/LCD screens (e.g., 6.5" AMOLED in modern phones).
- Connectivity: Wi-Fi, Bluetooth, NFC, cellular modems.
classDiagram
class MobileDevice {
+CPU: Snapdragon/Exynos
+RAM: 4GB–16GB
+Storage: 64GB–512GB
+Battery: 3000mAh–5000mAh
+Sensors: GPS, Accelerometer
+Display: OLED/LCD
+Connectivity: Wi-Fi, 5G, Bluetooth
}Software Components
- Mobile OS: Android (Linux-based), iOS (Apple), Windows Phone.
- Middleware: Frameworks like Android SDK, iOS SDK.
- Applications: Pre-installed (e.g., Google Maps) or third-party (e.g., Daraz).
Comparison Table:
| Feature | Android | iOS |
|---|---|---|
| OS Type | Open-source (Linux kernel) | Closed-source (Unix-based) |
| Customization | High (themes, sideloading) | Low (Apple restrictions) |
| App Store | Google Play Store | Apple App Store |
| Market Share | ~70% (global) | ~30% (global) |
Wireless Networks in Mobile Computing
Types of Wireless Networks
- Cellular Networks (4G/5G):
- Used by Ncell and Nepal Telecom for voice/data.
- 5G enables ultra-low latency (e.g., real-time stock trading via NEPSE apps).
- Wi-Fi (IEEE 802.11):
- Used in cafes, homes (e.g., Khalti transactions over Wi-Fi).
- Bluetooth (BLE):
- Short-range (e.g., Pathao driver-passenger pairing).
- Satellite Networks:
- Rural connectivity (e.g., Starlink in remote Nepal).
flowchart TD A["Mobile Device"] -->|"Wi-Fi"| B["Router"] A -->|"4G/5G"| C["Cell Tower"] A -->|"Bluetooth"| D["Smartwatch"] C -->|"Backhaul"| E["Internet"]
Network Protocols
- HTTP/HTTPS: Web traffic (e.g., Daraz orders).
- MQTT: IoT messaging (e.g., smart home devices).
- VoIP: Voice over IP (e.g., WhatsApp calls).
Mobile Applications and Their Categories
Types of Mobile Apps
- Native Apps: Built for a specific OS (e.g., Khalti Android/iOS apps).
- Web Apps: Browser-based (e.g., eSewa web version).
- Hybrid Apps: Combines native and web (e.g., Facebook app).
Worked Example: Pathao uses:
- GPS for location tracking.
- 5G/Wi-Fi for real-time ride updates.
- Bluetooth for driver-passenger pairing.
stateDiagram-v2 [*] --> UserOpensPathao UserOpensPathao --> RequestsLocation RequestsLocation --> GPSActivated GPSActivated --> MatchesDriver MatchesDriver --> DriverAccepts DriverAccepts --> RideStarted RideStarted --> [*]
Challenges in Mobile Computing
Key Challenges
- Battery Life:
- Problem: Short battery duration (e.g., 8-hour usage in budget phones).
- Solution: Adaptive battery (Android), low-power modes.
- Security:
- Problem: Phishing, malware (e.g., fake Khalti apps).
- Solution: Biometric authentication, encryption.
- Connectivity:
- Problem: Rural areas lack 4G/5G (e.g., Ncell coverage gaps).
- Solution: Satellite networks, Wi-Fi hotspots.
- Performance:
- Problem: Lag in low-end devices (e.g., Daraz app on 2GB RAM phones).
- Solution: Lightweight apps, cloud offloading.
Real-world example: NTC uses load balancing to manage traffic during Dashain when millions use mobile data.
In the Real World
- eSewa:
- Uses HTTPS + 4G/5G for secure transactions.
- Challenge: Battery drain during long transactions (solved via adaptive brightness).
- Pathao:
- GPS + Cellular for real-time navigation.
- Problem: Driver spoofing (solved via biometric verification).
- NEPSE App:
- 5G + MQTT for real-time stock updates.
- Challenge: Latency in rural areas (mitigated via edge computing).
Exam Tip
- Definitions: Know the difference between native, web, and hybrid apps.
- Networks: Compare 4G vs. 5G (speed, latency, use cases).
- Challenges: Explain battery optimization techniques (e.g., Doze mode in Android).
- Diagrams: Draw mobile device architecture and wireless network flowcharts.
- Examples: Relate concepts to Nepali apps (e.g., Khalti for security, Pathao for GPS).
Visual Summary:
flowchart LR A["Mobile Device"] --> B["Hardware\n(CPU, Battery, Sensors)"] A --> C["Software\n(Android/iOS, Apps)"] A --> D["Networks\n(4G/5G, Wi-Fi, Bluetooth)"] A --> E["Challenges\n(Battery, Security, Connectivity)"]
Based on the TU BIT syllabus for Mobile Application Development, unit 1.
Discussion
Loading…