MCA-112 Mobile Applications Design and Development Notes cover all 4 units of this MCA Semester 2 core elective in 110 pages: 109 Kotlin, XML and Swift code examples, 11 diagrams, 58 solved short answers and 44 long questions with answer hints, for batches admitted from 2025-26 onwards.
Written by Prateek Talwar, Founder, Unnati Educations · Reviewed by Ritik Rawat, B.Tech, Senior Full Stack Developer · Checked against the MCA Scheme of Examination and Detailed Syllabus (BoS USIC&T, 28 Jul 2025) · Updated 14 October 2026 · Editorial policy
Scheme: MCA (2 years), A.S. 2025-26 onwards | Applies to: batch admitted 2025-26 onwards | Verified against: MCA syllabus PDF, 28/07/2025
MCA-112 Mobile Applications Design and Development at a glance: GGSIPU MCA Sem 2 credits, units and exam pattern
| Code and title | MCA-112 Mobile Applications Design and Development |
|---|---|
| Course and semester | MCA (2 years), Semester 2 · 4 units |
| Category and credits | Core Elective I · 4 credits · L 3, T 1 |
| Marks | 100 per paper · end-term 60 · internal share not printed separately |
| End-term pattern | Q1 compulsory, whole syllabus, 12 marks · 1 of 2 questions per unit, 12 marks each (12 + 48 = 60 marks) |
| Passing marks | 40 out of 100 |
| Paired lab | MCA-168 Lab based on Core Elective I · 0-2-1 · marks not printed |
| Rules | GGSIPU Ordinance 11 |
The official PDF numbers the units but prints no unit titles, so the unit names here come from the notes. MCA-112 is listed with the other GGSIPU MCA Semester 2 papers.
MCA-112 Mobile Applications Design and Development Notes unit-wise: 109 Kotlin, XML and Swift code examples across 4 units
Android comes first in Kotlin, iOS second in Swift. Explanations are in English; the 16 exam-tip boxes use simple Hinglish. The header sample PDF shows four inside pages. Notes for other MCA papers sit under GGSIPU MCA notes.
MCA-112 Unit 1: Android Systems, Application Components, Activities and Intents
Pages 5 to 28: the Open Handset Alliance, the five-layer Android stack with Dalvik vs ART, the Gradle build flow (D8, R8, APK), the four components, manifest, intent filters and permissions, then the Activity Result API, life cycle and saving state. 20 code examples, 12 short answers, 10 long questions.
| User action | Callback sequence |
|---|---|
| Launches the app | onCreate → onStart → onResume |
| Presses Home | onPause → onStop |
| Presses Back | onPause → onStop → onDestroy |
| Rotates the screen | onPause → onStop → onSaveInstanceState → onDestroy, then recreated |
Quick look: activity callbacks by scenario (from page 23)
- User action
- Launches the app
- Callback sequence
onCreate → onStart → onResume
- User action
- Presses Home
- Callback sequence
onPause → onStop
- User action
- Presses Back
- Callback sequence
onPause → onStop → onDestroy
- User action
- Rotates the screen
- Callback sequence
onPause → onStop → onSaveInstanceState → onDestroy, then recreated
MCA-112 Unit 2: Android User Interface, Fragments and RecyclerView
Pages 29 to 52, the heaviest XML unit: layouts and every named widget, listeners, animations, notification channels, Toolbar, menus, FAB and ViewPager2 tabs. Fragments get a life cycle diagram and two ways to talk to the activity, and a full RecyclerView adapter closes the unit. 32 code examples, 15 short answers, 11 long questions.
| Layout | Arranges children | Typical use |
|---|---|---|
ConstraintLayout | By constraints, flat hierarchy | Default for complex screens |
RelativeLayout | Relative to parent or siblings | Older apps |
FrameLayout | Stacked on top of each other | Fragment container |
GridLayout | Grid with row and column spans | Dashboards, keypads |
Quick look: which Android layout to pick (from page 31)
- Layout
ConstraintLayout- Arranges children
- By constraints, flat hierarchy
- Typical use
- Default for complex screens
- Layout
RelativeLayout- Arranges children
- Relative to parent or siblings
- Typical use
- Older apps
- Layout
FrameLayout- Arranges children
- Stacked on top of each other
- Typical use
- Fragment container
- Layout
GridLayout- Arranges children
- Grid with row and column spans
- Typical use
- Dashboards, keypads
MCA-112 Unit 3: Android Storage and APIs, iOS Technology Stack and Swift
Pages 53 to 81, the bridge unit. The Android half has SharedPreferences, a SQLite CRUD class, Room, a custom ContentProvider, MediaPlayer, Retrofit, WebView, telephony and the Fused Location Provider. The iOS half covers Xcode, StoryBoard, AppDelegate and a pass/fail app, then Swift from optionals to closures. 32 code examples, 15 short answers, 12 long questions.
| Operator | What it does | Result |
|---|---|---|
is | Checks the type | Bool |
as | Upcast, checked at compile time | Value as the new type |
as? | Tries a downcast | Optional, nil on failure |
as! | Forced downcast | Crashes on failure |
Quick look: the four Swift type-casting operators (from page 73)
- Operator
is- What it does
- Checks the type
- Result
- Bool
- Operator
as- What it does
- Upcast, checked at compile time
- Result
- Value as the new type
- Operator
as?- What it does
- Tries a downcast
- Result
- Optional, nil on failure
- Operator
as!- What it does
- Forced downcast
- Result
- Crashes on failure
MCA-112 Unit 4: iOS User Interactions and Data Persistence (Core Data)
Pages 82 to 110, all UIKit and Swift: target-action controls, gesture recognisers and raw touches, Auto Layout, UIStackView, the navigation stack, timers and a master-detail UITableView, then Core Location, MapKit, Google Maps, Core Motion and Core Data CRUD. 25 code examples, 16 short answers, 11 long questions.
| Core Data | SQLite |
|---|---|
| Object graph and persistence framework | Relational database engine |
Swift objects, NSPredicate queries | Tables and SQL queries |
| Change tracking, undo, migration built in | Written by hand |
| Apple platforms only | Cross-platform |
Quick look: Core Data vs SQLite (from page 108)
- Core Data
- Object graph and persistence framework
- SQLite
- Relational database engine
- Core Data
- Swift objects,
NSPredicatequeries - SQLite
- Tables and SQL queries
- Core Data
- Change tracking, undo, migration built in
- SQLite
- Written by hand
- Core Data
- Apple platforms only
- SQLite
- Cross-platform
MCA-112 exam corner: 58 solved short answers and 44 long questions by unit
| Unit | Short answers | Long questions | Code examples |
|---|---|---|---|
| Unit 1 (p27-28) | 12 | 10 | 20 |
| Unit 2 (p51-52) | 15 | 11 | 32 |
| Unit 3 (p80-81) | 15 | 12 | 32 |
| Unit 4 (p108-110) | 16 | 11 | 25 |
MCA-112 exam corner by unit
- Unit
- Unit 1 (p27-28)
- Short answers
- 12
- Long questions
- 10
- Code examples
- 20
- Unit
- Unit 2 (p51-52)
- Short answers
- 15
- Long questions
- 11
- Code examples
- 32
- Unit
- Unit 3 (p80-81)
- Short answers
- 15
- Long questions
- 12
- Code examples
- 32
- Unit
- Unit 4 (p108-110)
- Short answers
- 16
- Long questions
- 11
- Code examples
- 25
The MCA-112 notes solve 58 short-answer questions and list 44 long questions with answer hints across 4 units, plus 109 code examples.
- Unit 1: Differentiate explicit and implicit intents. Pointer: explicit names the class; implicit gives an action such as
ACTION_VIEWand intent filters decide. - Unit 2: What is a notification channel? Pointer: compulsory from Android 8.0; lets the user control one type of notification.
- Unit 3: What is a content URI? Pointer:
content://authority/path/id: scheme, provider authority, table path, optional record id. - Unit 4: How is a Timer created and stopped in iOS? Pointer:
scheduledTimer(withTimeInterval:repeats:block:)starts it;invalidate()stops it.
More practice sits in the MCA-112 important questions.
iOS architecture and Android vs iOS in mobile app development: excerpt from page 64 of the MCA-112 notes
Excerpt from page 64 (Unit 3, Part C: Introduction to iOS Technology Stack)
1. iOS: overview
iOS is Apple's mobile operating system for the iPhone (iPadOS runs the iPad). It is closed-source and based on Darwin, which uses the Unix-like XNU kernel. Apps are built in Xcode with Swift or Objective-C and reach users through the App Store after Apple's review.
| Android | iOS |
|---|---|
| Open source (AOSP), Linux kernel | Closed source, Darwin (XNU) kernel |
| Many manufacturers | Only Apple devices |
| Kotlin or Java | Swift or Objective-C |
| Android Studio on Windows, macOS or Linux | Xcode, macOS only |
| APK or AAB on Google Play | IPA on the App Store |
| XML layouts or Jetpack Compose | StoryBoard (Interface Builder) or SwiftUI |
| Activity | ViewController |
Android and iOS compared (excerpt, page 64)
- Android
- Open source (AOSP), Linux kernel
- iOS
- Closed source, Darwin (XNU) kernel
- Android
- Many manufacturers
- iOS
- Only Apple devices
- Android
- Kotlin or Java
- iOS
- Swift or Objective-C
- Android
- Android Studio on Windows, macOS or Linux
- iOS
- Xcode, macOS only
- Android
- APK or AAB on Google Play
- iOS
- IPA on the App Store
- Android
- XML layouts or Jetpack Compose
- iOS
- StoryBoard (Interface Builder) or SwiftUI
- Android
- Activity
- iOS
- ViewController
2. iOS architecture
iOS is built in layers. The higher layers give high-level, object-oriented services and the lower layers give basic system services, so an app should always use the highest layer that does the job. From top to bottom the four layers are:
- Cocoa Touch: UIKit, SwiftUI, event handling and gestures, push notifications, MapKit, GameKit, Message UI, Auto Layout.
- Media: Core Graphics, Core Animation, Core Image, Metal, AVFoundation, Core Audio, AVKit, Photos.
- Core Services: Foundation, Core Foundation, Core Data, Core Location, CloudKit, networking, SQLite.
- Core OS: XNU kernel, security, Bluetooth, Accelerate, Local Authentication (Face ID, Touch ID), drivers, memory and file system.
(1) Core OS layer
This is the lowest layer, closest to the hardware. It holds the XNU kernel, device drivers, memory management, the file system, networking, the security framework (keychain and encryption), Bluetooth, power management and Accelerate for fast maths and signal processing.
(2) Core Services layer
These are the basic system services every app uses: Foundation for strings, collections, dates and URL loading, Core Data for object persistence, Core Location for GPS, plus CloudKit, SQLite, Core Motion, in-app purchase and HealthKit.
Do the MCA-112 notes cover the full GGSIPU syllabus?
Yes. Every official MCA-112 topic has a matching section, including Google Maps in iOS, sensors and Core Data CRUD.
| Official unit | Official topics | In the notes | Status |
|---|---|---|---|
| Unit I | Android systems and build system · application components, intents, manifest, permissions · activities, life cycle, context, data sharing | p6-26 | Covered |
| Unit II | Android UI, layouts, widgets, events, animations, notifications, menus, tabs · fragments · ListView, RecyclerView | p30-50 | Covered |
| Unit III | Android storage, SQLite, content providers · multimedia, networking, web, telephony, location APIs · iOS stack · Swift | p54-79 | Covered |
| Unit IV | Controls, gestures, touches, bounds and frame, navbar, toolbar, timers, container view, table, Core Location, MapKit, Google Maps, sensors · Core Data CRUD | p83-108 | Covered |
MCA-112 official topics mapped to the notes
- Official unit
- Unit I
- Official topics
- Android systems and build system · application components, intents, manifest, permissions · activities, life cycle, context, data sharing
- In the notes
- p6-26
- Status
- Covered
- Official unit
- Unit II
- Official topics
- Android UI, layouts, widgets, events, animations, notifications, menus, tabs · fragments · ListView, RecyclerView
- In the notes
- p30-50
- Status
- Covered
- Official unit
- Unit III
- Official topics
- Android storage, SQLite, content providers · multimedia, networking, web, telephony, location APIs · iOS stack · Swift
- In the notes
- p54-79
- Status
- Covered
- Official unit
- Unit IV
- Official topics
- Controls, gestures, touches, bounds and frame, navbar, toolbar, timers, container view, table, Core Location, MapKit, Google Maps, sensors · Core Data CRUD
- In the notes
- p83-108
- Status
- Covered
Official source: MCA (2 years) scheme of examination and detailed syllabus, A.S. 2025-26 onwards.
Room, Retrofit and SwiftUI code are extras, so these GGSIPU MCA Sem 2 mobile applications design and development notes work as a full-syllabus book. Every course in GGSIPU notes is mapped to its official PDF the same way.
Who writes and checks the MCA-112 mobile app notes?
- Prateek Talwar (author, plans and edits): Founder, Unnati Educations; Associate Company Secretary (ACS), ICSI, membership no. 58704, since 15 May 2019; B.Com, University of Delhi (School of Open Learning), 2012. Author bio
- Ritik Rawat (subject reviewer, checks the Kotlin, XML and Swift code): Senior Full Stack Developer, Unnati Educations · B.Tech
For the 2026-27 edition, all four units were mapped against the MCA scheme approved on 28 July 2025. These mobile applications design and development notes in English were last updated on 14 October 2026 under our editorial policy.
Anyone looking for MCA-112 Mobile Applications Design and Development IPU notes with runnable code will find two full CRUD programs, SQLite on page 56 and Core Data on page 106. The same team prepares GGSIPU important questions for every course.
MCA-112 and the MCA-168 mobile apps lab, plus other GGSIPU MCA Sem 2 papers
Your MCA-112 lab is the mobile apps version of MCA-168 (0-2-1, 1 credit): MCA-168 mobile apps lab notes. The syllabus gives six lab outcomes, no practical list.
- Unit 1 activities and intents → lab CO2
- Unit 2 fragments and views → lab CO4
- Unit 3 web and telephony APIs → lab CO3
- Unit 4 iOS SDK and Swift apps → lab CO5 and CO6
Other Semester 2 papers: MCA-102 Data and File Structures, MCA-104 Object Oriented Software Engineering, MCA-106 Python Programming, one Open Elective I (MCA-128 to MCA-134), MCA-170 Minor Project II and the NUES papers MCA-172 and MCA-174.
How to write MCA-112 answers: diagram-led long answers and code-backed Android and Swift short answers
The official paper has one compulsory 12-mark short-answer question and one 12-mark question per unit. The notes' exam corners label answers 2.5 and 12.5 marks, so plan your time on the official 12-mark pattern and use the notes for content.
- Long answers: the exam tips in the notes repeat one rule: a long answer needs a diagram or table plus a short piece of code. For Android architecture, draw the five layers bottom to top, write 2-3 points per layer and add the Dalvik vs ART table. For the activity or fragment life cycle, draw the callback chain and add a "when called, what to do" table.
- Two traps: iOS has four layers (Core OS, Core Services, Media, Cocoa Touch), so do not mix it up with Android's five; and Core Data is a framework, not a database, which belongs in the first line of a Core Data answer.
- Short answers: for Swift, a two-line example beats a definition, such as
letvsvar, oras?returning nil. In Android, name the exact class or method, e.g.SQLiteOpenHelperwithonCreate()andonUpgrade(), as the Unit 3 exam corner answer does.
Worked example: "Explain RecyclerView with its components and an example. Compare it with ListView." (Unit 2, long question 10)
Plan four blocks, as the page 50 tip says: a parts table (Adapter, ViewHolder, LayoutManager, ItemDecoration, ItemAnimator), the three adapter methods, the LayoutManager types and a ListView vs RecyclerView table. The code must show all three methods:
override fun onCreateViewHolder(parent: ViewGroup, viewType: Int): VH
override fun onBindViewHolder(h: VH, pos: Int)
override fun getItemCount() = list.sizeEnd with one line on DiffUtil (page 49).
Practise this format on GGSIPU MCA important questions.
MCA-112 mobile app notes FAQs
How do I get the full MCA-112 notes?
Use the "Get Full Notes" WhatsApp button on this page. The full MCA-112 notes come as a printed book only; they are not sold as a PDF. It has all 4 units in 110 pages with 109 code examples. Delivery takes 5 to 7 days at most, depending on your location, and the price is shared on WhatsApp.
Is MCA-112 compulsory in MCA Semester 2?
No. MCA-112 is one of ten papers in Core Elective I and each student picks one, such as MCA-108 Advanced DBMS or MCA-116 Web Technologies. The scheme says an elective needs at least 20 students for classes; with fewer, it may still be offered, but students complete it through a MOOC platform such as SWAYAM with prior approval.
What is the passing mark for MCA-112?
MCA-112 is marked out of 100, of which the end-term paper carries 60: a 12-mark compulsory question plus 4 unit questions of 12 marks each. The MCA scheme of examination states pass marks as 40 out of 100 for every paper. For end-term minimums, re-appear and result rules, check Ordinance 11 on ipu.ac.in, which governs the programme.
Do the MCA-112 notes use Kotlin or Java for Android?
The Android code in the MCA-112 notes is in Kotlin, with XML for layouts, menus, drawables and the manifest. The notes mention that Java is still supported, and older patterns such as startActivityForResult() are explained because exams still ask about them. The iOS code in Units 3 and 4 is in Swift with UIKit, plus one SwiftUI example.
Which MCA-112 unit has the most code examples?
Units 2 and 3 have 32 code examples each: Unit 2 is mostly XML and Kotlin for widgets, fragments and RecyclerView, while Unit 3 mixes SQLite, Room and Retrofit with the first Swift programs. Unit 4 has 25 Swift examples on UIKit, maps and Core Data; Unit 1 has 20 on components, intents and the life cycle.
Do I need a Mac to study the iOS part of MCA-112?
Not for the theory paper. The MCA-112 notes explain every Swift and UIKit topic with code, and many examples show the printed result in comments, so Units 3 and 4 can be learnt from the book. The notes point out that Xcode runs only on macOS, so running iOS programs for the MCA-168 lab needs Xcode on a Mac.
Get the full MCA-112 Mobile Applications Design and Development Notes on WhatsApp
110 pages with cover and index, 11 diagrams and 16 exam-tip boxes. Format: printed book only, not available as a PDF. Price is shared on WhatsApp. Delivery: within 5 to 7 days at most; the exact time may vary with your location.
Order the MCA-112 notes book on WhatsApp (4 units, 110 pages)
Unnati Educations is an independent education provider based in Vikaspuri, Delhi. We are not affiliated with, authorised by, or endorsed by Guru Gobind Singh Indraprastha University (GGSIPU). 'GGSIPU' and 'IPU' are used only to describe the syllabus our notes follow. For official information, visit ipu.ac.in.
Ready for the full notes?
Discuss coverage and delivery with our team.