Passing arguments in Android Kotlin - Build, Publish & Deploy

Build & Publish - Passing arguments

Performance Impact of Passing Arguments

Passing arguments between screens or components in Android using Kotlin is generally lightweight. Simple data types like strings, integers, or booleans have minimal impact on frame rate and memory. However, passing large objects or complex data structures can increase memory usage and slow down screen transitions, potentially causing frame drops below 60fps.

Efficient argument passing helps maintain smooth UI animations and reduces battery drain by avoiding unnecessary data copying.

💻

How to Optimize Passing Arguments for 60fps Rendering

• Pass only essential data needed for the next screen to avoid overhead.
• Use Parcelable or Serializable interfaces efficiently; Parcelable is faster and preferred in Android.
• For large data, consider using shared ViewModel or persistent storage instead of passing through arguments.
• Avoid passing complex objects directly; pass IDs or keys and fetch data asynchronously.
• Keep argument bundles small to speed up navigation and reduce UI thread blocking.

Impact on App Bundle Size and Startup Time

Passing arguments itself does not significantly affect app bundle size. However, including large data classes or libraries to support serialization can increase APK size slightly.

Startup time is mostly unaffected by argument passing, but inefficient data handling during navigation can delay screen rendering.

iOS vs Android Differences for Passing Arguments

On Android with Kotlin, arguments are passed via Bundles using Parcelable or Serializable objects. On iOS, SwiftUI or UIKit uses different patterns like property injection or Segues with prepare methods.

Android requires explicit serialization of objects, while iOS often uses direct property passing or delegates.

Android navigation components provide safe-args plugin for type-safe argument passing, which has no direct iOS equivalent.

Relevant Store Review Guidelines and Requirements

• Ensure no sensitive data is passed insecurely between screens to comply with privacy policies.
• Do not pass large amounts of user data that could cause app crashes or poor performance, which may lead to rejection.
• Follow platform guidelines for smooth navigation and responsiveness to meet user experience standards.
• Use recommended serialization methods to avoid crashes or data corruption that could cause app store rejection.

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

It is likely that you are passing large or complex objects directly as arguments, causing heavy serialization and blocking the UI thread.

Another possibility is fetching data synchronously during navigation instead of asynchronously.

To fix this, pass only minimal data like IDs and load heavy data in the background after the screen loads.

Key Result

Passing arguments efficiently in Android Kotlin ensures smooth navigation and UI performance by minimizing data size and using Parcelable. Avoid passing large objects directly to keep frame rates at 60fps and prevent memory issues.

Practice

1. What is the primary purpose of passing arguments between activities in Android Kotlin?

easy

A. To close the current activity

B. To change the app theme

C. To share data between different screens

D. To update the app version

Solution

1. Step 1: Understand activity communication

   Activities often need to share information like user input or selections.

2. Step 2: Purpose of passing arguments

   Passing arguments allows one screen to send data to another screen.

3. Final Answer:

   To share data between different screens -> Option C

4. Quick Check:

   Passing arguments = sharing data [OK]

Hint: Passing arguments means sending data between screens [OK]

Common Mistakes:

• Thinking it changes app theme
• Confusing with app version updates
• Assuming it closes activities

2. Which Kotlin code correctly passes a String argument "username" with value "Alice" to another activity using Intent?

easy

A. val intent = Intent(this, NextActivity::class.java)
intent.putExtra("username", "Alice")
startActivity(intent)

B. val intent = Intent(this, NextActivity::class.java)
intent.putString("username", "Alice")
startActivity(intent)

C. val intent = Intent(this, NextActivity::class.java)
intent.addExtra("username", "Alice")
startActivity(intent)

D. val intent = Intent(this, NextActivity::class.java)
intent.setExtra("username", "Alice")
startActivity(intent)

Solution

1. Step 1: Identify correct Intent method

   The method to add data is putExtra(key, value).

2. Step 2: Check method names in options

   Only val intent = Intent(this, NextActivity::class.java) intent.putExtra("username", "Alice") startActivity(intent) uses putExtra correctly; others use invalid method names.

3. Final Answer:

   val intent = Intent(this, NextActivity::class.java)\nintent.putExtra("username", "Alice")\nstartActivity(intent) -> Option A

4. Quick Check:

   Use putExtra() to pass data [OK]

Hint: Use putExtra() to add data to Intent [OK]

Common Mistakes:

• Using non-existent methods like putString or addExtra
• Forgetting to call startActivity()
• Passing wrong argument types

3. What will be the output of the following code in the receiving activity?

val username = intent.getStringExtra("username")
textView.text = username ?: "Guest"

If the sending activity did NOT pass any "username" extra?

medium

A. The app will crash with NullPointerException

B. The TextView will show "null"

C. The TextView will be empty

D. The TextView will show "Guest"

Solution

1. Step 1: Understand getStringExtra behavior

   If no extra is passed, getStringExtra returns null.

2. Step 2: Analyze Elvis operator usage

   The expression username ?: "Guest" means if username is null, use "Guest".

3. Final Answer:

   The TextView will show "Guest" -> Option D

4. Quick Check:

   Null fallback with ?: operator = "Guest" [OK]

Hint: ?: operator provides default if null [OK]

Common Mistakes:

• Expecting null string to display
• Assuming app crashes on null
• Forgetting ?: fallback

4. Identify the error in this code snippet that tries to retrieve an Int extra named "age":

val age = intent.getIntExtra("age")
textView.text = age.toString()

medium

A. getIntExtra requires a default value as second argument

B. getIntExtra should be getIntExtras

C. age.toString() is invalid for Int

D. Intent cannot carry Int values

Solution

1. Step 1: Check getIntExtra method signature

   getIntExtra requires two arguments: key and default value.

2. Step 2: Identify missing argument

   The code misses the default value argument, causing a compile error.

3. Final Answer:

   getIntExtra requires a default value as second argument -> Option A

4. Quick Check:

   getIntExtra(key, default) needs default [OK]

Hint: Always provide default value for getIntExtra [OK]

Common Mistakes:

• Omitting default value argument
• Using wrong method name getIntExtras
• Thinking Int can't be passed

5. You want to pass a list of Strings named "items" from one activity to another. Which is the correct way to pass and retrieve this list using Intent?

hard

A. Use intent.putExtra("items", items) and intent.getStringExtra("items")

B. Use intent.putStringArrayListExtra("items", items) and intent.getStringArrayListExtra("items")

C. Use intent.putExtra("items", items.toString()) and intent.getStringExtra("items")

D. Use intent.putExtra("items", items) and intent.getSerializableExtra("items")

Solution

1. Step 1: Passing a list of Strings

   For ArrayList<String>, use putStringArrayListExtra to pass the list.

2. Step 2: Retrieving the list

   Use getStringArrayListExtra to get the list back safely.

3. Final Answer:

   Use intent.putStringArrayListExtra("items", items) and intent.getStringArrayListExtra("items") -> Option B

4. Quick Check:

   Use put/getStringArrayListExtra for String lists [OK]

Hint: Use put/getStringArrayListExtra for String lists [OK]

Common Mistakes:

• Passing list as plain putExtra
• Converting list to string incorrectly
• Using getSerializableExtra without casting