#1 India's Top IT Training Institute

×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →

Android Basics · Beginner Glossary

Android Development Terms for Beginners

A complete beginner's guide to Android development terms — activities, fragments, intents, layouts, and more, explained simply so you can read the docs and start building.

Tracks
Android Glossary · Live Interactive
Category
—
Topic group
Key Term
—
Headline concept
What It Does
—
Practical role
Core → UI → Advanced → Proficient
Click a category to see its key terms. Master each layer to read Android docs with confidence and build real apps.

Home / Tutorials / Android Guides / Android Development Terms for Beginners

Android Basics · Beginner Glossary

Android Development Terms for Beginners

CORE UI ADVANCED PROFICIENT Core Concepts Activities & Intents Foundational Foundation UI & Layout XML & Views Rendering Build Advanced Fragments & ViewModels Modern Android Launch Proficient Build Real Apps Android Developer Success
An Android learning path — Core: Activities & Intents, UI: XML & Views, Advanced: Fragments & ViewModels, then build real apps.

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:

  1. Core concepts — Activity, Fragment, Intent, Context.
  2. UI & layout — View, ViewGroup, XML layouts, RecyclerView.
  3. Advanced terms — ViewModel, LiveData, Gradle, Coroutines.
  4. Glossary tables — quick reference.
  5. 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.
core-terms.md
Key insight: Activity, Fragment, Intent, and Context appear in almost every Android codebase. Learn these four first — everything else builds on them.

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.
ui-terms.md
Key insight: UI terms describe what the user sees. Learn View and ViewGroup first, then XML layouts and RecyclerView.

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.
advanced-terms.md
Key insight: Advanced terms describe modern Android practice. Understand ViewModel, LiveData, Coroutines, and Gradle before building larger apps.

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).
glossary-tables.md

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.
Pro tip: Depth beats breadth. Learn 5 terms per week and write a snippet for each — you will retain far more than skimming a long glossary.

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 / 5

Pick 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.

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 ₹24,000
  • Complete Android glossary
  • Hands-on projects
  • Mock interviews
  • Weekday & weekend batches