Every sub-task in the Azya phase plan, checked against the source code of the Flutter user app and both admin panels: the new React rebuild and the old Flutter one. Use the switch below to see them together or one at a time, and open any task to see what works and what is missing.
Each square is one sub-task. Select a square to jump to it.
Overall judges each sub-task on the user app plus the React admin, because the React panel is the replacement for the Flutter one. The React panel is at an early stage: login, roles, the dashboard and products have their own screens, and every other page is a generic record list with a raw JSON editor. Both panels are published on Cloudflare Pages. The React one was last published by hand on 3 Oct 2026; its GitHub workflow builds and tests the code but skips the publish step.
The plan has 61 sub-tasks in three phases. The counts follow the view chosen above. Pending means raw records only, screens only or not started.
| Phase | Sub-tasks | Done | Partial | Pending |
|---|
The plan documents open here on the page, with zoom for the large flow diagrams. A plan file is dated by the date printed on it, or by the date saved inside the file where none is printed.
The first phase list: 61 sub-tasks, with 36 in Phase 1, 15 in Phase 2 and 10 in Phase 3.
Five flow diagrams: normal user, VIP user, bidding user, blogger with the admin panel, and designer with the shop manager.
59 sub-tasks. Phases 2 and 3 are split into 2.1, 2.2, 3.1 and 3.2; Catalog and VIP Show / Private Show are dropped.
Back to 61 sub-tasks in three phases, with 24 highlighted in yellow. This is the plan the page follows.
The old admin panel, with the Store Valley warehouse link.
The Next.js rebuild of the admin panel, published to Cloudflare Pages the same day.
Latest commit on the user app.
The user app and the Flutter admin checked against V5.2.1.
React admin added and compared with Flutter; user app re-checked.
The React panel has its own screens for login, roles, the dashboard, the product list and the product editor. Every other page is one generic screen: a list of records with a raw JSON editor and Create, Save and Delete buttons, plus a small action box on orders, inventory, users, returns and notifications. What it adds over Flutter is speed and upkeep: static pages, an offline cache, page search, automatic updates and unit tests on every push.
| Sub-task | Flutter admin | React admin | React vs Flutter | Still to rebuild in React |
|---|
Select a sub-task to open its full detail. A Level mark can still hide a difference: Payout Management is mock rows in Flutter and real but read-only records in React.
Status comes from reading the source code on the main branch of the three GitHub repositories on 20 Nov 2026. Nothing was built, run or tested on a device. A sub-task can have a user app side, an admin side, or both. Each side is judged separately, and the admin side is judged once for each panel. In the Overall view a sub-task is Done only when its user app side and its React admin side are both Done.
Implemented means Done. Pending means Raw records only, Screens only or Not started.
None of the three repositories has had a commit since the 17 Nov check. For this update the React admin was read in full, the user app's Phase 2 and Phase 3 sub-tasks and its extras were re-checked one by one, and Phase 1 was spot-checked on its partial items. Flutter admin statuses are carried over from 17 Nov. Three user app statuses were corrected: Catalog is now Done because the app reads the catalogue switch, and Post Purchase Feedback and Share My Wishlist moved from Not started to Screens only because hidden screens for them exist.
Not verified: the payment webhook, whether the warehouse link works against the live Store Valley service, which payment gateway production uses (it is set in the database, not in code), and whether staff already use the React admin for daily work.