mobile-review

Reviewing React Native code for platform standards and performance issues involves evaluating list rendering, animation drivers, and Apple HIG or Material Design 3 compliance. You can run a mobile code review pass on targeted directories to catch these anti-patterns.

Mobile code review for accessibility and offline resilience is the process of auditing source files to ensure assistive-label coverage, offline persistence, and error retry states are present. It catches omissions in these categories before release.

Checking Flutter source files for security gaps and logging hygiene requires inspecting secrets handling and launch-time workload during a code review pass. This process identifies compliance failures and provides remediation suggestions based on severity.

Yes, the mobile code review process works for both iOS and Android files by evaluating Swift and Kotlin source. It confirms platform-specific typography scaling, touch target sizes, and gesture behavior for the relevant operating system.

The best way to automate mobile code reviews for native standards is running a targeted review pass on specific file paths or directories. This evaluates performance, platform standards, security, offline resilience, and accessibility in a single operation.

Yes, you need a project CLAUDE.md file because the review process requires inspecting it for stack identification. This determines whether the evaluation applies to React Native, Flutter, iOS, or Android files during the compliance checks.