CampusLearn
← BIT 305 Mobile Application Development

Mobile UI/UX and Android Fundamentals

Notes

Designing for mobile users User interface (UI) refers to the visible controls and layouts through which people interact with an application. User experience (UX) covers the wider experience of completing tasks, including clarity, accessibility and confidence. Mobile design must accommodate small screens, interruptions, varied literacy and unreliable connectivity. Start with user tasks and simple navigation rather than decorative screens. Use readable text, meaningful labels, adequate touch targets and clear feedback after actions. Validate forms near the relevant field, preserve entered information after recoverable errors and avoid communicating essential status through colour alone. Android application structure Android applications contain components managed by the operating system. An activity provides an interaction entry point, while a ViewModel holds screen-related state across supported configuration changes such as rotation. The activity lifecycle describes transitions between states as screens become visible, pause or stop. Persistent information needs durable storage because a process can be terminated. Declarative UI tools such as Jetpack Compose describe the interface as a function of state. Keep long-running work off the main thread to avoid frozen interactions, and request sensitive permissions only when the relevant feature needs them. Practical example A Garissa mobile money agent tests a transaction entry screen with eight staff members. Before redesign, completing one record takes an average of 75 seconds; after clearer labels and fewer fields, it takes 50 seconds. The reduction is 25 seconds per transaction, or 25 divided by 75 times 100, approximately 33.3 percent. At 120 entries daily, estimated time released is 120 times 25, or 3,000 seconds, equal to 50 minutes. The team also tests rotation and process recreation to ensure an unfinished amount is restored appropriately, while requiring confirmation before submission to avoid accidental duplicate transactions.

Quiz

1. Why should important data not exist only in activity memory?

2. Saving 25 seconds on each of 120 transactions releases how much time?

3. Which choice most directly improves accessibility?

Sign in to submit and securely grade your quiz.