Repository pattern in Flutter - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Repository pattern in Flutter?

The Repository pattern is a way to organize code by separating data access logic from the rest of the app. It acts like a middleman between data sources (like APIs or databases) and the app's UI, making the code cleaner and easier to manage.

beginner

Why use the Repository pattern in mobile apps?

Using the Repository pattern helps keep your app organized, makes testing easier, and allows you to change data sources without changing the UI code. It helps your app stay flexible and maintainable.

intermediate

In the Repository pattern, what does the repository class usually do?

The repository class provides methods to get, add, update, or delete data. It hides where the data comes from, so the rest of the app doesn't need to know if data is from the internet, a database, or somewhere else.

intermediate

How does the Repository pattern improve testing in Flutter apps?

Because the repository hides data sources, you can replace it with fake or mock repositories during testing. This way, you can test your app's logic without needing real data or internet connection.

beginner

Give a simple example of a repository method in Flutter.

Example: A method like Future<List<User>> fetchUsers() in a UserRepository class that gets a list of users from an API or database, hiding the details from the rest of the app.

What is the main role of a repository in Flutter apps?

A To handle data access and hide data sources

B To manage app navigation

C To style widgets

D To manage UI layout

The repository handles data access and hides where data comes from, keeping UI code clean.

Which benefit does the Repository pattern NOT provide?

A Better UI animations

B Cleaner code organization

C Easier testing

D Flexibility to change data sources

The Repository pattern does not affect UI animations; it focuses on data management.

How does the Repository pattern help with testing?

A By improving network speed

B By making UI components faster

C By reducing app size

D By allowing replacement with mock data sources

Repositories can be replaced with mock versions to test app logic without real data.

In Flutter, where would you typically call repository methods?

A Inside UI widgets directly

B Inside business logic or state management classes

C In the main() function only

D In the pubspec.yaml file

Repository methods are called in business logic or state management to keep UI clean.

Which of these is a typical repository method signature?

A int calculateSum(int a, int b)

B void buildUI()

C Future<List<Item>> getItems()

D String formatText(String text)

Repository methods often return Future data like lists fetched asynchronously.

Explain the Repository pattern and why it is useful in Flutter app development.

Think about how your app gets data and how you can keep that separate from the screen code.

Describe how you would implement a simple repository for fetching user data in Flutter.

Imagine you want to get users from an API but don’t want your UI to know about the API.

Practice

1. What is the main purpose of the Repository pattern in Flutter app development?

easy

A. To manage app navigation

B. To create UI widgets faster

C. To handle user input events

D. To separate data access logic from UI code

Solution

1. Step 1: Understand the role of Repository pattern

   The Repository pattern is designed to separate data access from the UI, so the UI does not directly handle data fetching or storage.

2. Step 2: Identify the correct purpose

   Among the options, only separating data access logic from UI code matches the Repository pattern's purpose.

3. Final Answer:

   To separate data access logic from UI code -> Option D

4. Quick Check:

   Repository pattern = separate data access from UI [OK]

Hint: Repository = data access separated from UI [OK]

Common Mistakes:

• Confusing Repository with UI widget creation
• Thinking Repository manages navigation
• Assuming Repository handles user input

2. Which of the following is the correct way to declare a repository interface in Dart for fetching a list of users?

easy

A. abstract class UserRepository { Future fetchUsers(); }

B. class UserRepository { List<User> fetchUsers() async {} }

C. interface UserRepository { List<User> fetchUsers(); }

D. abstract UserRepository { Future fetchUsers() List<User>; }

Solution

1. Step 1: Recall Dart syntax for abstract classes

   In Dart, interfaces are created using abstract classes with method signatures but no bodies.

2. Step 2: Check method signature for async fetching

   The method should return a Future to indicate asynchronous fetching.

3. Final Answer:

   abstract class UserRepository { Future fetchUsers(); } -> Option A

4. Quick Check:

   Dart interface = abstract class with Future method [OK]

Hint: Use abstract class with Future return for async methods [OK]

Common Mistakes:

• Using 'interface' keyword which Dart doesn't have
• Missing Future for async methods
• Incorrect method syntax or return type

3. Given this repository implementation snippet, what will be printed?

class UserRepositoryImpl implements UserRepository {
  @override
  Future fetchUsers() async {
    return ['Alice', 'Bob'];
  }
}

void main() async {
  var repo = UserRepositoryImpl();
  var users = await repo.fetchUsers();
  print(users.length);
}

medium

A. 2

B. ['Alice', 'Bob']

C. Error: fetchUsers is not async

D. 0

Solution

1. Step 1: Understand the fetchUsers method

   The method returns a Future with a list containing two strings: 'Alice' and 'Bob'.

2. Step 2: Analyze the main function output

   The code awaits the fetchUsers call, then prints the length of the list, which is 2.

3. Final Answer:

   2 -> Option A

4. Quick Check:

   List length = 2 [OK]

Hint: Count list items returned by async method [OK]

Common Mistakes:

• Confusing printed list with its length
• Ignoring async/await causing errors
• Assuming fetchUsers returns empty list

4. Identify the error in this repository implementation:

class UserRepositoryImpl implements UserRepository {
  Future fetchUsers() {
    return ['Alice', 'Bob'];
  }
}

medium

A. No error, code is correct

B. fetchUsers must return Future, but returns List<String>

C. UserRepositoryImpl should not implement UserRepository

D. Missing async keyword before fetchUsers method

Solution

1. Step 1: Check return type of fetchUsers

   The method signature says it returns Future, but the returned value is a List<String> without wrapping in Future.

2. Step 2: Identify type mismatch and missing Future

   Returning a plain list instead of a Future causes a type mismatch error.

3. Final Answer:

   fetchUsers must return Future, but returns List<String> -> Option B

4. Quick Check:

   Return type mismatch = fetchUsers must return Future, but returns List<String> [OK]

Hint: Check method return matches declared Future type [OK]

Common Mistakes:

• Forgetting to wrap return value in Future
• Ignoring type mismatch between User and String
• Assuming async keyword is always required

5. You want to combine data from a local database and a remote API in your repository. Which approach best follows the Repository pattern principles?

hard

A. Use only remote API and ignore local DB to simplify code

B. Let UI call local DB and remote API separately and merge data itself

C. Create a repository that fetches from local DB first, then updates from remote API, exposing a single method to UI

D. Create two separate repositories and let UI decide which to use

Solution

1. Step 1: Understand Repository pattern goal

   The pattern centralizes data access, hiding multiple sources behind one interface.

2. Step 2: Evaluate options for combining data sources

   Create a repository that fetches from local DB first, then updates from remote API, exposing a single method to UI combines local and remote data inside one repository method, exposing a simple interface to UI, which matches the pattern.

3. Step 3: Reject options that expose data sources to UI

   Options B and D let UI handle data sources, breaking separation. Use only remote API and ignore local DB to simplify code ignores local data, losing benefits.

4. Final Answer:

   Create a repository that fetches from local DB first, then updates from remote API, exposing a single method to UI -> Option C

5. Quick Check:

   Repository hides multiple sources behind one interface [OK]

Hint: Repository hides data sources, exposes one method to UI [OK]

Common Mistakes:

• Letting UI handle multiple data sources
• Ignoring local cache benefits
• Splitting data sources into separate repositories without abstraction