Mobile App Quality Audit

Download SKILL.mdGet Murage How skills work

Open source. macOS, Windows and Linux.

At a glance

What it is

Comprehensive mobile application quality assessment covering performance, UX, accessibility, security, and app store compliance to produce an actionable audit scorecard.

A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.

File: SKILL.md
Length: 345 lines2,250 words, about 11 min read
Category: Software engineeringmobile development
Level: Advanced
License: Apache-2.0

More software engineering skills.

The full skill.

The whole file, exactly as it downloads. Read it before you rely on it.

SKILL.md

345 lines · 2,250 words

Download

Mobile App Quality Audit

You are a senior mobile engineer specializing in app quality auditing. Your role is to systematically evaluate a mobile application across performance, user experience, accessibility, security, and platform compliance to produce a structured audit scorecard with prioritized improvements. You evaluate apps from the perspective of users, developers, and platform reviewers.

When to Use

Use this skill when:

User asks about mobile app quality audit techniques or best practices

Put this skill to work.

Questions.

What is the Mobile App Quality Audit skill?

Comprehensive mobile application quality assessment covering performance, UX, accessibility, security, and app store compliance to produce an actionable audit scorecard.

How much does it cost?

Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.

Can I change it?

Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.

Give your first job to Murage.

Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.

Download Murage

No account needed · Runs on the AI plan you already pay for

Score	Criteria
1	App launch >5s. Frequent ANR/freezes. Scrolling is janky. Memory leaks cause crashes. Battery drain is extreme.
2	Launch 3-5s. Occasional stuttering. Some screens are slow. Memory usage grows over time.
3	Launch 2-3s. Mostly smooth scrolling. Acceptable memory footprint. Battery usage reasonable.
4	Launch <2s. Consistent 60fps. Efficient memory usage. Battery impact minimal. Offline capability for core features.
5	Launch <1s. 120fps on supported devices. Exemplary resource efficiency. Background processing optimized. Predictive preloading.

Score	Criteria
1	Non-standard navigation. Confusing flows. No loading states. Error messages are cryptic. Inconsistent design.
2	Basic navigation. Some UX issues. Inconsistent interaction patterns. Limited feedback for user actions.
3	Standard platform navigation patterns. Consistent design system. Loading and error states handled. Reasonable onboarding.
4	Polished UX. Delightful interactions. Smooth transitions. Contextual help. Gesture support. Platform-idiomatic design.
5	Exceptional UX. Anticipates user needs. Personalized experience. Haptic feedback. Microinteractions. Accessibility as a feature.

Score	Criteria
1	Crash-free rate <95%. Frequent crashes in core flows. No crash reporting. Users lose data on crash.
2	Crash-free rate 95-97%. Known crashes in specific flows. Basic crash reporting. Some data loss on crash.
3	Crash-free rate 97-99%. Crashes are non-critical edge cases. Crash reporting with symbolication. Graceful recovery.
4	Crash-free rate 99-99.5%. Proactive crash monitoring. Auto-recovery from errors. State preservation on crash.
5	Crash-free rate >99.5%. Near-zero crashes. Predictive error prevention. Full state recovery. Automated crash triage.

Score	Criteria
1	No offline support. Crashes without network. Excessive API calls. No caching. Large payloads.
2	Basic error handling for no network. Minimal caching. Redundant API calls. No request optimization.
3	Graceful offline handling. Response caching. Reasonable payload sizes. Request deduplication.
4	Offline-first for key features. Smart caching strategy. Optimized payloads. Request batching. Background sync.
5	Full offline capability. Conflict resolution for sync. Edge caching. Adaptive quality based on connection. Delta syncs.

Score	Criteria
1	No accessibility support. Screen readers cannot navigate. No content descriptions. Touch targets are tiny.
2	Partial accessibility. Some labels present. Screen reader can navigate basics. Insufficient contrast in places.
3	VoiceOver/TalkBack works for main flows. Adequate touch targets. Reasonable contrast. Dynamic type partially supported.
4	Full screen reader support. Dynamic type/font scaling. High contrast mode. Reduced motion support. Comprehensive labels.
5	Exemplary accessibility. Custom accessibility actions. Braille support. Switch control tested. Cognitive accessibility considered. Accessibility testing automated.

Score	Criteria
1	Data stored in plaintext. No certificate pinning. Sensitive data in logs. No obfuscation. Hardcoded secrets.
2	Basic encryption for credentials. No jailbreak detection. Some sensitive data exposure. Minimal network security.
3	Keychain/Keystore for credentials. TLS for all connections. No sensitive data in logs. Basic obfuscation.
4	Certificate pinning. Biometric authentication. Root/jailbreak detection. Encrypted local storage. Runtime protection.
5	Advanced security. Tamper detection. Secure enclave usage. Automated security scanning. Penetration tested. Threat model maintained.

Score	Criteria
1	Multiple guideline violations. App rejected repeatedly. Privacy policy missing. No age rating.
2	Marginal compliance. Occasional review issues. Privacy labels incomplete.
3	Compliant with guidelines. Privacy labels and policy current. Appropriate age rating. In-app purchase rules followed.
4	Proactive compliance. App preview/screenshots optimized. ASO basics covered. All metadata complete and compelling.
5	Exemplary store presence. A+ compliance. Rich preview content. Localized listings. Regular metadata optimization.

Score	Criteria
1	No architecture. Massive view controllers/activities. No tests. Dependency management absent.
2	Some architecture patterns. Minimal tests. High coupling. Outdated dependencies.
3	Clear architecture (MVVM, Clean, etc.). Unit tests for business logic. Dependency injection. CI/CD pipeline.
4	Well-structured codebase. Comprehensive test coverage. Modular architecture. Automated builds and testing.
5	Exemplary code quality. Full test pyramid. Feature flags. Modular for team scaling. Automated quality gates.

Score Range	Quality Level	Interpretation
4.5 - 5.0	Excellent	Top-tier app quality. Focus on delighting users and staying ahead.
3.5 - 4.4	Good	Solid app. Address specific gaps for a best-in-class experience.
2.5 - 3.4	Adequate	Functional but room for improvement. Users may prefer competitor apps.
1.5 - 2.4	Poor	Significant quality issues. Ratings will suffer. Urgent improvements needed.
1.0 - 1.4	Critical	App is nearly unusable. Risk of store removal. Emergency intervention needed.

Mobile App Quality Audit

More software engineering skills.

The full skill.

Mobile App Quality Audit

When to Use

Put this skill to work.

Questions.

Give your first job to Murage.

Search murage.ai

Mobile App Quality Audit

More software engineering skills.

The full skill.

Mobile App Quality Audit

When to Use

Put this skill to work.

Questions.

Give your first job to Murage.

Create a bot and use this skill.

Ask Ember to create the bot

Open the bot’s skills

Find Mobile App Quality Audit and switch it on

Ask the bot for the job

About this skill.

Questions to Ask First

App Context

Technical Context

Business Context

Assessment Framework

Dimension 1: App Performance (Weight: 20%)

What to Measure

Dimension 2: User Experience Design (Weight: 15%)

What to Evaluate

Dimension 3: Stability and Crash Handling (Weight: 15%)

What to Measure

Dimension 4: Network Efficiency (Weight: 10%)

What to Evaluate

Dimension 5: Accessibility (Weight: 10%)

What to Evaluate

Dimension 6: Security (Weight: 15%)

What to Evaluate

Dimension 7: App Store Compliance (Weight: 10%)

What to Evaluate

Dimension 8: Code Quality and Maintainability (Weight: 5%)

Scoring Template

Results Interpretation

Recommendations by Priority

Critical Fixes (This Sprint)

High Priority (This Month)

Medium Priority (This Quarter)

Strategic (This Half)

Report Template

Process

Output Format

Edge Cases

Example