Android

What we build and ship for Android — the engineering stack behind our apps, the products in people’s hands, and how updates reach them.

Kotlin Jetpack Compose Material 3 Coroutines & Flow Google Play
Two Android phones glowing blue over a dark circuit-board background

Android at Galaxy Vast

Four apps, one Android team: the same chain of craft described on the products page, told from the platform side.

Technology

The stack we build on

The tools and disciplines every Android release leans on.

Kotlin, coroutines & Flow

Everything is Kotlin. Coroutines and Flow carry background work off the main thread, so typing and scrolling stay smooth even on mid-range devices.

Jetpack Compose & Material 3

New screens are declarative Compose; Material 3 theming — including dynamic colour — keeps our apps at home on any Android skin.

Architecture you can test

MVVM with unidirectional data flow and a shared design-system module, so Galaxy Notes, Ledger and Scan feel like one family.

Performance & hardening

R8 shrinking, baseline profiles for cold starts, minimal permissions, and min/target SDK levels tracked with every platform release.

Quality

From device lab to your phone

How a build becomes an update on your home screen.

  • Tested on real devices

    Every candidate build runs across screen sizes, OEM skins and Android versions before it leaves the team — emulators alone never sign off a release.

  • Beta first

    New features go to open testers first; what the feedback shows shapes — or stops — the public release.

  • Staged rollout

    Google Play’s staged rollout lifts updates to users gradually, and a problem discovered at five percent never reaches the rest.

  • Then it keeps evolving

    Crash triage, anonymised analytics and store reviews feed the next iteration — evolution on purpose, not by accident.

Abstract network of glowing data nodes

See the whole product family

Notes, Ledger, Scan and whatever comes next — the products page is where the Android and iOS stories converge.