BCA 318T Mobile Application Development Notes cover all 4 units of the BCA Semester 6 Android paper in 76 pages, with 73 code listings in Java, XML and Gradle, 20 labelled diagrams and 108 exam questions (65 two-mark, 43 ten-mark). They follow the syllabus for the batch admitted in 2024-25 onwards.
Written by Prateek Talwar, Founder, Unnati Educations · Reviewed by Ritik Rawat, B.Tech, Senior Full Stack Developer · Checked against the BCA Scheme of Examination & Syllabi, 19.08.2026 · Updated 13 October 2026 · Editorial policy
Scheme: BCA Scheme of Examination & Syllabi (USICT) | Applies to: batch admitted 2024-25 onwards | Verified against: BCA Scheme of Examination & Syllabi, 19.08.2026
BCA 318T Mobile Application Development at a glance: GGSIPU BCA Sem 6 credits, units and exam pattern
BCA 318T is an elective Android paper: students pick one Programme Core Elective theory paper with its lab. It is one of the GGSIPU BCA Semester 6 papers, with Java Programming as its listed pre-requisite.
| Code and title | BCA 318T · Mobile Application Development |
|---|---|
| Course and semester | BCA, Semester 6 |
| Category and credits | Programme Core Elective (PCE) · 4 credits · L-T-C 4-0-4 |
| Marks | 100: 40 internal + 60 end-term |
| Applies to | Batch admitted 2024-25 onwards |
| End-term pattern | Q1: 10 compulsory two-mark questions, at least 2 per unit; then one 10-mark question from each unit (20 + 40 = 60 marks) |
| Exam duration | 3 hours |
| Units | 4, with 11 lecture hours each |
| Paired lab | BCA 318P · PCE · 2 credits · 100 marks (40 + 60) |
The official PDF numbers units only; the unit titles here are from the notes.
BCA 318T Mobile Application Development Notes unit-wise: 73 code listings and 108 exam questions across 4 units
These BCA 318T Mobile Application Development IPU notes teach each topic with a definition, a table or diagram and working code, and end every unit with exam questions and a revision table. Notes for every other paper sit under GGSIPU BCA notes. Seven pages sit in the sample PDF above.
BCA 318T Unit 1: Introduction to Android & Android Application Basics
From the IBM Simon to Android 16: app types, Android versions and architecture, a first app in Android Studio, Context, the Activity lifecycle, started and bound Services, Intents, Broadcast Receivers, the manifest and runtime permissions.
Pages 4 to 21 · 18 sections · 14 code listings · 7 diagrams · 15 two-mark and 9 ten-mark questions.
| Point | Application | Activity |
|---|---|---|
| Get it with | getApplicationContext() | this |
| Lives as long as | The whole app | That screen |
| Use for | Database helper, singletons | Dialogs, Toasts, layouts |
Quick look: Application Context vs Activity Context (from page 13)
- Point
- Get it with
- Application
getApplicationContext()- Activity
this
- Point
- Lives as long as
- Application
- The whole app
- Activity
- That screen
- Point
- Use for
- Application
- Database helper, singletons
- Activity
- Dialogs, Toasts, layouts
BCA 318T Unit 2: User Interface in Android & Application Components
The biggest coding unit: seven layouts, adaptive screens, input controls and listeners, three menu types, navigation, a RecyclerView adapter, drawables, themes, Fragments with 11 callbacks, Material Design, widgets, threads and ANR, dialogs, notifications and Espresso tests.
Pages 22 to 40 · 20 sections · 23 code listings · 6 diagrams · 17 two-mark and 13 ten-mark questions.
| Density | dpi | 1 dp |
|---|---|---|
| mdpi | 160 | 1 px |
| xhdpi | 320 | 2 px |
| xxhdpi | 480 | 3 px (48 dp = 144 px) |
Quick look: what one dp becomes (from page 25)
- Density
- mdpi
- dpi
- 160
- 1 dp
- 1 px
- Density
- xhdpi
- dpi
- 320
- 1 dp
- 2 px
- Density
- xxhdpi
- dpi
- 480
- 1 dp
- 3 px (48 dp = 144 px)
BCA 318T Unit 3: Background Tasks, Sensors, Location & Maps
Keeping slow work off the main thread, AsyncTaskLoader, JSON over HttpURLConnection, foreground services, progress notifications and AlarmManager, then a shake detector, a compass, Fused Location, Google Maps with a marker and Places Autocomplete.
Pages 41 to 57 · 14 sections · 17 code listings · 4 diagrams · 16 two-mark and 10 ten-mark questions.
| Type | Clock | Wakes device? |
|---|---|---|
ELAPSED_REALTIME | Since boot | No |
RTC | Wall clock | No |
RTC_WAKEUP | Wall clock | Yes |
Quick look: AlarmManager alarm types (from page 48)
- Type
ELAPSED_REALTIME- Clock
- Since boot
- Wakes device?
- No
- Type
RTC- Clock
- Wall clock
- Wakes device?
- No
- Type
RTC_WAKEUP- Clock
- Wall clock
- Wakes device?
- Yes
BCA 318T Unit 4: Working with Data, Publishing & Common Android APIs
Shared Preferences, settings, SQLite CRUD, a custom Content Provider, Content Resolver and CursorLoader, scoped storage, FileProvider, networking, WebView, Retrofit, Telephony, then release builds, keystore signing, store graphics and Play Console tracks.
Pages 58 to 76 · 18 sections · 19 code listings · 3 diagrams · 17 two-mark and 11 ten-mark questions.
Quick look: saving a login with Shared Preferences (from page 60)
SharedPreferences sp = getSharedPreferences("user_prefs", MODE_PRIVATE);
sp.edit().putString("username", "Riya").apply();
String name = sp.getString("username", "Guest");name is "Riya" after the save and "Guest" on a fresh install.
AsyncTask callbacks and threads in Android: excerpt from page 43 of the BCA 318T notes
Excerpt from page 43
The four steps of an AsyncTask
An AsyncTask is started from the UI thread with execute(params). Android then runs four callback methods in a fixed order, each on a fixed thread. That split is the whole point of the class: the slow work goes to a background thread, and everything that touches the screen stays on the UI thread.
onPreExecute()runs on the UI thread before the work starts. Use it to show a ProgressBar.doInBackground(Params...)runs on a background thread. It is the only compulsory (abstract) method, does the heavy work, returns the Result and must never touch the UI. It may callpublishProgress().onProgressUpdate(Progress...)runs on the UI thread each timepublishProgress()is called, so the progress bar can move.onPostExecute(Result)runs on the UI thread with the value returned bydoInBackground(). Show the result and hide the ProgressBar here.
If the task is stopped with cancel(true), Android calls onCancelled() on the UI thread instead of onPostExecute().
A download task with progress
The class below uses AsyncTask<String, Integer, String>: a URL goes in, whole-number percentages come out as progress, and a text message is the result.
private class DownloadTask extends AsyncTask<String, Integer, String> {
@Override protected void onPreExecute() {
progressBar.setVisibility(View.VISIBLE);
tvStatus.setText("Downloading...");
}
@Override protected String doInBackground(String... urls) {
for (int i = 1; i <= 10; i++) {
if (isCancelled()) return null;
try { Thread.sleep(500); } catch (InterruptedException e) { }
publishProgress(i * 10);
}
return "Downloaded: " + urls[0];
}
@Override protected void onProgressUpdate(Integer... values) {
progressBar.setProgress(values[0]);
}
@Override protected void onPostExecute(String result) {
progressBar.setVisibility(View.GONE);
tvStatus.setText(result);
}
}
new DownloadTask().execute("https://unnatieducations.com/notes.pdf");Rules to remember
Create the task and call execute() on the UI thread, and run each instance only once. Never call the four callbacks yourself; Android calls them. By default tasks run one after another on a single background thread, while executeOnExecutor(THREAD_POOL_EXECUTOR) runs them in parallel.
BCA 318T exam corner: 65 two-mark and 43 ten-mark exam questions by unit
Each unit ends with questions labelled "2 Marks" and "10 Marks", matching the end-term paper.
| Unit | 2 Marks | 10 Marks | Code listings |
|---|---|---|---|
| Unit 1 | 15 | 9 | 14 |
| Unit 2 | 17 | 13 | 23 |
| Unit 3 | 16 | 10 | 17 |
| Unit 4 | 17 | 11 | 19 |
BCA 318T exam questions and code listings per unit
- Unit
- Unit 1
- 2 Marks
- 15
- 10 Marks
- 9
- Code listings
- 14
- Unit
- Unit 2
- 2 Marks
- 17
- 10 Marks
- 13
- Code listings
- 23
- Unit
- Unit 3
- 2 Marks
- 16
- 10 Marks
- 10
- Code listings
- 17
- Unit
- Unit 4
- 2 Marks
- 17
- 10 Marks
- 11
- Code listings
- 19
- Unit 1, 10 Marks: Explain how to receive and broadcast intents using Broadcast Receivers (static and dynamic). Pointer: page 17, the
onReceive()class and the static vs dynamic table. - Unit 2, 2 Marks: Differentiate Toast and Snackbar. Pointer: a Snackbar sits in the app and can carry one action such as UNDO; a Toast has none (page 38).
- Unit 3, 2 Marks: What is the Fused Location Provider? Pointer: it mixes GPS, Wi-Fi and cell data for the best accuracy at low battery cost (page 52).
- Unit 4, 10 Marks: Write a program for insert, update, delete and select using SQLiteOpenHelper. Pointer: the
DBHelperclass on page 63.
The BCA 318T notes list 65 two-mark and 43 ten-mark exam questions across 4 units, plus 73 code listings.
More practice sits in the BCA 318T important questions.
Who writes and checks the BCA 318T Mobile App Development notes?
- Prateek Talwar, author · Founder, Unnati Educations · ACS (ICSI), membership no. 58704, since 15 May 2019 · B.Com, University of Delhi (SOL), 2012 · Profile
- Ritik Rawat, subject reviewer · Senior Full Stack Developer, Unnati Educations · B.Tech · checks the Java, XML and Gradle code · Profile
These GGSIPU BCA Sem 6 Mobile Application Development notes follow the BCA scheme for the 2024-25 batch onwards. The 2026-27 edition marks where Android has moved on from the syllabus names: AsyncTask deprecated in API 30, Loaders in API 28, Android 14 foreground service types and Material 3. Read our editorial policy.
The same team prepares GGSIPU important questions for every course.
Do the BCA 318T notes cover the full GGSIPU syllabus?
Yes. Every topic in the four official BCA 318T units has its own section in the notes; the unit check found no gap.
| Unit | Official topics | In the notes | Status |
|---|---|---|---|
| I | History and types of mobile applications, history of Android, development environment, application anatomy, first application, real device, emulator, Application Context, Activities, Services, Intents, broadcasting Intents, Manifest, Intent Filter, Permissions | Sections 1 to 18, pages 5 to 20 | Covered |
| II | Adaptive UI, input controls, menus, screen navigation, Recycler View, drawables, themes and styles, Fragment Life Cycle, Material Design, App Widgets, processes and threads, views and layouts, input events, settings, dialogs, notifications, toasts, testing the UI | Sections 1 to 20, pages 23 to 39 | Covered |
| III | AsyncTask, AsyncTask Loader, connecting to the Internet, broadcast receivers, services, notifications, alarm managers, motion and position sensors, location services, Google Maps API, Google Places API | Sections 1 to 14, pages 42 to 55 | Covered |
| IV | Shared Preferences, App Setting, SQLite, Content Providers, Content Resolver, Loader, publishing and signing, graphics, Android Market, data, networking, web and telephony APIs, deploying the app | Sections 1 to 18, pages 59 to 74 | Covered |
Official BCA 318T syllabus mapped to the notes
- Unit
- I
- Official topics
- History and types of mobile applications, history of Android, development environment, application anatomy, first application, real device, emulator, Application Context, Activities, Services, Intents, broadcasting Intents, Manifest, Intent Filter, Permissions
- In the notes
- Sections 1 to 18, pages 5 to 20
- Status
- Covered
- Unit
- II
- Official topics
- Adaptive UI, input controls, menus, screen navigation, Recycler View, drawables, themes and styles, Fragment Life Cycle, Material Design, App Widgets, processes and threads, views and layouts, input events, settings, dialogs, notifications, toasts, testing the UI
- In the notes
- Sections 1 to 20, pages 23 to 39
- Status
- Covered
- Unit
- III
- Official topics
- AsyncTask, AsyncTask Loader, connecting to the Internet, broadcast receivers, services, notifications, alarm managers, motion and position sensors, location services, Google Maps API, Google Places API
- In the notes
- Sections 1 to 14, pages 42 to 55
- Status
- Covered
- Unit
- IV
- Official topics
- Shared Preferences, App Setting, SQLite, Content Providers, Content Resolver, Loader, publishing and signing, graphics, Android Market, data, networking, web and telephony APIs, deploying the app
- In the notes
- Sections 1 to 18, pages 59 to 74
- Status
- Covered
Official sources: BCA Scheme of Examination & Syllabi, batch 2024-25 onwards (2026) and the BCA scheme of examination, w.e.f. 2024-25.
Every course in GGSIPU notes is mapped to its official PDF the same way.
How to write BCA 318T answers: lifecycle diagrams, code-backed ten-mark answers and two-mark comparisons
Two-mark answers need a definition plus one difference or example; ten-mark answers need a diagram or table, method names and short code. The notes' exam tips show what each long answer carries:
- Activity lifecycle (page 15): draw the flow, write all 7 methods with one line each, name the 4 states and the back stack, end with the Logcat demo, and call
super.onXxx()first. - Layouts (page 24): a small box sketch per layout, 3 key attributes each, and one line that ConstraintLayout is the default because it avoids deep nesting.
- Fragment life cycle (page 33): the 11 callbacks from
onAttach()toonDetach(), the flow, and the Activity vs Fragment table. - Maps and Places (page 55): one line on restricting the API key to the package name and SHA-1 fingerprint.
- SQLite (page 64):
?placeholders with selection arguments instead of joined user input, plus transactions for bulk inserts.
Worked example (2 Marks): Differentiate explicit and implicit intents.
An explicit intent names the exact class, for example new Intent(this, SecondActivity.class), and starts components inside your own app. An implicit intent names only an action and data, for example new Intent(Intent.ACTION_VIEW, uri); Android matches it against the intent filters of installed apps.
Two mistakes the notes warn about: hard-coding text in Java instead of strings.xml, and running network or database work on the main thread, which brings an ANR after about 5 seconds. Practise this format on GGSIPU BCA important questions.
BCA 318T and the BCA 318P Mobile Application Development lab, plus other GGSIPU BCA Sem 6 papers
Paired lab: BCA 318P Mobile Application Development lab notes · PCE · 4 practical hours a week · 2 credits · 100 marks.
The official PDF leaves the BCA 318P practical list to the teacher, who notifies it in the first week. The code to rehearse is already here, from intents in Unit 1 to SQLite in Unit 4. These Mobile Application Development notes in English use the same Java and XML you type in the lab.
Taking BCA 318T means skipping the other electives: BCA 312T Data Visualization & Analytics, BCA 314T Deep Learning with Python and BCA 316T Web Security. Everyone takes BCA 302T Distributed systems and Cloud Computing, BCA 304T Machine Learning, BCA 306T Software Project Management and BCA 320 Minor Project.
BCA 318T Mobile App Development notes FAQs
How do I get the full BCA 318T notes?
The full BCA 318T notes come only as a printed book; they are not sold as a PDF. Tap "Get Full Notes" or message 9899436384 on WhatsApp with the reference code, and the team shares order and delivery details there. Before ordering, "View Sample PDF" shows the cover, the index and one page from each unit.
Is BCA 318T compulsory in GGSIPU BCA Semester 6?
No. BCA 318T is one of four Programme Core Electives in Semester 6, alongside BCA 312T, BCA 314T and BCA 316T. A student picks one elective theory paper and its matching lab, so choosing BCA 318T also means taking BCA 318P. Together the pair carries 6 credits: 4 for the theory paper and 2 for the lab.
What is the passing mark for BCA 318T?
BCA 318T is marked out of 100: 40 internal and 60 end-term. The official BCA scheme and syllabus PDFs do not print a separate pass percentage for this paper, so we do not quote one. End-term minimums, the overall pass rule and re-appear rules come from GGSIPU Ordinance 11, which the BCA scheme refers to. Check the current ordinance on ipu.ac.in.
Which BCA 318T unit has the most code?
Unit 2, with 23 code listings across pages 22 to 40: layout XML, a registration form, three menu types, a RecyclerView adapter, a selector drawable, a theme file, a Fragment transaction, a widget, settings, dialogs, a notification and an Espresso test. Unit 4 comes next with 19 listings, led by the full SQLite helper class and a custom Content Provider.
Do the BCA 318T notes use Java or Kotlin?
Java, with XML for layouts and resources and Gradle for build settings. The BCA 318T syllabus lists Java Programming as a pre-requisite, so every program in the notes is in Java. Kotlin appears only in short mentions, such as coroutines as a modern option for background work and Kotlin Multiplatform as a cross-platform framework in Unit 1.
Why do the BCA 318T notes still teach AsyncTask and Loaders?
Because the official BCA 318T syllabus lists them: AsyncTask and AsyncTask Loader in Unit 3, Loader in Unit 4. The notes teach both topics in full, clearly mark their status (AsyncTask deprecated in API 30, Loaders in API 28) and name what modern Android apps use instead: ExecutorService, ViewModel with LiveData, WorkManager and Kotlin coroutines.
Get the full BCA 318T Mobile Application Development Notes on WhatsApp
76 pages: 70 topic sections, 73 code listings, 20 diagrams and 108 exam questions. Printed book in English only, not a PDF; order and delivery details on WhatsApp.
Order the BCA 318T notes book on WhatsApp (4 units, 76 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.