Flutter Forward: Crafting Type-Safe Native Interfaces with Pigeon
Mercari uses Pigeon for tight, safe Flutter-to-native connections.
Showing 20 of 528 articles (Page 4 of 27)
Mercari uses Pigeon for tight, safe Flutter-to-native connections.
Coinbase fine-tunes network calls to make their app feel snappier for users.
Meta fine-tunes Threads on iOS to keep it fast and frustration-free.
Meta shifted their giant Android codebase from Java to Kotlin over years.
We made our engineers happier by cutting build times down from 50 minutes to 16.
Mercari shares what they learned adopting Swift Testing for iOS.
Details how Reddit optimized app startup times using Baseline Profiles and R8 for better performance on Android.
Today, when you open Apple Maps and choose a destination, you are able to see a list of available Lyft offers, seamlessly routing you to the Lyft app to book your next ride.
We all strive to build flawless apps, but let's face it - bugs happen. And sometimes, those pesky bugs are elusive, only showing up in the unpredictable chaos of production.
At Pinterest, our mobile infrastructure is core to delivering a high-quality experience for our users. In this blog, I’ll showcase how the Pinterest Mobile Builds team is leveraging Honeycomb.
There is a lot of obsession with app size reduction. This usually is tracked as a metric, compared with peers and I see teams work hard for months to squeeze it up to the last bit.
Discord used synthetic control to measure voice message impact cleanly.
Grab speeds up their GrabX SDK startup to get users rolling quicker.
One of the things that users usually don’t like is stuttering in our application. Basically, Flutter itself provides a way to overcome this.
A single backend response can do a lot more than you think.
Shopify dumped old code for React Native, cutting millions of lines and boosting speed.
Our GrabX clients noticed that the GrabX SDK tended to require high memory and CPU usage. From this, we saw opportunities for further improvements that could:
Unit tests are great. They give us confidence to build and change our software. Sometimes I want to write a test once and run it for multiple algorithms, inputs, or environments. It’s been possible to do this with JUnit for a long time:
I have been searching the web to find the answer to this, but it seems that people are split down the middle in this topic. On one hand, UIKit is best for trying to get a job in iOS development since its mainly maintaining older code
DoorDash uses deep learning to nail ETA predictions with precision.