React Native performance audit
Stuttering lists, a frozen tab, a battery that melts: React Native performance can be measured, understood and fixed. Before optimising, I measure. At Odisei Music the result was steady 120 fps, CPU down 40%, memory down 20%.
The method: measure first
An audit starts with measurements on your real screens, low-end devices included: re-render profiling, JS thread and native, memory, startup time. Every issue is quantified and reproduced before being fixed. No gut-feeling optimisation, no cosmetic refactor.
What you receive
A prioritised report: root causes, their measured cost, and the fix plan ordered by return. I can then apply the fixes myself or support your team doing it, with before/after measurements.
What I do
- Full profiling: re-renders, JS thread, native, memory, startup.
- Lists and scroll: virtualisation, Legend List, images.
- Animations: Reanimated, worklets, frame budget at 60 and 120 Hz.
- Bundle and startup: lazy loading, Hermes, JS size.
- Prioritised, costed report, then fixes, measured before/after.
Missions that prove it
Frequent questions
Which symptoms justify an audit?
A stuttering scroll, slow screens, an app that heats up or drains the battery, memory crashes, startup beyond two seconds. If your users can feel it, it can be measured, and if it can be measured, it can be fixed.
How long does an audit take?
The initial diagnosis usually fits in a week. Fixing depends on the findings: sometimes two days handle the bulk of the problem, sometimes it is a project we plan together, ordered by return.
Which apps do you work on?
Any React Native or Expo app in production or preproduction, including inherited or AI-generated codebases. The entry point is the same: reproduce, measure, fix.
Got a project in mind?
Guaranteed reply within the hour, plus a free thirty-minute video audit.