Customized Logo and Splash Screen in MDK Mobile App for Android

Estimated read time 6 min read

This blog explains how to customize the app launcher icon (logo) and the splash screen for an Android customized client built using SAP Mobile Development Kit (MDK).

The approach described here is based on real project experience with an MDK customized client built using tools provided by SAP and targeting the Android platform maintained by Google.

When do we need Android branding in MDK?

You normally customize the Android logo and splash screen when:

you build a customized MDK client

your customer requires corporate branding

the app will be distributed internally or through an app store

This is different from a standard MDK client where you cannot change native branding.

 

Android branding folder in MDK customized app

All Android-specific branding is handled inside:

project_folderApp_Resources_MergeAndroidsrcmainres

You should only work inside the native resource folders and only replace images.

Customizing the Android App Logo (Launcher Icon) :

In Android, the launcher icon is maintained using the standard Android mipmap folders.

In an MDK customized app, go to:

App_Resources/Android/src/main/res/

You will find folders such as (if not create the folders):

mipmap-mdpi

mipmap-hdpi

mipmap-xhdpi

mipmap-xxhdpi

mipmap-xxxhdpi

Inside each folder, there will already be an existing launcher icon file ( if not generate the icon file from android studio asset).

What you should do

Replace the image file with your customer logo

Keep:

the same file name

the same folder structure

What you should not do

Do not rename the icon files

Do not delete any mipmap folders

Do not change any Android manifest or build files

MDK and the Android project already reference these resource names internally.

It will look like this after adding the icon: 

Customizing the Android Splash Screen

The splash screen is the first screen shown when the MDK client starts.

In an Android MDK customized app, the splash screen image is usually stored under:

App_Resources_Merge/Android/src/main/res/drawable/

You will see a default splash image used by the MDK client.

How to customize

Replace the existing splash image with your branded image

Keep the same file name

If your project uses a background color together with the splash image, the color is usually defined in the Android style configuration (for example in ic_launcher_background.xml).
In most MDK projects, you do not need to modify this unless your branding requires a different background color.

After adding drawable folder and logo , following structure will be like this : 

Important rule for Android MDK branding

In an MDK customized Android app:

Only replace image resources.

Do not modify:

native Java / Kotlin files

AndroidManifest.xml

Gradle configuration

MDK internal resources

Changing anything beyond images can cause build failures or runtime issues during future MDK or Android upgrades.

 

Conclusion

In an Android customized MDK client, changing the app logo and splash screen is a simple and safe activity if done correctly.

The key point is:

For Android MDK branding, only replace the existing image resources under
App_Resources/Android/src/main/res/ and never change native configuration or code files.

Following this approach ensures that your branded MDK Android app remains stable and upgrade-safe.

 

​ This blog explains how to customize the app launcher icon (logo) and the splash screen for an Android customized client built using SAP Mobile Development Kit (MDK).The approach described here is based on real project experience with an MDK customized client built using tools provided by SAP and targeting the Android platform maintained by Google.When do we need Android branding in MDK?You normally customize the Android logo and splash screen when:you build a customized MDK clientyour customer requires corporate brandingthe app will be distributed internally or through an app storeThis is different from a standard MDK client where you cannot change native branding. Android branding folder in MDK customized appAll Android-specific branding is handled inside:project_folderApp_Resources_MergeAndroidsrcmainresYou should only work inside the native resource folders and only replace images.Customizing the Android App Logo (Launcher Icon) :In Android, the launcher icon is maintained using the standard Android mipmap folders.In an MDK customized app, go to:App_Resources/Android/src/main/res/You will find folders such as (if not create the folders):mipmap-mdpimipmap-hdpimipmap-xhdpimipmap-xxhdpimipmap-xxxhdpiInside each folder, there will already be an existing launcher icon file ( if not generate the icon file from android studio asset).What you should doReplace the image file with your customer logoKeep:the same file namethe same folder structureWhat you should not doDo not rename the icon filesDo not delete any mipmap foldersDo not change any Android manifest or build filesMDK and the Android project already reference these resource names internally.It will look like this after adding the icon: Customizing the Android Splash ScreenThe splash screen is the first screen shown when the MDK client starts.In an Android MDK customized app, the splash screen image is usually stored under:App_Resources_Merge/Android/src/main/res/drawable/You will see a default splash image used by the MDK client.How to customizeReplace the existing splash image with your branded imageKeep the same file nameIf your project uses a background color together with the splash image, the color is usually defined in the Android style configuration (for example in ic_launcher_background.xml).In most MDK projects, you do not need to modify this unless your branding requires a different background color.After adding drawable folder and logo , following structure will be like this : Important rule for Android MDK brandingIn an MDK customized Android app:Only replace image resources.Do not modify:native Java / Kotlin filesAndroidManifest.xmlGradle configurationMDK internal resourcesChanging anything beyond images can cause build failures or runtime issues during future MDK or Android upgrades. ConclusionIn an Android customized MDK client, changing the app logo and splash screen is a simple and safe activity if done correctly.The key point is:For Android MDK branding, only replace the existing image resources underApp_Resources/Android/src/main/res/ and never change native configuration or code files.Following this approach ensures that your branded MDK Android app remains stable and upgrade-safe.   Read More Technology Blog Posts by Members articles 

#SAP

#SAPTechnologyblog

You May Also Like

More From Author