Activity concept in Android Kotlin - Build, Publish & Deploy

Build & Publish - Activity concept

Performance Impact of Activity Concept

Activities are the building blocks of Android apps. Each Activity creates a screen with UI. Having many Activities can increase memory use because each one holds its own UI and state. Switching between Activities involves system work to start and stop them, which can cause small delays and affect smoothness if overused. Properly managing Activity lifecycle helps keep battery use low and frame rates smooth, aiming for 60fps for good user experience.

💻

How to Optimize Activities for 60fps Rendering

• Reuse Activities when possible instead of creating many new ones.
• Keep UI simple and avoid heavy work on the main thread during Activity startup.
• Use asynchronous loading for data to prevent UI blocking.
• Manage lifecycle events to release resources when Activity is paused or stopped.
• Consider using Fragments or Jetpack Navigation to reduce Activity switches.

Impact on App Bundle Size and Startup Time

Activities themselves add minimal size to the app bundle since they are mostly code. However, each Activity may load different layouts and resources, increasing overall size. More Activities can increase app startup time if the launcher Activity loads many resources. Keeping layouts lightweight and sharing resources helps keep the app size and startup time small.

iOS vs Android Differences for Activity Concept

Android uses Activities as screens, while iOS uses ViewControllers. Android Activities have a complex lifecycle with states like created, started, resumed, paused, stopped, and destroyed. iOS ViewControllers have a simpler lifecycle. Android requires explicit management of Activity lifecycle to avoid memory leaks and performance issues. iOS handles some lifecycle events automatically. Navigation patterns differ: Android often uses Activities and Fragments, iOS uses ViewControllers and Navigation Controllers.

Relevant Store Review Guidelines and Requirements

• Ensure Activities do not crash or freeze during startup to meet stability guidelines.
• Follow Android Material Design for UI consistency in Activities.
• Respect user privacy and permissions when Activities request sensitive data.
• Optimize Activity launch time to avoid poor user experience flagged by store reviews.
• Sign your APK or AAB properly before publishing.

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

Possible issues include heavy work on the main thread during Activity startup, loading large resources synchronously, or creating too many Activities unnecessarily. Optimizing by moving work off the main thread and simplifying the UI can help reduce load time.

Key Result

Activities are core to Android apps but can impact memory and smoothness if overused. Optimize by managing lifecycle well, keeping UI light, and using asynchronous loading to maintain 60fps and fast startup.

Practice

1. What is the main role of an Activity in an Android app?

easy

A. It stores app data permanently.

B. It handles network requests only.

C. It manages background tasks without UI.

D. It represents a single screen with a user interface.

Solution

1. Step 1: Understand Activity purpose

   An Activity is designed to show a screen where users interact.

2. Step 2: Compare options

   Only It represents a single screen with a user interface. correctly describes an Activity as a UI screen.

3. Final Answer:

   It represents a single screen with a user interface. -> Option D

4. Quick Check:

   Activity = Screen UI [OK]

Hint: Remember: Activity = one screen in app [OK]

Common Mistakes:

• Confusing Activity with data storage
• Thinking Activity runs without UI
• Mixing Activity with background services

2. Which method is used to set up the UI when an Activity starts?

easy

A. onResume()

B. onStart()

C. onCreate()

D. onPause()

Solution

1. Step 1: Identify lifecycle methods

   onCreate() is called when the Activity is first created to set up UI.

2. Step 2: Eliminate other methods

   onStart() and onResume() happen later; onPause() is for pausing.

3. Final Answer:

   onCreate() -> Option C

4. Quick Check:

   UI setup = onCreate() [OK]

Hint: UI setup always starts in onCreate() [OK]

Common Mistakes:

• Choosing onStart() or onResume() for UI setup
• Confusing onPause() as setup method
• Not knowing Activity lifecycle order

3. What will happen when this Activity code runs?

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

medium

A. The screen shows the layout defined in activity_main.xml.

B. The app shows a blank screen.

C. Nothing happens because onCreate is empty.

D. The app crashes due to missing layout.

Solution

1. Step 1: Analyze onCreate method

   It calls super.onCreate and sets content view to activity_main layout.

2. Step 2: Understand setContentView effect

   This loads and displays the UI from activity_main.xml on screen.

3. Final Answer:

   The screen shows the layout defined in activity_main.xml. -> Option A

4. Quick Check:

   setContentView loads layout = screen shows layout [OK]

Hint: setContentView shows UI layout on screen [OK]

Common Mistakes:

• Assuming onCreate does nothing
• Thinking app crashes without error
• Confusing blank screen with missing layout

4. Identify the error in this Activity code:

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

medium

A. setContentView called before super.onCreate()

B. No error, code is correct

C. Missing call to super.onCreate()

D. onCreate method should not be overridden

Solution

1. Step 1: Check order of calls in onCreate

   super.onCreate() must be called before setContentView to initialize Activity properly.

2. Step 2: Identify mistake

   Here, setContentView is called first, which is incorrect and can cause issues.

3. Final Answer:

   setContentView called before super.onCreate() -> Option A

4. Quick Check:

   super.onCreate() first, then setContentView [OK]

Hint: Always call super.onCreate() before setContentView [OK]

Common Mistakes:

• Calling setContentView before super.onCreate()
• Forgetting to override onCreate
• Not calling super.onCreate() at all

5. You want to start a new Activity called DetailActivity from MainActivity. Which code snippet correctly starts the new Activity?

hard

A. startActivity(DetailActivity::class.java)

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

C. Intent intent = new Intent(DetailActivity)
startActivity(intent)

D. val intent = Intent(DetailActivity)
startActivity()

Solution

1. Step 1: Understand Intent creation

   Intent requires context (this) and target Activity class (DetailActivity::class.java).

2. Step 2: Check startActivity usage

   startActivity(intent) correctly starts the new Activity with the Intent.

3. Final Answer:

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

4. Quick Check:

   Intent(this, TargetClass) + startActivity(intent) [OK]

Hint: Use Intent(this, TargetActivity::class.java) to start Activity [OK]

Common Mistakes:

• Omitting context in Intent constructor
• Calling startActivity without Intent
• Using wrong syntax for Intent creation