A Multithreading Saga, Part 1 (iOS)
This is the first post of a three part series discussing recent performance improvements we made in our iOS app.
Showing 17 of 57 articles (Page 3 of 3)
This is the first post of a three part series discussing recent performance improvements we made in our iOS app.
The Cash App Android app uses presenters because they’re easy to write, easy to review, and result in boring code that just works.
Pinterest found a single tweak that slashed their build times by a jaw-dropping 99%.
Netflix switched to AV1 on Android for sharper video and better compression.
Dropbox used coroutines to load Android data faster and smoother.
Meta’s Hermes makes JavaScript run lean and mean on mobile devices.
Uber teamed up with JetBrains to figure out how Kotlin builds hold up when things get big and messy at scale.
Imagine that you’re new to Android and trying to display an image. You’ve already added the image to your res folder and now you need to get a Drawable.
Skyscanner tackles a billion calculations with efficient, fast solutions.
Kotlin already has TODOs. That’s awesome! but it’s a tad bit aggressive.
Flipkart shrank their Android app below 10 MB for low-bandwidth users.
In case you haven’t heard: RxJava 2 was released sometime back. RxJava 2 was a massive rewrite with breaking apis (but for good reasons).
This was the part that I initially found most tricky to grasp but also most important to know as an AndroidDev (memory leak and all).
Zalando slashed Swift compile times from 12 minutes to just 2 with tweaks.
LinkedIn drops 10 hot tips for making Node.js fly in mobile apps.
LinkedIn tunes Java garbage collection for high speed and low lag.
Dropbox tuned their data model to make their app respond even faster.