- 0:00–0:06
Use one booking brief • Give both candidates the same task. • Booking brief • Flutter • React Native
The GPT Image Booking brief document supplies equally weighted Flutter and React Native records. Its shared branches indicate identical content, task and acceptance criteria, not a ranking or completed tests.
- 0:06–0:12
Keep the chosen appointment • Test the same language switch in both. • English • Arabic • Appointment • Expected retention
An Appointment token moves from the English area into the Arabic area. Expected retention is highlighted. Keeping the selected appointment is the proposed acceptance condition for both prototypes; this is not a recorded pass.
- 0:12–0:18
Test the critical dependency • Include cancellation, return and retry. • Payment test • Booking • Cancellation • Then test retry
Cancellation moves from Payment test back into Booking. Then test retry is highlighted. The requested failure-case exercise checks return and retry; no successful payment or integration result is shown.
- 0:18–0:24
Ask the receiving team to build • Use the repository and written guide. • Receiving team • Fresh build to test • Repository + guide
Repository + guide enters the bounded Receiving team area below its title. Fresh build to test is highlighted as the next proposed exercise. The receiving team should attempt the build and then the journey in both languages; no actual successful build is asserted.
- 0:24–0:30
Keep unresolved work visible • Record evidence and untested conditions. • Open work • Missing steps • Untested
Missing steps and Untested move into separate rows of Open work. The record remains open so the eventual framework decision can cite evidence and unresolved conditions. Neither framework is ranked.
A silent 30-second illustrative guide to comparing booking prototypes through language, integrations and handover, without declaring a winner.
Read the article: Flutter vs React Native: A Saudi App Buyer’s Guide