Material Theme customization in Android Kotlin - Build, Publish & Deploy

Build & Publish - Material Theme customization

Performance Impact of Material Theme Customization

Customizing Material Theme mainly affects UI rendering. Using complex custom styles or many layered themes can slightly reduce frame rates, especially on older devices. However, simple color and typography changes have minimal impact on memory and battery. Overusing custom fonts or heavy drawable resources can increase memory use and slow rendering.

💻

How to Optimize Material Theme Customization for 60fps

Keep your theme changes simple and consistent. Use system-supported colors and typography to leverage hardware acceleration. Avoid large or complex drawable assets in your theme. Use vector drawables instead of bitmaps for icons. Cache theme resources and avoid recalculating styles at runtime. Test on low-end devices to ensure smooth animations and scrolling.

Impact on App Bundle Size and Startup Time

Custom themes add minimal size if you only change colors and fonts. Adding multiple font files or large image assets increases APK size. Using downloadable fonts can reduce initial bundle size. Excessive theme overlays or unused styles increase app size and can slow startup as styles load. Keep your theme lean to maintain fast app launch.

iOS vs Android Differences for Material Theme Customization

Android uses Material Design with XML styles and Kotlin code for themes. iOS uses UIKit or SwiftUI with different theming approaches. Android themes affect the entire app UI consistently. iOS requires manual styling per component or uses appearance proxies. Material Theme customization is native to Android and not directly portable to iOS, which follows Human Interface Guidelines.

Relevant Store Review Guidelines and Requirements

• Google Play: Ensure your theme does not mislead users or mimic system UI in a confusing way.
• Accessibility: Maintain sufficient color contrast for readability per WCAG standards.
• Performance: Avoid themes that cause janky animations or slow UI responsiveness.
• Privacy: Themes should not interfere with permission dialogs or system UI elements.

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

Likely causes include heavy custom fonts loading synchronously, large drawable assets in the theme, or complex style calculations at runtime. Check if your theme uses large images or multiple font files that delay rendering. Optimize by using vector assets, downloadable fonts, and caching theme resources.

Key Result

Material Theme customization affects UI smoothness and app size mainly through fonts and drawable assets. Keep themes simple and use vector assets to maintain 60fps and fast startup.

Practice

1. What is the main purpose of customizing the MaterialTheme in an Android app?

easy

A. To add new activities to the app

B. To change the app's colors, fonts, and shapes globally

C. To manage app permissions

D. To handle network requests

Solution

1. Step 1: Understand MaterialTheme role

   The MaterialTheme controls the look and feel of the app by setting colors, typography, and shapes.

2. Step 2: Identify customization purpose

   Customizing MaterialTheme changes these visual styles globally for consistency.

3. Final Answer:

   To change the app's colors, fonts, and shapes globally -> Option B

4. Quick Check:

   MaterialTheme customization = change colors, fonts, shapes [OK]

Hint: MaterialTheme controls app-wide style settings [OK]

Common Mistakes:

• Confusing theme customization with adding app features
• Thinking it manages app permissions
• Assuming it handles network or data logic

2. Which of the following is the correct way to apply a custom color scheme in MaterialTheme in Kotlin?

easy

A. MaterialTheme(colorScheme = myColors) { /* UI content */ }

B. MaterialTheme(colors = myColors) { /* UI content */ }

C. MaterialTheme(setColors = myColors) { /* UI content */ }

D. MaterialTheme(applyColors = myColors) { /* UI content */ }

Solution

1. Step 1: Recall MaterialTheme parameters

   The correct parameter for colors in MaterialTheme is colorScheme.

2. Step 2: Match correct syntax

   MaterialTheme(colorScheme = myColors) { /* UI content */ } uses colorScheme = myColors, which is the correct syntax in Kotlin.

3. Final Answer:

   MaterialTheme(colorScheme = myColors) { /* UI content */ } -> Option A

4. Quick Check:

   Use colorScheme parameter for colors [OK]

Hint: Use colorScheme, not colors, in MaterialTheme [OK]

Common Mistakes:

• Using 'colors' instead of 'colorScheme'
• Using non-existent parameters like 'setColors' or 'applyColors'
• Forgetting to wrap UI content inside the theme block

3. Given the code snippet below, what color will the Text component display if primary in colorScheme is set to Color.Red?

MaterialTheme(
  colorScheme = ColorScheme(
    primary = Color.Red,
    secondary = Color.Blue
  )
) {
  Text("Hello", color = MaterialTheme.colorScheme.primary)
}

medium

A. Blue

B. Green

C. Red

D. Default text color

Solution

1. Step 1: Identify colorScheme primary value

   The primary color in colorScheme is set to Color.Red.

2. Step 2: Check Text color usage

   The Text color uses MaterialTheme.colorScheme.primary, so it will be Color.Red.

3. Final Answer:

   Red -> Option C

4. Quick Check:

   Text color = primary color = Red [OK]

Hint: Text color uses primary from colorScheme [OK]

Common Mistakes:

• Confusing primary with secondary color
• Assuming default color instead of theme color
• Mixing up color names

4. What is wrong with the following Kotlin code that tries to customize the MaterialTheme's typography?

MaterialTheme(
  typography = Typography(
    bodyLarge = TextStyle(fontSize = 20)
  )
) {
  Text("Welcome")
}

medium

A. TextStyle requires a unit for fontSize, like sp or dp

B. Typography cannot be customized in MaterialTheme

C. Text component must specify typography explicitly

D. MaterialTheme must not have a typography parameter

Solution

1. Step 1: Check TextStyle fontSize usage

   The fontSize must include a unit like 20.sp, not just 20.

2. Step 2: Identify correct syntax

   Without the unit, the code will cause a type error because fontSize expects a TextUnit.

3. Final Answer:

   TextStyle requires a unit for fontSize, like sp or dp -> Option A

4. Quick Check:

   fontSize needs unit like sp [OK]

Hint: Always add .sp for fontSize values [OK]

Common Mistakes:

• Omitting units for fontSize
• Thinking typography can't be customized
• Expecting Text to need explicit typography parameter

5. You want to create a custom shape for buttons in your app using MaterialTheme. Which approach correctly applies a rounded corner shape of 16.dp to all buttons?

hard

A. MaterialTheme(shapes = Shapes(extraLarge = RoundedCornerShape(16.dp))) { Button(...) }

B. MaterialTheme(shapes = Shapes(small = RoundedCornerShape(16.dp))) { Button(...) }

C. MaterialTheme(shapes = Shapes(large = RoundedCornerShape(16.dp))) { Button(...) }

D. MaterialTheme(shapes = Shapes(medium = RoundedCornerShape(16.dp))) { Button(...) }

Solution

1. Step 1: Understand shape categories in MaterialTheme

   MaterialTheme defines shapes as small, medium, and large. Buttons use the medium shape by default.

2. Step 2: Apply rounded corners to medium shape

   Setting medium = RoundedCornerShape(16.dp) customizes button corners.

3. Final Answer:

   MaterialTheme(shapes = Shapes(medium = RoundedCornerShape(16.dp))) { Button(...) } -> Option D

4. Quick Check:

   Buttons use medium shape slot [OK]

Hint: Buttons use medium shape in MaterialTheme [OK]

Common Mistakes:

• Changing small or large shapes instead of medium
• Using non-existent shape categories like extraLarge
• Forgetting to wrap Button inside MaterialTheme