Mobile Computing Foundations and Ecosystems

Introduction

Mobile computing is the use of portable computing devices, wireless communication networks, mobile software, and cloud or edge services to support information processing while users and devices change location. It is more than “computing on a smaller screen.” Mobile systems operate under distinctive conditions: limited battery capacity, variable connectivity, heterogeneous hardware, location awareness, changing user contexts, small or adaptive interfaces, and strict platform governance.

Mobile applications are now central to banking, commerce, education, health, logistics, entertainment, public services, and workplace collaboration. Understanding their foundations is therefore essential before studying user-interface development, mobile programming, databases, testing, or deployment. This chapter introduces the terminology, historical development, ecosystems, application types, operating-system constraints, application lifecycles, distribution models, and digital-transformation role of mobile applications.

Learning Objectives

By the end of this chapter, you should be able to:

1. Define major mobile-computing and mobile-application concepts.
2. Explain the evolution of mobile platforms and app ecosystems.
3. Compare the Android and iOS ecosystems.
4. Classify mobile applications by architecture, deployment, and purpose.
5. Explain how mobile operating systems manage resources, security, and application lifecycles.
6. Evaluate application-distribution models and their governance implications.
7. Relate mobile applications to digital transformation using an applied case.
8. Identify professional, ethical, accessibility, privacy, and security responsibilities in mobile development.

1. Foundations of Mobile Computing

1.1 Core terminology

A mobile device is a portable computing device capable of processing data and usually communicating through wireless networks. Smartphones and tablets are the most visible examples, but smart watches, vehicle terminals, handheld scanners, medical devices, and industrial sensors are also mobile devices.

A mobile application, or mobile app, is software designed to operate on a mobile device or through a mobile-oriented interface. An app may run locally, communicate with remote services, or combine local and remote processing.

A mobile platform is the combination of operating system, software-development tools, application programming interfaces (APIs), runtime services, security mechanisms, and distribution channels that support mobile applications. Android and iOS are the dominant general-purpose smartphone platforms.

A mobile ecosystem is broader than a platform. It includes the operating-system vendor, device manufacturers, developers, users, app stores, cloud providers, advertisers, accessory manufacturers, regulators, payment services, and standards organizations. Ecosystems create network effects: a platform becomes more valuable when it attracts more users and developers, while developers are attracted by a large and commercially active user base.

Mobility refers to the ability of users, devices, or services to operate while location or network attachment changes. Ubiquitous computing describes computing embedded into everyday environments so that digital services are available across places and contexts. Context-aware computing uses information such as location, time, movement, device state, or user activity to adapt behavior.

Wireless connectivity may include cellular networks, Wi-Fi, Bluetooth, near-field communication (NFC), and low-power wide-area technologies. Connectivity is not equivalent to continuous Internet access. A well-designed mobile app must tolerate delay, weak signals, roaming, disconnection, and changing bandwidth.

1.2 Characteristics that distinguish mobile computing

Mobile computing has several defining characteristics:

• Portability: devices are small enough to carry and use in changing locations.
• Intermittent connectivity: network access may be unavailable or expensive.
• Resource constraints: battery, memory, storage, processing capacity, and thermal capacity are limited compared with many servers or desktop computers.
• Heterogeneity: devices vary in screen size, input method, processor architecture, sensors, operating-system version, and manufacturer customization.
• Context sensitivity: location, orientation, motion, time, and environmental conditions may affect application behavior.
• Personalization: a device is often associated with a person, identity, preferences, credentials, and sensitive data.
• Exposure to physical risk: a lost or stolen device may expose data unless strong security controls are used.
• Short interaction sessions: users often interact while walking, waiting, travelling, or multitasking.

These characteristics affect architecture and user experience. For example, a desktop application may assume a stable network and long sessions; a mobile application should save progress, provide meaningful offline behavior, and recover safely after interruption.

2. Evolution of Mobile Platforms

Mobile computing developed through several overlapping phases rather than a single linear sequence.

2.1 From cellular telephony to programmable devices

Early mobile telephones primarily provided voice communication and text messaging. Feature phones later introduced calendars, address books, simple games, cameras, and limited downloadable software. Their software environments were often fragmented, constrained, and dependent on manufacturer or carrier technologies.

Personal digital assistants introduced portable calendars, contacts, note-taking, and stylus-based interfaces. Wireless data networks then enabled email, web browsing, and enterprise messaging. These developments established the idea that a handheld device could be a general information tool rather than only a telephone.

2.2 The smartphone platform era

The modern smartphone combined telephony, a general-purpose operating system, touch interaction, sensors, cameras, local storage, high-speed networking, and a software-distribution channel. Apple’s introduction of the iPhone in 2007 and the subsequent growth of Android transformed mobile development by popularizing touch-first interfaces and centralized app marketplaces.

The important transformation was institutional as well as technical. Developers gained standardized software-development kits (SDKs), app stores provided discovery and payment mechanisms, and users could install applications directly. This created a scalable commercial model for independent developers and small companies.

2.3 Current direction

Mobile platforms now function as gateways to cloud services, identity systems, digital payments, smart-home devices, vehicles, wearables, and enterprise systems. Development increasingly uses shared codebases, declarative user-interface frameworks, automated testing, remote configuration, analytics, and continuous delivery. At the same time, platform vendors have strengthened privacy controls, permission systems, sandboxing, and review policies.

Emerging developments include on-device machine learning, foldable and multi-screen devices, 5G-enabled services, passkeys, spatial interfaces, edge computing, and tighter integration with wearable and automotive systems. These developments do not eliminate foundational constraints; they make platform knowledge and responsible design more important.

3. Android and iOS Ecosystems

3.1 Android

Android is a Linux-based mobile operating-system platform developed under the leadership of Google and used by many device manufacturers. Its ecosystem includes Google services, manufacturer-customized distributions, third-party app stores, enterprise-management tools, and a broad range of hardware.

Android development commonly uses Kotlin and Android Studio. The Android SDK provides APIs for activities, services, user interfaces, storage, networking, notifications, sensors, location, media, and security. Android applications are packaged for installation and are executed within an application sandbox. The platform uses components such as activities for user-facing screens, services for selected background work, broadcast receivers for event handling, and content providers for controlled data sharing.

Android’s strengths include hardware diversity, broad market reach, flexibility, and availability across price ranges. Its challenges include device and operating-system fragmentation, differences in manufacturer behavior, varied screen dimensions, and uneven update timing. Developers must use compatibility libraries, test across representative device configurations, and avoid assuming that a feature is available merely because it exists on one device.

3.2 iOS

iOS is Apple’s mobile operating system for devices such as the iPhone. Its ecosystem is characterized by tightly integrated hardware and software, centralized distribution through the Apple App Store, strong design conventions, and a relatively limited range of device configurations compared with Android.

Development commonly uses Swift and Apple’s SDKs, including frameworks for user interfaces, data persistence, networking, notifications, media, health, location, and machine learning. iOS applications are sandboxed and subject to entitlements, privacy declarations, signing requirements, and App Store review policies.

iOS’s strengths include a comparatively consistent hardware environment, predictable system APIs, strong integration among Apple devices, and a commercially significant user base. Its constraints include stricter distribution controls, platform-specific review requirements, and less freedom to modify system behavior. Developers must follow Apple’s interface, privacy, and security guidelines and must account for background-execution restrictions.

3.3 Comparative analysis

The comparison should not be reduced to “open versus closed.” Both platforms use sandboxing, permissions, signing, secure storage, and review or verification mechanisms. The practical difference is the degree of hardware variation, distribution control, and platform customization.

3.4 Cross-platform development

Cross-platform approaches allow developers to share some code across Android and iOS. They include:

• Web applications: run in a browser and use web standards.
• Progressive web applications: web applications that can support installation-like behavior, caching, and limited offline use where platform capabilities permit.
• Hybrid applications: package web technologies inside a native shell and expose selected device APIs.
• Cross-platform native frameworks: use a shared programming model while rendering or invoking platform-specific components.
• Shared business-logic architectures: reuse networking, validation, domain rules, and data layers while implementing platform-specific interfaces.

Code sharing can reduce duplicated effort, but it does not remove platform differences. Notifications, permissions, background execution, accessibility behavior, navigation conventions, and store policies may still require native adaptation. A sound decision considers user experience, performance, device integration, team skills, time, maintenance cost, and long-term platform risk.

4. Types of Mobile Applications

Applications can be classified using more than one dimension.

4.1 Native applications

A native application is developed for a particular operating system using its official languages, SDKs, and interface conventions. Native apps generally provide strong access to device capabilities and can deliver high performance and platform-consistent behavior. Their disadvantages include duplicated development and maintenance when supporting multiple platforms.

Native development is appropriate when an app requires intensive graphics, advanced sensors, accessibility integration, specialized background behavior, high responsiveness, or deep integration with platform services.

4.2 Web and progressive web applications

A mobile web application is accessed through a browser. It can reach a broad range of devices without installation through an app store, and updates are often immediate because the main code is delivered from a server. However, browser security boundaries and platform support may limit access to sensors, background tasks, files, notifications, and device-specific features.

A progressive web application enhances a web application with responsive design, caching, a web app manifest, and service-worker capabilities where supported. It may offer an installable experience and selected offline functions, but developers must test actual platform support rather than assume that browser capabilities are uniform.

4.3 Hybrid and cross-platform applications

Hybrid applications combine web technologies with a native container. Cross-platform frameworks may compile shared code to native components or provide a shared runtime. These approaches can improve development efficiency, especially for business applications with conventional forms, workflows, and content.

Potential limitations include larger application packages, delays in supporting new platform APIs, performance overhead in demanding tasks, and difficulty reproducing platform-specific interaction patterns. The correct choice depends on requirements rather than fashion.

4.4 Application purpose and deployment context

Mobile applications may also be categorized as:

• Consumer applications: social networking, commerce, entertainment, travel, and personal finance.
• Enterprise applications: field service, inventory, sales, approval workflows, and workforce communication.
• Embedded or companion applications: interfaces for wearables, vehicles, appliances, and industrial equipment.
• Real-time or safety-relevant applications: systems supporting health, transport, or emergency operations.
• Data-intensive applications: apps that synchronize records, media, or sensor streams with cloud services.

Classification by purpose influences risk, testing depth, authentication, offline design, regulatory obligations, and support arrangements.

5. Operating-System Constraints and Design Consequences

5.1 Resource management

Mobile operating systems manage scarce resources to preserve responsiveness, battery life, privacy, and reliability. They may suspend, stop, or terminate applications that are not visible or that consume excessive resources. Developers cannot assume that a background process will run indefinitely.

Battery use is affected by processor activity, screen brightness, radio use, sensor sampling, location frequency, data transfer, and wake-ups. Efficient design batches network work where appropriate, avoids unnecessary polling, reduces high-frequency sensor use, compresses or caches data carefully, and responds to lifecycle events.

Memory pressure may cause an operating system to reclaim application processes. Important user data should therefore be persisted before an app becomes inactive, not only when the user explicitly chooses “Save.” Persistent storage may include local databases, files, key-value stores, or secure credential storage.

5.2 Connectivity and offline behavior

A mobile network can change from fast Wi-Fi to slow cellular service or no service. Applications should distinguish between “no connection,” “request in progress,” “server unavailable,” and “authentication expired.” Useful strategies include:

1. Cache stable or recently used data.
2. Display the age and status of cached information.
3. Queue safe user actions for later synchronization.
4. Make synchronization idempotent where possible, so repeating an operation does not create unintended duplicates.
5. Resolve conflicts explicitly when both local and remote data have changed.
6. Provide retry controls and meaningful error messages.

Offline-first design does not mean that every feature must work without a network. It means that network dependence is designed deliberately and communicated clearly.

5.3 Permissions and privacy

Modern platforms use runtime permissions and privacy controls for sensitive resources such as location, camera, microphone, contacts, health information, photos, and notifications. Permission requests should be contextual, minimal, and understandable. An application should not request access merely because it might be useful in the future.

Privacy engineering includes data minimization, purpose limitation, access control, encryption in transit and at rest where appropriate, secure deletion practices, retention limits, transparent notices, and user control. Developers must also consider legal requirements such as data-protection law, sector-specific health or financial regulation, child-safety obligations, and consumer-protection rules. Legal requirements vary by jurisdiction; technical teams should consult institutional or legal specialists for specific deployments.

5.4 Security constraints

A mobile application should be treated as operating in an untrusted environment. Its package may be reverse engineered, its device may be compromised, and network traffic may be observed or manipulated. Security controls should therefore be enforced on trusted servers as well as in the client.

Important practices include secure authentication, short-lived tokens, multifactor authentication where appropriate, certificate and transport validation, secure secret storage, input validation, least privilege, dependency management, logging without sensitive data, and timely vulnerability response. Hard-coding passwords, API keys, or private signing material in an application is unsafe.

6. The Mobile Application Lifecycle

The application lifecycle describes the changing operational states of an app as users and the operating system interact with it. Exact names differ by platform, but the concepts are similar.

A typical lifecycle includes:

1. Installation and first launch: the application is installed, initialized, and possibly guided through consent or account setup.
2. Active or foreground state: the user can interact with the application and it has access to foreground resources.
3. Inactive or transitioning state: a temporary interruption, such as a system prompt or incoming call, affects interaction.
4. Background state: the app is not currently visible; the platform may permit limited work.
5. Suspended state: execution may be paused while memory is retained.
6. Terminated state: the process is removed, either by the user, the operating system, a crash, or a reboot.
7. Update or removal: a new version replaces the app, or the app and its local data are removed.

Lifecycle-aware design separates temporary interface state from durable application data. For example, a shopping app may persist an unfinished cart, but it should not assume that a screen object remains in memory. Network operations should be cancellable or resumable, and duplicate lifecycle callbacks should not cause duplicate payments or submissions.

A simplified conceptual sequence is:

Install → Launch → Active ⇄ Background → Suspended/Terminated
                         ↓
                 Persist and synchronize state

The lifecycle is also a testing concern. Test cases should cover interruption, rotation or resizing, low memory, loss of connectivity, permission denial, process termination, device restart, account expiry, and application update.

7. Distribution and Business Models

7.1 Public app stores

Public app stores provide discovery, identity, payment, update delivery, malware screening, policy enforcement, ratings, and analytics. They reduce distribution friction but impose review rules, metadata requirements, platform fees or commercial terms, and limits on certain content or behaviors.

Store optimization includes a clear title and description, accurate screenshots, accessibility-aware presentation, privacy disclosures, appropriate age classification, crash-free releases, and responsive handling of user feedback. Developers should not manipulate reviews or obscure subscription terms.

7.2 Enterprise and private distribution

Organizations may distribute applications privately through enterprise mobility-management systems, managed app catalogs, or controlled device enrollment. This is useful for field workers, hospitals, universities, and internal operations. Private distribution requires governance of identity, device compliance, update deadlines, support, revocation, and data separation.

7.3 Direct, web, and alternative channels

Web applications can be distributed through a URL, reducing dependence on a store. Direct installation and alternative app marketplaces may be available under particular technical or regulatory conditions. These channels can increase flexibility but may reduce centralized vetting, complicate updates, and increase user-security risks. Distribution decisions should evaluate authenticity, signing, update integrity, supportability, and jurisdictional requirements.

7.4 Revenue models

Common models include one-time purchase, advertising, subscription, transaction commission, in-app purchase, licensing to organizations, and freemium access. Revenue design affects architecture and ethics. Subscription systems must clearly communicate renewal, cancellation, pricing, and trial conditions. Advertising should not collect excessive personal data or undermine usability and privacy.

8. Mobile Applications and Digital Transformation

Digital transformation is the organizational redesign of processes, services, capabilities, and decision-making through digital technologies. A mobile app is not automatically a transformation. Reproducing a paper form on a screen may digitize an existing task without improving the underlying service.

Mobile applications can contribute to transformation by:

• moving work to the point of activity;
• connecting customers, employees, suppliers, and devices;
• collecting timely operational data;
• enabling self-service and personalized interaction;
• integrating payments, identity, location, and notifications;
• supporting evidence-based decisions through analytics;
• reducing delays and manual transcription;
• enabling new service and revenue models.

A useful analysis considers the complete service system: user needs, process redesign, backend integration, data governance, staff roles, accessibility, support, and performance measures. For example, a field-service app may improve scheduling only if it is integrated with inventory, customer records, dispatch rules, and billing.

Artificial intelligence may add value through recommendations, speech interfaces, document classification, anomaly detection, translation, or predictive maintenance. However, mobile AI requires careful attention to privacy, model reliability, bias, explainability, energy consumption, and whether processing occurs on the device or in the cloud. AI should support a defined user or organizational need rather than being added solely as a marketing feature.

9. Illustrative Case: Mobile Transformation in Community Healthcare

Background

Consider CareLink, a fictional community-health organization serving patients through clinics and home visits. Nurses previously used paper forms and later entered information into a central system. This created delays, transcription errors, and limited visibility of urgent cases.

Problem

The organization needed a mobile solution that could operate in homes with unreliable connectivity, protect sensitive health information, support accessibility, and integrate with its existing patient-record system. A simple online form would fail when staff had no signal and could encourage unsafe storage of patient data.

Analysis

The requirements revealed several mobile-computing constraints:

• intermittent connectivity required local encrypted storage and controlled synchronization;
• battery and network use required efficient data transfer;
• health data required strong authentication, authorization, audit trails, and retention controls;
• different staff roles required least-privilege access;
• the app needed to save work during interruptions and device restarts;
• accessible text, contrast, touch targets, and screen-reader labels were essential;
• organizational success depended on workflow redesign and training, not only software installation.

Approach and solution

CareLink selected a cross-platform approach for shared clinical workflow logic, while using platform-specific security and notification services when needed. The app allowed nurses to download only assigned cases, record observations offline, encrypt local data, and synchronize when a trusted connection was available. Synchronization used unique operation identifiers so that retries would not duplicate records. Conflicts were shown to authorized staff rather than silently overwriting clinical information.

The backend enforced authorization independently of the mobile client. Devices were managed through an enterprise mobility system, could be remotely revoked, and required operating-system security updates. The application recorded an audit event for access to sensitive records but avoided placing clinical details in ordinary notification previews.

Outcome

In this illustrative scenario, the organization reduced duplicate data entry and obtained faster visibility of completed visits. More importantly, it established a governed digital workflow. The project also exposed limitations: staff needed training, some rural locations still required later synchronization, and integration maintenance became an ongoing responsibility.

Learning points

1. Mobile transformation combines device software, networks, backend systems, people, and governance.
2. Offline capability must protect data integrity rather than merely cache screens.
3. Security cannot depend only on the app; the server and organization must enforce policy.
4. Platform selection should follow requirements, risk, skills, and lifecycle cost.
5. Accessibility and privacy are quality attributes, not optional enhancements.
6. Outcomes should be measured using service quality and safety, not only download counts.

10. Best Practices for Mobile Application Development

A professional mobile team should:

• begin with user journeys, constraints, and measurable outcomes;
• select native, web, hybrid, or cross-platform architecture intentionally;
• design for interruption, disconnection, resizing, and process termination;
• minimize permissions and explain their purpose;
• protect credentials and sensitive data using platform security facilities;
• validate authorization on the server;
• follow accessibility standards and test with assistive technologies;
• test across representative devices, operating-system versions, network conditions, and input methods;
• monitor crashes, latency, battery impact, and failed synchronization without collecting unnecessary personal data;
• automate builds, tests, signing, and release controls securely;
• use staged releases, rollback plans, and documented incident response;
• maintain dependencies and respond to security advisories;
• provide transparent privacy notices, subscription terms, and support channels.

11. Challenges and Limitations

Mobile ecosystems create strategic and technical dependencies. A platform vendor may change APIs, permission policies, store rules, or commercial terms. Device fragmentation increases testing cost. Users may reject intrusive permissions or abandon apps that consume excessive battery. Connectivity and location data can be inaccurate. Accessibility can be undermined by custom interfaces. Analytics can become surveillance if collected without necessity or meaningful consent.

There are also social and organizational limitations. Not all users own modern smartphones, have reliable data service, or possess the same digital skills. A mobile-only service may exclude people with disabilities, older users, low-income users, or people who require shared-device access. Digital transformation should therefore provide appropriate alternatives, support human assistance, and evaluate inclusion as a design requirement.

Chapter Summary

Mobile computing combines portable devices, wireless networks, operating systems, applications, cloud services, and context-aware interaction. Its distinctive conditions include mobility, intermittent connectivity, resource constraints, device heterogeneity, personalization, and physical exposure.

Android and iOS provide mature but different ecosystems. Android offers broad hardware diversity and market reach, while iOS provides tightly integrated hardware, software, and distribution. Native, web, progressive web, hybrid, and cross-platform applications each involve trade-offs among performance, device access, user experience, development cost, and platform dependence.

Mobile operating systems control memory, battery, permissions, background execution, security, and application lifecycle states. Robust applications persist state, tolerate interruption and disconnection, minimize permissions, protect data, and test realistic device conditions. Distribution may occur through public stores, private enterprise channels, web delivery, or regulated alternative channels, each with governance and security implications.

Mobile applications support digital transformation when they improve complete organizational services rather than merely reproduce paper processes. Successful transformation integrates mobile interfaces with backend systems, people, data governance, accessibility, security, and measurable outcomes. Professional developers must therefore treat privacy, inclusion, reliability, and lifecycle maintenance as central engineering responsibilities.

Key Terms

Mobile computing: Computing performed through portable devices and wireless or mobile communication.

Mobile device: A portable computing device capable of processing data and usually communicating wirelessly.

Mobile application: Software designed to operate on or through a mobile device.

Mobile platform: An operating system, SDK, APIs, runtime, security model, and distribution infrastructure.

Mobile ecosystem: The connected community of vendors, developers, users, services, stores, and regulators surrounding a platform.

Mobility: The ability of users, devices, or services to operate while location or network attachment changes.

Context-aware computing: Computing that adapts using information about location, time, activity, or device state.

Native application: An app developed specifically for a particular operating system.

Progressive web application: A web application enhanced with responsive, installable, and caching capabilities where supported.

Hybrid application: An application combining web technologies with a native container.

Cross-platform development: Development that shares code or a programming model across multiple mobile platforms.

Sandbox: An isolated execution and data environment that limits an application’s access to other software and resources.

Permission: User- or system-controlled authorization for access to protected device or data capabilities.

Application lifecycle: The sequence of operational states through which an app passes during installation, use, suspension, and termination.

Offline-first design: Designing an application so that network absence is anticipated and useful behavior continues where appropriate.

Synchronization: The controlled exchange and reconciliation of local and remote data.

Digital transformation: Organizational redesign using digital technologies to improve services, processes, capabilities, or business models.

Enterprise mobility management: Policies and technologies used to manage mobile devices, applications, identities, and organizational data.

Review Questions

Short Answer Questions

1. What is the difference between a mobile platform and a mobile ecosystem?
2. Identify four characteristics that distinguish mobile computing from desktop computing.
3. What is a native mobile application?
4. Why must mobile applications persist state during lifecycle transitions?
5. Name two risks associated with distributing an application through uncontrolled channels.

Long Answer Questions

1. Compare the Android and iOS ecosystems in terms of hardware diversity, development, distribution, and testing.
2. Explain how intermittent connectivity affects mobile application architecture and user experience.
3. Discuss the advantages and limitations of native, web, hybrid, and cross-platform application approaches.
4. Explain the relationship among permissions, privacy, security, and user trust in mobile applications.
5. Describe how a mobile application can contribute to digital transformation without simply digitizing an existing paper process.

Analytical / Application Questions

1. A university wants an application for campus navigation, event notifications, digital identity, and emergency communication. Recommend an application architecture and distribution model, and justify your decision using platform, connectivity, privacy, and lifecycle considerations.
2. A retail app repeatedly submits the same order when the user reconnects after an offline period. Analyze the likely design failure and propose a safer synchronization strategy.
3. Using the CareLink case, identify three technical risks and three organizational or ethical risks. For each, propose a control or mitigation and explain how success could be evaluated.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a mobile ecosystem from a mobile platform?

A. A platform refers only to device hardware, while an ecosystem refers only to software.

B. A platform includes the operating system and development infrastructure, while an ecosystem also includes users, vendors, stores, services, and regulators.

C. A platform is used for web applications, while an ecosystem is used only for native applications.

D. A platform is always open source, while an ecosystem is always proprietary.

Correct Answer: B. A platform includes the operating system and development infrastructure, while an ecosystem also includes users, vendors, stores, services, and regulators.

Question 2

Which characteristic most directly requires an application to support caching and retry behavior?

A. Intermittent connectivity

B. Large screen size

C. High-resolution graphics

D. Mechanical keyboard input

Correct Answer: A. Intermittent connectivity

Question 3

What is a major development consequence of Android’s hardware diversity?

A. Android applications cannot use sensors.

B. Developers need compatibility testing across representative devices and configurations.

C. Android applications must be distributed only through Apple’s App Store.

D. Android applications never require permissions.

Correct Answer: B. Developers need compatibility testing across representative devices and configurations.

Question 4

Which application type is developed specifically with the SDK and conventions of one operating system?

A. Native application

B. Progressive web application

C. Hybrid application

D. Browser bookmark

Correct Answer: A. Native application

Question 5

Why should an application persist important data before it enters a background or suspended state?

A. The operating system may later terminate the application process.

B. The application store requires all data to be deleted.

C. Persistence increases screen brightness.

D. Background applications always receive unlimited memory.

Correct Answer: A. The operating system may later terminate the application process.

Question 6

Which is the best example of least-privilege permission design?

A. Requesting camera, contacts, microphone, and location access at first launch regardless of features used.

B. Requesting location only when the user activates a location-based feature and explaining why it is needed.

C. Disabling all permission controls to simplify development.

D. Storing permission decisions in a public text file.

Correct Answer: B. Requesting location only when the user activates a location-based feature and explaining why it is needed.

Question 7

Which distribution model is most appropriate for an internal application used only by an organization’s managed employees?

A. A private enterprise distribution channel

B. An anonymous public download with no authentication

C. A printed manual

D. A public advertising network

Correct Answer: A. A private enterprise distribution channel

Question 8

In the CareLink case, why should synchronization operations have unique identifiers?

A. To make the screen use more colors

B. To prevent retries from creating duplicate records

C. To eliminate the need for server authorization

D. To ensure that the app works only on Wi-Fi

Correct Answer: B. To prevent retries from creating duplicate records

Question 9

Which statement best describes digital transformation?

A. Replacing every employee with a mobile device

B. Putting a paper form on a phone without changing the process

C. Redesigning services, processes, capabilities, or business models through digital technologies

D. Increasing the number of application icons on a device

Correct Answer: C. Redesigning services, processes, capabilities, or business models through digital technologies

Question 10

Which practice is most important for protecting against a compromised or reverse-engineered mobile client?

A. Enforcing authorization only in the user interface

B. Relying on hidden buttons for security

C. Enforcing authorization and business rules on trusted backend services as well as in the client

D. Hard-coding server passwords in the application package

Correct Answer: C. Enforcing authorization and business rules on trusted backend services as well as in the client