Roadmap signal

Tell us the stack you need Ubriot to support

Ubriot is not waiting for a form to know the next move. The next default bet is bare React Native, especially teams replacing App Center and CodePush. This page captures the demand that decides what comes after that.

See migration path React Native CI/CD

Bare React Native

Next bet

The release-memory, OTA, Metro, signing, and App Center migration story carries cleanly here.

Expo

Supported now

Ubriot should deepen the release surface around EAS-adjacent workflows, not fight Expo as a category.

Flutter

Demand-gated

The market is real, but the moat does not carry cleanly and Flutter-native release tooling is already strong.

Kotlin Multiplatform

Evaluate

Promising momentum, but the release-intelligence model only partly transfers.

Next without waiting

Build the bare React Native migration path now. It carries the OTA and release-memory moat.

Capture real demand

Use requests to decide what comes after bare React Native, not to postpone the current bet.

Keep promises narrow

Do not name Flutter, KMP, or native as supported until there is evidence behind the work.