Post

the cat is out of the bag: we have rebuilt from the ground up Shop in SwiftUI and Jetpack Compose. it still feels weird to think that it actually worked out lol. needless to say, it was a crazy few months. Can you believe it? full rewrite, and now it's already out in prod 🤯

0 reposts5 likes

there's so much, SO MUCH I want to chat about and tell about what we've experienced, what we've learned, what we've found and what we've figured out. Comments on the decisions, on what we'd do differently now, etc etc ...we'll get there at some point. not today, im too X_X

two observation, just to put some sprinkles on top: • if a migration takes weeks, there's not enough time for the backlog to grow so big to add more weeks at the end • having a hard rollout deadline is a great forcing function to make things happen

i'm a nerd, and there's so much I wanna dive in, even in mindset and vision changes (it is indeed true that, in the age of agentic, refactoring is cheap). At some point I'll do a talk, or something. We've sailed in uncharted waters, and I want people to learn from us.

A full production rewrite in two UI frameworks is a huge test. Which screen exposed the biggest difference between SwiftUI and Compose?

That is a strong endorsement of Compose. A demanding home feed tends to expose recomposition and scrolling problems quickly, so handling it cleanly in production says more than a demo ever could.

That combination is hard to shortcut: CI makes parallel work safe, and enough ownership on each platform keeps the shared product from collapsing into lowest-common-denominator UI.