Showing 20 of 35 articles (Page 1 of 2)
At Wealthfront, testing is one of our core engineering principles—in the form of unit and end-to-end testing on all platforms. The iOS team in particular manages its own CI infrastructure to run tests against an integration server
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:
We had a single developer when we first released our iOS app in October 2012. Over the past 12 years, our team of software engineers has grown tremendously
This story is not about pretty code, it is even less about pretty design.
When Cash App was originally developed we had a single service powering all backend functionality, codenamed “Franklin”.
Skeelo tunes Node.js concurrency to keep their app humming along.
Principal iOS engineer Joel Kin shares more about Handshake's choice in our API development using GraphQL on iOS and how it best serves our users.
Meta adopts xHE-AAC to pump up audio quality across their apps.
Grab lightens the load on memory and CPU in their GrabX SDK.
Swiggy puts their app on a diet, trimming size without losing flavor.
Klarna shares six big lessons from speeding up their Node.js service.
Zomato boosted iOS compile speed by 99% with major tune-ups.
Grab finds and clears bottlenecks in their Go-based apps with care.
Klarna ditched caching and somehow boosted mobile speed by 25%.
Swiggy cuts Xcode compile times with advanced, practical tweaks.
Snapchat’s EfficientFormer brings speedy vision transformers to mobile.
Grab uses profile-guided tweaks to make their apps run smoother.
Code is much like a conversation, and misunderstandings can happen when assumptions aren’t stated upfront. It brings to mind a quote (perhaps apocryphal) from the Enlightenment philosopher Voltaire
Tokopedia slashed iOS build times by 1000% with bold moves.
Walmart’s ACF tool auto-generates clean code for consistency.