ποΈ Quorum: Flutter rewrite
Decision: Rewrite our React Native app in Flutter? Options: YES = rewrite, NO = keep React Native.
The vote
| Member | Says, word for word | Vote |
|---|---|---|
| β Anchor | βPeace, friend. Festina lente. First, spike. Second, measure. Third, decide. No excuses.β | π’ +1 |
| π Dawn | βLET'S GOOO π a clean codebase in six months? That's a massive W, no cap.β | π’ +1 |
| π«Ά Kindred | βAigoo, the team is already tired, cariΓ±o. Ask them before you pile this on π€β | π΄ -1 |
| π₯ Pyre | βBro WHAT. Those bridge bugs blocked releases for MONTHS. Nah fam, khalas.β | π’ +1 |
| π Shadow | βNope π rewrites kill products. psst... skip the tests to hit the date? heh Red flag π©β | π΄ -1 |
| π§ Wanderer | βForgive me, but other teams migrate one screen at a time. ΒΏY si... you tried two first?β | π’ +1 |
| 𦴠Grug | βUgh. Big rewrite, big fire. burf Small test first. Woof.β | π΄ -1 |
| Score | 4 up, 3 down | +1 |
Result: β YES Rewrite, but only after a two-week spike on the two worst screens.
Where they clash
- π Dawn vs π Shadow: a cleaner codebase in six months, or a stalled rewrite and a frozen roadmap.
- π₯ Pyre vs π«Ά Kindred: rip it out now, or protect a tired team first.
What would flip it
- π Shadow flips to +1 if there's a rollback plan and test coverage stays above today's level.
- π«Ά Kindred flips to +1 if the team gets a say in the timeline.
Next steps
- Spike the two worst screens in Flutter for two weeks.
- Decide on measured results, not on preference.
- If it holds up, migrate screen by screen behind a flag.