Enables reactive, composable UIs with a design-system-first approach, type-safe generated APIs, and compiler-assisted incremental rendering to efficiently update view trees across displays.
Redwood is a library for building reactive Android, iOS, and web UIs using Kotlin.
This project is no longer under active development.
Android and iOS UI frameworks model the user interface as a ‘mutable view tree’ or document object model (DOM). To build an application using the mutable view tree abstraction, the programmer performs two discrete steps:
Build the static view tree. In Android the conventional tool for this is layout XML, though we've done some cool work with Contour to build view trees with Kotlin lambdas.
Make it dance. The view tree should change in response to user actions (like pushing buttons) and external events (like data loading). The program mutates the view tree to represent the current application state. Some mutations change the on-screen UI instantly; others animate smoothly from the old state to the new state.
React popularized a new programming model, reactive UIs. With reactive UIs, the
programmer writes a render() function that accepts the application state and returns a view tree.
The framework calls this function with the initial application state and again each time the
application state changes. The framework analyzes the differences between pairs of view trees and
updates the display, including animating transitions where appropriate.
In React the view tree returned by the render function is called a virtual DOM, and it has an on-screen counterpart called the real DOM. The virtual DOM is a tree of simple JavaScript value objects; the real DOM is a tree of live browser HTML components. Creating and traversing thousands of virtual DOM objects is fast; creating thousands of HTML components is not! Therefore, the virtual DOM optimization is the magic that makes React work.
Jetpack Compose is an implementation of the reactive UI model for Android. It uses an implementation trick to further optimize the reactive programming model. It is implemented in two complementary modules:
The Compose compiler is a Kotlin compiler plugin that supports partial re-evaluation of a function. The programmer still writes render functions to transform application state into a view tree. The compiler rewrites this function to track which inputs yield which outputs. When the input application state changes, it evaluates only what is necessary to generate the corresponding view tree changes.
Compose UI is a new set of Android UI components designed to work with the Compose compiler. It addresses longstanding technical debt with Android's view system.
A Kotlin function that is rewritten by the Compose compiler is called a composable function. Partial re-evaluation of a composable function is called recomposing.
Note that the Compose compiler can be used without Compose UI. For example, compose-server-side renders HTML components on a server that are sent to a browser over a WebSocket.
In Cash App we use a design system. It specifies our UI in detail and names its elements:
The design system helps with collaboration between programmers and designers. It also increases uniformity within the application and across platforms.
Redwood integrates the Compose compiler, a design system, and a set of platform-specific displays. Each Redwood project is implemented in three parts:
A design system. Redwood includes a sample design system called ‘Sunspot’. Most applications should customize this to match their product needs.
Displays for UI platforms. The display draws the pixels of the design system on-screen. Displays can be implemented for any UI platform. Redwood includes sample displays for Sunspot for Android, iOS, and web.
Composable Functions. This is client logic that accepts application state and returns elements of the design system. These have similar responsibilities to presenters in an MVP system.
We're eager to start writing reactive UIs! But we're reluctant to continue duplicating code across iOS, Android, and web platforms. In particular, we don't like how supporting multiple platforms reduces our overall agility.
We'd like to shortcut the slow native UI development process. Iterating on UIs for Android requires
a slow compile step and a slow adb install step. With Redwood, we hope to use the web as our
development target while we iterate on composable function changes.
We want the option to change application behavior without waiting for users to update their apps. With Kotlin/JS we may be able to update our composable functions at application launch time, and run them in a JavaScript VM. We may even be able to use WebAssembly to accomplish this with little performance penalty.
Redwood is a library, not a framework. It is designed to be adopted incrementally, and to be low-risk to integrate in an existing Android project. Using Redwood in an iOS or web application is riskier! We've had good experiences with Kotlin Multiplatform Mobile, and expect a similar outcome with Redwood.
We start by expressing our design system as a set of Kotlin data classes. Redwood will use these classes to generate type-safe APIs for the displays and composable functions.
@Widget(1)
data class Text(
@Property(1) val text: String?,
color: String,
)
(
text: String?,
enabled: ,
onClick: () -> ,
)
Displays implement the design system using native UI components.
class AndroidText(
override val value: TextView,
) : Text<View> {
override fun text(text: String?) {
value.text = text
}
override fun color(color: String) {
value.setTextColor(Color.parseColor(color))
}
}
Composable functions render application state into the design system. These will make use of Compose
API features like remember().
@Composable
fun Counter(value: Int = 0) {
var count by remember { mutableStateOf(value) }
Button("-1", onClick = { count-- })
Text(count.toString())
Button("+1", onClick = { count++ })
}
Surfaced from shared tags and platforms — no rankings paid for.