Intent for activity navigation in Android Kotlin - Build, Publish & Deploy

Build & Publish - Intent for activity navigation

Performance Impact

Using intents for activity navigation is lightweight and fast. It typically maintains smooth 60fps UI transitions if activities are simple. However, launching heavy activities or passing large data via intents can increase memory use and slow down navigation.

Battery impact is minimal unless the new activity triggers heavy background work.

Optimization Tips

• Keep data passed via intents small and simple (e.g., primitive types, small strings).
• Avoid passing large objects or bitmaps; use shared ViewModel or persistent storage instead.
• Use startActivityForResult only when needed to reduce overhead.
• Preload data asynchronously before navigation to avoid UI delays.
• Use animations sparingly to maintain 60fps smoothness.

App Size and Startup Time

Intents themselves do not affect app bundle size. However, adding many activities increases APK size and can slightly increase app startup time due to more classes to load.

Keep activities focused and avoid unnecessary ones to keep app size small (ideally under 50MB for medium apps).

iOS vs Android Differences

Android uses intents to navigate between activities. iOS uses view controllers and navigation controllers instead.

Android requires explicit intent declarations in the manifest for some activities; iOS uses storyboard segues or programmatic navigation.

Android intents can carry data bundles; iOS passes data via properties or delegates.

Store Review Guidelines

• Ensure all activities launched via intents comply with privacy policies (e.g., no unauthorized data sharing).
• Do not launch activities that confuse users or cause unexpected behavior.
• Follow Android's guidelines for intent filters and permissions to avoid rejection.
• Test navigation flows thoroughly to prevent crashes or freezes.

Self Check

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

• Passing large data objects via intent causing serialization delays.
• Heavy initialization or blocking operations in the new activity's onCreate.
• Unoptimized UI layout or loading large images synchronously.
• Missing asynchronous data loading or caching strategies.

Key Result

Using intents for activity navigation is efficient and fast if data passed is small and activities are optimized. Avoid large data in intents and heavy UI work on startup to maintain smooth 60fps navigation and quick screen loads.

Practice

1. What is the main purpose of an Intent in Android Kotlin?

easy

A. To store user data permanently

B. To style the user interface

C. To navigate from one activity to another

D. To handle background tasks

Solution

1. Step 1: Understand Intent usage

   An Intent is used to request an action from another app component, commonly to start a new activity.

2. Step 2: Identify navigation role

   In Android, Intent is primarily used to navigate between screens (activities).

3. Final Answer:

   To navigate from one activity to another -> Option C

4. Quick Check:

   Intent = Navigation [OK]

Hint: Intent is for moving between screens [OK]

Common Mistakes:

• Confusing Intent with data storage
• Thinking Intent styles UI
• Assuming Intent handles background tasks

2. Which of the following is the correct syntax to create an Intent to start SecondActivity from the current activity?

easy

A. val intent = Intent(this, SecondActivity::class.java)

B. val intent = Intent(SecondActivity, this::class.java)

C. val intent = Intent(this, SecondActivity)

D. val intent = Intent(SecondActivity::class.java, this)

Solution

1. Step 1: Check Intent constructor parameters

   The Intent constructor requires the current context and the target activity class with ::class.java.

2. Step 2: Validate syntax correctness

   val intent = Intent(this, SecondActivity::class.java) correctly uses this for context and SecondActivity::class.java for the target.

3. Final Answer:

   val intent = Intent(this, SecondActivity::class.java) -> Option A

4. Quick Check:

   Intent(this, TargetActivity::class.java) = Correct [OK]

Hint: Use this and TargetActivity::class.java in Intent [OK]

Common Mistakes:

• Swapping parameters order
• Omitting ::class.java
• Using activity instance instead of class

3. What will happen when the following code runs inside an activity?

val intent = Intent(this, DetailActivity::class.java)
startActivity(intent)

medium

A. The app will crash due to missing permissions

B. The current activity will close and DetailActivity will open

C. Nothing will happen because startActivity is missing parameters

D. DetailActivity will open on top of the current activity

Solution

1. Step 1: Analyze Intent creation

   The Intent is correctly created to open DetailActivity from the current context.

2. Step 2: Understand startActivity behavior

   Calling startActivity launches the new activity on top without closing the current one.

3. Final Answer:

   DetailActivity will open on top of the current activity -> Option D

4. Quick Check:

   startActivity(intent) = Opens new screen on top [OK]

Hint: startActivity opens new screen on top [OK]

Common Mistakes:

• Thinking startActivity closes current activity
• Assuming permissions needed for navigation
• Believing startActivity requires extra parameters

4. Identify the error in this code snippet that tries to start ProfileActivity:

val intent = Intent(ProfileActivity::class.java, this)
startActivity(intent)

medium

A. The parameters in Intent are reversed

B. startActivity is missing parentheses

C. ProfileActivity should be an instance, not a class

D. Intent requires a string action, not classes

Solution

1. Step 1: Check Intent constructor parameter order

   The Intent constructor expects the current context first, then the target activity class.

2. Step 2: Identify parameter reversal

   Here, the target activity class is given first, then the context, which is incorrect.

3. Final Answer:

   The parameters in Intent are reversed -> Option A

4. Quick Check:

   Intent(this, TargetActivity::class.java) = Correct order [OK]

Hint: Context first, target class second in Intent [OK]

Common Mistakes:

• Swapping context and target activity
• Forgetting ::class.java
• Using activity instance instead of context

5. You want to open SettingsActivity and close the current activity so the user cannot return by pressing back. Which code snippet achieves this?

hard

A. val intent = Intent(this, SettingsActivity::class.java)
startActivity(intent)

B. val intent = Intent(this, SettingsActivity::class.java)
startActivity(intent)
finish()

C. val intent = Intent(this, SettingsActivity::class.java)
finish()
startActivity(intent)

D. val intent = Intent(this, SettingsActivity::class.java)
startActivityForResult(intent, 1)

Solution

1. Step 1: Understand startActivity and finish

   startActivity opens the new activity; finish closes the current one.

2. Step 2: Order matters

   Calling finish() after startActivity ensures the new screen opens before current closes.

3. Step 3: Check options

   val intent = Intent(this, SettingsActivity::class.java) startActivity(intent) finish() correctly calls startActivity then finish to prevent back navigation.

4. Final Answer:

   val intent = Intent(this, SettingsActivity::class.java) startActivity(intent) finish() -> Option B

5. Quick Check:

   startActivity + finish = Open new and close current [OK]

Hint: Call finish() after startActivity to close current [OK]

Common Mistakes:

• Calling finish() before startActivity
• Not calling finish() at all
• Using startActivityForResult unnecessarily