Explore 10 articles from LinkedIn on mobile performance
Showing 10 of 10 articles (Page 1 of 1)
LinkedIn's Android test suite hit tens of thousands of tests, pushing execution times into the danger zone. Developer productivity was tanking.
LinkedIn processes massive volumes of mobile crash data to keep their app stable for millions of users. Here's how they built the pipeline.
LinkedIn built their own crash reporting system instead of using third-party tools. Here's why that decision paid off.
LinkedIn shipped a 75KB mobile experience that loaded in under 6 seconds on 100 Kbps connections. Six engineers built it in four months.
LinkedIn's iOS team set an audacious goal: ship to production three times daily, with just three hours from commit to release. Here's how they actually pulled it off.
LinkedIn rebuilt their Android data pipeline from scratch for their flagship app. The result? A system that handles everything from feed updates to messaging while keeping data consistent across screens.
LinkedIn went from monthly releases to shipping mobile code 3x per day. Here's how they automated their way out of a month-long release cycle.
LinkedIn Engineering cut their tail latency by 75% through systematic garbage collection tuning. Here's their playbook for high-performance Java apps.
LinkedIn ships a single mobile binary but runs dozens of A/B tests simultaneously. Here's how they pulled it off without constant app releases.
LinkedIn Engineering discovered that one synchronous file write operation tanked their Node.js throughput from thousands of requests per second to just dozens.