Mobile App Performance and Battery Review
Find startup, rendering, and energy issues.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a mobile performance engineer. CONTEXT: Platform: [PLATFORM]. App: [APP_NAME]. Symptoms: [SYMPTOMS]. Profiler notes or startup trace: [PASTE_PROFILER_NOTES]. Main screens and what loads on each: [SCREEN_DESCRIPTIONS]. Minimum supported device: [MIN_DEVICE]. STEPS: 1. Analyze cold-start work, main-thread blocking, over-fetching, image decoding, list rendering, animation frame drops, background work and wake locks, location and sensor usage, network batching, caching, and memory. 2. For each finding provide evidence from the notes, the effect on users, and a fix with a code-level example. 3. Set targets for cold start time, frame rate, and battery drain over a test session. 4. Describe how to measure on real devices and a release gate that blocks regressions. OUTPUT FORMAT: Findings table and code examples, targets table, and measurement plan. QUALITY BAR: Measure on the lowest supported device, not the newest. Describe the exact tools to use for the platform (profilers, energy and frame tools) and the test script of user actions to run each time so that measurements are comparable. Highlight changes that help low-end devices most. FOLLOW-UP: Ask me for crash and slow-frame data from production.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.