Bird
Raised Fist0
Android Kotlinmobile~5 mins

Transition animations in Android Kotlin

Choose your learning style10 modes available
Introduction

Transition animations make moving between screens smooth and nice to look at. They help users understand changes in the app.

When switching from one screen to another in an app.
When showing or hiding parts of the screen with animation.
When you want to make your app feel more friendly and polished.
When guiding users' attention to important changes on the screen.
Syntax
Android Kotlin
override fun onCreate(savedInstanceState: Bundle?) {
  super.onCreate(savedInstanceState)
  setContentView(R.layout.activity_main)
  overridePendingTransition(R.anim.enter_anim, R.anim.exit_anim)
}
Use overridePendingTransition right after startActivity or in onCreate to set animations.
Animations are defined in XML files inside res/anim/ folder.
Examples
This makes the new screen slide in from the right and the old screen slide out to the left.
Android Kotlin
overridePendingTransition(R.anim.slide_in_right, R.anim.slide_out_left)
This uses built-in Android fade animations for smooth fading between screens.
Android Kotlin
overridePendingTransition(android.R.anim.fade_in, android.R.anim.fade_out)
Start a new screen and apply zoom in/out animations for transition.
Android Kotlin
startActivity(intent)
overridePendingTransition(R.anim.zoom_in, R.anim.zoom_out)
Sample App

This app has two screens. When you tap the button on the first screen, it opens the second screen with a slide animation from right to left.

Android Kotlin
class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)

    val button = findViewById<Button>(R.id.button)
    button.setOnClickListener {
      val intent = Intent(this, SecondActivity::class.java)
      startActivity(intent)
      overridePendingTransition(R.anim.slide_in_right, R.anim.slide_out_left)
    }
  }
}

class SecondActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_second)
  }
}
OutputSuccess
Important Notes

Animations must be defined as XML files in res/anim/ folder.

Use simple animations like slide, fade, or zoom for best user experience.

Test animations on different devices to ensure smoothness.

Summary

Transition animations improve app feel by smoothing screen changes.

Use overridePendingTransition after starting a new activity.

Animations are XML files placed in res/anim/ folder.

Practice

(1/5)
1. What is the main purpose of using overridePendingTransition in Android Kotlin apps?
easy
A. To apply custom animations when transitioning between activities
B. To change the app's theme dynamically
C. To start a new activity without animation
D. To stop all running animations in the app

Solution

  1. Step 1: Understand the role of overridePendingTransition

    This method is called right after starting a new activity to specify the enter and exit animations.
  2. Step 2: Identify its effect on activity transitions

    It customizes how the new activity appears and how the old one disappears, improving user experience.
  3. Final Answer:

    To apply custom animations when transitioning between activities -> Option A
  4. Quick Check:

    overridePendingTransition = custom animations [OK]
Hint: Remember: overridePendingTransition controls activity switch animations [OK]
Common Mistakes:
  • Thinking it changes app theme
  • Assuming it disables animations
  • Confusing it with stopping animations
2. Which of the following is the correct syntax to apply a transition animation after starting a new activity in Kotlin?
easy
A. startActivity(intent) overridePendingTransition(R.anim.slide_in, R.anim.slide_out)
B. overridePendingTransition(R.anim.slide_in, R.anim.slide_out) startActivity(intent)
C. startActivity(intent) setTransition(R.anim.slide_in, R.anim.slide_out)
D. startActivity(intent) overrideTransition(R.anim.slide_in, R.anim.slide_out)

Solution

  1. Step 1: Recall the correct order of method calls

    You must call startActivity(intent) first, then overridePendingTransition immediately after.
  2. Step 2: Verify method names and parameters

    The method is overridePendingTransition, taking two animation resource IDs for enter and exit animations.
  3. Final Answer:

    startActivity(intent) overridePendingTransition(R.anim.slide_in, R.anim.slide_out) -> Option A
  4. Quick Check:

    startActivity then overridePendingTransition [OK]
Hint: Call overridePendingTransition right after startActivity [OK]
Common Mistakes:
  • Calling overridePendingTransition before startActivity
  • Using wrong method names like setTransition
  • Passing incorrect parameters
3. Given the following code snippet in an Android Kotlin app, what animation effect will the user see when transitioning to SecondActivity?
startActivity(Intent(this, SecondActivity::class.java))
overridePendingTransition(R.anim.fade_in, R.anim.fade_out)
medium
A. No animation will occur because fade_in and fade_out are invalid
B. SecondActivity slides in from the right, current activity slides out to the left
C. SecondActivity zooms in while current activity zooms out
D. SecondActivity fades in while the current activity fades out

Solution

  1. Step 1: Understand the animation resource names

    Animations named fade_in and fade_out typically cause views to gradually appear or disappear by changing opacity.
  2. Step 2: Apply to activity transition

    The new activity will fade in, and the old activity will fade out, creating a smooth crossfade effect.
  3. Final Answer:

    SecondActivity fades in while the current activity fades out -> Option D
  4. Quick Check:

    fade_in + fade_out = crossfade effect [OK]
Hint: fade_in/out means smooth appearing/disappearing [OK]
Common Mistakes:
  • Assuming slide or zoom animations without checking names
  • Thinking no animation occurs if unsure about resource validity
  • Confusing fade with zoom or slide
4. Identify the error in the following Kotlin code snippet that tries to apply a transition animation:
startActivity(Intent(this, NextActivity::class.java))
overridePendingTransition(R.anim.slide_in_left)
medium
A. Animation resource IDs must be strings, not integers
B. Incorrect method name; should be setPendingTransition
C. Missing second animation resource parameter in overridePendingTransition
D. startActivity should be called after overridePendingTransition

Solution

  1. Step 1: Check the method signature of overridePendingTransition

    This method requires two parameters: one for the enter animation and one for the exit animation.
  2. Step 2: Identify the missing parameter

    The code only provides one animation resource, causing a compile-time error.
  3. Final Answer:

    Missing second animation resource parameter in overridePendingTransition -> Option C
  4. Quick Check:

    overridePendingTransition needs two animations [OK]
Hint: overridePendingTransition always needs two animation IDs [OK]
Common Mistakes:
  • Providing only one animation resource
  • Using wrong method names
  • Calling overridePendingTransition before startActivity
5. You want to create a smooth slide transition when moving from MainActivity to DetailActivity. You have two animation XML files: slide_in_right.xml and slide_out_left.xml in res/anim/. Which code snippet correctly applies these animations during the activity transition?
hard
A. overridePendingTransition(R.anim.slide_in_right, R.anim.slide_out_left) startActivity(Intent(this, DetailActivity::class.java))
B. startActivity(Intent(this, DetailActivity::class.java)) overridePendingTransition(R.anim.slide_in_right, R.anim.slide_out_left)
C. startActivity(Intent(this, DetailActivity::class.java)) overridePendingTransition(R.anim.slide_out_left, R.anim.slide_in_right)
D. startActivity(Intent(this, DetailActivity::class.java)) overridePendingTransition(R.anim.slide_in_left, R.anim.slide_out_right)

Solution

  1. Step 1: Confirm the order of method calls

    You must call startActivity first, then overridePendingTransition immediately after.
  2. Step 2: Match animations to correct enter and exit roles

    slide_in_right is the enter animation for the new activity, and slide_out_left is the exit animation for the current activity.
  3. Final Answer:

    startActivity(Intent(this, DetailActivity::class.java)) overridePendingTransition(R.anim.slide_in_right, R.anim.slide_out_left) -> Option B
  4. Quick Check:

    startActivity then overridePendingTransition with correct animations [OK]
Hint: Enter animation first, exit animation second after startActivity [OK]
Common Mistakes:
  • Swapping enter and exit animations
  • Calling overridePendingTransition before startActivity
  • Using wrong animation resource names
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard