I aligned on scope: Ola Driver app, widespread crashes after the latest release, mostly on older Android devices with low RAM. The issue began immediately after an update that introduced heavy navigation features.
The pattern showed crashes mainly during the navigation step—especially when routes recalculated or when drivers entered low-network areas. No other apps or competitors faced similar problems, confirming it’s internal. Inflation and reduced driver income likely led to more drivers using older devices, compounding the issue.
The probable causes were memory overload from large map data, poor handling of low network conditions, and overuse of system resources by new real-time navigation features.
Root cause: the new navigation module exceeded the memory and network tolerance of older Android devices, causing out-of-memory crashes and app freezes during route recalculation or poor connectivity.
Immediate actions:
Roll back the latest update or disable heavy navigation layers via remote config for low-end devices.
Release a hotfix optimizing the navigation SDK by limiting real-time data, reducing map cache size, and fixing memory leaks.
Communicate clearly to drivers about updating the app and provide temporary solutions such as using offline navigation.
Closely monitor crash logs in real time segmented by device model, OS version, and app version.
Staff a priority support queue for drivers facing crashes and provide goodwill credits where applicable.
Long-term solutions:
Optimize app architecture for backward compatibility and low-memory devices.
Introduce offline or lightweight navigation modes with fewer graphics and smaller data consumption.
Add automated crash regression tests and device-based gating before rollouts.
Implement feature-flag-based rollout control so heavy modules can be dynamically disabled.
Metrics to measure success:
North star: crash-free rate ≥ 99.5%.
Supporting: crash reports from older devices ↓ by 80%, driver satisfaction ↑, trip completion rate restored to baseline.
Counter: no rise in GPS or navigation errors post-fix.
Summary: the crashes were caused by memory and network overload from the recent navigation update. The fix involves immediate rollback and optimization, followed by long-term architectural hardening and improved rollout gating to ensure future stability.