Battery Monitor, CPU Control and Backup are already live in next-gen as fresh Flutter apps under brand-new Play listings, with no upgrade path from their legacy counterparts. This asks whether that’s the right way to keep going.

Cast your vote
Background, pros & cons

new apps, simpler lineup, faster evolution, no purchase migration.

Pros

  • smaller codebase per app, most of legacy's Java is gone for three of the four apps (only root access still reaches studio/), faster to add features.

Cons

  • past legacy purchases/subscriptions don't carry over.

Constraints: Root access shared with legacy

Background, pros & cons

new apps, but honor old purchases where possible.

Pros

  • rewards existing paying users.

Cons

  • would need an entitlement bridge across differently-signed, differently-IDed apps
  • real engineering cost

Constraints: only matters to users who actually paid for something on the legacy app.

Background, pros & cons

keep the current Java apps and purchase model, evolve them gradually instead.

Pros

  • preserves every existing purchase/install/review on day one.

Cons

  • lots of technical debt - slow to release
  • every screen needs complete rewrite
  • complex model

Constraints: Keep the same options

Background, pros & cons

whatever gives 3C the best long-term future

Clean start
Votes: 2 · 100%
Migrate existing purchases
Votes: 0 · 0%
Modernize the existing apps
Votes: 0 · 0%
No preference
Votes: 0 · 0%

Total voters: 2