Passing data between activities in Android Kotlin - Build, Publish & Deploy

Build & Publish - Passing data between activities

Performance Impact

Passing data between activities in Android using intents has minimal impact on frame rate and memory if the data size is small, such as strings or numbers. Large data objects or complex serializable data can increase memory usage and slow down activity transitions, potentially causing jank or dropped frames. Efficient data passing helps maintain smooth 60fps UI and conserves battery life by avoiding heavy processing during navigation.

Optimization Tips

• Pass only essential data using intent extras to keep the payload small.
• Use Parcelable instead of Serializable for custom objects to reduce serialization overhead.
• Avoid passing large bitmaps or files; instead, pass references like URIs or file paths.
• Consider using ViewModel or shared data repositories for complex data sharing to reduce intent size.
• Preload or cache data in the receiving activity to speed up UI rendering after navigation.

App Bundle Size and Startup Time

Passing data between activities does not directly affect the app bundle size. However, including large data classes or heavy serialization libraries can increase APK size. Efficient data passing keeps activity startup fast, reducing perceived load time. Avoid embedding large static data in intents to prevent slow activity launches.

iOS vs Android Differences

On Android, data is passed between activities using intents with extras. On iOS, data is passed between view controllers typically via segues or direct property setting. Android requires data to be Parcelable or Serializable for intents, while iOS uses native Swift types or Codable. Android's activity lifecycle and intent system differ from iOS's view controller navigation, so data passing patterns are platform-specific.

Store Review Guidelines

• Ensure data passed between activities does not expose sensitive user information unintentionally.
• Follow privacy policies by not passing personal data without user consent.
• Keep app responsive during navigation to meet user experience guidelines.
• Do not pass executable code or unsafe data that could cause crashes or security issues.
• Test on multiple devices to ensure smooth transitions and no memory leaks.

Self-Check Question

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

• Passing large or complex data objects via intent extras causing slow serialization.
• Loading heavy resources synchronously in the receiving activity's onCreate method.
• Not using Parcelable for custom objects, causing inefficient serialization.
• Passing bitmaps or large files directly instead of references.

Key Result

Passing data between activities using intents is lightweight when data is small and simple. Optimize by passing minimal data, using Parcelable, and avoiding large objects to maintain smooth 60fps UI and fast activity transitions.