Girraj Sharma

← Freelance

Freelance

React Native performance and crash fixes

I help teams diagnose and fix slow startup, rendering issues and crashes in React Native apps. Each engagement starts with a specific problem and a measured baseline, then addresses the code and data flow behind it.

Scope of work

Startup and data loading

Analysis of API calls, local data and blocking work during app launch. On Khedmah Delivery, caching and API changes brought typical opening time down from 7–8 seconds to 2–3 seconds.

Rendering

Reduction of unnecessary re-renders, slow lists and repeated work on complex screens. On Khedmah, this included animation and layout refinements guided by event-tracking data.

Crashes

Firebase Crashlytics and Sentry reports are used to connect crashes to specific user flows and releases. On Khedmah, crash-free sessions went from 90% to 100% over one measured three-month period.

Offline data

Local-first reads with background sync improve responsiveness and keep apps usable on poor connections. On SnapHatch, this produced a measured 20% faster startup.

Process

  1. Identify the screens, devices and user actions that are affected.
  2. Look at existing measurements, crash reports and the relevant code.
  3. Fix the most important causes first, then measure the same flow again.
  4. Document the changes and what to monitor after release.
  • Khedmah DeliveryA multi-sided delivery platform in Oman with separate React Native apps for customers, vendors and drivers.
  • SnapHatchA fly-fishing guide with insect identification, a catch log and map-based hatch reports, built for areas with limited coverage.
  • Making a React Native app fasterArticle on the startup, rendering and local-data work behind these results.

Questions

How are improvements measured?

The affected flow is measured before any changes and again afterwards, using the same method.

Can we start with a single issue?

Yes. A focused engagement on one screen or one crash is a good starting point.

Do you also make UI changes?

Yes, where UI changes support the performance or usability goals.