Repository pattern in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main purpose of the Repository pattern in Flutter?

Choose the best explanation for why developers use the Repository pattern in Flutter apps.

A To separate data access logic from UI code, making the app easier to maintain and test.

B To directly connect UI widgets to the database without any middle layer.

C To combine all app logic into one class for faster development.

D To replace Flutter's built-in state management with a new system.

💡 Hint

Think about how to keep your UI code clean and easy to change.

The Repository pattern acts as a middleman between data sources and UI, helping keep code organized and testable.

❓ ui_behavior

intermediate

How does the Repository pattern affect UI updates in Flutter?

If you use a Repository to fetch data, what happens when the data changes?

A The UI automatically updates without any notification from the Repository.

B The UI never updates because the Repository blocks changes.

C The Repository directly changes UI widgets without rebuilding.

D The Repository notifies the UI, which then rebuilds to show updated data.

💡 Hint

Think about how Flutter knows when to redraw widgets.

Repositories usually notify listeners or use streams so UI can rebuild with fresh data.

❓ lifecycle

advanced

When should you dispose resources in a Repository in Flutter?

Consider a Repository that uses streams to fetch data. When is the best time to close these streams?

A Immediately after creating the Repository, before any data is fetched.

B Never, streams stay open for the app's entire lifetime.

C When the Repository is no longer needed, typically when the app or feature is closed.

D Only when the UI widget using the Repository is disposed, regardless of Repository lifecycle.

💡 Hint

Think about cleaning up to avoid memory leaks.

Closing streams when the Repository is disposed prevents resource leaks and unexpected behavior.

❓ navigation

advanced

How does the Repository pattern help with navigation decisions in Flutter apps?

If your app needs to decide which screen to show based on user data from a Repository, how should this be handled?

A The Repository directly calls Navigator methods to change screens.

B The UI listens to the Repository and navigates when data changes indicate a new screen is needed.

C Navigation logic is hardcoded in the UI without consulting the Repository.

D The Repository blocks navigation until the user manually refreshes the app.

💡 Hint

Think about separation of concerns between data and UI.

UI listens to Repository data changes and decides navigation, keeping Repository focused on data only.

🔧 Debug

expert

What error will this Flutter Repository code cause?

Consider this Dart code snippet for a Repository: class UserRepository { StreamController _controller = StreamController(); Stream get userStream => _controller.stream; void fetchUser() { _controller.add('User data'); } void dispose() { // Missing _controller.close() } } What problem will happen if dispose() is called without closing _controller?

A Memory leak and possible StreamSubscription errors because the stream is not closed.

B No problem; streams do not need to be closed in Dart.

C The app will crash immediately when fetchUser() is called.

D The UI will never receive any data from the stream.

💡 Hint

Think about resource cleanup for streams.

Not closing StreamControllers causes memory leaks and can cause errors when listeners remain active.

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