Notifications (local) in Flutter - Build, Publish & Deploy

Build & Publish - Notifications (local)

Performance Impact

Local notifications have minimal impact on frame rate and memory because they run outside the main UI thread. They do not affect battery significantly if used sparingly. However, frequent or complex notifications with images or sounds can increase battery use slightly.

Optimization Tips

Schedule notifications efficiently by batching them when possible. Avoid heavy payloads like large images or long sounds. Use lightweight notification content to keep the app responsive. Cancel unnecessary notifications to reduce system load.

App Size and Startup Time

Adding local notification support usually adds a small library (~1-3MB) to your app bundle. This has a minor effect on startup time. Keep notification assets small and minimal to avoid increasing app size.

iOS vs Android Differences

iOS requires user permission to show notifications and supports rich notifications with images and actions. Android also requires permission on newer versions and supports notification channels for grouping. Android allows more customization of notification appearance and behavior.

Store Review Guidelines

• Request notification permission clearly and only when needed.
• Do not spam users with excessive notifications; follow Apple HIG and Google Play policies.
• Ensure notifications respect user privacy and do not collect sensitive data without consent.
• Test notifications on real devices to comply with platform behavior.

Self-Check Question

Your app takes 5 seconds to load this screen. What's likely wrong?

Answer: You might be scheduling or loading notifications synchronously on the main thread, blocking UI rendering. Move notification setup to background tasks or initialize lazily.

Key Result

Local notifications in Flutter add minimal performance overhead but require careful permission handling and lightweight content to maintain smooth UI and comply with store policies.

Practice

1. What is the main purpose of local notifications in a Flutter app?

easy

A. To alert users even when the app is closed or in the background

B. To send messages to a server

C. To update the app's UI instantly

D. To change app theme colors automatically

Solution

1. Step 1: Understand local notifications

   Local notifications are alerts shown to users even if the app is not open or running in the background.

2. Step 2: Compare options

   Options B, C, and D describe other app features unrelated to local notifications.

3. Final Answer:

   To alert users even when the app is closed or in the background -> Option A

4. Quick Check:

   Local notifications alert users outside app use = A [OK]

Hint: Local notifications work when app is not active [OK]

Common Mistakes:

• Confusing local notifications with server messages
• Thinking notifications only work when app is open
• Mixing UI updates with notification purpose

2. Which Flutter plugin is commonly used to show local notifications?

easy

A. firebase_messaging

B. flutter_local_notifications

C. provider

D. http

Solution

1. Step 1: Identify notification plugins

   The plugin flutter_local_notifications is designed for local notifications in Flutter apps.

2. Step 2: Eliminate unrelated plugins

   http is for network calls, provider for state management, firebase_messaging for push notifications, not local.

3. Final Answer:

   flutter_local_notifications -> Option B

4. Quick Check:

   Local notifications plugin = flutter_local_notifications [OK]

Hint: Local notifications use flutter_local_notifications plugin [OK]

Common Mistakes:

• Choosing firebase_messaging which is for push, not local
• Confusing state management plugins with notification plugins
• Selecting network plugins by mistake

3. What will happen if you call show() on a local notification without initializing the plugin first?

medium

A. The notification will show normally

B. The notification will show only on Android devices

C. The notification will be delayed by 5 seconds

D. The app will crash or throw an error

Solution

1. Step 1: Understand plugin initialization

   Local notification plugins require initialization before use to set up channels and permissions.

2. Step 2: Consequence of missing initialization

   Calling show() without initialization causes runtime errors or crashes because the plugin is not ready.

3. Final Answer:

   The app will crash or throw an error -> Option D

4. Quick Check:

   Uninitialized plugin causes error/crash = B [OK]

Hint: Always initialize plugin before showing notifications [OK]

Common Mistakes:

• Assuming notifications show without initialization
• Thinking notifications delay automatically
• Believing platform-specific behavior without init

4. Given this code snippet, what is the error?

final FlutterLocalNotificationsPlugin flutterLocalNotificationsPlugin = FlutterLocalNotificationsPlugin();

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  // Missing initialization here
  await flutterLocalNotificationsPlugin.show(
    0,
    'Hello',
    'Welcome to Flutter',
    NotificationDetails(
      android: AndroidNotificationDetails('channelId', 'channelName')
    )
  );
}

medium

A. WidgetsFlutterBinding.ensureInitialized() is unnecessary

B. NotificationDetails is not imported

C. Missing call to initialize() before show()

D. Notification ID cannot be zero

Solution

1. Step 1: Check plugin initialization

   The code calls show() without calling initialize() on flutterLocalNotificationsPlugin first.

2. Step 2: Understand consequences

   Without initialize(), the plugin is not ready, causing errors when showing notifications.

3. Final Answer:

   Missing call to initialize() before show() -> Option C

4. Quick Check:

   Initialize plugin before show() = C [OK]

Hint: Always initialize plugin before calling show() [OK]

Common Mistakes:

• Ignoring the need to initialize plugin
• Thinking zero ID is invalid
• Assuming ensureInitialized() replaces plugin init

5. You want to create a local notification channel with high importance and priority on Android. Which code snippet correctly sets this up?

hard

A. AndroidNotificationDetails('channelId', 'channelName', importance: Importance.high, priority: Priority.high)

B. AndroidNotificationDetails('channelId', 'channelName', importance: Importance.low, priority: Priority.min)

C. AndroidNotificationDetails('channelId', 'channelName', importance: Importance.defaultImportance, priority: Priority.defaultPriority)

D. AndroidNotificationDetails('channelId', 'channelName')

Solution

1. Step 1: Understand importance and priority

   High importance and priority make notifications more visible and urgent on Android.

2. Step 2: Check code options

   AndroidNotificationDetails('channelId', 'channelName', importance: Importance.high, priority: Priority.high) sets importance and priority to high, matching the requirement. Others set low, default, or omit these settings.

3. Final Answer:

   AndroidNotificationDetails('channelId', 'channelName', importance: Importance.high, priority: Priority.high) -> Option A

4. Quick Check:

   High importance and priority = AndroidNotificationDetails('channelId', 'channelName', importance: Importance.high, priority: Priority.high) [OK]

Hint: Use Importance.high and Priority.high for urgent notifications [OK]

Common Mistakes:

• Leaving importance and priority at default
• Using low importance for urgent alerts
• Omitting priority setting