Explore 892 articles on Android performance

Clear Filters

Showing 12 of 892 articles (Page 45 of 45)

Natalia Ukhorskaya from JetBrains shows how Kotlin's seamless Java interop makes adoption frictionless. Just create a .kt file and let IntelliJ do the heavy lifting.

JetBrains made history in 2013 by bringing Kotlin to Android Studio for the first time. This walkthrough from the early days shows just how far Android development has come.

Etsy's Device Lab

Company: Etsy · Aug 9, 2013
Platform: iOS / Android

When mobile traffic jumped from 25% to 40% in six months, Etsy knew they had a problem. Their engineers were testing on personal iPhones while users browsed on dozens of different devices.

Twitter built a 2FA system where your private keys never leave your phone and the server stores no persistent secrets. Here's the engineering behind it:

Twitter's iOS team shipped beta builds to employees and discovered crashes that would never show up in testing. The culprit? Jailbroken devices and unprefixed Objective-C categories.

Brian Smith from Dropbox introduced an API in 2013 that promised to make cloud sync feel like working with local files. Developers loved it, but there's a twist.

Low Latency Switching in Signal

Company: Signal · Jan 31, 2013
Platform: Android

Signal's team discovered that building encrypted voice calls was easy. Building a VoIP system that actually worked well? That was the hard part.

Christine Tieu from Twitter's Mobile Web Team reveals how they flipped their entire mobile UI for Arabic and Farsi without drowning in duplicate CSS rules.

Instagram's Android launch brought 1 million new users in 12 hours. Here's how their infrastructure team kept the lights on during hypergrowth.

LinkedIn Engineering discovered that one synchronous file write operation tanked their Node.js throughput from thousands of requests per second to just dozens.

Most Memory Leaks Are Good

Company: Shopify · Oct 14, 2011
Platform: Android

Shopify Engineering shares a war story: their app servers were hitting 16GB+ memory usage, crashing with ENOMEM errors, and requiring constant restarts. The culprit? Not where they expected.

SoundCloud's mobile team hit a wall: their API-first approach broke down when browsers couldn't handle CORS redirects properly. Their solution? A proxy architecture that evolved from nginx to Node.js.

Prev 45 / 45
Next
Loading articles...