How Applications Store Information

An application is the software a person uses.

A website, mobile app, desktop program, game, checkout system, school portal, and banking app are all applications.

Applications use databases when they need to remember information after a screen changes, a program closes, or a device restarts.

With SQLite, that remembered information usually lives in a single ordinary database file on disk.

The basic app and database loop

Most application database work follows a simple loop:

1. A person does something in the application.
2. The application sends a request to SQLite.
3. SQLite reads or changes stored data.
4. SQLite returns a result.
5. The application shows something to the person.

This loop happens constantly.

When you log in, send a message, like a photo, buy a ticket, or mark a task complete, an application is usually reading from or writing to a database.

Saving information

Suppose you write a new task in a to-do app and click Save.

The application may collect facts like this:

title: Buy milk
done: 0
due_date: 2026-04-15

SQLite stores those facts as a row in a table.

Later, the app can ask for your unfinished tasks and show them again.

Reading information

Reading means asking the database for facts that already exist.

Examples:

• A music app asks for your playlists.
• A bank app asks for your account balance.
• A store asks for products in stock.
• A school portal asks for your grades.

The application does not need to know every detail of how SQLite stores information inside the file. It asks a structured question and receives structured results.

Changing information

Information changes because the real world changes.

Examples:

• A package changes from "processing" to "shipped."
• A user changes their email address.
• A student submits an assignment.
• A payment changes from "pending" to "paid."

The application sends the change to SQLite so future screens and future sessions see the updated fact.

The database is not the screen

Beginners sometimes imagine the database as the thing the user sees.

Usually, it is not.

The application owns the buttons, forms, pages, images, and interactions.

The database owns the stored facts.

A database may be invisible to the user, but it is often the reason the application can remember anything.

How rows become a file

A database does not store information as one giant paragraph.

In a relational database, information is organized into tables, rows, and columns.

tasks

id | title        | done | due_date
-- | ------------ | ---- | ----------
1  | Buy milk     | 0    | 2026-04-15
2  | Submit form  | 1    | 2026-04-10

A table stores one kind of thing. A row is one record. A column is one piece of information every row is expected to have.

SQLite then stores the database on disk in one ordinary file.

You usually do not edit this file by hand. SQLite manages it for you.

A database request is usually small

Applications rarely ask for "everything."

Instead, they ask for what one screen or task needs.

Examples:

• "Give me the 10 newest messages."
• "Save this new shipping address."
• "Mark this invoice as paid."
• "Find products under $50."

This is one reason databases matter: they help applications work with the relevant slice of information.

The main idea

Applications use databases as dependable memory.

The user clicks, types, searches, or pays. The application turns that action into a database request. SQLite reads or changes rows in a database file and sends a result back.

Check your understanding