Faster startup and data loading
I added caching and changed how the app used its APIs so useful data became available sooner and repeated work was reduced. Typical opening time dropped from 7–8 seconds to 2–3 seconds.
CASE NOTE / 01PRODUCTION / DELIVERY ECOSYSTEM
React Native Delivery App Development for a Faster, More Reliable Platform
Khedmah connects customers, drivers, and vendors across ordering, payment, fulfilment, notifications, rewards, and live tracking. I worked on the React Native apps with the product, backend, and QA teams, focusing on startup speed, rendering, interaction quality, and production stability. Typical opening time fell from 7–8 seconds to 2–3 seconds, while crash-free sessions improved from 90% to 100% during a measured three-month period.
Case study by Girraj Sharma
- Google Play downloads
- 100K+
01 / THE CHALLENGE
What needed to improve.
A delivery action rarely belongs to one app. A customer order affects vendor fulfilment, driver availability, payment state, tracking, notifications, rewards, and support. The three mobile roles needed to show the same dependable order state without making any one experience feel slow or fragile.
The product also had measurable performance and stability problems. Startup could take four to eight seconds, unnecessary re-renders made complex screens less responsive, and production issues needed root-cause fixes. Any change had to fit an active release process without disrupting ordering and payment flows.
02 / THE SOLUTION
Changes tied to measurable product quality.
The work focused on the parts users notice directly: how quickly the app becomes useful, how smoothly important screens respond, whether integrations remain dependable, and whether a release improves the full customer, driver, and vendor journey.
Smoother interactions
I reduced unnecessary component re-renders and added animation where it helped users understand a change or action. Event tracking also informed Figma-led revisions that made useful customer features easier to find.
Production stability
I traced production issues to their underlying causes, improved API and error-state handling, and used Firebase data to check the effect after release. AppCenter CodePush provided a faster route for suitable hotfixes between store submissions.
Connected delivery flows
I built and maintained features across authentication, orders, payments, push notifications, loyalty rewards, and live tracking. Close coordination with product, backend, and QA kept behaviour consistent across customer, driver, and vendor apps.
Technology used
03 / SYSTEM VIEW
How the product was structured.
Khedmah DeliveryMOBILE PRODUCT
Shared order lifecycle across three mobile roles
Defensive API and error-state handling
Secure payment and notification flows
OTA release path with post-release monitoring
04 / RESULTS & IMPACT
What changed.
2–3 secReduced from 7–8 seconds · approximately 67% less startup time using range midpoints
100%Crash-free sessions during a measured three-month period, improved from 90%
100K+Public Google Play downloads
This React Native delivery app development work improved the product without separating performance, interface quality, and release stability into unrelated tasks. Khedmah became faster to open, smoother to use, and more dependable across important delivery journeys.
MY ROLEBuilt mobile features and integrated APIs for orders, payments, notifications, loyalty rewards, and live tracking. Worked with product, backend, and QA teams on production releases.
RELATED SERVICES
Need help improving a React Native product?
Discuss the app