How We Reduced GrabX SDK Initialisation Time
Grab speeds up their GrabX SDK startup to get users rolling quicker.
Search over 1000 articles on mobile performance
Showing 16 of 16 articles (Page 1 of 1)
Grab speeds up their GrabX SDK startup to get users rolling quicker.
Our GrabX clients noticed that the GrabX SDK tended to require high memory and CPU usage. From this, we saw opportunities for further improvements that could:
Grab keeps their app steady when ride demand spikes out of nowhere.
Grab lightens the load on memory and CPU in their GrabX SDK.
Grab digs into high latency in their Market Store and fixes it fast.
Grab finds and clears bottlenecks in their Go-based apps with care.
Grab uses profile-guided tweaks to make their apps run smoother.
Grab shares how they made their super app lightning-fast for daily use.
Grab chases every millisecond to make their super app blazing fast.
Grab finishes with patterns and chaos testing for unbreakable systems.
Grab adds bulkheads, balancing, and fallbacks for resilient apps.
Grab starts building tough systems with rate limiting to stay strong.
Grab keeps Redis steady when pipeline calls hit hard and heavy.
Grab’s Project Bonsai spruces up their mobile dev process nicely.
Grab splits their app into modules to scale big and stay nimble.
Grab logs smartly to troubleshoot app issues quick and painlessly.