How Cash App optimizes Android performance

×
×
×

Showing 8 of 8 articles (Page 1 of 1)

Article thumbnail

From 30 Minutes Down to 10: Taming our Monolith's CI Build Times

When Cash App was originally developed we had a single service powering all backend functionality, codenamed “Franklin”.

Article thumbnail

A stable, multiplatform Molecule 1.0

Molecule is a Compose-based library which we announced two years ago for managing application state. I’m excited to announce that today we are releasing version 1.0, its first stable version!

Article thumbnail

Native UI and multiplatform Compose with Redwood

Redwood is Cash App’s take on multiplatform mobile client UI. Unlike many of the existing solutions to this problem, our values are slightly different

Article thumbnail

Flow testing with Turbine

Say hello to Turbine 1.0, our library for testing kotlinx.coroutines Flow and more.

Article thumbnail

How We Sped Up Zipline Hot Reload

Zipline is a library Cash App has developed for fetching and executing code on demand in a mobile app. Developers write their code in Kotlin and it gets compiled to JS, hosted on a server or CDN

Article thumbnail

Molecule: Build a StateFlow stream using Jetpack Compose

Back in November 2021, Jake wrote about Molecule on this blog when it was still under development. A few weeks ago, we released 0.4.0 which we are using in production with great satisfaction.

Article thumbnail

The state of managing state (with Compose)

Five years ago the Cash App Android client started splitting our UI rendering and UI presenter responsibilities into distinct types. We had leaned into RxJava heavily in the years prior

Article thumbnail

A Great Way to do Android Presenters

The Cash App Android app uses presenters because they’re easy to write, easy to review, and result in boring code that just works.

Loading articles...