Android Basics · Beginner Glossary
Android Development Terms for Beginners
Quick summary — Android development terms
Read the docs without getting lost. This guide explains the everyday Android vocabulary — from Activity and Fragment to Intent, Gradle, and ViewModel — in plain language with what each term actually does.
In this guide you will learn:
- Core concepts — Activity, Fragment, Intent, Context.
- UI & layout — View, ViewGroup, XML layouts, RecyclerView.
- Advanced terms — ViewModel, LiveData, Gradle, Coroutines.
- Glossary tables — quick reference.
- Learning tips — how to go from terms to code.
SECTION 01Core Concepts: Activity, Fragment, Intent
These are the foundation terms you will see in every Android tutorial. Here is the breakdown:
| Category | Term | What It Means | Why It Matters |
|---|---|---|---|
| Core | Activity | A single screen with a user interface | The entry point of most apps |
| Core | Fragment | A reusable portion of UI inside an Activity | Build flexible, multi-pane screens |
| Core | Intent | A message that requests an action from another component | Navigate between screens and apps |
| Core | Context | Handle to app environment and resources | Needed to access resources and start components |
Core Android Terms:
Activity
- A single screen with UI.
- Has a lifecycle: onCreate, onStart, onResume.
- Declared in AndroidManifest.xml.
Fragment
- A reusable piece of UI inside an Activity.
- Has its own lifecycle.
- Ideal for tablets and modular screens.
Intent
- Explicit: targets a specific component (e.g., open DetailActivity).
- Implicit: describes an action (e.g., open a URL).
Context
- Gives access to resources, databases, and system services.
- Activity, Service, and Application all extend Context.
Activity Lifecycle Quick Notes:
onCreate() — UI initialized once.
onStart() — Activity becomes visible.
onResume() — Activity is in the foreground.
onPause() — Another activity comes in front.
onStop() — Activity no longer visible.
onDestroy() — Activity is destroyed.
Remember:
- Avoid heavy work in onCreate.
- Release resources in onStop/onDestroy.
- Use ViewModel to survive configuration changes.
SECTION 02UI & Layout: View, ViewGroup, XML
These terms describe how Android draws and arranges what the user sees. Here is the breakdown:
| Category | Term | What It Means | Why It Matters |
|---|---|---|---|
| UI | View | A basic UI element (button, text, image) | The building block of every screen |
| UI | ViewGroup | A container that holds and arranges other Views | Defines the screen's layout structure |
| UI | XML Layout | Declarative UI definition in an XML file | Separates UI from logic |
| UI | RecyclerView | Efficient list renderer for large data sets | Standard for scrollable lists |
UI & Layout Terms:
View
- The base class for all UI widgets.
- Examples: TextView, Button, ImageView.
ViewGroup
- Extends View and contains other Views.
- Examples: LinearLayout, ConstraintLayout, FrameLayout.
XML Layout
- Describes the UI in res/layout/*.xml.
- Easily previewed in Android Studio.
RecyclerView
- Reuses views as you scroll.
- Uses an Adapter to bind data.
Layout Choice Notes:
LinearLayout
- Stacks children horizontally or vertically.
- Simple and predictable.
ConstraintLayout
- Positions views relative to each other.
- Best for complex, flat hierarchies.
FrameLayout
- Stacks children on top of each other.
- Useful for overlays.
Guidelines:
- Keep layouts shallow.
- Avoid deep nesting for performance.
- Use ConstraintLayout for complex screens.
SECTION 03Advanced Terms: ViewModel, Gradle, Coroutines
These terms appear as you move into modern Android development. Here is the breakdown:
| Category | Term | What It Means | Why It Matters |
|---|---|---|---|
| Advanced | ViewModel | Stores UI data across configuration changes | Survives rotation; keeps state clean |
| Advanced | LiveData | Observable, lifecycle-aware data holder | Updates the UI safely |
| Advanced | Gradle | Build system for dependencies and tasks | Manages libraries and builds |
| Advanced | Coroutines | Kotlin's way to write asynchronous code | Handles background work without blocking UI |
Advanced Android Terms:
ViewModel
- Holds UI-related data.
- Survives configuration changes.
- Part of Android Jetpack.
LiveData
- Lifecycle-aware observable.
- Automatically updates active observers.
- Prevents memory leaks.
Coroutines
- Suspend functions run without blocking threads.
- Use viewModelScope for UI work.
- Simplifies async code.
Gradle
- Declares dependencies in build.gradle.
- Runs tasks: build, install, test.
- Supports flavors and build types.
Gradle Quick Notes:
dependencies {
implementation "androidx.core:core-ktx:..."
implementation "androidx.appcompat:appcompat:..."
implementation "androidx.lifecycle:lifecycle-viewmodel-ktx:..."
}
Tasks:
./gradlew assembleDebug
./gradlew installDebug
./gradlew test
Tips:
- Keep dependency versions aligned.
- Use Gradle version catalogs.
- Sync often in Android Studio.
SECTION 04Glossary reference tables
Use these reference tables as a quick glossary:
Core Glossary:
Activity — A single screen with UI.
Fragment — Reusable UI inside an Activity.
Intent — Message to trigger an action.
Context — Access to app environment.
Manifest — Declares components and permissions.
APK — Installable Android package.
AVD — Android Virtual Device (emulator).
UI Glossary:
View — Basic UI element.
ViewGroup — Container of Views.
XML Layout — Declarative UI file.
RecyclerView — Efficient scrollable list.
ConstraintLayout — Flexible positioning layout.
Adapter — Binds data to list items.
Drawable — Image or shape resource.
Advanced Glossary:
ViewModel — UI data across config changes.
LiveData — Observable, lifecycle-aware data.
Coroutines — Kotlin async tool.
Gradle — Build system.
Room — Local database library.
Retrofit — HTTP client library.
Compose — Declarative UI toolkit.
SECTION 05Learning tips
Here are tips to go from terms to real Android code:
- Build a tiny app first — a counter or note app exercises Activity, View, and Intent.
- Read the official docs — developer.android.com uses this exact vocabulary.
- Keep a term journal — write each new term and one sentence on what it does.
- Use Android Studio actively — autocompletion teaches class names and packages.
- Pair terms with code — for each term, find a 5-line snippet that uses it.
SECTION 06Interview Q&A — Android terms
Q1What is the difference between an Activity and a Fragment?
An Activity is a screen; a Fragment is a reusable portion of a screen. Fragments live inside an Activity, can be reused across screens, and have their own lifecycle.
Q2What is an Intent?
An Intent is a message object that describes an action. Explicit intents target a specific component; implicit intents describe an action for the system to resolve.
Q3Why use a ViewModel?
A ViewModel survives configuration changes such as rotation. It keeps UI data separate from Activities and Fragments, which makes code cleaner and avoids losing state.
Q4What does Gradle do?
Gradle is the build system. It manages dependencies, compiles code, packages APKs, and runs tasks. Most project configuration lives in build.gradle files.
Q5What are coroutines used for?
Coroutines make asynchronous code look synchronous. They run background work without blocking the UI thread and are the recommended way to handle async tasks in Kotlin.
SECTION 07Test yourself — Android terms quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
What is the most important Android term to learn first?
Start with Activity, Fragment, Intent, and Context. Almost every other concept builds on these four.
Do I need to know Kotlin before learning these terms?
Basic Kotlin helps, but you can learn the terms in parallel. Start with Kotlin syntax and then apply each term to a small project.
What is the difference between a View and a ViewGroup?
A View is a single UI element such as a button. A ViewGroup is a container that holds and arranges Views. ViewGroup extends View.
Should I learn Jetpack Compose or XML layouts first?
Learn XML layouts first to understand the View system, then move to Jetpack Compose for modern declarative UI.
How much time do I need to become comfortable with these terms?
With 5-6 hours per week, you can understand the core terms in a few weeks. Build at least one small app per phase to reinforce them.
SECTION 09Related reads
Classroom & online · Noida
Your Android journey starts now
Our Android Development Training Course is designed to help you master Android basics — terms, UI, and real apps that get you job-ready.
₹15,500 · full programme- Complete Android glossary
- Hands-on projects
- Mock interviews
- Weekday & weekend batches