Discover 86 articles on App Startup in mobile performance
Showing 20 of 86 articles (Page 4 of 5)
Gonçalo Alvarez from Farfetch drops a hard truth: 86% of users uninstall apps after one use due to poor performance. Your launch time might be costing you customers before they even see your product.
At Farfetch, a 0.1 second delay in warm app launch costs $4.2M annually. That's less time than it takes to blink.
Expedia's iOS team breaks down the complete performance monitoring toolkit every mobile team needs. Your users notice lag after just 300ms—here's how to stay ahead.
Microsoft Teams Android engineers faced a critical problem: heavy initialization code in lifecycle callbacks was killing app launch times. Their solution? Get lazy.
Tom Doron from Apple's Swift team just open-sourced a solution to one of server development's most error-prone challenges: managing startup and shutdown sequences safely.
Slack cut load times by 65% for large teams by doing less work, not more. Their secret? Strategic laziness.
First impressions matter. For iOS apps, that means every millisecond between tap and first screen counts.
Dream11's 110M+ users join fantasy sports contests minutes before deadlines. A slow app launch means lost revenue and unfilled contests.
Grab reduced their super app's startup time by 60% while shipping dozens of new features. Here's how they saved users 59,582 hours per day.
Grab cut app startup time by 60% while shipping dozens of new features. Here's how they did it without compromising velocity.
Artem Sharypov from Strava's Experience team rebuilt their entire Android upload service from scratch. Why throw away working code? Because sometimes technical debt costs more than a rewrite.
Facebook just open-sourced Hermes, a JavaScript engine built specifically for React Native on Android. This isn't just another optimization tweak. It's a ground-up rethink of how JS should run on mobile.
Facebook built a JavaScript engine from scratch because existing ones weren't cutting it for mobile. Hermes prioritizes what actually matters: startup time, app size, and memory usage.
Stacey Tay from Carousell reveals how her team achieved a 3x speed improvement on mobile web—and turned it into a 63% traffic surge. The secret? A ruthless performance budget and smart PWA architecture.
Monzo's iOS app got 60% slower over time, and their team structure was partly to blame. Here's how they fixed it and prevented it from happening again.
Slack's engineering team faced a classic scale problem: three platforms, three definitions of 'app launch,' and zero ability to compare performance meaningfully.
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.
Adam Carpenter from Google reveals that most mobile games lose over half their new players in the first 10 minutes. The data shows exactly where retention breaks down and how top performers avoid it.
Facebook cut React Native Time to Interaction in half on low-end Android devices. The secret? They stopped trusting their testing tools and went straight to production data.
Francis Kam from Thumbtack reveals how they partnered with Google pre-launch to build one of the first Android Instant Apps. The results? Instant app messages now equal their full installed app.