Why Dependency injection (GetIt) in Flutter? - Purpose & Use Cases

The Big Idea

Discover how a simple tool can untangle your Flutter app's messy dependencies!

The Scenario

Imagine building a Flutter app where every screen needs to create and manage its own data helpers and services manually.

You have to pass objects around everywhere, making your code messy and tangled.

The Problem

Manually creating and passing dependencies leads to duplicated code, tight coupling, and hard-to-maintain apps.

It becomes a nightmare to change or test parts of your app because everything depends on everything else.

The Solution

Dependency injection with GetIt lets you register your services once and access them anywhere easily.

This keeps your code clean, modular, and simple to test or update.

Before vs After

✗ Before

final apiService = ApiService();
final userRepo = UserRepository(apiService);

// Pass userRepo to every widget needing it

✓ After

GetIt.I.registerSingleton<ApiService>(ApiService());
GetIt.I.registerSingleton<UserRepository>(UserRepository(GetIt.I<ApiService>()));

// Access anywhere with GetIt.I<UserRepository>()

What It Enables

You can build scalable Flutter apps where dependencies are managed automatically and cleanly.

Real Life Example

In a shopping app, you can register your CartService and ProductService once, then access them from any screen without passing them around.

Key Takeaways

Manual dependency management causes messy, hard-to-change code.

GetIt simplifies access to shared services across your app.

This leads to cleaner, more testable, and maintainable Flutter apps.

Practice

1. What is the main purpose of using GetIt in a Flutter app?

easy

A. To handle user input events

B. To style widgets with custom themes

C. To manage app navigation between screens

D. To provide shared objects to parts of the app without creating them each time

Solution

1. Step 1: Understand Dependency Injection

   Dependency injection means giving parts of your app the objects they need without making them create those objects themselves.

2. Step 2: Role of GetIt

   GetIt is a tool that helps register and provide these shared objects easily in Flutter.

3. Final Answer:

   To provide shared objects to parts of the app without creating them each time -> Option D

4. Quick Check:

   Dependency injection = shared objects without recreation [OK]

Hint: GetIt shares objects so you don't recreate them [OK]

Common Mistakes:

• Confusing GetIt with UI styling tools
• Thinking GetIt manages navigation
• Assuming GetIt handles user input

2. Which of the following is the correct way to register a singleton instance with GetIt?

easy

A. GetIt.instance.registerSingleton(() => MyService());

B. GetIt.instance.registerSingleton(MyService());

C. GetIt.instance.registerFactory(() => MyService());

D. GetIt.instance.registerLazySingleton(MyService());

Solution

1. Step 1: Understand Singleton Registration Syntax

   To register a singleton, you pass an instance directly, not a function.

2. Step 2: Analyze Options

   GetIt.instance.registerSingleton(MyService()); correctly passes an instance: MyService(). GetIt.instance.registerSingleton(() => MyService()); wrongly passes a function. GetIt.instance.registerFactory(() => MyService()); registers a factory, not a singleton. GetIt.instance.registerLazySingleton(MyService()); passes an instance to lazy singleton incorrectly.

3. Final Answer:

   GetIt.instance.registerSingleton(MyService()); -> Option B

4. Quick Check:

   Singleton registration needs instance, not function [OK]

Hint: Singletons get instances, factories get functions [OK]

Common Mistakes:

• Passing a function instead of an instance for singleton
• Confusing registerFactory with registerSingleton
• Using wrong syntax for lazy singleton

3. Given the code below, what will be printed?

final getIt = GetIt.instance;

class Counter {
  int value = 0;
  void increment() => value++;
}

void main() {
  getIt.registerSingleton(Counter());
  final counter1 = getIt<Counter>();
  final counter2 = getIt<Counter>();
  counter1.increment();
  print(counter2.value);
}

medium

A. 1

B. null

C. 0

D. Throws an error

Solution

1. Step 1: Understand Singleton Behavior

   Registering Counter as a singleton means counter1 and counter2 point to the same instance.

2. Step 2: Trace the Code Execution

   Calling counter1.increment() increases value from 0 to 1. Since counter2 is the same instance, counter2.value is 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Singleton shares state, so value = 1 [OK]

Hint: Singleton means one shared instance, so changes reflect everywhere [OK]

Common Mistakes:

• Thinking counter2 is a new instance with value 0
• Assuming increment does not affect shared instance
• Expecting null or error without registration

4. What is wrong with this GetIt registration code?

final getIt = GetIt.instance;

void setup() {
  getIt.registerFactory<MyService>(MyService());
}

medium

A. registerFactory expects a function, not an instance

B. registerFactory cannot be called inside a function

C. MyService must be a singleton, not a factory

D. GetIt.instance should not be assigned to a variable

Solution

1. Step 1: Check registerFactory Syntax

   The registerFactory method expects a function that returns a new instance each time, not an instance itself.

2. Step 2: Identify the Error

   Passing MyService() directly is an instance, not a function. The correct usage is registerFactory(() => MyService()).

3. Final Answer:

   registerFactory expects a function, not an instance -> Option A

4. Quick Check:

   Factories need functions returning new instances [OK]

Hint: Factories need functions, singletons need instances [OK]

Common Mistakes:

• Passing instance instead of function to registerFactory
• Thinking registerFactory only works outside functions
• Confusing singleton and factory registration

5. You want to register a service that should create a new instance every time it is requested. Which GetIt method should you use, and how should you register it?

hard

A. Use registerLazySingleton with a function returning a new instance

B. Use registerSingleton with an instance of the service

C. Use registerFactory with a function returning a new instance

D. Use registerSingleton with a function returning a new instance

Solution

1. Step 1: Understand the Requirement

   The service must create a new instance every time it is requested, so it should not be a singleton.

2. Step 2: Choose Correct GetIt Method

   registerFactory registers a function that returns a new instance on each call, matching the requirement.

3. Step 3: Confirm Registration Syntax

   The correct syntax is registerFactory(() => Service()), passing a function that creates a new instance.

4. Final Answer:

   Use registerFactory with a function returning a new instance -> Option C

5. Quick Check:

   New instance each time = registerFactory with function [OK]

Hint: New instance each time? Use registerFactory with a function [OK]

Common Mistakes:

• Using registerSingleton for new instances
• Passing instance instead of function to registerFactory
• Confusing lazy singleton with factory