An application's home screen presence is prime real estate. Giving users the option to customize their app icon manually creates a delightful sense of personalization. Simultaneously, having the power to change app icons remotely allows you to ship global thematic shifts - like a festive holiday theme, a dark mode rebranding, or temporary promotional campaign artwork - without pushing a new build to the App Store or Google Play Store.
In this deep-dive guide, we will implement a dual-mode dynamic icon framework in Flutter without relying on buggy or outdated third-party packages. We will build our own MethodChannels using Kotlin and Swift to support two core features:
- Manual Selection: Letting the user pick their preference inside an settings UI menu.
- Over-the-Air Updates: Overriding or syncing the icon automatically using Firebase Remote Config.
Architectural Deep Dive
Before writing code, it is important to understand how the underlying platform behaviors differ. Flutter operates on a single execution context, meaning we must use platform channels to trigger native operating system APIs.
Android: Component Aliases
Android handles launcher icons statically via the AndroidManifest.xml. To circumvent this limitation, we declare multiple <activity-alias> tags that all point to the primary MainActivity. By toggling the enablement state of these aliases via the native PackageManager, the device home screen refreshes to reflect the icon linked to the active alias.
⚠️ Android Side Effect: Enabling or disabling an activity alias clears the recent apps stack and briefly kills the background application state to remap the launcher profile.
iOS: Alternate Icons API
Apple provides an explicit native framework via UIApplication.shared.setAlternateIconName(). Unlike standard graphic bundles, alternative icon resources cannot be included in a compiled asset catalog (Assets.xcassets). Instead, they must be bundled into the root app directory as loose files and mapped manually inside the project's properties dictionary (Info.plist).
Step 1: Building the Native Infrastructure
1. Flutter MethodChannel Connection
Create a clean utility class in your Dart project to establish the native system communication pipeline.
import 'package:flutter/services.dart';
class DynamicIconService {
static const MethodChannel _channel = MethodChannel('com.dynamicicon.app/dynamic_icon');
/// Requests the native OS platform layer to swap the active launcher asset icon profile.
static Future<void> changeIcon(String iconName) async {
try {
await _channel.invokeMethod('setIcon', {'iconName': iconName});
} on PlatformException catch (e) {
print("Failed to change application launcher profile: '${e.message}'.");
}
}
}
2. Android Integration (AndroidManifest.xml & Kotlin)
First, add your alternative graphic assets directly to your resource directories:
android/app/src/main/res/mipmap-hdpi/ic_launcher_dark.pngandroid/app/src/main/res/mipmap-hdpi/ic_launcher_festive.png
Next, modify android/app/src/main/AndroidManifest.xml. Set the root .MainActivity property android:enabled to false. We will delegate all initial system hooks to our aliases.
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
<application
android:label="Dynamic App"
android:name="${applicationName}">
<!-- Base Target Activity Framework (Deactivated) -->
<activity
android:name=".MainActivity"
android:exported="true"
android:enabled="false"
android:launchMode="singleTop"
android:theme="@style/LaunchTheme">
<meta-data
android:name="io.flutter.embedding.android.NormalTheme"
android:resource="@style/NormalTheme" />
</activity>
<!-- Default Application Icon Alias -->
<activity-alias
android:name=".DefaultIcon"
android:enabled="true"
android:exported="true"
android:icon="@mipmap/ic_launcher"
android:targetActivity=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
</activity-alias>
<!-- Dark Variant Icon Alias -->
<activity-alias
android:name=".DarkIcon"
android:enabled="false"
android:exported="true"
android:icon="@mipmap/ic_launcher_dark"
android:targetActivity=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
</activity-alias>
<!-- Festive Variant Icon Alias -->
<activity-alias
android:name=".FestiveIcon"
android:enabled="false"
android:exported="true"
android:icon="@mipmap/ic_launcher_festive"
android:targetActivity=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
</activity-alias>
</application>
</manifest>
Open your MainActivity.kt file to receive channel methods and trigger the state switch loop:
package com.dynamicicon.app
import android.content.ComponentName
import android.content.pm.PackageManager
import io.flutter.embedding.android.FlutterActivity
import io.flutter.embedding.engine.FlutterEngine
import io.flutter.plugin.common.MethodChannel
class MainActivity: FlutterActivity() {
private val CHANNEL = "com.dynamicicon.app/dynamic_icon"
private val packageNamespace = "com.dynamicicon.app"
private val aliasRegistry = listOf("DefaultIcon", "DarkIcon", "FestiveIcon")
override fun configureFlutterEngine(flutterEngine: FlutterEngine) {
super.configureFlutterEngine(flutterEngine)
MethodChannel(flutterEngine.dartExecutor.binaryMessenger, CHANNEL).setMethodCallHandler { call, result ->
if (call.method == "setIcon") {
val targetIcon = call.argument<String>("iconName")
if (targetIcon != null && aliasRegistry.contains(targetIcon)) {
toggleLauncherComponent(targetIcon)
result.success(null)
} else {
result.error("ALIAS_NOT_FOUND", "The target alias mapping configuration is missing.", null)
}
} else {
result.notImplemented()
}
}
}
private fun toggleLauncherComponent(targetAlias: String) {
val pm = applicationContext.packageManager
for (alias in aliasRegistry) {
val componentState = if (alias == targetAlias) {
PackageManager.COMPONENT_ENABLED_STATE_ENABLED
} else {
PackageManager.COMPONENT_ENABLED_STATE_DISABLED
}
pm.setComponentEnabledSetting(
ComponentName(applicationContext, "$packageNamespace.$alias"),
componentState,
PackageManager.DONT_KILL_APP
)
}
}
}
3. iOS Integration (Info.plist & Swift)
Drop your loose alternative icon images directly under the ios/Runner/ folder structure as un-cataloged raw items (e.g., ic_launcher_dark@2x.png, ic_launcher_festive@3x.png).
Register these keys in ios/Runner/Info.plist:
<key>CFBundleIcons</key>
<dict>
<key>CFBundlePrimaryIcon</key>
<dict>
<key>CFBundleIconFiles</key>
<array>
<string>AppIcon</string>
</array>
</dict>
<key>CFBundleAlternateIcons</key>
<dict>
<key>DarkIcon</key>
<dict>
<key>CFBundleIconFiles</key>
<array>
<string>ic_launcher_dark</string>
</array>
<key>UIPrerenderedIcon</key>
<false/>
</dict>
<key>FestiveIcon</key>
<dict>
<key>CFBundleIconFiles</key>
<array>
<string>ic_launcher_festive</string>
</array>
<key>UIPrerenderedIcon</key>
<false/>
</dict>
</dict>
</dict>
Open ios/Runner/AppDelegate.swift and configure the channel logic:
import UIKit
import Flutter
@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
override func application(
_ application: UIApplication,
didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
) -> Bool {
let controller : FlutterViewController = window?.rootViewController as! FlutterViewController
let iconChannel = FlutterMethodChannel(name: "com.dynamicicon.app/dynamic_icon",
binaryMessenger: controller.binaryMessenger)
iconChannel.setMethodCallHandler({
(call: FlutterMethodCall, result: @escaping FlutterResult) -> Void in
guard call.method == "setIcon" else {
result(FlutterMethodNotImplemented)
return
}
if let arguments = call.arguments as? [String: Any],
let iconName = arguments["iconName"] as? String {
self.updateAlternateIcon(named: iconName, response: result)
} else {
result(FlutterError(code: "BAD_ARGS", message: "Arguments malformed", details: nil))
}
})
GeneratedPluginRegistrant.register(with: self)
return super.application(application, didFinishLaunchingWithOptions: launchOptions)
}
private func updateAlternateIcon(named targetName: String, response: @escaping FlutterResult) {
if #available(iOS 10.3, *) {
let systemKey = (targetName == "DefaultIcon") ? nil : targetName
UIApplication.shared.setAlternateIconName(systemKey) { error in
if let error = error {
response(FlutterError(code: "IOS_ERROR", message: error.localizedDescription, details: nil))
} else {
response(null)
}
}
} else {
response(FlutterError(code: "UNSUPPORTED_OS", message: "Minimum OS layout required", details: nil))
}
}
}
Step 2: Implementing the Management Strategy
Now that our native code is ready, we need to balance manual selection with remote config updates.
To handle this cleanly, we'll establish a business rule priority: Firebase Remote Config acts as a global override. If a remote key is published from the cloud dashboard, it overrides manual user settings. If no cloud configuration override is set (or it returns 'DefaultIcon'), the application respects the user's manual in-app selection.
First, add your framework dependencies to your pubspec.yaml:
dependencies:
flutter:
sdk: flutter
firebase_core: ^3.0.0
firebase_remote_config: ^5.0.0
shared_preferences: ^2.2.0
The Dual-Control Integration Engine
Create a manager file app_icon_manager.dart to cleanly orchestrate both sources:
import 'package:firebase_remote_config/firebase_remote_config.dart';
import 'package:shared_preferences/shared_preferences.dart';
import 'dynamic_icon_service.dart';
class AppIconManager {
static const String _remoteOverrideKey = 'cloud_icon_override';
static const String _userPrefKey = 'user_selected_icon';
static const String _activeCachedKey = 'currently_applied_icon';
/// Mode 1: Executed manually when a user taps an in-app icon preference menu item
static Future<void> updateUserIconPreference(String targetIconName) async {
final SharedPreferences prefs = await SharedPreferences.getInstance();
await prefs.setString(_userPrefKey, targetIconName);
// Evaluate if the cloud override is currently blocking changes before updating
final FirebaseRemoteConfig remoteConfig = FirebaseRemoteConfig.instance;
final String cloudOverride = remoteConfig.getString(_remoteOverrideKey);
if (cloudOverride == 'DefaultIcon' || cloudOverride.isEmpty) {
await _applyIconSafetyGuard(targetIconName);
} else {
print("User setting cached, but blocked by active Cloud Override: $cloudOverride");
}
}
/// Mode 2: Triggered automatically during application launch to fetch cloud rules over-the-air
static Future<void> syncCloudConfiguration() async {
final FirebaseRemoteConfig remoteConfig = FirebaseRemoteConfig.instance;
try {
await remoteConfig.setDefaults(<String, dynamic>{_remoteOverrideKey: 'DefaultIcon'});
await remoteConfig.setConfigSettings(RemoteConfigSettings(
fetchTimeout: const Duration(seconds: 10),
minimumFetchInterval: const Duration(hours: 2),
));
bool updated = await remoteConfig.fetchAndActivate();
if (!updated) return;
final String cloudOverrideValue = remoteConfig.getString(_remoteOverrideKey);
final SharedPreferences prefs = await SharedPreferences.getInstance();
if (cloudOverrideValue != 'DefaultIcon' && cloudOverrideValue.isNotEmpty) {
// Cloud override takes precedence
await _applyIconSafetyGuard(cloudOverrideValue);
} else {
// Fall back to local user selection or fallback default
final String userPreference = prefs.getString(_userPrefKey) ?? 'DefaultIcon';
await _applyIconSafetyGuard(userPreference);
}
} catch (e) {
print('Failed to synchronize Firebase Remote Config layer: $e');
}
}
/// Evaluates and runs the method channel call only if a real delta is detected
static Future<void> _applyIconSafetyGuard(String targetValue) async {
final SharedPreferences prefs = await SharedPreferences.getInstance();
final String currentlyActive = prefs.getString(_activeCachedKey) ?? 'DefaultIcon';
// Guard Clause: Stop redundant channel triggers to avoid execution loops or app flash cycles
if (currentlyActive == targetValue) return;
print('Modifying launcher layout state from $currentlyActive to $targetValue');
await DynamicIconService.changeIcon(targetValue);
await prefs.setString(_activeCachedKey, targetValue);
}
}
Step 3: Wiring It to the UI Layer & Lifecycle Boot
To wrap things up, initialize our syncing layer inside your app's main() startup routine, and build a quick selection UI.
import 'package:firebase_core/firebase_core.dart';
import 'package:flutter/material.dart';
import 'app_icon_manager.dart';
void main() async {
WidgetsFlutterBinding.ensureInitialized();
await Firebase.initializeApp();
// Run the cloud check instantly at boot time
await AppIconManager.syncCloudConfiguration();
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
@override
Widget build(BuildContext context) {
return const MaterialApp(
home: SettingsIconScreen(),
);
}
}
class SettingsIconScreen extends StatelessWidget {
const SettingsIconScreen({super.key});
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(title: const Text('Customize App Icon')),
body: Padding(
padding: const EdgeInsets.all(16.0),
child: Column(
crossAxisAlignment: CrossAxisAlignment.start,
children: [
const Text(
'Select Your Preference:',
style: TextStyle(fontSize: 18, fontWeight: FontWeight.bold),
),
const SizedBox(height: 12),
ListTile(
leading: const Icon(Icons.phone_android),
title: const Text('Default Classic Blue'),
onTap: () => AppIconManager.updateUserIconPreference('DefaultIcon'),
),
ListTile(
leading: const Icon(Icons.dark_mode),
title: const Text('Premium Minimalist Dark'),
onTap: () => AppIconManager.updateUserIconPreference('DarkIcon'),
),
ListTile(
leading: const Icon(Icons.celebration),
title: const Text('Festive Celebration Theme'),
onTap: () => AppIconManager.updateUserIconPreference('FestiveIcon'),
),
],
),
),
);
}
}
Wrap Up & Cloud Control
Your application is now fully dual-controlled! To push a global theme override over the air:
- Open the Firebase Console and head to Remote Config.
- Create a parameter matching
cloud_icon_override. - Set its value to
FestiveIcon(or keep it asDefaultIconto defer to your user's preferences). - Hit Publish Changes.
Top comments (0)