FarmX screen mapEvery screen, how they connect, what is missing
Built (161) Built, has issues (21) To design (81)

FarmX in one page

FarmX is one shared backend with six front doors. Everybody posts into the same network — I have, I need or emergency — and the system matches those posts by product, place and time. The rest of the product is what happens around that loop: showing interest, releasing contact details, talking, agreeing, and recording the outcome.

263screens in the map
182already built in the code
21built but flagged in the review
81still to design (tagged NEW)

The one loop everything hangs off

If this loop is wrong, nothing else matters — the client's review says it is wrong today.

Post (I have / I need / emergency) → matched by product, distance and date → lands in the other person's opportunity inbox → they tap Interested → the publisher accepts → contact details are released → chat, offer, counter-offer → deal → outcome and rating recorded.

Where it breaks now: turmeric is matched against a banana requirement, a tractor against a labour need, and the acceptance → consent → outcome half of the loop is not finished. Everything else is secondary to fixing that.

The map

Six apps, the modules inside them, and the layers the new scope adds. Click any branch to open it in the flow board.

How to read the flow board

The board is the Figma-style part: each screen is a card, arrows show which screen opens which.

  • Green = built and no issue reported.
  • Red = built, but the client review found a problem. The problems are listed on the card.
  • Purple NEW = does not exist yet; added from the new scope with a priority (P0/P1/P2).
  • Arrows come from the actual code — every routerLink and navigate() in each screen.
  • Click a card to read its detail and leave a comment. Comments are saved on the server and visible to everyone with the link.

What to fix first

  1. Matching rules — reject impossible matches before scoring them.
  2. Business cannot post a requirement — the main Business journey is blocked.
  3. Photo and voice capture — both buttons do nothing today.
  4. Interested → consent → contact → outcome — finish the second half of the loop.
  5. Validation — negative quantity and price currently reach Publish.
  6. Six languages, real OTP, payments and notifications.
  7. Separate demo data from production and lock down Admin.

Gaps & issues

Everything the review flagged, plus every screen the new scope needs. Click a row to open it on the board.

AppScreenGroupStatusWhat is needed