pittsdev_
NotesBook intro call
React Native Performance Consulting

I make slow React Native apps fast.

A fixed-price performance audit for React Native and Expo apps that are slow, janky, or built fast and now need to be production-hardened. You get a prioritized findings report and a fix for every finding — written up, packaged as AI-ready prompts, or shipped by me, depending on tier. Not a proposal for more billable hours.

Book a 30-min intro callSee what’s in the audit
$pittsdev audit --target=performance --devices=real
01/Why this matters

Slow apps lose users. Quietly.

Performance problems don’t announce themselves in your roadmap. They show up as churn, one-star reviews, and checkout flows people abandon before they convert.

  • Cold start takes 4+ seconds and onboarding drop-off shows it
  • Scrolling stutters on the exact screens where users spend money
  • App Store reviews say "slow" and "laggy" more than anything else
  • Sentry is full of ANRs and OOM crashes nobody has time to triage
  • Every feature ships a little heavier, and nobody owns the regression
  • It was built fast — maybe with AI tools — and now it has to survive real traffic

Users don’t file bug reports about a 4-second cold start or a stuttering list. They just leave. If any of the above sounds familiar, the problem is measurable, findable, and fixable — but only if someone actually measures it.

02/The audit

What the performance audit covers.

Not vague consulting. A defined engagement with concrete deliverables, measured against your real users on real devices.

01

Startup time analysis

Cold and warm start traced end to end — native init, bundle load, JS execution, time to first meaningful render — with the biggest contributors ranked.

02

Frame drops & jank

The screens and interactions where you're dropping frames, profiled on real devices your users actually own, with the root cause behind each one.

03

Memory issues

Leaks, retained images, listener buildup, and the OOM crashes they produce — the ones your crash reporter buckets as low priority while they eat sessions.

04

Bundle size breakdown

What's actually in your JS bundle, what's loading eagerly that shouldn't be, and where code splitting and lazy loading pay off.

05

Render-cost hotspots

The components re-rendering too often or too expensively — found with profiling, not guessing — including whether React Compiler adoption is worth it for your codebase.

06

A fix for every finding

No finding is left as "investigate further." Depending on tier, each one comes with written fix instructions, a ready-to-run AI prompt, or a pull request I ship myself.

07

Prioritized findings report

Every finding severity-rated, with evidence, user impact, and an effort estimate. Sequenced so your team knows what to fix first and why.

08

Findings call (60 min)

Walk through the report with your team. Decide what to fix, in what order, and who does it — you, your team, or a follow-on engagement.

Findings your team can start acting on the day the report lands.

03/Why me

This is my day job, at scale.

PittsDev is run by Ben Pitts, a senior React Native engineer who works on performance for one of the largest retail apps in the country — millions of users, real revenue on the line, and a performance regression is a business problem, not a backlog ticket.

That work includes leading React Compiler adoption in a large production codebase, Sentry-driven performance triage against real-user data, and render-cost analysis to find and eliminate the components quietly burning frame budget.

The audit is the same discipline applied to your app: measure first, rank by user impact, fix the highest-leverage problems first. No guessing, no premature rewrites.

04/How it works

Audit → findings → fixes.

The audit is the entry point. It stands on its own — and if you want the bigger fixes executed too, the report becomes the scope for that engagement.

  1. 01

    Intro call

    30 min
    You describe the symptoms, I tell you honestly whether an audit will help. No prep, no pitch deck.
  2. 02

    Kickoff

    60 min
    Read-only repo access, production monitoring access (Sentry or equivalent), and agreement on the metrics that matter to you.
  3. 03

    The audit

    5–15 business days
    Profiling on real devices, trace analysis, render-cost measurement, bundle inspection. Duration scales with the tier you pick.
  4. 04

    Findings report

    Written, prioritized
    Every issue severity-rated with evidence, user impact, and an effort estimate — sequenced so the highest-leverage work comes first.
  5. 05

    Findings call

    60 min
    Walk through the report with your team. You leave knowing exactly what to fix and in what order.
  6. 06

    Fixes

    Per tier
    Your team works from the fix plan, runs the AI-ready prompts, or reviews the PRs I've shipped — depending on the tier you chose.
  7. 07

    Optimization engagement

    Optional
    For the findings too big for quick wins. Fixed-scope, priced from the report, with your audit fee credited toward it.
05/Pricing

Same audit. Three ways to get the fixes done.

Every tier includes the full audit, the prioritized findings report, and the findings call. The tiers differ in one thing: how much of the fixing lands on your team versus me. Fixed price, confirmed in writing before anything starts.

Audit + Fix Plan
$3,500
5–7 business days

The full audit and findings report. Every finding includes a written fix: what to change, where, and the expected impact. Your team executes at their own pace.

Most popular
Audit + Fix Prompts
$5,000
7–10 business days

Everything in Fix Plan, plus each finding packaged as a ready-to-run AI prompt — scoped for Cursor or Claude, loaded with codebase context and acceptance criteria — so your team ships the fixes in days, not sprints.

Audit + Shipped Fixes
$7,500
10–15 business days

Everything in Fix Prompts, plus I personally implement the highest-leverage quick wins — typically the top 3–5 findings — as pull requests your team reviews and merges.

After the audit: optimization engagement

Some findings are bigger than quick wins — list architecture rewrites, navigation restructuring, startup re-sequencing. If the report surfaces work like that and you want me to execute it, we scope a fixed-price engagement directly from the findings, with your audit fee credited toward it.

Not sure which tier fits? Book the intro call — sizing it is half the point of the call.

06/FAQ

Common questions.

01How is this different from hiring a React Native contractor?
A contractor bills hours to build features. This is a fixed-price diagnostic engagement with a defined deliverable: a prioritized report of what's making your app slow, plus the quick wins already shipped. You know the cost and the output before you commit, and you're not paying someone to learn performance work on your codebase.
02Our app was built quickly with AI tools. Is that a problem?
No — it's one of the most common profiles I see. Apps built fast with Cursor, v0, Bolt, or similar tools usually work, but carry predictable performance debt: unnecessary re-renders, eager loading, bloated bundles, no memoization strategy. The audit finds exactly that and gives you a concrete path to production-ready, without rewriting the app.
03What access do you need?
Read-only repo access and access to your production monitoring (Sentry, Crashlytics, or equivalent). Real-user data is where performance problems actually show up — profiling in a simulator only tells you half the story. I don't push to production and I don't need write access; on the Shipped Fixes tier, fixes go up as PRs your team reviews and merges.
04Do you fix the problems, or just report them?
That's what the tiers are for. Every tier gets the full audit and a concrete fix for each finding. At $3,500 your team executes from written fix instructions. At $5,000 each fix also comes as a ready-to-run AI prompt your team can execute in Cursor or Claude. At $7,500 I implement the highest-leverage fixes myself as PRs. Larger structural work becomes a separate fixed-scope engagement priced from the report.
05What are the AI-ready fix prompts, exactly?
Each finding gets a self-contained prompt: the relevant file paths and code context, the specific change to make, the constraints to respect, and acceptance criteria to verify the fix worked. Your engineers run them in Cursor or Claude and review the output like any PR. It's the difference between handing your team a diagnosis and handing them a prescription they can fill the same afternoon.
06What if the audit doesn't find much?
Then you get something almost as valuable: evidence that your performance problem is somewhere other than where you thought — backend latency, network, or product design — and you stop spending engineering time optimizing the wrong layer. That said, I've yet to profile a production React Native app that didn't have meaningful, fixable hotspots.
07Why fixed price instead of hourly?
Hourly billing rewards slow work. Fixed price means you know the cost up front and I'm paid to deliver findings, not to accumulate hours. If the analysis runs long, that's my problem, not your invoice.
Next step

Find out exactly why your app is slow.

Book a free 30-minute intro call. Bring the symptoms — I’ll tell you whether an audit will find the cause. If it won’t, I’ll tell you that too.

Book the call