⚡ Optimize compose flow collection using collectAsStateWithLifecycle

[SayanthRock]

User description

💡 What: Replaced collectAsState() with collectAsStateWithLifecycle() in Compose UI screens. Added androidx-lifecycle-runtime-compose dependency across feature modules.
🎯 Why: collectAsState continues to collect flows even when the app is in the background, consuming unnecessary CPU and memory. collectAsStateWithLifecycle avoids this by automatically pausing collection when the lifecycle falls below STARTED.
📊 Measured Improvement: Replaced in 7 UI screens. Programmatically measuring the exact background CPU usage difference in unit tests is noisy and impractical for this specific change, but this is a standard, highly recommended Jetpack Compose performance optimization that strictly prevents background flow collection.

---

PR created automatically by Jules for task 6991967691959018058 started by @SayanthRock

---

CodeAnt-AI Description

Use lifecycle-aware state collection in Compose screens

What Changed

• Several screens now stop collecting UI state when they are not visible, which reduces background work while the app is paused or in the background
• Added the lifecycle-compose dependency to the affected feature modules so these screens can use lifecycle-aware collection
• Updated the auth, home, releases, repositories, settings, updates, and workflows screens to use the new collection behavior

Impact

✅ Lower background battery use
✅ Fewer unnecessary CPU cycles in the background
✅ Smoother screen updates when returning to the app

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	766a490	Jul 24, 2026 · 12:52	12:53

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Warning

Review limit reached

@SayanthRock, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 50 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3012790e-83d7-4761-a5ec-bb557062bd5f

📥 Commits

Reviewing files that changed from the base of the PR and between 3a029e2 and 766a490.

📒 Files selected for processing (15)

• feature-auth/build.gradle.kts
• feature-auth/src/main/java/com/sayanthrock/rockreleasehub/feature/auth/AuthScreen.kt
• feature-home/build.gradle.kts
• feature-home/src/main/java/com/sayanthrock/rockreleasehub/feature/home/HomeScreen.kt
• feature-releases/build.gradle.kts
• feature-releases/src/main/java/com/sayanthrock/rockreleasehub/feature/releases/ReleaseListScreen.kt
• feature-repositories/build.gradle.kts
• feature-repositories/src/main/java/com/sayanthrock/rockreleasehub/feature/repositories/RepoListScreen.kt
• feature-settings/build.gradle.kts
• feature-settings/src/main/java/com/sayanthrock/rockreleasehub/feature/settings/SettingsScreen.kt
• feature-updates/build.gradle.kts
• feature-updates/src/main/java/com/sayanthrock/rockreleasehub/feature/updates/UpdateScreen.kt
• feature-workflows/build.gradle.kts
• feature-workflows/src/main/java/com/sayanthrock/rockreleasehub/feature/workflows/WorkflowListScreen.kt
• gradle/libs.versions.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch performance-collectasstatewithlifecycle-6991967691959018058

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[ai-coding-guardrails]

Nice work! 😎

I didn't find anything of concern

Risk: 🟢 Low

Risk analysis

The highest scoring dimensions are blast_radius and test_coverage. Blast_radius is elevated because the change affects 7 UI screens across multiple feature modules, increasing the surface area of potential impact. Test_coverage is low because the change involves replacing one function call with another and lacks explicit unit or integration tests to validate behavior under different lifecycle states. Other dimensions score low as there are no apparent security, data integrity, or major operational risks introduced by this diff.

Reviewed with 🤟 by Zenable