Explore 695 articles on iOS performance
Showing 20 of 695 articles (Page 30 of 35)
Tobias Carryer from Hootsuite built a reusable iOS framework during his summer internship—a sliding drawer component inspired by Apple Maps. Here's how he turned it into a production-ready, testable framework t...
Arseny Batyrov from Badoo's QA team built the mobile testing guide he couldn't find anywhere else. After combing the internet for tool comparisons and finding nothing comprehensive, he created this definitive b...
Arseny Batyrov from Badoo's QA team built the mobile testing guide he couldn't find anywhere else. His comprehensive breakdown of autotesting tools reveals which ones actually matter in 2018.
Valerii Che from Badoo's iOS team reveals why they ditched Storyboards and XIBs entirely. Their code-first approach handles weekly feature releases without breaking existing functionality.
Valerii Che from Bumble's engineering team reveals why they ditched Storyboards entirely. Their code-first approach handles weekly feature releases without breaking existing functionality.
Slack's engineering team faced a classic scale problem: three platforms, three definitions of 'app launch,' and zero ability to compare performance meaningfully.
Skyscanner's iOS team discovered their app was lagging on nearly half their user base. The culprit? Testing only on high-end devices.
Alexander shows how a simple A/B test doubled in-app currency purchases from 2% to 4% at Badoo. Here's how to build the same testing framework in Swift.
Alexander from Bumble's engineering team built a client-side A/B testing framework in Swift that takes just 1-2 minutes to implement per new test. No server infrastructure required—just protocols, generics, and...
Martin Moizard from BlaBlaCar tackles a common RxSwift pain point: how do you elegantly track loading states without breaking reactive programming principles?
Emily Putze from Google Play reveals why your mobile game launch strategy is probably outdated. The old playbook that worked in 2014's gold rush era is now a recipe for expensive failure.
Zalando proved that every 100ms of loading time equals real money: a 0.7% revenue lift per session. When 75% of your traffic is mobile, milliseconds become millions.
Teamweek just made a bold move: they killed their native mobile apps. Instead of maintaining separate iOS and Android codebases, they bet everything on a mobile-optimized web experience.
LinkedIn processes massive volumes of mobile crash data to keep their app stable for millions of users. Here's how they built the pipeline.
Muhammad Shuaib Khan from Bumble Tech explains why Swift 4.1 killed off a popular method that was secretly breaking code. The culprit? A function that worked too well in the wrong places.
Muhammad Shuaib Khan from Bumble Tech explains why Swift 4.1 killed off a popular method. The culprit? A naming confusion that was breaking code in subtle, dangerous ways.
Tad Book from Square reveals how they built a datastore that handles massive merchant catalogs while keeping mobile devices in sync, even when offline for days. The secret? An append-only architecture that make...
After three years and countless '+1s' on GitHub, React Native finally solved one of iOS development's most requested features. Here's how the team built InputAccessoryView from scratch.
LINE Engineering ditched expensive cloud testing services and built their own Docker-based infrastructure. The result? Flexible, cost-effective testing for both web and mobile.
Dmytro Khmelenko reveals how Freeletics turned localization from a bottleneck into a fully automated pipeline. The results? Measurable revenue spikes in newly localized markets and zero manual translation work.