AXIOM Reviewed a 2,000+ Line Android PR

[salmanashraf]

Axiom-recording.mov

I tested AXIOM against a real Android codebase to see whether it could identify production-level engineering issues beyond simple lint warnings.

What AXIOM Found

Memory Leak Risk

Problem

Each call to:

• saveMessage()
• setReplyStatus()
• deleteMessage()

created a brand-new CoroutineScope(Dispatchers.IO) with no lifecycle ownership and no cancellation path.

This creates fire-and-forget background work that can continue running even after the caller is gone.

AXIOM Recommendation

Use a shared class-level scope with:

kotlin SupervisorJob() + Dispatchers.IO

to avoid orphaned coroutine work and improve lifecycle safety.

---

Dependency Injection Cleanup

Problem

@ApplicationContext was already being injected, but .applicationContext was called again.

AXIOM Recommendation

Use the injected context directly.

This removes redundant code and improves clarity.

---

Firestore Error Handling

Problem

Multiple Firestore operations used:

kotlin runCatching { }

without surfacing failures to the caller.

Errors were silently swallowed.

AXIOM Recommendation

At minimum:

• Log failures
• Emit error states to the ViewModel
• Allow UI to react appropriately

---

Serialization Cleanup

Problem

Repeated fully-qualified:

kotlin kotlinx.serialization.builtins.ListSerializer

references were used despite already having the import.

AXIOM Recommendation

Use the existing import instead of repeating the fully-qualified reference.

---

Why This Matters

Most AI code reviewers focus on style.

AXIOM focuses on:

• Architecture
• Lifecycle safety
• Concurrency risks
• Memory leaks
• Performance bottlenecks
• Maintainability

The goal is not to generate code.

The goal is to help mobile engineers ship safer production apps.

---

Mobile Agency

Mobile Agency is an open-source collection of AI-powered specialists for:

• Android
• iOS
• Flutter
• React Native
• Unity
• Unreal

Repository:

https://github.com/salmanashraf/mobile-agency

Would love feedback from Android engineers:
What engineering issue should AXIOM learn to detect next?