is the creation of software designed to run on one or more mobile devices while accounting for device hardware and interface constraints.

Context: Definition and constraints of mobile app development

Mobile apps must be built around limited CPU/RAM/storage and diverse display and input methods, which is called .

Context: Meaningful concept: device constraints shaping app design

Mobile UI design aims for an understandable, user-friendly interface by considering constraints, context cues, screen space, and input methods. This is .

Context: Core concept: Mobile UI design

In the interaction model, the user manipulates the system through input, and the device outputs indicate the effects of that manipulation.

Context: UI interaction model meaning

Mobile UI context clues are signals from user activity (for example, time or location) observed from interactions that can drive suggestions or filtering. This concept is .

Context: Meaningful term: UI context clues

Mobile UIs rely on mobile back-ends to access enterprise systems securely. This enables features like authentication/authorization, offline work, and service orchestration. The enabling component is the .

Context: Core concept: Mobile back-end responsibilities

Mobile back-end responsibilities include routing data, enforcing security, handling authentication/authorization, supporting offline work, and orchestrating services. This set of responsibilities is called .

Context: Meaningful term: Mobile back-end responsibilities

Mobile UIs rely on middleware such as MBaaS and SOA infrastructure to support back-end functionality. The middleware service that provides back-end functionality is .

Context: Meaningful term: MBaaS

Service orchestration for mobile back-ends is supported by infrastructure.

Context: Meaningful term: SOA

Development packages (SDKs and IDEs) provide tools to write, test, and deploy apps for target platforms. These tools are .

Context: Core concept: SDKs/IDEs and developer tooling

A formal process where developers submit apps for review before inclusion in official outlets is called .

Context: Meaningful term: Marketplace submission and approval

Official marketplaces require formal review/approval for app inclusion. This means developers must submit apps through an approval process before distribution. The cause→effect relationship is: Official marketplaces require review/approval, which causes which leads to distribution.

Context: Cause→effect chain: marketplaces enforce submission and approval

Mobile displays and input methods vary widely (screen technology/size/resolution; buttons/keyboards/touch with or without styluses). This causes mobile UI design to adapt to different form factors and interaction patterns, which is why must adapt.

Context: Cause→effect chain: device variation drives UI adaptation

Developers must support many devices with different screen sizes and configurations. This causes them to need cross-platform accommodations and testing across device variants, which is supported by and packaging approaches.

Context: Cause→effect chain: many devices drive cross-platform accommodations

Cross-platform approaches and packaging formats determine whether apps are built once or separately and how they are installed on each platform. This concept is .

Context: Core concept: Cross-platform deployment and packaging