Exams on an introductory mobile application development course at this level usually follow a familiar shape. A common layout is five or six questions, of which you answer four in 2 to 3 hours; some papers make the first question compulsory. Each question is usually worth 15–20 marks, split into two to four parts. Where the course has a practical component, a project or lab work often carries a share of the continuous-assessment marks, and the written paper focuses on concepts, diagrams and short pieces of code.

The questions come from a predictable territory. Expect definitions and lists (what a mobile app is, the constraints of mobile development, the lifecycle stages), comparisons (native vs hybrid vs cross-platform vs web and PWA, Android vs iOS, USSD vs app, Flutter vs React Native), architecture diagrams (the Android platform stack, the iOS layers), and the Android activity lifecycle, very often as a labelled diagram plus a scenario ("what callbacks run when the user rotates the phone, or presses Home?"). The four application components and intents make tidy short parts. Later topics bring storage options, REST APIs and offline-first design, runtime permissions, mobile security risks, testing types, and the steps to publish on Google Play or the App Store. Some papers ask you to write or complete a short piece of Kotlin, Java or Dart: a composable or layout, a ViewModel, a permission request, a Room entity.

A calm strategy: read every question before choosing, and favour the ones where you can draw a clean, labelled diagram or build a comparison table. For every "explain N", give N numbered points, each with a one-line example. For every "compare", define both sides first, then a table with at least as many rows as the marks suggest. For code, write less but write it correctly, with the key annotations and names spelled right, and add a comment saying what each part does. Calm, structured, labelled: that is what full marks look like here.