The Repository Pattern
Mediate between data sources cleanly.
The Repository Pattern is a free Jetpack Compose Academy lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Jetpack Compose Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Hide the Data Details
Your ViewModel should not know about DAOs or networks. A repository hides those details behind a clean, simple interface.
A Single Doorway to Data
The repository is the one place the rest of the app asks for data, whether it comes from Room, the network, or memory.
Wrap the DAO
Give the repository the DAO and let it expose friendly methods. Callers see notes, not SQL queries.
class NoteRepository(private val dao: NoteDao) {
val notes = dao.observeAll()
}Expose Actions, Not Tables
Add purposeful functions like addNote. The name says what happens; the storage mechanism stays hidden inside.
suspend fun addNote(text: String) = dao.insert(Note(text = text))Swap Sources Freely
Because callers depend on the repository, you can switch from Room to a fake or a remote API without touching the ViewModel.
Easier to Test
Tests can pass a fake repository to the ViewModel, so you verify logic without a real database on disk. ✅
class FakeRepo : NoteRepository { /* in-memory */ }Inject the Repository
The ViewModel receives the repository through its constructor, never creating it directly. That keeps dependencies explicit.
class NoteViewModel(private val repo: NoteRepository) : ViewModel()Combine Multiple Sources
A repository can merge cache and network, deciding what to return. The UI just asks once and stays unaware of the plumbing.
Pass Flows Straight Through
For reactive data the repository can simply forward the DAO Flow, adding transformations only when the app actually needs them.
val notes: Flow<List<Note>> = dao.observeAll()One Repository per Domain
Keep repositories focused: one for notes, one for users. Each owns a single area of data and its sources.
Clean Layers, Clear Roles
UI shows data, ViewModel holds state, repository fetches it, Room stores it. Each layer has one job and stays replaceable.
Quick Check
What is the main job of a repository in this architecture?
Recap: A Clean Middle Layer
You put a repository between the ViewModel and your data, exposing actions and Flows while hiding the source. Next you will make it work offline first.
Frequently asked questions
Is the “The Repository Pattern” lesson free?
Yes — the full text of “The Repository Pattern” is free to read here on the web, and the Jetpack Compose Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Jetpack Compose Academy course, upgrade to CoddyKit PRO.
What will I learn in “The Repository Pattern”?
Mediate between data sources cleanly. You practise Jetpack Compose Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Jetpack Compose Academy?
No prior experience is required. Jetpack Compose Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “The Repository Pattern” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Jetpack Compose Academy lesson?
Yes. Every Jetpack Compose Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.