stacks / pick

Stack picker

What would a dev do?

A few questions about what you're building, then the playbook a developer would reach for — and when to skip it.

A mobile appHeavy device workAndroid first Start over

A dev would reach for

Native Android — Kotlin + Jetpack Compose

An Android app with Compose screens and Kotlin services around platform APIs, with explicit state ownership, device testing, and task-specific background scheduling.

Why this fits

  • Android is the first target and device integration is central to the app.
  • Kotlin services own platform operations while Compose renders lifecycle-aware screen state.

Common trap

Treating every background job as a foreground service — choose the API for the task, account for OS restrictions, and test process recreation on real devices.

Check this before you commit

Skip if iOS is the first target, or one shared UI implementation across iOS and Android is a hard requirement.

Read the playbook

WWADD — Choose the tool. Make the move. Build the stack.

FREE REFERENCE · NO LOGINCONTACTPRIVACYTERMS