# Gerobak: Product Requirements Document

| | |
|---|---|
| **Status** | **v2.9 · Ready for tech design**, except F-16, F-18 and F-19, which wait for a CTO effort check. F-22 is CTO-checked and Ready. Owner questions open: Q7, Q10; neither blocks the demo |
| **Date** | 2026-10-28 · v2.2 on 2026-11-03 · v2.3 on 2026-11-04 · v2.4 on 2026-11-05 · v2.5 on 2026-11-05 · v2.5.1 on 2026-11-10 · v2.6 on 2026-11-12 · v2.6.1 on 2026-11-12 · v2.6.2 on 2026-11-12 · v2.7 on 2026-11-13 · v2.7.1 on 2026-11-13 · v2.8 on 2026-11-13 · v2.9 on 2026-11-17 |
| **Owner** | Product owner (decisions), Pia (PM) |
| **Market** | Bali, Indonesia. Canggu and Seminyak first |
| **Current phase** | Phase 0: demo for the Bali counterpart |
| **Mockups** | `../mockups-v3/index.html` (the GitHub app design, D29). Earlier sets kept as history: `../mockups/`, `../mockups-v2/`, `../opendesign/` |
| **Replaces** | v0.9 (2026-10-25). The v0.9 features that were removed are kept in section 13 (Phase 3) so none of the thinking is lost |

Indonesian words in **bold** are the labels used in the app. **(proposed)** marks a default that Pia set and the pilot should test.

---

## Changelog

### v2.9 (2026-11-17): sellers ask their followers a question (D70, D71)
Owner request: sellers start a vote for their followers, with free text and a timer. Pia decided the details; nothing needs an Owner answer.
- **New F-22 Polling pengikut (P0):** the seller writes one question and 2–4 answers in their own words, picks how long it runs (**1 jam, 6 jam, 24 jam, 3 hari, 7 hari**; 24 jam preselected) and starts it. One poll at a time per shop.
- **Who votes:** followers, one vote each, changeable until the poll ends. Everyone sees the poll on the cart page; a non-follower who taps an answer is offered **Ikuti & pilih**. Results show to a buyer after they vote; the seller sees counts live, never names.
- **"Free text" read as:** the seller types the question and answers (no ready-made templates, no link to menu items). Buyers pick one of those answers; they don't type their own (D70, Assumption A10).
- **Ending:** at the chosen time, or earlier with **Akhiri sekarang**. Final results stay on the cart page for 24 hours. **Hapus** removes the poll and its votes for everyone. No editing after the start.
- **D71, no push when a poll starts:** the poll shows on the cart page and as a *Polling* line in Diikuti. Keeps alerts to the two kinds buyers already know. Revisit if votes are low in the pilot.
- **CTO check (Kai, 2026-11-17), folded in:** 8–9 days, $0 extra running cost (Estimated). Changes and seller views update when a page opens or is pulled down, not live (AC1, AC4, AC7, AC8). Time left always comes from our clock (AC3). After sign-in a visitor returns to the poll and taps again; no automatic vote (AC6). New **F-22.AC13** (poll deleted while a buyer looks) and **F-22.AC14** (seller hidden by admin). Limit of 10 new polls per shop per day. Reaches phones only with new builds of both apps, which the Owner approves.
- **Also fixed:** the Phase 0 scope line now lists F-15 and F-21, which were moved into P0 in v2.7 but not added there.
- **Mockups:** `round-v29.html`.

### v2.8 (2026-11-13): ratings everywhere, auto-close after 1 hour lost (D68, D69)
Owner found four points. Pia decided; nothing needs an Owner answer.
- **Rating missing in Ringkasan:** not a delay. The average was hidden on purpose until a cart had 3 reviews. **D68** drops that rule: the average shows from the **first** review, always with the count beside it, e.g. *★ 5,0 · 1 ulasan*. Applies to Ringkasan, the cart page and every cart card.
- **Average on the cart page:** already in the numbers row; now from the first review (F-05.AC5).
- **Average on cart cards (D68):** Di sekitar Anda, search results and Diikuti cards show *★ 4,3 (12)*; no reviews, nothing. New **F-04.AC15**, **F-06.AC8**.
- **D69, auto-close after 1 hour lost (supersedes the "only the seller's Tutup ends a shift" part of D42):** if no position reaches the server for 60 minutes while Buka, the shift ends by itself at the time of the last position. When the phone reconnects, the seller sees Tutup and a banner explaining why. 10–30 minutes dimmed and 30–60 minutes hidden stay as they are. New **F-03.AC14–AC16**; F-03.AC9 retired.
- **Mockups:** `round-v28.html`.

### v2.7.1 (2026-11-13): wording and IDs after the build
All eight v2.7 points are built and live on testing (main 32ea79f); 15 of 15 web-checkable rules pass. Pia's follow-ups; no requirement changes for users.
- **F-03.AC13:** tapping the BUKA notification opens the app (Beranda on a fresh start). On Android 14 and newer, Android always lets users swipe it away; location keeps sending.
- **IDs renumbered** (they clashed with older ones): the numbers row is **F-05.AC5** (was F-05.AC3), dated 7-day rows are **F-11.AC12** (was F-11.AC11). Old IDs keep their old meaning.
- **Copy confirmed** as built: admin *Ulasan*, *Disembunyikan*, *Ulasan disembunyikan dari pembeli.*, *Ulasan ditampilkan lagi.*; stock *Tidak dihitung*; seller *Pengumuman sudah tidak tampil*.
- **1–2 reviews:** the cart page shows the reviews and *"Ulasan baru · {n} ulasan"* instead of *"Jadilah yang pertama setelah mencoba"*, which is only for 0 reviews. New **F-17.AC10**.

### v2.7 (2026-11-13): Owner's test round, eight points
The Owner tested the apps and sent eight points. Pia decided each; nothing needs an Owner answer.
- **D63, buyers write reviews (F-17 writing moves from P1 to P0):** an **Ulas** button on the cart page opens a sheet: stars (required), quick tags, a short note. Any signed-in buyer can review, one review per cart, changeable. The 100 m "was near" rule is dropped. New **F-17.AC6–AC9**; F-17.AC1–AC2 retired.
- **Pengikut count not updating (F-16, bug):** Fact, from the Owner: the seller saw 0 pengikut after a buyer followed, until a sale was recorded. Counts must refresh whenever the screen opens and on pull-down. New **F-16.AC10**.
- **D64, numbers at a glance (F-16, F-05):** Toko saya gets a **Ringkasan** card (Pengikut, Nilai, Ulasan); the buyer's cart page gets the same three numbers in one row under the name. New **F-16.AC11**, **F-05.AC5** (renumbered in v2.7.1).
- **Running in the background (F-03):** answer: only the seller app, and only while **Buka**; the buyer app never runs in the background (D59). Android already requires a notification for this. **D65:** its text is plain, it stays while Buka and disappears at Tutup. New **F-03.AC13**.
- **7 hari terakhir shows dates (F-11):** each row shows the day and date, e.g. *Rab · 11 Nov*. New **F-11.AC12** (renumbered in v2.7.1).
- **"Nyalakan lokasi" explained (F-10):** a line under the button says what it does. Copy table 3.5a.
- **D66, stok hari ini (new F-21, P0):** optional count per menu item; each recorded sale lowers it; at 0 the item turns Habis. Buyers see *Tinggal n* only when 5 or fewer are left.
- **D67, pengumuman (F-15 moves from P1 to P0):** one line, up to 80 characters, on the cart page and in the buyer's Diikuti list, gone after 24 hours unless renewed.
- **Mockups:** `owner-round-v27.html`.

### v2.6.2 (2026-11-12): plain words and Rumah/Kantor on the map (D61, D62)
The Owner asked for plain, simple Bahasa Indonesia and for Rumah and Kantor to show on the map. Pia decided the details; nothing needs an Owner answer.
- **D61, plain copy for F-10:** every buyer text in Dekat Anda (first-follow sheet, place picker, Profil rows and reminder, error states, both pushes) follows `copy/f10-copy-plain-id.md`. Coordinates and the Utara/Selatan/Barat/Timur buttons leave the screen; the arrow moves stay for screen readers only. New **F-10.AC7**.
- **D62, saved places as pins:** the buyer's own Rumah and Kantor show as house/office pins on Peta, on a small map in Profil, and faded in the picker. Only that buyer sees them; nothing new is sent to the server. New **F-10.AC8**.
- **Next (not in this version):** the same plain-language pass for the whole seller app, then the buyer app, as a separate job.

### v2.6.1 (2026-11-12): no double push at opening (D60)
- **D60:** when a followed cart opens right next to a buyer's saved place, the buyer gets only the **buka** push, not a **near** push a minute later. A near push for that cart is skipped if the buyer got its buka push in the last 15 minutes. New **F-10.AC6**. Small follow-up build; F-10 otherwise stands as built.

### v2.6 (2026-11-12): Dekat Anda uses saved places (D59, Q7 closed)
The Owner chose option B for Q7. Pia decided the details; nothing needs an Owner answer.
- **D59, supersedes D3:** the buyer app never asks for location *all the time*. A "near" alert fires when a followed cart comes within about 500 m of a saved place (**Rumah** or **Kantor**, up to 2), or of the buyer's own position while the app is open. "Always" location may come back after the pilot if buyers ask for it, and only after the Google Play review.
- **Setup:** at the first follow, the buyer is invited to save a place. The spot is pre-filled from their current position if they allow location *while using the app*; otherwise they move the map pin to it. They can skip.
- **F-10** rewritten; **F-10.AC1** and **AC4** replaced; journey J2, demo script step 2, A4, the risk row and the effort table updated. **Q7 closed.** The seller app is unchanged: it still needs background location while Buka.
- **Mockups:** `buyer-cart.html` 04–06.

### v2.5.1 (2026-11-10): one account across the apps (D58)
The Owner asked whether one sign-in system can serve all the apps, and whether a seller account is the same as a buyer account. Pia decided; no requirement changes for buyers or admins.
- **D58:** one Google account is one Gerobak account. The buyer app and the seller app are two ways into it: in the buyer app it holds follows, reviews and saved places; in the seller app it holds the shop. The same Gmail can use both apps without a second account. The admin page does not use this sign-in. New **F-12.AC5**.

### v2.5 (2026-11-05): Owner's revision on seller setup and stats, five points
The Owner tried seller setup and Beranda on the testing links. Pia decided each point; nothing needs an Owner answer.
- **D56, check each step before moving on (F-01):** Fact, from the Owner: *“This phone number is already used by another shop”* only appeared at the end of step 2. Now **Lanjut ke menu** checks every step 1 field, including whether the WhatsApp number is already used by another shop, and stays on step 1 if anything is wrong (new **F-01.AC10**). **+ Tambah menu** checks the menu being edited before a new one is added (new **F-01.AC11**). With no signal, the number is checked again at **Simpan dan mulai**.
- **No “sign in first” during setup (F-01):** Fact, from the Owner: creating a menu during setup said *“Sign in first”*. A seller who signed in to start setup is never asked to sign in again before the shop is saved; if the session lapses, the app renews it quietly, and if it can't, the seller signs in and returns to the same step with everything kept (new **F-01.AC12**). Build fix.
- **Dilihat hari ini shows real numbers (F-07):** Fact, from the Owner: the figure looks like a placeholder. Beranda's **Hari ini** card shows today's real counts (Dilihat, Pengikut baru, Porsi), or 0 with a line saying what to do; never example numbers (new **F-07.AC3, AC4**).
- **“Ketuk hari untuk rincian” spacing (F-11):** a grey hint line right under the **7 hari terakhir** heading, then the list; never inside a row or overlapping (new **F-11.AC10**). Build fix.
- **D57, Pengikut becomes a card (F-07):** replaces the single line under the BUKA button. The card shows the total, new followers this week, a 7-day bar of new followers per day and who gets the Buka alert; no buyer names (new **F-07.AC5**).
- **Mockups:** `seller-start.html` 11–12, `seller-home.html` 01 and 10, `seller-sales.html` 02.

### v2.4 (2026-11-05): Jenis menu is three choices (D55)
The Owner asked to simplify the kind of food to three choices. Pia accepted and decided the details; nothing needs an Owner answer.
- **D55, Jenis menu = Makanan, Minuman or Camilan (F-02):** replaces the D47/D53 dish dropdown. Each menu item gets one of three buttons, **Makanan**, **Minuman** or **Camilan**. One tap, required, none chosen in advance. The field label is **Jenis menu**, because a drink is not a *masakan*. *Camilan* is the standard spelling of the Owner's *cemilan*.
- **Buyers see the three kinds:** the cart page lists the menu under **Makanan**, **Minuman** and **Camilan** headings, in that order, and hides a heading with no items.
- **The 264-dish list stays, unseen:** sellers no longer see or pick a dish. The list (`dish-list-v2.md`) is kept only so that demand counts (F-13) can recognise words such as *bakso* or *kopi* in buyer searches.
- **Search:** buyers find carts by cart name and menu item name, as before. Finding a dish by another name (typing *terang bulan* to find *Martabak manis*) needed the seller's dish pick, so it goes. A seller who writes "Terang bulan" in the item name is still found that way.
- **Existing menu items** get a kind from their old dish group (table in F-02); items saved as **Lainnya** become **Makanan**. Sellers can change it in Toko saya. Only testing data exists, so nothing real is mislabelled.
- **Retired:** F-02.AC6–AC9, assumption A8 and the "dish not in the list" path. **New:** F-02.AC10–AC12.
- **Mockups:** `seller-start.html` 07 and 08, `seller-shop.html` 03, `buyer-cart.html` 01.

### v2.3 (2026-11-04): Owner's second look at the testing app, five points
The Owner checked the testing app after photo upload went live and sent five points. Pia decided each; nothing needs an Owner answer.
- **Photo choice sheet shows wrongly (F-01):** Fact, from the Owner's screenshot: the **Foto gerobak** sheet appears half-hidden under the step title, mid-page, with the form showing around it. That doesn't match F-01.AC6 or the mockup, so it is a build fix. To make it testable, new **F-01.AC9** says how the sheet must appear: from the bottom edge, over a dimmed page, above everything, fully visible.
- **“Biasa berjualan di” still shows (F-01):** already removed by **D46** in v2.2; the testing build doesn't have it yet. No PRD change; still P0 for the next build.
- **D53, Jenis masakan is a dropdown with more choices (F-02):** refines D47. The field is a dropdown (**▾**) that shows the chosen dish; tapping it opens the whole list (**Sering dipilih**, then every dish by group, **Lainnya** last). A search box at the top is optional. The list grows from 188 to **264 dishes in 16 groups**, including the new groups **Roti & kue modern** and **Jajanan Korea & Jepang**: `dish-list-v2.md`. F-02.AC6–AC8 still apply; new **F-02.AC9**.
- **“Mengandung babi” still shows (F-02):** already replaced by **Halal / Non-halal** (**D48**) in v2.2; the testing build doesn't have it yet. No PRD change; still P0 for the next build.
- **D54, a menu photo shows wherever the item shows (F-02, F-16, F-05):** Fact, from the Owner's screenshot: a menu item on the seller's Beranda shows the fork-and-knife placeholder instead of its photo. A menu item's photo now shows on seller Beranda, Toko saya, Catat penjualan and the buyer cart page, cropped to fill a square. The placeholder is only for an item with no photo. New **F-16.AC9**.
- **Mockups:** the dropdown (`seller-start.html` 07–10, `seller-shop.html` 03), the photo sheet rule (`seller-start.html` 03), and menu and cart photos instead of emoji on every menu row and list card. Emoji remain only on map pins.

### v2.2 (2026-11-03): Owner feedback on the testing app, nine points
Owner tried the real testing app and sent nine points. Pia decided each; nothing here needs an Owner answer except the halal wording check (Q10).
- **D45, photos (F-01, F-02, F-16):** real photo upload from the camera or the gallery is **P0**, for the cart (1 required at setup, up to 5) and for each menu item (optional). The picture choices (bowl, pancake, cup…) in the current build were a demo stand-in and go away. Fact: the testing app cannot upload because nothing was built to store photos yet; the CTO owns the how and the cost. New ACs F-01.AC6–AC8, F-16.AC8.
- **D46, “Biasa berjualan di” removed (F-01):** the usual selling area is no longer asked at setup or shown in Toko saya. The live position while Buka is what buyers use; no screen used the field. F-01.AC1 changed.
- **D47, Jenis masakan is a search, not a row of pills (F-02):** the seller types and picks from a dish list grown from 4 visible pills to **about 190 dishes** in 14 groups, with Bali dishes and common other names (e.g. *terang bulan* finds Martabak manis). If nothing fits, **Lainnya**. List: `dish-list-v1.md`. New ACs F-02.AC6–AC8.
- **D48, “Mengandung babi” becomes Halal / Non-halal (F-02, F-05, F-16, F-08):** one required choice per cart at setup, not per item: **Halal** or **Non-halal**. Buyers see **Halal** or **Non-halal** next to the cart name; the cart page adds *“Status halal menurut penjual”*. The official halal logo is never used. F-02.AC2 and F-16.AC4 retired; new F-02.AC5, F-16.AC7.
- **D49, Buka and Tutup ask for confirmation (F-03):** tapping BUKA or TUTUP opens a short confirmation sheet; nothing changes until **Ya, buka** or **Ya, tutup**. Prevents a pocket tap from alerting every follower or dropping the cart off the map. Refines D2: still no form, now two taps. New ACs F-03.AC10–AC12.
- **D50, Rute hari ini on seller Beranda (new F-19, P0):** a card with today's route on a small map, **Lama buka** (time open) and **Jarak** (distance travelled while Buka). Seller only. Waits for a CTO effort check.
- **D51, short messages (toasts) sit at the bottom and leave on their own (new F-20):** shown above the tab bar, never over the BUKA/TUTUP button, gone after 4 seconds (6 with a button), swipe to close, one at a time. Lasting conditions (location off, no signal, hidden by admin, unsent sales) are banners on the page, not toasts.
- **D52, Di sekitar Anda pulls up to full screen (F-04):** the sheet has three heights, **Kecil**, **Sedang** (default) and **Penuh**. Drag the handle or tap it; typing in search opens Penuh; tapping a card drops to Sedang so the focused pin shows. New ACs F-04.AC11–AC14.
- **Catch-up, not a new decision:** seller sign-in text in F-12, J3, J5, F-01 and F-08 now matches ADR-009 (Owner, 2026-11-02): sellers sign in with Google like buyers; the testing build uses **Masuk (akun uji)** (ADR-010). The old phone code text is gone.
- Mockups updated: `seller-start.html`, `seller-shop.html`, `seller-home.html`, `buyer-map.html`, `buyer-cart.html`, `admin-sellers.html`, `design-system.html`.


### v2.1.3 (2026-11-02): names on the map, card focuses the pin, Profil button
- **D44:** Every cart pin on Peta now carries its **cart name** in a small label, so a buyer can read the map without cross-checking the list. The label is the cart's name, shortened with “…” when long; a dimmed (STALE) pin keeps its name; a hidden cart shows neither pin nor name.
- Tapping a card in the Peta list (Diikuti, Terdekat or search results) **focuses that cart's pin** instead of opening the cart page: the map pans so the pin sits above the sheet, the pin is enlarged and its name stays bold. The card shows as selected. No account is needed to focus a pin.
- Each card carries a **Profil** button that opens the cart page (F-05). This replaces the one-tap row, so reaching the profile is now two taps: card to focus, then Profil to open. Accepted, because the map focus is the card's main job on Peta.
- Tapping a pin on the map still opens the cart page directly (F-05.AC1). No new screen; no change to search, visibility rules, sign-in or the alert.

### v2.1.2 (2026-11-01): area name in opening alert
- **D43:** The followed-cart opening alert names the cart and its **current broad area**, never a street or gang: **“Bakso Pak Made buka sekarang di Canggu. Lihat di peta.”** The map shows its precise current pin. If no reliable area name is available, omit the area: **“Bakso Pak Made buka sekarang. Lihat di peta.”** Do not use the seller's usual area as a substitute when the cart is elsewhere. No address or street-name lookup is needed for the alert.


### v2.1.1 (2026-11-01): distinguish no signal from stopped tracking
- **D42 clarified:** buyers use the age of the newest position **recorded on the seller phone and received by the server**, never the arrival time of an old upload. A phone timestamp later than the server's receipt time is capped at receipt time for freshness. A phone that kept recording offline may reappear automatically when its batch arrives, at LIVE, dimmed or hidden according to that newest recorded position. A phone that stopped recording for over 30 minutes requires **Lanjut Buka** and a fresh position before it reappears.
- Offline sales stay available while the seller has chosen Buka. If their latest phone position is over 30 minutes old, the sale shows **Lokasi perkiraan**; it is not discarded. Near alerts use LIVE positions only.
- A hidden shift does **not** end automatically at midnight. Only the seller's **Tutup** ends it. The admin sees **Hilang** until recovery or Tutup; no screen guesses that the seller intentionally closed. The seller app warns immediately when phone location is turned off. Seller warning push is deferred beyond Phase 0.


### v2.1 (2026-11-01): contact lost while the seller is Buka
- **D42:** No server update does not mean the seller tapped Tutup. Up to 10 minutes since the newest phone-recorded position: LIVE; 10–30 minutes: dimmed with last-seen time; over 30 minutes: no buyer map pin or nearby/search result, and admin status Hilang. The seller's Buka choice remains until they tap Tutup.
- A phone that continued recording offline restores the correct visibility automatically when those positions arrive. A phone that recorded nothing for over 30 minutes needs **Lanjut Buka** and a fresh position. Old positions alone cannot make the cart look LIVE. No second Buka alert is sent in the same day.
- Until recovery, the cart remains in the follower's Diikuti Buka tab with **Lokasi tidak tersedia**, no distance or map action. The seller can still record sales offline; an old phone position is labelled **Lokasi perkiraan**.

### v2.0.1 (2026-11-01): Phase 0 rules after CTO review
- The seller enters a variable item's **unit price for one portion** each time it sells. The line amount is unit price × portions; whole rupiah only, from Rp 1 to Rp 5.000.000 per portion. A blank or invalid amount blocks saving. Fixed-price sales keep the three-tap path.
- In Diikuti, tab counts cover all followed carts in each status and do not change with search. Search only filters the selected tab. Buka sorts by distance; Tutup sorts by most recent open time. A status change moves the cart between tabs while preserving the search text.
- Onboarding location means the seller's **labelled usual selling area**; the live map position comes from the phone while Buka. Step 1 stays as an on-device draft if the seller leaves; no shop appears to admin until step 2 is saved.
- Mockup sizing: body 14–15 px, numbers 13–14 px, secondary 11–12 px (11 only for nonessential detail), controls at least 44 px; the collapsed map occupies at least 55% of the 800 px phone screen. This is the target for the app screens too.
- Sales lists show exact rupiah, with aligned right edges. Use at least 100 px for the amount column. A cart with a fixed-price item shows the lowest available fixed price as *mulai*; an all-variable cart shows *Harga sesuai pesanan*. The Peta sheet lists only open followed carts and links to the full tabbed Diikuti view.
- Kai estimates D37–D41 add 11–15 engineer-days to Phase 0; no new recurring cost. F-18 remains outside the prior 55–65-day estimate.

### v2.0 (2026-11-01): compact screens and variable prices
- **D37:** Penjualan uses aligned columns for time/day, item or portions, and takings. Seven-day details use the same columns; a variable-price sale contributes the amount entered at sale time.
- **D38:** Use a denser type and spacing scale on mockups, with the map given more of the phone height. Keep primary actions at least 44 px high and core text legible.
- **D39:** Diikuti has Buka and Tutup tabs and a name/dish search within the selected tab. Status changes move the cart to the matching tab; the search is preserved.
- **D40:** Seller setup has two steps: shop identity (name, photo, cart type, location) then menu. Keep entered values when moving back or when validation fails. At least one menu item is needed to finish.
- **D41:** Each menu item has either a fixed price or *Harga sesuai pesanan*. The latter has no shown numeric price; the seller enters its actual amount when recording the sale. That amount is required, positive and included in totals. The three-tap path still applies to fixed-price items.

### v1.9 (2026-11-01): open map, reviews on the cart page, sales per menu, no demo in admin
Owner: four changes.
- **The admin demo page is gone (D33).** The admin console is now just Penjual and Pantau visibilitas. The Phase 0 simulation stays, but it is no longer an admin screen: the team turns it on before the demo, and nothing about it is visible to sellers, buyers or admins.
- **7 hari terakhir opens per day (D34).** Tap a day and it shows which menu sold, how many portions and how much each dish took; the day's totals stay in the row. Days with no sales open to a plain "Tidak ada penjualan hari itu."
- **Reviews show on the cart page (D35, Q8 closed).** Average, count and the latest reviews are on the cart page from Phase 0, with "Ulasan baru" until there are 3. Writing a review stays P1, because it needs proof of a visit.
- **Peta opens without an account (D36).** The map, list and search work signed out. Opening a cart, Ikuti, ulasan, saved places and alerts ask for sign-in, once, on top of the same map. D4 is superseded; the sign-in-before-map rule no longer applies.
- Mockups: `admin-demo.html` removed; new states in `seller-sales.html` (05, 06), `buyer-cart.html` (07) and `buyer-map.html` (05, 06). No other look change.

### v1.8.3 (2026-11-01): Manrope is the typeface (D32)
Owner: "Much better. Now explore alternative fonts." Five typefaces were drawn on the real screens (`../mockups-v3/font-lab.html`), and the Owner chose **Manrope**.
- Manrope replaces Plus Jakarta Sans in every mockup. Sizes, weights, colours and spacing are unchanged, so no acceptance test changes.
- A **Typeface switch** at the bottom right of every mockup page flips the whole page live between Manrope, Plus Jakarta Sans, Inter, DM Sans and Nunito Sans. It is a static, script-free switch and starts again at Manrope on each page.
- Checked with Manrope: no text spills past the phone edge on any of the 13 pages, no row or button clips its text, and the 7-day list and price columns still line up.
- The app itself still ships Plus Jakarta Sans. Bundling Manrope is a build change for the CTO, not a product change.
- Q9 is closed.

### v1.8.2 (2026-11-01): section headings stand apart (D31)
Owner: improve “Menu”, “7 hari terakhir”, “Hari ini · 13 porsi · Rp 252 rb”, and similar section headings.
- Section headings sit on white bands with a divider separating their content; headings remain smaller than screen titles.
- “Hari ini” is a separate heading, with portions and sales total on the next line.
- The same treatment covers menu setup, saved places, followed/nearby groups, and admin sections. Headings already inside white cards use a divider without adding another card.
- Existing GitHub styling, features, priorities and acceptance tests stay unchanged. Design-system section 06 documents the pattern, with a before/after of the Penjualan screen.
- Adds **Q9** (typeface) and the `font-lab.html` page: the Penjualan and Gerobak screens in Plus Jakarta Sans, Inter, Manrope, DM Sans and Nunito Sans, same sizes and weights. No decision yet.
- Published on the same preview link (gerobak-v1-mockups-static-mockups-for-gerobak-v1-vj8y6xxayq.openbot.site) on 2026-11-01, replacing v1.8.1 there; all 13 pages checked, and the D30 version is kept in `../mockups-v3-before-d31/`.


### v1.8.1 (2026-11-01): headings get their own white surface
Owner: "Di sekitar Anda", "Siomay Mas Joko", "Halo, Rizky" and "Isi toko Anda" still blended into the background. The text was already dark and bold (about 16:1 contrast), but each heading sat on the same grey-blue ground as everything around it (D30).
- Screen titles sit in a white header band under a white status bar, with a hairline divider and a soft shadow. Titles are 28 px, with a small blue overline (for example "Profil" or the shop name).
- The map sheet has a white head with "Di sekitar Anda" (24 px) and the search box. The list stays below on the ground.
- The cart page shows the name, status and tags on a white block under the photo. The menu sits below.
- Admin page titles sit on a white title bar.
- Applied to all 12 pages. The design-system page shows the before and after.
- Look only: no feature, priority or acceptance test changed. The rest of the D29 GitHub design stays.

### v1.8 (2026-11-01): mockups follow the GitHub app design
Owner: the existing app design on GitHub is much better than the redesigns. Keep it; only fix headings and titles that blend into the background (D29).
- New mockups in `../mockups-v3/`: every P0 screen rebuilt in the app's own style (blue, rounded white cards, map with a bottom sheet, round BUKA/TUTUP disc, Habis buttons, Plus Jakarta Sans).
- Heading fix: screen titles 26 px weight 800 in navy; sheet titles 22 px; card titles 17 px; small labels 12 px bold dark grey; secondary text darkened from #8C949F to #4F5B6B.
- D29 replaces the visual parts of D22, D23 (bar instead of disc, Habis switch, tab named Toko saya), D24 and D28. The seller's third tab stays **Akun**, opening on Toko saya, as F-16.AC1 says.
- One phone per state (Android 360 × 800). iOS uses the same screens; only sign-in adds Sign in with Apple.
- The GitHub dark-mode setting is left out (not in scope). The GitHub "Studio demo" panel becomes the admin Demo page.
- No feature, priority or acceptance test changed.

### v1.7 (2026-11-01): OpenDesign redesign proposal
Owner requested OpenDesign and chose **Create a new system**. D28 keeps the blue brand and existing P0 scope, with a new layout and component proposal.
- New source: `../opendesign/mockups/gerobak-redesign/index.html`; reusable system in `../opendesign/design-systems/gerobak-product/`.
- Solid white headers, white outlined groups, 6 px cards/buttons and 4 px chips. Android 360 × 800 and iOS 393 × 852 remain side by side. Body sizes remain 16/17 with 13 secondary copy.
- Buyer, seller and admin pages include their main failure states. Photos and maps are labelled placeholders/illustrations; all data is illustrative.
- Seller onboarding and information ownership (D27), visibility control (D26), freshness rules, three-tap cash sale and sign-in requirements are unchanged.
- No new P0 feature or acceptance criterion. Reviews remain P1 and Q7/Q8 remain open. The new visual system is a review proposal; no claim of app implementation or real-device timing verification.
- Published 2026-11-01 on the existing preview link (the server allows one site), after a browser check of all 12 pages. The earlier v2 mockups stay in `../mockups-v2/` as history and can be republished.

### v1.6.1 (2026-11-01): seller information belongs to the seller
Owner clarification (D27): sellers supply and maintain all their shop information. Admins read it and decide whether the seller may appear to buyers; they never create or edit seller details.
- F-01 moves from the admin console into the seller app. Field agents coach the seller; they do not enter information through the console.
- F-08 shows seller-provided details read-only, with **Tampil ke pembeli** as its only seller-management change.
- F-12 accepts a new seller number after its one-time code; the seller then completes their shop information. Returning sellers keep their existing account.
- Admin editing on a seller's behalf is removed from Phase 1 too. Corrections come from the seller.
- D26 visibility timing and hidden-seller behaviour stay unchanged. This is a product clarification; revised onboarding effort still needs the CTO check.

### v1.6 (2026-11-01): the admin console gets simpler: one visibility switch
Owner: the admin console is too much for now (D26). **No P0 feature was added or removed**: F-08 got smaller, and F-18 gained one rule about hidden sellers.
- **Removed:** the **Daftar menu** page. The dish list is fixed and ships with the app; adding or renaming a dish is P1.
- **Removed:** editing a seller's profile and menu from the console, and the separate **Nonaktifkan** flow.
- **Added:** one **Tampil ke pembeli** switch per seller. Off hides the seller from the buyer map and lists within 1 minute, stops them tapping Buka, and their phone says *Disembunyikan admin*.
- **F-18** doesn't count hidden sellers as Buka or Hilang, and names them in one line under the numbers.
- **Mockups:** `admin-sellers.html` (one switch, dish-list screen removed), `admin-monitor.html` and `admin-demo.html` (nav without Daftar menu). Demo script gains a step: the admin hides and restores Pak Made.

### v1.5 (2026-11-01): admin visibility monitor
- **New F-18 Pantau visibilitas (P0):** the Owner asked for a quality-control screen where admins see which sellers are visible to buyers. One live list and map of all real sellers, problems first, with a likely reason and a one-tap WhatsApp to the seller (D25).
- Mockup: `../mockups-v2/admin-monitor.html` (laptop, 2 states).
- Effort not yet checked by the CTO.

### v1.4.1 (2026-11-01): solid headers, cards, smaller corners
Look only. **No requirement, feature or acceptance test changed.**
- Owner feedback: some content blended into the background, especially headers, and corners were too round (D24).
- **Headers:** every screen title sits on a white bar with a divider line, including the status bar area.
- **Cards:** content groups (cart title block, profile header, stats, lists, status) sit on white cards with a thin outline.
- **Corners:** cards 8, buttons 8, the big BUKA button 10, chips 6, tags 4, sheets 16 (were 16–28 and full pills).
- Sign-in and the location explanation are full white screens.

### v1.4 (2026-11-01): design redone from scratch for Android and iOS
The Owner asked to research the design from scratch, for both platforms. **No requirement or acceptance test changed**; three layout calls changed (D23).
- **New mockups:** `../mockups-v2/` (open `index.html`). Every screen state is drawn on Android (360 × 800 dp) and iOS (393 × 852 pt) side by side. The v1 folder stays as history.
- **One design, two native skins (D22):** shared colours and content; each platform's own fonts (Roboto, SF Pro), bars, back, tabs, switches, segmented controls and sheets. Brand blue stays (D19).
- **Research page** (`research.html`): who and where, the platform rules we follow (48 dp / 44 pt touch targets, 16 / 17 body text), map-app patterns, and what changed from v1.
- **iOS sign-in shows Sign in with Apple next to Google** (Apple's App Review guideline 4.8), in Phase 1 with the iOS app.
- **Research supports Q7 option B:** on both platforms "Always" location is a second, separate step after "while using".

### v1.3 (2026-11-01): blue stays; layout and sizing revamp
Look only. **No requirement, feature or acceptance test changed.**
- The Owner tried a black-and-white style (D20), then chose to **keep the app's blue** (D19 stands) and fix **layout and sizing** instead (D21). D20 is withdrawn.
- **Real phone size:** mockups are now drawn at 360 × 780, a common Android size, instead of 300 wide, which squeezed every screen.
- **Type scale:** body 15–16 px, secondary text 13 px, nothing below 12 px. Titles 20 / 24 / 28 px.
- **Lists:** each row is photo, name and one line of facts, then status. Nothing wraps; long text ends with "…". Rows are at least 72 px tall.
- **Spacing:** one 8-point grid, 16 px side margins, 16 px between blocks.
- **Tap targets:** buttons 52 px, small buttons, chips and round buttons 44 px.
- **Seller home:** the BUKA/TUTUP button grows to 200 px, with room around it.

### v1.2.1 (2026-11-01): mockups follow the app's blue look
Mockups only. **No requirement, feature or acceptance test changed.**
- The Owner asked for the mockups to follow the current app's blue colours (D19, replaces D10).
- Every mockup page is recoloured: grey-blue ground `#F4F7FB`, blue for action `#1E6BFF`, navy `#0D1B2E` for the dark button and active chips, green `#12A37D` for open, white cards. Titles are less heavy, as in the app.
- The values come from screenshots of the current demo app. Where a shade differs, the app's own colour wins in the build.

### v1.2 (2026-10-29): sellers set up their own page
The Owner asked for a page where the seller sets up the menu with photos and descriptions, sees how many people follow them, and sees reviews like Google reviews.

- **New F-16 Toko saya (P0):** in the seller's Akun tab. Cart photos (up to 5), a short description, and a photo and description per menu item. Shows the follower count. The seller can add, change and delete menu items themselves; before, only the field agent could (D17).
- **New F-17 Ulasan (proposed P1, Q8):** star ratings and short reviews, only from buyers who were near the cart while it was open; the seller can reply and report but not delete (D18). Reviews were in Phase 3 (section 13); this brings them forward to the pilot.
- **F-02 and F-05:** a menu item now has an optional description; the cart page shows the cart description, item photos and descriptions, and the follower count.
- **Mockups:** new `seller-toko.html` (6 screens; screens 4–6 are P1).
- **Effort:** F-16 waits for Kai's estimate. Ready status for everything else is unchanged.

### v1.1 (2026-10-28): CTO pressure test folded in · Ready
Kai's check: nothing blocks the demo. About 55–65 engineer-days in total (CTO estimate, section 13.1). Changes:

- **Two apps, Pembeli and Penjual** (D11, closes Q5). The Play Store allows one "location while closed" feature per app, and the seller app needs it for Buka.
- **Acceptance tests made testable:**
  - F-04.AC6: the pin updates within 30 s of the cart's latest position, not of every movement. F-04.AC3: Habis items don't count as available.
  - F-08.AC1: the cart leaves the map within 1 minute; the seller's phone is signed out the next time it connects.
  - F-11.AC1: **Tunai is preselected**, so one cash sale is 3 taps: + Penjualan, item, Simpan (D13).
  - F-13.AC1: admins see exact counts; the "hide under 3" rule applies to what sellers see in membership. Defined what counts as a search and which area it counts in (D15).
  - F-03.AC2: tested on a real phone. F-07.AC1: the seller's own views don't count. F-10.AC1: a freshness rule and a ±100 m tolerance.
- **Moved to P1, invisible in the demo** (D14): editing a sale (delete stays), and changing the dish list (there is no console page for it in Phase 0; D26).
- **New:** F-09.AC4, the simulation stops on its own after 2 hours, to stay inside the current hosting budget (D16).
- **Share links** use a free temporary address in the demo; an own web address comes with the pilot (D12).
- **Phase 1** now lists the paid items for the Owner and the pilot-only work (map hosting and store listing; the street-name alert was later removed by D43).
- **No P0 feature was added or removed.** D3 is unchanged; Kai recommends a change, which is open as Q7 for the Owner.

### v1.0.1 (2026-10-28): mockups follow the existing app
Mockups only. **No requirement, feature or acceptance test changed.**

- The mockups now continue the **existing app's design system** (D10) instead of a new one: cream ground, white borderless cards, coral for action, ink pills, pastel emoji tiles, heavy display type.
- Colours, radii and weights are sampled from the app's own screens. Where a value differs by a shade, the app's token wins in the build.
- Restyled pages: sign-in (buyer and seller), the map with the app's header and pins, the cart page, the seller home with the round BUKA/TUTUP control, and the design system page.

### v1.0 (2026-10-28): visibility first
The Owner refocused the product: **Gerobak is first a visibility app.** Buyers see the carts around them. Sellers get a new distribution channel just by broadcasting where they are. Anything that is hard on day one is removed.

- **Kept:** onboarding, profile and menu, Buka/Tutup with live location, map and nearby list, cart page, follow.
- **New:**
  - **F-10 Dekat Anda**: a push when a followed cart is near the buyer (D3)
  - **F-11 Catat penjualan**: the seller records a sale in 3 taps (D5)
  - **F-13 demand signals**: buyer searches and cart page views counted by area and hour (D6)
  - **one global notification switch** (D7)
- **Sign-in is asked at the first action**, not before the map (D36, supersedes D4).
- **Removed for now (moved to Phase 3, section 13):**
  - Teriak (shout) and the yes/no claim
  - QR ordering and QRIS payment
  - Transaksi, Keuangan, cash drawer, Cek awal, Stok perkiraan
  - Jadwal pintar, Rencana hari ini, Peta keramaian, the heatmap and forecast
  - Komunitas, Reviews, the sponsored Populer row
  - Pengingat, seller tiers and billing, the Free 4-hour limit
- **Simplified:**
  - The seller app has 3 tabs (Beranda, Penjualan, Akun) instead of 5.
  - The buyer app has 3 tabs (Peta, Diikuti, Profil).
  - The notifications drop from 16 kinds to 2.
- **Membership** for sellers (demand locations, sales history and more) is planned for Phase 2 (D8). Phase 0 and the pilot are free (D1).

---

## 1. Summary

Gerobak shows **where street-food carts (*gerobak*) are right now**.

- **Buyers** open a map, see the open carts around them with what they sell, follow their favourites, and get a push when a favourite opens or comes near.
- **Sellers** tap **Buka** and appear on the map. It's a new way to be found, far beyond the bell's range. They record each sale in 3 taps and see their day's takings.
- **Gerobak** builds a data asset as a side effect: where carts go, what sells where and when, and what buyers look for. Later a paid **seller membership** turns that data into insights (Phase 2).

---

## 2. Problem

| Who | Problem today | Tag |
|---|---|---|
| Buyers | Roaming carts are found by sound (the bakso bell, the nasi goreng "tek-tek") or by luck. You can't tell what's nearby or when your favourite cart passes | Assumption (from v0.9 and the Owner) |
| Sellers | Their only "marketing" is a bell with a short range and a habitual route. Regulars (*langganan*) lose track of a cart that moves | Assumption |
| Sellers | Many keep no record of sales, so they can't tell which spots and hours pay off | Assumption, to validate in the pilot |
| Market | Delivery apps (GoFood, GrabFood) serve fixed shops. Roaming carts are largely unserved | Assumption |

**Opportunity:** a digital bell with a much bigger reach. Every Buka, sale and search becomes data that sellers will later pay to see.

---

## 3. Options considered

| Option | Pros | Cons | Result |
|---|---|---|---|
| **A. Visibility first** (map, follow, alerts, simple sales record) | Easiest to explain and build; useful from the first cart; builds data from day one | Less "wow" than shouting; earns nothing until membership | **Chosen by the Owner (D0)** |
| B. Shout and claim (v0.9 Teriak) | New and exciting; the buyer gets the cart to come to them | Needs many active sellers answering live, or shouts go unanswered | Phase 3 |
| C. Cashier and books (v0.9 Transaksi and Keuangan) | Used daily | Competes with free tools (BukuWarung, Qasir); payments and merchant onboarding are heavy | Only the 3-tap sale record is kept (F-11) |

**Cons accepted:** no buyer-to-seller call in v1, and no revenue before membership.

---

## 4. Goals and metrics

| ID | Goal | Metric | Target |
|---|---|---|---|
| G1 | Buyers find open carts near them, and what each one sells, in seconds | Time from opening the app to seeing the first cart; share of sessions that open a cart page | To validate in the pilot |
| G2 | Sellers get a new channel: more people see them | Cart page views per seller per day; new followers per seller per week | To validate |
| G3 | Followed carts bring buyers back | Share of buyers with at least 1 follow; share of pushes that are tapped | To validate |
| G4 | Build the data asset | Share of Buka hours with location; sales recorded per Buka day; searches per day | To validate |
| G5 | Phase 0: the demo convinces the Bali counterpart | Every step of the demo script (section 12) works on two Android phones twice in a row, with a reset in between | Pass |

No targets are set yet because there is no real data. The pilot sets them.

---

## 5. Users

| ID | Persona | Needs |
|---|---|---|
| P1 | **Local buyer**: lives or works in Bali and buys from carts often | Know when their usual cart is open and near; find something new close by |
| P2 | **Tourist buyer**: in a villa or guesthouse, curious about street food | See what's around, prices, and whether it's halal |
| P3 | **Roaming seller**: push cart or motorbike cart moving through neighbourhoods | Be found; keep regulars; little typing |
| P4 | **Regular-spot seller**: the same corner most evenings | Let people know they're open |
| P5 | **Field agent**: our Bali team member who helps sellers sign up in person | Coach sellers through setting up their own shop and menu |
| P6 | **Admin**: runs the platform and the demo | Read seller information, control who buyers can see, run the demo |

For now one seller = one cart = one phone. The owner is the seller.

---

## 6. Journeys

### J1: A buyer finds a cart nearby (P1, P2)
1. Opens Gerobak and sees the map, the list and search without an account (F-04.AC7); signs in with Google and accepts the terms when they open a cart (F-12).
2. The map centres on them and shows open carts within 3 km (F-04).
3. Searches "bakso", taps a card to bring that cart's pin forward, then taps its **Profil** button → cart page (F-04.AC9, F-05). A pin opens the cart page directly.
4. Sees the menu, prices, Halal or Non-halal label and last seen → walks there.

**Unhappy paths**
- **Location denied:** the map opens on Batu Bolong, Canggu, with a banner, *"Aktifkan lokasi untuk melihat gerobak di sekitar Anda"*.
- **No carts within 3 km:** *"Belum ada gerobak buka di sekitar Anda"*, plus the followed carts.
- **The cart hasn't reported in a while:** dimmed, *"terakhir terlihat 14 menit lalu"*. After 30 minutes it's hidden.
- **No signal:** the last map stays, with *"Tidak ada koneksi"*.
- **Declines the terms:** signed out, back to the sign-in screen.

### J2: A buyer follows a cart and gets alerts (P1)
1. Taps **Ikuti** on a cart page (F-06).
2. First follow only: a short screen explains why the app needs location. The phone asks for permission (F-10).
3. Saves a place (Rumah or Kantor), pre-filled from the current position or set by moving the map pin. Can skip (D59).
4. Later: *"Bakso Pak Made buka sekarang di Canggu. Lihat di peta."*, and *"Bakso Pak Made 300 m dari Anda"* → tap → the map flies to the cart.

**Unhappy paths**
- **Denies location and skips saving a spot:** "open" alerts only, and Profil shows a reminder.
- **Notifications blocked on the phone:** a banner in Profil with a button to the phone's settings.
- **Too many alerts:** turn off **Notifikasi gerobak favorit**, or unfollow the cart.
- **Takes the permission away later:** the app switches to the saved spot and says so once.

### J3: A seller opens and is visible (P3, P4)
1. Signs in once with Google (F-12). Stays signed in.
2. Taps **BUKA**, checks the confirmation and taps **Ya, buka** (F-03) → appears on buyers' maps within a minute and followers get a push.
3. Moves around. The position keeps updating, even with the screen off.
4. Taps **Habis** on an item that's sold out (F-02).
5. Taps **TUTUP**, then **Ya, tutup** → disappears from the map.
6. Looks at **Rute hari ini** on Beranda: where they went, how long they were open and how far they travelled (F-19).

**Unhappy paths**
- **Location off on the phone:** Buka is refused, with a button to turn location on.
- **Taps BUKA or TUTUP by mistake:** the confirmation sheet appears; **Batal**, back or a tap outside leaves everything as it was (F-03.AC11).
- **No signal for a while:** the cart shows as "last seen" and positions upload later.
- **The phone dies or stops recording locations:** after 10 minutes the pin is dimmed; after 30 it is removed from the map while Buka remains selected. On return the seller sees *"Buka · Tidak terlihat"* and chooses **Lanjut Buka** (requires a fresh position) or **Tutup**. A mere loss of signal is different: positions and sales recorded on the phone upload later, and a recent recorded position restores visibility automatically.
- **Forgets to tap Tutup, or loses signal:** no stale location stays public. Hidden after 30 minutes; after 60 minutes without a position the shift closes by itself (D69), and the seller sees why when the phone reconnects.

### J4: A seller records a sale (P3, P4)
1. While Buka, opens **Penjualan** and taps **+ Penjualan** (F-11).
2. Taps items (one tap = one portion), picks **Tunai** or **QRIS**, then **Simpan**.
3. Beranda shows *"Hari ini: 23 porsi · Rp 345.000"* (F-07).

**Unhappy paths**
- **Not Buka:** the button is disabled, with *"Buka dulu untuk mencatat penjualan"*.
- **No signal:** the sale is saved on the phone and uploaded later.
- **A mistake:** delete the sale the same day and record it again. Editing a sale comes in P1 (D14).

### J5: A seller sets up their shop, with coaching if needed (P3, P4, P5)
1. In the seller app, the seller signs in with Google and accepts the terms (F-12).
2. They complete shop details first: name, cart photo taken or picked from the phone, type, Halal or Non-halal, WhatsApp number for the admin and payment methods. Next they add at least one menu item: name, **Jenis menu** (Makanan, Minuman or Camilan), a fixed or variable price, and an optional photo (F-01).
3. They save. The admin can read the submitted information and control **Tampil ke pembeli**, without changing any detail (F-08).

**Unhappy paths**
- **The Google account already has a shop:** sign in to the existing shop; never create a second shop for the same account.
- **A required detail is missing:** keep the entered information and highlight what must be completed.
- **A photo won't upload (weak signal):** the photo stays on the phone with **Foto belum terkirim** and is sent automatically later; setup is not blocked (F-01.AC7).
- **A detail is wrong:** the seller corrects it in **Toko saya**; an admin may contact them but cannot make the correction.

### J7: A seller asks their followers a question (P3, P4, P1)
1. In Akun → Toko saya, the seller taps **Buat polling**, writes *"Menu baru apa yang Anda mau minggu depan?"* and three answers, picks **3 hari** and taps **Mulai polling**, then **Ya, mulai** (F-22).
2. A follower opens the cart page or sees *Polling · sisa 2 hari* in Diikuti, taps an answer and sees the results so far.
3. The seller watches the counts on Beranda and Toko saya. When the time runs out, the poll shows **Selesai** with the most-chosen answer.

**Unhappy paths**
- **A non-follower taps an answer:** a sheet offers **Ikuti & pilih**; signed-out visitors sign in first (D36).
- **The seller made a typo after starting:** no editing; **Hapus** and start again (votes are lost, the confirmation says so).
- **The poll ends while a buyer is looking:** their tap is refused with *"Polling sudah selesai"* and the final results show.
- **No signal:** the seller can't start (*"Butuh sinyal untuk memulai polling"*); a buyer's vote isn't counted until it reaches us, and the app says so.
- **Nobody votes:** the seller sees *Belum ada suara*; the poll still ends on time.

### J6: The presenter runs the demo (P6)
See the demo script in section 12.

---

## 7. Features

Priorities: **P0** is needed for Phase 0, **P1** comes next, **P2** later.

### F-01 · Seller-provided onboarding (P0)
*As a seller, I want to enter my own shop information, so buyers and admins see the details I provide.*
- All shop details come from the seller app, including the name, phone, cart type, Halal or Non-halal, payment methods, photos, descriptions, menu, prices and the kind of each item. A field agent may coach the seller in person.
- **Photos (D45):** **Ambil foto** opens the camera, **Pilih dari galeri** opens the phone's photos. The seller sees the photo before saving and can replace or remove it. The app shrinks large photos itself; the seller is never asked about size. There are no stand-in pictures to choose from.
- **No usual selling area (D46):** setup does not ask where the seller usually sells. Buyers see the live position while Buka.
- **Photo choice sheet (v2.3):** the **Ambil foto / Pilih dari galeri / Batal** choice is a bottom sheet over the whole screen, the same for cart photos, menu photos and Toko saya.
- **F-01.AC1:** Given a seller has signed in and accepted the terms, when they complete step 1 with name, one cart photo from the camera or gallery, cart type, Halal or Non-halal and WhatsApp number, then step 2 with at least one menu item with a name, a **Jenis menu** (Makanan, Minuman or Camilan) and a fixed price or variable-price choice, then their shop is created and the admin sees the same submitted information read-only. Step 1 has no usual-selling-area field (D46).
- **F-01.AC2:** Given a Google account already belongs to a shop, when its owner signs in, then that existing shop opens and no duplicate shop is created.
- **F-01.AC3:** Given the seller adds photos, when they save, then the same photos are available in their shop information for the admin to read and on the buyer page when visibility permits.
- **F-01.AC5:** Given a new seller, when they complete step 1 and go to step 2, then their shop details remain filled if they go back; they cannot finish without at least one valid menu item. If they leave before step 2, step 1 stays on that phone; no shop is created or visible to admin until step 2 is saved.
- **F-01.AC4:** Given required details are missing, when the seller saves, then the incomplete fields are identified and their entered information is retained.
- **F-01.AC6:** Given step 1, when the seller taps the cart photo area, then they can choose **Ambil foto** or **Pilih dari galeri**; the chosen photo shows as the cover before saving, with **Ganti** and **Hapus**. A menu item offers the same two choices and can be saved without a photo.
- **F-01.AC7:** Given a photo is chosen on a weak or no signal, when the seller saves, then the shop or item is saved, the photo shows **Foto belum terkirim** on the seller's phone and is sent automatically when the signal returns; buyers see it within 1 minute of arrival. Until then buyers see the plain placeholder, never a broken image.
- **F-01.AC8:** Given the phone refuses camera or photo access, when the seller taps **Ambil foto** or **Pilih dari galeri**, then the app explains why it needs access with a button to the phone's settings, and the other choice still works.
- **F-01.AC10 (D56):** Given step 1 is filled and the WhatsApp number already belongs to another shop, when the seller taps **Lanjut ke menu**, then step 2 does not open, the number field is marked *“Nomor ini sudah dipakai toko lain. Pakai nomor lain, atau hubungi admin Gerobak jika ini nomor Anda.”* and every other entry stays. The same tap marks any other missing step 1 field. Given there is no signal, step 2 opens and the number is checked again at **Simpan dan mulai**; if it is taken then, the app returns to step 1 with the same message and nothing is lost.
- **F-01.AC11 (D56):** Given a menu in step 2 or Toko saya is missing its name, Jenis menu, or a price (when *Harga tetap* is chosen), when the seller taps **+ Tambah menu**, then no new menu is added, the missing fields of that menu are marked and the view stays on it; **Simpan dan mulai** checks every menu the same way.
- **F-01.AC12:** Given a seller signed in to start setup, when they add, edit or save a menu or a photo before the shop is saved, then they are never told to sign in; if the session has lapsed, it is renewed without a message; if renewal fails, they sign in once and return to the same step with all entries and photos kept.
- **F-01.AC9:** Given any screen with a photo box (setup step 1, a menu item, Toko saya), when the seller taps it, then the choice sheet rises from the bottom edge of the screen over a dimmed page and sits above everything, including the screen title and the bottom button; its title, text, **Ambil foto**, **Pilih dari galeri** and **Batal** are fully visible with nothing overlapping them, on a phone 360 points wide or wider. **Batal**, tapping the dimmed area or the phone's Back closes it and nothing changes.

### F-02 · Seller profile and menu (P0)
*As a seller, I want buyers to see what I sell and the prices, so they come to me.*
- **Profile:** name, cart photo, cart type (*berkeliling* roaming, *menetap* regular spot, fixed), payment methods accepted (Tunai, QRIS, as information only).
- **Profile** also has an optional description (up to 160 characters) and up to 5 cart photos (F-16).
- **Menu item:** name, either a fixed price (Rp) or *Harga sesuai pesanan*, one **Jenis menu** (D55); photo and description (up to 80 characters) optional.
- **Menu photo everywhere (D54):** an item's photo shows wherever the item is listed: seller Beranda, Toko saya, Catat penjualan and the buyer cart page, cropped to fill a square, never stretched or letterboxed. The plain fork-and-knife tile is only for an item without a photo.
- **Halal label (D48):** one choice per cart, **Halal** or **Non-halal**, required at setup and changeable in Toko saya. It replaces the per-item pork flag: a cart that cooks any non-halal food is Non-halal for a Muslim buyer, so a per-item flag says too little. Buyers see **Halal** or **Non-halal** beside the name; the cart page adds *“Status halal menurut penjual”*. The official halal logo is never shown, because it needs a certificate (UU 33/2014). Carts set up before v2.2 that had any pork item become Non-halal; the rest show no label until the seller chooses, prompted by a banner on Beranda that never blocks Buka.
- **Jenis menu (D55, replaces D47 and D53):** three buttons in one row, **Makanan**, **Minuman**, **Camilan**. None is chosen in advance; one is required. There is no dish list, dropdown, search or **Lainnya** for the seller.
- **On the cart page:** the menu is grouped under **Makanan**, **Minuman** and **Camilan**, in that order; a heading with no items is hidden.
- **Kind for items saved before v2.4:** taken from the old dish group. Groups 1–9 and 11 (bakso, soto, mie, nasi, bubur, sate, ayam/ikan/daging, sayur/rujak, siomay/batagor, martabak/makanan barat) and **Lainnya** → **Makanan**. Groups 13–14 (es, minuman manis, kopi, minuman hangat) → **Minuman**. Groups 10, 12, 15 and 16 (gorengan, kue, jajan pasar, roti & kue modern, jajanan Korea & Jepang) → **Camilan**.
- **Dish list (kept, unseen):** `dish-list-v2.md` stays only as the word list for demand counts (F-13). Sellers and buyers never see it.
- **F-02.AC1:** Given a seller, when they tap **Habis** on an item, then buyers see it marked Habis within 1 minute.
- **F-02.AC2:** *Retired in v2.2 (D48), replaced by F-02.AC5.*
- **F-02.AC5:** Given a seller chose **Non-halal**, when a buyer sees the cart in the Peta list or opens its page, then **Non-halal** shows beside the name; given **Halal**, then **Halal** shows, and the cart page adds *“Status halal menurut penjual”*. No cart shows the official halal logo or any pork wording.
- **F-02.AC3:** Given a seller, when they tap **Habis** again, then the item is available again.

- **F-02.AC4:** Given a seller selects *Harga sesuai pesanan* for an item, when buyers see that item, then it shows that label and no numeric price or misleading starting price. The seller can switch between fixed and variable pricing when editing.
- **F-02.AC6:** *Retired in v2.4 (D55).*
- **F-02.AC7:** *Retired in v2.4 (D55).*
- **F-02.AC8:** *Retired in v2.4 (D55).*
- **F-02.AC9:** *Retired in v2.4 (D55).*
- **F-02.AC10:** Given a seller adds or edits a menu item, when they look at **Jenis menu**, then they see three buttons, **Makanan**, **Minuman** and **Camilan**, with none selected for a new item; one tap selects one, and no list or search opens. Given none is selected, when they save, then the field is marked *“Pilih jenis menu”* and everything they entered stays.
- **F-02.AC11:** Given a cart has Makanan and Minuman items but no Camilan, when a buyer opens the cart page, then the menu shows under **Makanan** then **Minuman**, and no **Camilan** heading shows; Habis items stay under their heading, marked Habis.
- **F-02.AC12:** Given a menu item saved before v2.4 with the dish *Es teh manis*, *Pisang goreng* or **Lainnya**, when the seller opens it after the update, then its Jenis menu is **Minuman**, **Camilan** or **Makanan** respectively, and the seller can change it and save.

### F-03 · Buka / Tutup and live location (P0)
*As a seller, I want to be on the map whenever I'm selling, without thinking about it.*
- **Buka:** one big button on Beranda, with no form (D2). **Tutup:** the same button.
- **Confirmation (D49):** each tap on BUKA or TUTUP opens a short sheet first.
  - **Buka sekarang?** *“Gerobak Anda tampil di peta. 12 pengikut dikabari.”* (after the first Buka of the day: *“Pengikut sudah dikabari hari ini.”*) · **Ya, buka** · **Batal**
  - **Tutup sekarang?** *“Gerobak hilang dari peta dalam 1 menit. Penjualan hari ini tetap tersimpan.”* · **Ya, tutup** · **Batal**
  - The confirm button sits at the bottom of the sheet, never under the BUKA/TUTUP disc, so a double tap cannot confirm. There is no “don't ask again”. **Lanjut Buka** (F-03.AC8) needs no second confirmation, because it is already a choice in a prompt.
- **While Buka,** the position is shared even with the screen off. This live position comes from the phone. Android shows a notification for as long as the app runs in the background (D65): **Gerobak Anda tampil di peta** · *Lokasi terkirim selama BUKA. Buka aplikasi untuk TUTUP.* Only the seller app does this, and only while Buka.
- **Freshness** (carried over from v0.9):
  - position updated every 5 minutes or after 150 m of movement
  - **LIVE** up to 10 minutes since the last update
  - **STALE**, dimmed, from 10 to 30 minutes
  - hidden after 30 minutes; after 60 minutes without a position the shift closes automatically (D69)
- **F-03.AC1:** Given a signed-in seller with location on, when they tap BUKA and then **Ya, buka**, then the cart appears on buyers' maps within 1 minute.
- **F-03.AC2:** Given Buka with the screen off for 20 minutes while moving, when a buyer looks, then the pin has moved and is LIVE. Tested on a real phone: Phone B for the demo; before the pilot, also on the low-cost Android models the pilot sellers use (field agents list them; To validate).
- **F-03.AC3:** Given Buka and no update for 10–30 minutes, when a buyer looks, then the pin is dimmed with *"terakhir terlihat N menit lalu"*. After 30 minutes it's hidden.
- **F-03.AC7:** Given Buka and the newest phone-recorded position received by the server is over 30 minutes old, without a Tutup tap, then buyers see no pin or nearby/search result, the admin sees **Hilang**, and the seller sees **Buka · Tidak terlihat** when connected; none says the seller tapped Tutup.
- **F-03.AC8:** Given the phone kept recording positions while offline, when they arrive, then buyer visibility follows the age of the newest phone-recorded position, capped at server receipt time if the phone clock is ahead: LIVE up to 10 minutes, dimmed from 10 to 30, hidden after 30; a delayed arrival alone never resets its age. If the phone itself recorded no position for over 30 minutes, **Lanjut Buka** plus a fresh position restores visibility within 1 minute. Neither recovery sends a second Buka alert that day.
- **F-03.AC9:** *Retired in v2.8 (D69): a lost shift now closes after 60 minutes.*
- **F-03.AC4:** Given location is off on the phone, when the seller taps BUKA, then it is refused with a button to turn location on. If location is turned off mid-shift, the phone immediately shows **Lokasi HP mati — pembeli mungkin tidak melihat Anda**, without waiting for the server timeout.
- **F-03.AC5:** Given Buka, when the seller taps TUTUP and then **Ya, tutup**, then the cart disappears from buyers' maps within 1 minute.
- **F-03.AC14 (D69):** Given Buka and no position from the phone has reached the server for 60 minutes, then the shift ends automatically: the cart is Tutup for buyers (it moves to the Tutup tab in Diikuti), the admin sees **Ditutup otomatis** with the time, and the shift's end time is the time of the last received position, so Lama buka and Rute hari ini stop there.
- **F-03.AC15 (D69):** Given the shift was closed automatically, when the seller's phone reconnects, then Beranda shows **TUTUP** and the banner *"Gerobak ditutup otomatis karena tidak ada sinyal lebih dari 1 jam. Terakhir terlihat 15.02. Tekan BUKA untuk buka lagi."*; the BUKA notification on the phone goes away; positions recorded after the close time are not shown to buyers or added to the route; tapping BUKA uses the normal confirmation and sends no second follower alert that day.
- **F-03.AC16 (D69):** Given sales were recorded offline during the lost hour, when the phone reconnects, then they are saved with their original times and count in that day's totals; none is lost.
- **F-03.AC10:** Given Tutup with location on, when the seller taps BUKA, then the **Buka sekarang?** sheet shows with the number of followers who will be told (or that they were told today); the cart is not on the map, no push is sent and no position is shared until **Ya, buka**.
- **F-03.AC11:** Given the Buka or Tutup sheet is open, when the seller taps **Batal**, taps outside the sheet or presses back, then the sheet closes and nothing changes: no push, no position, no state change.
- **F-03.AC12:** Given the seller taps the disc twice quickly, when the sheet opens, then the second tap lands outside the confirm button and does not confirm; the confirm button is at least 52 px high and sits in the bottom third of the screen.
- **F-03.AC6:** Given positions recorded with no signal, when the signal returns, then they upload with their original times.

- **F-03.AC13 (D65):** Given the seller taps **Ya, buka**, when they leave the app or turn the screen off, then the phone's notification list shows **Gerobak Anda tampil di peta** with *"Lokasi terkirim selama BUKA. Buka aplikasi untuk TUTUP."*; tapping it opens the app (Beranda on a fresh start); on Android 13 and older it cannot be swiped away while Buka, and on Android 14 and newer Android allows swiping it away while location keeps sending; after **Ya, tutup** it disappears within 10 seconds. The buyer app never shows such a notification.

### F-04 · Map and Di sekitar Anda (P0)
*As a buyer, I want to see the open carts around me and what they sell, in seconds, without filling in a form first (D36).*
- **Map:** full screen, centred on the buyer, can be dragged and zoomed. Shows open carts within 3 km, plus followed carts at any distance (with a small heart on the pin). Every pin carries the cart's name in a small label beside it (D44).
- **Bottom sheet, Di sekitar Anda:** Diikuti first, then carts within 3 km by distance. Each row: name, distance, the lowest available fixed item price as *mulai* when one exists (otherwise *Harga sesuai pesanan*), main dishes, LIVE or STALE, and a **Profil** button.
- **Card and pin actions (D44):** tapping a row focuses that cart's pin on the map and marks the row as selected; the **Profil** button on the row opens the cart page (F-05). Tapping a pin opens the cart page directly. The Diikuti and Profil lists keep the one-tap row that opens the cart page, because neither has a map.
- **Search:** filters by cart name or menu, e.g. "keju" finds martabak keju.
- **Sheet heights (D52):** the Di sekitar Anda sheet has three heights. **Kecil:** title, count and search only, most of the map visible. **Sedang** (default): about half the screen. **Penuh:** the sheet covers the map up to just below the status bar; a **Peta** button at the top and the handle bring the map back. The seller drags the handle or the sheet head, or taps the handle to step up (Kecil → Sedang → Penuh → Sedang). The list scrolls inside the sheet at every height.
- **F-04.AC15 (D68):** Given a cart with 12 reviews averaging 4,3, when it appears in Di sekitar Anda or in search results, then its card shows *★ 4,3 (12)* next to the distance; a cart with 0 reviews shows no stars.
- **F-04.AC1:** Given location allowed, when the buyer opens Peta, then the map centres on them and shows open carts within 3 km.
- **F-04.AC2:** Given a followed cart is open 8 km away, when the buyer opens Peta, then it's in the Diikuti section of the list.
- **F-04.AC3:** Given the buyer types "bakso", when results show, then only carts with an available bakso item are listed. An item marked Habis doesn't count as available.
- **F-04.AC4:** Given location denied, when the buyer opens Peta, then the map opens on Batu Bolong, Canggu, with a banner to turn on location.
- **F-04.AC5:** Given no open carts within 3 km, when the buyer opens Peta, then the empty state *"Belum ada gerobak buka di sekitar Anda"* shows.
- **No account needed:** the map, list and search open for a visitor who has not signed in. Only public facts show: name, distance, the lowest available fixed item price as *mulai* when one exists or *Harga sesuai pesanan*, main dishes, LIVE/STALE. A card's tap focuses the pin and is open to visitors too; opening a cart (pin or **Profil**), Ikuti, ulasan, saved places and alerts ask for sign-in (F-12.AC4).
- **F-04.AC7:** Given a visitor has not signed in, when they open Peta, then the map, the Di sekitar Anda list and search work; tapping a card focuses its pin without an account, while tapping a pin, a **Profil** button or Ikuti asks them to sign in without losing the map.
- **F-04.AC6:** Given the map is open, when a cart sends a new position, then its pin moves within 30 seconds. (Carts send a position every 5 minutes or 150 m, so a pin can be up to 5 minutes behind the real cart. Accepted.)
- **F-04.AC8:** Given the map shows open carts, when the buyer looks at a pin, then the cart's name shows in a small label beside it, shortened with “…” when it does not fit; a STALE pin keeps its name and is dimmed; a cart hidden after 30 minutes shows no pin and no name. Where two labels would overlap, the nearer cart keeps its label and the other shows its pin only until the map is zoomed in. A focused pin's label always shows.
- **F-04.AC9:** Given the buyer taps a card in Diikuti, Terdekat or the search results, when the card is released, then the map moves that cart's pin above the sheet, the pin is drawn larger with its name bold, and the tapped card is marked as selected; the cart page does not open and the buyer stays on Peta. This works without an account.
- **F-04.AC10:** Given a card in the Peta list is visible, when the buyer taps its **Profil** button, then that cart's page opens (F-05); a signed-out visitor is asked to sign in first (F-04.AC7). The button is at least 44 × 44 px and carries the cart's name for screen readers.
- **F-04.AC11:** Given the sheet is at Sedang, when the buyer drags the handle up past the middle of the remaining space and lets go, then the sheet settles at Penuh and shows at least 4 full cards on a 360 × 800 screen (about twice as many as Sedang); dragging down settles at the nearest lower height.
- **F-04.AC12:** Given the sheet is at Penuh, when the buyer taps **Peta** or drags the head down, then the sheet returns to Sedang and the map shows the same carts, centre and zoom as before.
- **F-04.AC13:** Given the sheet is at Kecil or Sedang, when the buyer taps the search box, then the sheet opens to Penuh with the keyboard up; clearing the search and closing the keyboard returns it to the height it had before.
- **F-04.AC14:** Given the sheet is at Penuh, when the buyer taps a card, then the sheet drops to Sedang and the card's pin is focused above the sheet (F-04.AC9).

### F-05 · Cart page (P0)
*As a buyer, I want to know if a cart is worth walking to.*
- **Content:**
  - photo, name, cart type, **Halal** or **Non-halal** with *“Status halal menurut penjual”*, payment methods
  - LIVE, or last seen; distance
  - the cart's description
  - **numbers row (D64):** ★ rating · ulasan count · pengikut, e.g. *★ 4,8 · 27 ulasan · 214 pengikut*; with 0 reviews, *Belum ada ulasan*; from the first review the average shows with the count (D68)
  - **pengumuman (D67)** when the seller has one
  - menu with prices, Habis labels, and each item's photo and description when set
- **Actions:**
  - **Lihat di peta**
  - **Ikuti**, or **Diikuti** to unfollow
  - **Bagikan**: a share link that opens a web page with the cart's name and menu. Phase 0 uses a free temporary web address; from the pilot, Gerobak's own address, and the link opens the app when it's installed (D12)
- **F-05.AC1:** Given a buyer taps a pin on the map, or a card's **Profil** button, when the cart page opens, then it shows all the content above. A cart page is also reachable from Diikuti, Profil and a shared link.
- **F-05.AC5 (D64):** Given a cart has 27 reviews averaging 4,8 and 214 followers, when a buyer opens its page, then *★ 4,8 · 27 ulasan · 214 pengikut* shows under the name; tapping *27 ulasan* scrolls to the reviews.
- **F-05.AC2:** Given a cart is Tutup, when a follower opens its page, then it shows *"Tutup"* and the time it was last open.
- **F-05.AC3:** Given a buyer taps Bagikan, when the share sheet opens, then it includes a link to the cart's page.
- **F-05.AC4:** Given a buyer opens a followed cart page while its latest position is over 30 minutes old, then it says **Lokasi tidak tersedia sejak [time]**, shows no distance or map/route action, and does not label the seller Tutup unless they tapped Tutup.

### F-06 · Ikuti and the "open" alert (P0)
*As a regular, I want to know when my favourite cart is selling.*
- **Ikuti** from the cart page or the list. Followed carts appear in **Diikuti** under separate **Buka** and **Tutup** tabs, with a search for cart name or dish inside the selected tab.
- **Push:** *"Bakso Pak Made buka sekarang di Canggu. Lihat di peta."* on the first Buka of the day. Use the broad area of the cart's current LIVE position, not a street name or the usual selling-area label when the cart is elsewhere. If a reliable area is unavailable, say *"Bakso Pak Made buka sekarang. Lihat di peta."* The map provides the precise pin.
- **One global switch** in Profil, **Notifikasi gerobak favorit**, on by default, for both F-06 and F-10 alerts (D7).
- **F-06.AC1:** Given a buyer follows a cart and the switch is on, when the cart opens for the first time that day with a LIVE position in a known broad area, then they get one push naming the cart and area with **Lihat di peta**; it contains no street name. If the current area is unknown, the same push omits the area. The second Buka that day sends no push.
- **F-06.AC2:** Given the switch is off, when a followed cart opens or comes near, then no push is sent.
- **F-06.AC3:** Given the switch is turned back on, when a followed cart next opens or comes near, then the push is sent again (still at most 1 of each per cart per day).
- **F-06.AC4:** Given the switch is on but notifications are blocked on the phone, when the buyer opens Profil, then a banner, *"Notifikasi diblokir di pengaturan HP"*, shows with a button to the phone's settings.
- **F-06.AC5:** Given a buyer taps the push, when the app opens, then the map flies to that cart.

### F-07 · Seller stats, light (P0)
*As a seller, I want proof that Gerobak brings me customers, so I keep using it.*
- **Beranda, today:**
  - *"Dilihat 48 kali"*: cart page views, counting each buyer at most once an hour
  - *"+3 pengikut"*: new followers
- **Pengikut card (D57):** on Beranda below **Hari ini**: total followers, new this week, a 7-day bar of new followers per day, and who gets the Buka alert. Counts only, never names.
  - *"23 porsi · Rp 345.000"*: from F-11
- **Penjualan:** the last 7 days, one row per day, with portions and total.
- **F-07.AC1:** Given 2 buyers opened the cart page today, one of them twice in the same hour, when the seller opens Beranda, then *"Dilihat 2 kali"* shows. The seller's own views never count.
- **F-07.AC3:** Given the seller opens Beranda, when the **Hari ini** card shows, then Dilihat, Pengikut baru and Porsi are today's real counts for this shop (WITA day), refreshed at least each time Beranda opens; no example or fixed number appears in any build used by sellers.
- **F-07.AC4:** Given nobody viewed the cart today, when the seller opens Beranda, then Dilihat shows **0** and the line *“Belum ada yang melihat gerobak Anda hari ini. Tekan BUKA agar pembeli di sekitar melihat Anda.”*
- **F-07.AC5 (D57):** Given 214 buyers follow the cart and 9 followed in the last 7 days, when the seller opens Beranda, then the **Pengikut** card shows *214*, *+9 minggu ini*, one bar per day for the last 7 days (today highlighted) and *“214 pengikut dikabari saat Anda BUKA, sekali sehari. Nama mereka tidak ditampilkan.”*; no buyer names anywhere. Given 0 followers, it shows 0 and how buyers follow (**Ikuti** on the cart page).
- **F-07.AC2:** Given sales recorded on 3 of the last 7 days, when the seller opens Penjualan, then 7 rows show, with zero on the days without sales.

### F-08 · Admin console (P0)
*As an admin, I want to read seller-provided information and control who buyers can see, so I can check quality without changing their details.*
- **Sellers:** list and search by name or phone. Open a read-only detail view of the seller’s name, phone, cart type, Halal or Non-halal, payment methods, photos, descriptions and menu, including prices and dishes. No **+ Penjual baru**, edit or save-details controls (D27).
- **One switch per seller, Tampil ke pembeli:**
  - **On:** the seller behaves normally (F-03, F-04).
  - **Off:** hidden from the buyer map and lists within 1 minute, can't Buka, and the seller's phone says *Disembunyikan admin* the next time it connects. The account, number and menu stay, so switching it back on restores everything. If the seller was Buka, they come back only when they tap Buka again.
- **Not in the console (D26, D27):** creating sellers or editing any seller detail. Sellers enter and correct their own information. There is no **Daftar menu** page. The dish list is fixed and ships with the app; a new dish is requested from Pia or Kai and is P1.
- **F-08.AC1:** Given an admin switches a seller off while the seller is Buka, when buyers look, then the cart is gone from the map within 1 minute. The seller can't Buka, and their phone shows *Disembunyikan admin* the next time it connects.
- **F-08.AC2:** Given a seller is switched off, when the admin switches them back on, then the seller can Buka again and appears on the map at their next Buka, not before.

- **F-08.AC3:** Given a seller has saved shop information, when an admin opens its details, then the submitted values are displayed read-only with no creation or editing controls; only **Tampil ke pembeli** can change seller management state.
- **F-08.AC4:** Given an admin changes **Tampil ke pembeli**, when the seller information is read again, then every profile and menu value remains unchanged.

### F-09 · Demo simulation (Phase 0 only, no admin screen) (D33)
*As the presenter, I want a busy, believable map anywhere in Canggu and Seminyak, without a demo panel in the admin console.*
- **Carts:** 20–30 simulated carts with real-looking menus and photos, moving along real roads (push cart about 4 km/h, motorbike about 20 km/h). Buyers see them exactly like real carts.
- **Turning it on:** the team starts the simulation before the demo. There is **no screen for it in the admin console, the seller app or the buyer app**.
- **Auto-stop:** the simulation stops on its own 2 hours after it starts, and simulated carts send positions at the same pace as real ones, so a forgotten simulation can't run up the hosting bill (D16).
- **No fake history** is needed.
- **F-09.AC1:** Given the simulation is running, when a buyer opens Peta in Canggu, then at least 10 carts are visible and moving.
- **F-09.AC2:** Given a followed simulated cart, when it moves within 500 m of the buyer, then the F-10 push arrives.
- **F-09.AC3:** Given the simulation runs for 2 hours, when the time is up, then it stops on its own and simulated carts disappear from the map.
- **F-09.AC4:** Given any admin, seller or buyer screen, when it is open, then there is no control for the simulation anywhere.
- **F-09.AC5:** Given the simulation stops after two hours, then each simulated cart explicitly ends its Buka session and does not remain Hilang in admin or Diikuti.

### F-10 · Dekat Anda: followed cart near you (P0)
*As a regular, I want a push when my favourite cart is near me.*
- **What "near" means (D59, supersedes D3):** a followed open cart within about 500 m of:
  - a **saved place**, **Rumah** or **Kantor** (up to 2), at any time, app open or closed; or
  - the **buyer's own position while the app is open**, if they allowed location *while using the app*.
  - With no saved place and the app closed, there are no "near" alerts. Following and "open" alerts still work.
- **Never "always":** the buyer app does not ask for location *all the time* and does not track the buyer in the background. This may be revisited after the pilot (P1), only with the Google Play background-location review.
- **First follow:** a short screen, *"Kabari saya saat gerobak favorit lewat dekat Rumah atau Kantor"*, then **Simpan tempat**. The spot is pre-filled from the buyer's current position if they allow location while using the app; otherwise they move the map pin to the spot. The buyer can skip.
- **Privacy:**
  - Sellers never see buyers.
  - The buyer's position is used only to check distance to followed carts.
  - No history of where the buyer has been is kept.
- **Limits:** at most 1 "near" push per cart per day (Bali time). Controlled by the global switch (F-06).
- **Timing:** saved places don't move, so the alert follows the cart's position updates (every 5 minutes or 150 m). A buyer away from their saved places with the app closed gets no "near" alert (accepted, D59).
- **F-10.AC1 (D59):** Given a buyer saved **Rumah** and follows an open cart with a LIVE position no more than 10 minutes old, when the cart comes within 500 m of Rumah, with the app open or closed, then the buyer gets one push, e.g. *"Bakso Pak Made 300 m dari Rumah"*; given the app is open with location allowed while using it, when the cart comes within 500 m of the buyer, then the push says *"…300 m dari Anda"*. The test passes between 400 and 600 m. At no point does the buyer app ask for location *all the time*.
- **F-10.AC5:** Given a cart is dimmed or hidden because its newest recorded position is over 10 minutes old, then it triggers no Dekat Anda alert; after recovery, the normal one-per-day limit applies.
- **F-10.AC2:** Given location denied and a saved spot, when a followed cart comes within 500 m of that spot, then the push names the spot (*"…dari Rumah"*).
- **F-10.AC3:** Given a push already sent today for that cart, when it comes near again, then no second push is sent.
- **F-10.AC6 (D60):** Given a buyer received the **buka** push for a followed cart less than 15 minutes ago, when that cart comes within 500 m of their saved place or position, then no **near** push is sent for it; after 15 minutes the normal near rule and the one-per-day limit apply.
- **F-10.AC7 (D61):** Given any Dekat Anda screen, error state or push, when it shows, then its text matches `copy/f10-copy-plain-id.md` word for word, and no screen shows coordinates, compass words, "titik", "izin lokasi" or technical terms. The map credit stays.
- **F-10.AC8 (D62):** Given a buyer saved Rumah and Kantor, when they open Peta, then both show as labelled house/office pins, visibly different from cart pins and below them, and tapping one does not open a cart; when they open Profil, then a small map shows both with *"Hanya Anda yang bisa lihat."*, and tapping it or a row opens the picker for that place; in the picker, the other saved place shows faded. Given none is saved, the Profil map shows *"Belum ada Rumah atau Kantor."* with **Simpan sekarang**.
- **F-10.AC4 (D59):** Given the buyer refuses location, when they save a place, then they can set it by moving the map pin, and alerts for that place still work.
- **F-10.AC5:** Given a buyer denied location and skipped saving a spot, when they open Profil, then a reminder offers to save one.

- **F-06.AC8 (D68):** Given a followed cart with reviews, when the buyer opens Diikuti, then its card shows *★ 4,3 (12)*; with 0 reviews, nothing.
- **F-06.AC7:** Given a followed cart is hidden because its location is over 30 minutes old, when a buyer opens Diikuti, then it remains in the Buka tab with **Lokasi tidak tersedia**, no distance or map action, and no claim that the seller tapped Tutup. It moves to Tutup only after the seller taps Tutup. Hidden carts sort last in Buka; use a clock time for long gaps, e.g. **Lokasi tidak tersedia sejak 15.02**.
- **F-06.AC6:** Given followed carts, when the buyer switches Buka/Tutup, then only carts with the selected status show. Both tab counts show all followed carts in that status and stay unchanged by search. Search filters the selected tab by cart name or dish; a status change moves a cart between tabs while keeping the search text. Buka sorts by nearest first; Tutup by most recent open time. An empty result names the other tab when it has carts.

### F-11 · Catat penjualan: record a sale (P0)
*As a seller, I want to record a sale in seconds, so I know my takings without a notebook.*
- **Recording:** **+ Penjualan** → tap menu items (one tap = one portion, with −) → **Simpan**. **Tunai is preselected**; tap **QRIS** if the buyer paid by QR (a label only; no payment runs through the app) (D13).
- **Stored:** items, total, method, time, and the cart's position. Fixed prices fill automatically; variable-price items require an amount during each sale.
- **Only while Buka**, so every sale has a place.
- **Works offline;** uploads later with the original time.
- **7 hari terakhir:** every day in the last 7 days, including days with no sales.
  - Tap a day and it opens to **which menu sold, how many portions, and how much each dish took**, highest portions first.
  - The day's portions and total stay in the day row; tap again to close. One day open at a time.
  - A day with no sales opens to *"Tidak ada penjualan hari itu."*
- **Today's list:** newest first, with aligned time, item and amount columns. Seven-day rows and expanded dish rows align their portions and takings columns. Each sale can be deleted the same day. Editing a sale is P1 (D14).
- **Seller data is private:** buyers and other sellers never see it (D8).
- **F-11.AC1:** Given the cart is Buka, when the seller taps **+ Penjualan**, 1 item and **Simpan**, then a Tunai sale of a fixed-price item is saved with items, total, method, time and location, in 3 taps. A QRIS sale takes 1 more tap.
- **F-11.AC9:** Given a variable-price item is selected for a sale, when the seller enters the whole-rupiah unit price for one portion (Rp 1–5.000.000) and saves, then that unit price is stored on the sale line; its amount equals unit price × portions and contributes to the sale total, day total and dish takings. Blank, zero, negative, decimal or over-limit amounts prevent saving and preserve entered items.
- **F-11.AC10:** Given the seller views today's list or seven-day details, then time/day, item/portions and amount use consistent aligned columns; exact rupiah amounts align at the right edge in a column at least 100 px wide; abbreviated *rb* amounts are not mixed with exact amounts on the same screen.
- **F-11.AC2:** Given no signal, when the seller saves a sale, then it's kept and uploaded later with its original time.
- **F-11.AC3:** Given sales today, when the seller opens Beranda, then they see today's portions and total.
- **F-11.AC4:** Given a sale saved today, when the seller deletes it, then the totals update.
- **F-11.AC6:** Given a sale saved offline and the upload is retried, when the signal returns, then the sale is counted once, never twice.
- **F-11.AC12:** Given the **7 hari terakhir** list on 13 Nov, then each row shows the day with its date under it, e.g. *Hari ini* / *13 Nov*, *Kemarin* / *12 Nov*, *Rab* / *11 Nov*, oldest last, Bali time.
- **F-11.AC7:** Given the last 7 days, when the seller taps a day, then it shows each dish that sold that day with its portions and takings, and the dishes add up to the day's total.
- **F-11.AC8:** Given a day with no sales, when the seller taps it, then it opens to *"Tidak ada penjualan hari itu."* and no dish rows.
- **F-11.AC10:** Given the **7 hari terakhir** list, when it shows, then *“Ketuk hari untuk rincian”* sits as one grey line directly under the heading, inside the page margin, with space above the list; it never sits inside a row, overlaps text or wraps under a number.
- **F-11.AC11:** Given the seller chose Buka and is temporarily hidden because positions stopped arriving, when they record a sale offline or with no recent phone position, then the sale is saved on the phone with its original time and uploaded later. If the newest phone position is over 30 minutes old, the sale is marked **Lokasi perkiraan**. Recording is blocked only after the seller taps Tutup.
- **F-11.AC5:** Given the cart is Tutup, when the seller opens Penjualan, then **+ Penjualan** is disabled, with *"Buka dulu untuk mencatat penjualan"*.

### F-12 · Sign-in and consent (P0)
*As the business, we want buyers and sellers identified before they act, and the map itself open to anyone (D36, supersedes D4).*
- **Buyer:** the map opens without an account. Google sign-in is asked at the first action (F-12.AC4). Apple sign-in comes with iOS in Phase 1.
- **Seller:** Google sign-in, like buyers (ADR-009, Owner, 2026-11-02); one Google account is one shop. The WhatsApp number is asked in setup for the admin, not for sign-in. New accounts complete seller onboarding; existing accounts open their saved shop. Long-lived sign-in, so they're never signed out mid-shift. The testing build replaces Google with **Masuk (akun uji)** under a **Mode uji — bukan Google** banner (ADR-010); that is a test tool, not a product sign-in.
- **One account, two apps (D58):** a Google account is one Gerobak account. Signing in to the seller app with it adds a shop; signing in to the buyer app gives the same person follows and saved places. A seller can follow other carts from the buyer app with the same Gmail. The admin page has its own access (Cloudflare email code) and is never opened by this sign-in. Consent is asked once per account, plus the seller terms the first time the seller app is used.
- **Consent at first sign-in:** in plain words, what is collected and why (see section 9). Declining signs them out.
- **F-12.AC1:** Given a new buyer, when they open the app, then the map shows straight away; sign-in and consent are asked at the first action.
- **F-12.AC2:** Given a buyer declines the terms, when they tap Tolak, then they're signed out.
- **F-12.AC4:** Given a visitor who has not signed in, when they open a cart, tap Ikuti, open ulasan, save a place or set an alert, then one sign-in prompt appears naming what they tapped; after sign-in they continue where they were, and "Nanti saja" returns to the map signed out.
- **F-12.AC5 (D58):** Given a seller with a shop signs in to the buyer app with the same Google account, when sign-in completes, then they are signed in as a buyer without a second account or a new consent, they can follow carts, their own cart's page views still don't count (F-07.AC1), and the seller app still opens their shop. Given a buyer signs in to the seller app with their Google account, then they start seller setup (F-01) and keep their follows.
- **F-12.AC3:** Given a new seller signs in with Google and accepts the terms, when sign-in completes, then they enter F-01 to provide their own shop information; an existing seller opens their existing shop.

### F-13 · Demand signals (P0, no screen)
*As the business, we want to know what buyers look for, where and when, so membership can show demand later (D6, D8).*
- **Counted, by area (about 460 m cells) and hour:**
  - every search: a term the buyer submits or stops typing for a moment, not every keystroke; capitals ignored
  - every cart page view
  - every follow
- **Which area:** where the buyer is, not where the map is looking. If the buyer's location is unknown, the search is counted without an area.
- **Which words:** only terms that match a dish in the dish list (`dish-list-v2.md`, kept unseen for this, D55) or a cart name are counted by name. Anything else counts as **lainnya**, and the words aren't kept, because free text can contain personal details (D15).
- **Kept only as counts per area.** Individual searches are not shown to anyone.
- **Who sees what:** admins see exact counts. In the membership (Phase 2), sellers see areas only when a count is 3 or more.
- **F-13.AC1:** Given a buyer in Canggu searches "kopi" at 19.10, when the admin views the demand counts, then the count of "kopi" for the buyer's area and the 19.00 hour has gone up by exactly 1.
- **F-13.AC2:** Given a buyer searches a term that matches no dish and no cart name, when the admin views the counts, then **lainnya** has gone up by 1 and the term itself isn't shown or kept.

### F-16 · Toko saya: the seller sets up their page (P0)
*As a seller, I want to show buyers my cart and my food the way I like, and see that people follow me, without waiting for an agent.*
- **Where:** seller app, Akun tab, **Toko saya**. The seller completes the two-step setup (F-01), with field-agent coaching if needed; afterwards they edit their own page and menu here.
- **Profile:** up to 5 cart photos from the camera or gallery (the first is the cover), name, description (160 characters), Halal or Non-halal, payment methods.
- **Menu:** add, change or delete an item: photo from the camera or gallery, name, fixed or variable price, description (80 characters), Jenis menu (D55).
- **Ringkasan (D64):** one card at the top with three numbers: **Pengikut** (with *+n minggu ini*), **Nilai** (average stars) and **Ulasan** (count). No names: sellers never see who follows them.
- **Fresh numbers:** follower and review counts refresh each time Toko saya or Beranda opens, and when the seller pulls the page down.
- **Lihat:** opens the cart page as buyers see it.
- **F-16.AC1:** Given a signed-in seller, when they open Akun → Toko saya, then they see their photos, description, follower count and menu.
- **F-16.AC2:** Given the seller changes the description or a photo and taps Simpan, when a buyer opens the cart page, then the change shows within 1 minute.
- **F-16.AC3:** Given the seller adds an item with a photo and description, when a buyer opens the cart page, then the item shows with both, under its Jenis menu heading, and search finds it by name.
- **F-16.AC4:** *Retired in v2.2 (D48), replaced by F-16.AC7.*
- **F-16.AC10 (bug, 2026-11-13):** Given a buyer follows the cart, when the seller next opens Toko saya or Beranda, or pulls either page down, then the follower count includes that buyer within 1 minute, with no sale or other action needed.
- **F-16.AC11 (D64, D68):** Given the seller opens Toko saya, then the **Ringkasan** card shows Pengikut, Nilai and Ulasan; Nilai shows the average from the first review (e.g. *5,0*), and *Belum ada* only with 0 reviews. A new review shows within 1 minute of the seller opening or pulling down Toko saya.
- **F-16.AC5:** Given 214 buyers follow the cart, when the seller opens Toko saya, then *"214 Pengikut"* shows, and no buyer names.

- **F-16.AC6:** Given a seller edits a menu item, when they choose fixed or variable pricing and save, then buyers see the matching price display; existing recorded sales keep the amount used when each sale was saved.
- **F-16.AC7:** Given the seller changes Halal to Non-halal (or back) in Toko saya and taps Simpan, when a buyer looks at the cart, then the new label shows within 1 minute in the list and on the cart page.
- **F-16.AC8:** Given the seller adds a second to fifth cart photo or replaces a menu photo from the camera or gallery and taps Simpan, when a buyer opens the cart page, then the photos show within 1 minute, the first as the cover; a sixth cart photo is refused with *“Maksimal 5 foto”*.
- **F-16.AC9:** Given a menu item has a photo, when the seller looks at Beranda, Toko saya or Catat penjualan, or a buyer opens the cart page, then that item's own photo shows in its row, cropped to fill a square, not the fork-and-knife tile; given an item has no photo, then the tile shows; given the photo is still waiting to send, then the seller sees their photo marked **Foto belum terkirim** and buyers see the tile until it arrives (F-01.AC7).

### F-17 · Ulasan: star reviews (P0, writing from v2.7) (D35, D63)
*As a buyer, I want to know if a cart is good before I walk over. As a seller, I want good reviews to bring me new buyers.*
- **Writing (P0, D63):** an **Ulas** button in the cart page's Ulasan section opens a sheet: **Beri ulasan untuk {cart}**, five stars (required), quick tags (**Enak, Bersih, Ramah, Porsi pas, Harga pas**, any number), an optional note (140 characters) and **Kirim**. After sending: toast *"Terima kasih, ulasan terkirim."*
- **Who can review (D63):** any signed-in buyer, except the shop's own Google account (D58). Not signed in: the sign-in prompt (F-12.AC4). The earlier "within 100 m in the last 7 days" rule is dropped: buyers rarely open the app while buying, and checking it needs location history we don't keep (D59).
- **What:** 1–5 stars, tags, optional note, first name shown. One review per buyer per cart; tapping **Ulas** again opens their review to change it.
- **Shown (Phase 0):** on the cart page, the average, the count, the three tags with the most mentions and the latest two reviews with a "Lihat semua" link. From the first review the average shows, always with the count (D68). Cart cards show it too (P0, D68).
- **No example reviews** on testing or production once writing is live; only real ones.
- **Seller:** sees all reviews in Toko saya. Reply and report are P1. Can't delete.
- **Admin (P0, D63):** can hide any review from the seller's detail page in the admin console; a hidden review no longer shows or counts.
- **F-17.AC1:** *Retired in v2.7 (D63).*
- **F-17.AC2:** *Retired in v2.7 (D63).*
- **F-17.AC10 (D68):** Given a cart has 0 reviews, then the Ulasan section says *"Belum ada ulasan. Jadilah yang pertama setelah mencoba."*; given 1 or more reviews, it shows the average and count (e.g. *★ 4,5 · 2 ulasan*) and the latest reviews.
- **F-17.AC6 (D63):** Given a signed-in buyer opens a cart page, when they tap **Ulas**, choose 4 stars and **Enak**, and tap **Kirim**, then the toast shows, and within 1 minute the review shows on the cart page and counts in the average and in the seller's Ringkasan.
- **F-17.AC7:** Given no star is chosen, then **Kirim** stays disabled with *"Pilih bintang dulu"*.
- **F-17.AC8:** Given a buyer already reviewed the cart, when they tap **Ulas**, then their review opens to change; saving replaces it, never adds a second one.
- **F-17.AC9:** Given the seller opens their own cart page from the buyer app with the same Google account, then **Ulas** is not shown.
- **F-17.AC3 (D68):** Given a cart has 1 or more reviews, when a buyer opens its page, then the average and count show.
- **F-17.AC4:** Given a review, when the seller replies, then the reply shows under it on the cart page.
- **F-17.AC5:** Given a review is reported and an admin hides it, then it no longer shows and no longer counts in the average.

### F-18 · Pantau visibilitas: admin quality control (P0)
*As an admin, I want to see at a glance which sellers who are Buka buyers can actually see, so field agents can fix problems the same evening.*
- **Where:** admin console, new page **Pantau visibilitas**. Real sellers only; simulated carts hidden unless the admin turns them on. Sellers switched off in **Penjual** (F-08) never count as Buka or Hilang; they are named in one line under the numbers.
- **Top bar:** Buka now · Terlihat · Terlambat (10–30 min) · Buka tapi hilang (> 30 min) · share of Buka time visible today.
- **List, problems first:** seller and number, status for buyers with minutes since the last position, last position and time, likely reason, share of today's Buka time visible, and a **WhatsApp** button.
- **Status rules** are exactly the buyer map's (F-03): Terlihat ≤ 10 min, Terlambat 10–30 min, Hilang > 30 min while Buka.
- **Likely reason** (a best guess, labelled as such): location off on the phone, app stopped by the phone, no signal, unknown.
- **Map:** every Buka seller's last position, coloured by status.
- **One seller's day:** a timeline of Tutup / terlihat / terlambat / hilang, and the events behind it.
- **WhatsApp:** opens a chat on the admin's own phone or laptop with a prepared message. The admin sends it; nothing is sent automatically.
- **F-18.AC1:** Given a seller is Buka and sent a position 4 minutes ago, when the admin opens the page, then the seller shows as *Terlihat · 4 mnt*.
- **F-18.AC2:** Given a seller is Buka and the last position is 14 minutes old, when the admin looks, then the seller shows as *Terlambat · 14 mnt*.
- **F-18.AC3:** Given a seller is Buka and the last position is more than 30 minutes old, when the admin looks, then the seller shows as *Hilang*, is listed at the top and is counted in "Buka tapi hilang".
- **F-18.AC9:** Given a seller has not tapped Tutup and their newest recorded position is over 30 minutes old, then the admin sees **Hilang** with the last recorded time until a recent position arrives or the seller taps Tutup. The timeline distinguishes missed arrivals from gaps in phone-recorded positions when delayed points arrive; the reason remains a labelled guess until then. Hidden time stays in the denominator of **Terlihat hari ini** while the seller remains Buka, so the share reflects the actual buyer experience.
- **F-18.AC4:** Given the page is open, when a seller's status changes, then the page shows it within 1 minute without a reload.
- **F-18.AC5:** Given a seller turned off location on the phone, when the seller goes missing, then the likely reason says *Lokasi HP dimatikan*.
- **F-18.AC6:** Given the admin taps WhatsApp on a row, when the chat opens, then it is addressed to that seller's number with the prepared message, unsent.
- **F-18.AC7:** Given a seller was Buka 4 hours today and visible for 3, when the admin looks, then "Terlihat hari ini" shows 75%.
- **F-18.AC8:** Given a seller is switched off in Penjual, when the admin opens Pantau visibilitas, then that seller is not counted as Buka, Terlihat, Terlambat or Hilang, and is listed by name as hidden.

### F-19 · Rute hari ini: the seller's route today (P0) (D50)
*As a seller, I want to see where I went today, how long I was open and how far I travelled, so I can judge my day and plan tomorrow.*
- **Where:** seller Beranda, a card **Rute hari ini** under **Hari ini**.
- **Card content:** a small map of today's route (a line through the positions recorded while Buka, a start dot and a dot for the latest position), **Lama buka** (time open today, e.g. *3 j 25 mnt*, counting up while Buka) and **Jarak** (distance travelled while Buka, e.g. *± 4,2 km*).
- **Tap the card:** a full-screen map with the same route, the times of each Buka session (*17.02–19.10*) and the same two numbers.
- **Rules:**
  - Day boundary: midnight Bali time (WITA). A session that runs past midnight counts in both days, split at midnight.
  - Lama buka adds up every Buka session today, from **Ya, buka** to **Ya, tutup** (or to now).
  - Jarak adds the straight lines between positions recorded while Buka, so it reads *±*. A gap of over 30 minutes without positions is drawn as a break and not counted.
  - The route comes from positions the phone recorded, so it also shows with no signal.
  - A cart that stays in one spot (Menetap) sees a short or zero distance; that is correct.
- **Private:** only the seller sees it. Buyers never see a route (D8). Admins already have the F-18 timeline.
- **F-19.AC1:** Given the seller was Buka 17.00–19.00 and 19.30–21.00 today, when they open Beranda after Tutup, then **Lama buka** shows *3 j 30 mnt* and the map shows two route pieces.
- **F-19.AC2:** Given the recorded positions of a route that is 4.0 km along those points, when the seller looks, then **Jarak** shows between *± 3,6 km* and *± 4,4 km*.
- **F-19.AC3:** Given the seller is Buka with Beranda open, when the phone records a new position, then the line and Jarak update within 1 minute, and Lama buka keeps counting, with or without signal.
- **F-19.AC4:** Given no Buka yet today, when the seller opens Beranda, then the card says *“Belum ada rute hari ini. Tekan BUKA untuk mulai.”* with no map.
- **F-19.AC5:** Given a gap of over 30 minutes without positions while Buka, when the seller looks, then the route shows a break there and the gap adds nothing to Jarak; Lama buka still counts it, because the seller was Buka.
- **F-19.AC6:** Given any buyer screen or a shared cart link, when it opens, then no seller route is shown.

### F-20 · Short messages (toasts) in both apps (P0) (D51)
*As a user, I want a quick confirmation that something worked, without it covering what I need to tap or staying on screen.*
- **Where:** at the bottom of the screen, above the tab bar (or above the bottom edge when there is none), full width with 16 px side margins. Never over the BUKA/TUTUP disc, **+ Penjualan**, **Simpan** or the map search.
- **Timing:** gone after 4 seconds; 6 seconds if it carries a button (e.g. **Urungkan**). Swipe sideways or tap ✕ to close sooner. One at a time: a new message replaces the old one.
- **Use for:** short results, e.g. *“Anda terlihat di peta · 12 pengikut dikabari”*, *“Penjualan tersimpan”*, *“Diikuti”*.
- **Not for lasting conditions:** location off, no signal, *Disembunyikan admin*, *Buka · Tidak terlihat*, unsent sales or photos. These are banners inside the page that stay until the condition ends.
- **F-20.AC1:** Given a toast appears, when 4 seconds pass (6 with a button), then it disappears without a tap.
- **F-20.AC2:** Given the seller taps **Ya, buka**, when the confirmation toast shows, then the BUKA/TUTUP disc and the tab bar stay fully visible and tappable.
- **F-20.AC3:** Given a toast is showing, when another one fires, then the first is replaced, never stacked.
- **F-20.AC4:** Given location is turned off while Buka, then the warning shows as a banner in the page, not a toast, and stays until location is back (F-03.AC4).
- **F-20.AC5:** Given a screen reader is on, when a toast appears, then its text is read once.

### F-14 · Jadwal by hand and Bagikan ke WhatsApp (P1)
The seller sets today's stops (a time and a point on the map) by hand. Followers see them on the cart page. **Bagikan ke WhatsApp** shares the list. Taken from v0.9 section 7.10, without Jadwal pintar.

### F-21 · Stok hari ini (P0) (D66)
*As a seller, I want to know how many portions I have left, and buyers to know before it runs out.*
- **Optional per menu item.** On Beranda each menu row has **Stok**: tap to set a number (e.g. 30), with − and + to adjust. Blank means not counted.
- **Sales lower it:** each portion recorded in Catat penjualan (F-11) lowers that item's stock by one. Deleting a sale adds it back.
- **At 0:** the item turns **Habis** automatically (F-02); setting a new number turns it back on.
- **Buyers see** *Tinggal {n}* next to the price only when 5 or fewer are left; above 5 they see nothing, because counts are only as good as recorded sales.
- **New day:** stock clears at midnight Bali time; the seller sets it again when they want.
- **F-21.AC1:** Given Bakso urat has stock 3, when the seller records 1 sale of 2 portions, then the row shows 1 and buyers see *Tinggal 1* within 1 minute; when 1 more portion is sold, the item turns Habis for buyers.
- **F-21.AC2:** Given an item has no stock set, then sales record normally and nothing about stock shows to buyers.
- **F-21.AC3:** Given stock was set yesterday, when the seller opens Beranda after midnight, then the stock field is blank again and Habis set by stock is cleared.

### F-15 · Pengumuman, one line (P0 from v2.7) (D67)
*As a seller, I want to tell buyers something quick, e.g. "Hari ini sampai jam 21.00 di Berawa".*
- **One line, up to 80 characters,** set from Beranda or Toko saya: **Pengumuman** · *"Tulis kabar singkat untuk pembeli"* · **Simpan** / **Hapus**. Only one at a time; a new one replaces the old.
- **Shown** on the cart page under the name, and in the buyer's Diikuti list under the cart name. No push.
- **Lasts 24 hours,** then hides on its own; the seller sees *"Pengumuman sudah tidak tampil"* with **Tampilkan lagi**.
- **F-15.AC1:** Given the seller saves *"Hari ini sampai jam 21.00 di Berawa"*, when a buyer opens the cart page or Diikuti, then the line shows within 1 minute.
- **F-15.AC2:** Given 81 characters, then **Simpan** is disabled and the counter shows *81/80*.
- **F-15.AC3:** Given the announcement is 24 hours old, then buyers no longer see it and the seller sees **Tampilkan lagi**; given the seller taps **Hapus**, it disappears for buyers within 1 minute.

### F-22 · Polling pengikut: sellers ask their followers (P0) (D70, D71)
*As a seller, I want to ask my regulars what they want (a new menu, a place, a time) so I sell what they'll buy. As a follower, I want a quick say in my favourite cart.*
- **Where (seller):** Akun → Toko saya, card **Polling** under Pengumuman: **Buat polling** when none is running. While one runs, the same card shows live results, and Beranda shows a one-line card *Polling aktif · {n} suara · sisa {time}* that opens it.
- **Create:** **Pertanyaan** (required, up to 100 characters) and **Pilihan** (2 to 4, each up to 40 characters, typed by the seller; **+ Tambah pilihan** adds the 3rd and 4th). **Lama polling:** **1 jam · 6 jam · 24 jam · 3 hari · 7 hari**, 24 jam preselected; the end time shows under it, e.g. *Berakhir Rab, 18 Nov 19.02*. **Mulai polling** opens a confirmation: *"Pengikut bisa memilih sampai Rab, 18 Nov 19.02. Setelah dimulai, pertanyaan dan pilihan tidak bisa diubah."* · **Ya, mulai** / **Batal**.
- **One at a time,** independent of Buka/Tutup. No editing once started. At most **10 new polls per shop per day** (stops a delete-and-restart loop); the 11th shows *"Maksimal 10 polling per hari. Coba lagi besok."*
- **Where (buyer):** on the cart page, a **Polling dari penjual** card under the numbers row and pengumuman; in Diikuti, a *Polling · sisa {time}* line on the cart's row while it runs and the buyer hasn't voted. **No push** (D71).
- **Voting:** followers tap one answer; it counts at once and the card switches to results: each answer's share in % and the total, their own answer marked **Pilihan Anda**. They can tap another answer to change their vote until the end. One vote per account. Before voting, a buyer sees the answers without results, so early numbers don't sway them.
- **Non-followers and guests:** see the poll. Tapping an answer opens a sheet: *"Polling ini untuk pengikut. Ikuti Bakso Pak Made untuk memilih; Anda juga dikabari saat gerobak ini buka."* · **Ikuti & pilih** / **Batal**. A signed-out visitor signs in first (D36). The shop's own account can't vote.
- **Seller's view:** answers with counts and %, total votes, time left. No names, ever (as for followers, D57). Counts refresh when the page opens and on pull-down (as F-16.AC10); nothing updates live while a page stays open.
- **Ending:** automatically at the end time, by our clock, not the phone's; or by **Akhiri sekarang** → *"Akhiri polling sekarang? Pengikut tidak bisa memilih lagi. Hasil tetap tampil 24 jam."* · **Ya, akhiri**. **Hapus** → *"Hapus polling? Polling dan semua suara hilang untuk semua orang."* · **Ya, hapus**.
- **After the end:** buyers see **Polling selesai** with final results and the top answer marked **Terbanyak** for 24 hours, then the card goes. The seller keeps the last result in Toko saya until they start a new poll. Earlier polls are not listed (history is P1).
- **Unfollowing** leaves an earlier vote counted.
- **F-22.AC1:** Given a seller with no running poll, when they enter a question and 2 answers, keep 24 jam, tap **Mulai polling** and **Ya, mulai**, then a toast says *"Polling dimulai"*, and a buyer who opens or pulls down the cart page within 1 minute sees the poll with *Sisa 24 jam*.
- **F-22.AC2:** Given the question is empty or fewer than 2 answers are filled, then **Mulai polling** is disabled with *"Isi pertanyaan dan minimal 2 pilihan"*; given 4 answers, then **+ Tambah pilihan** is hidden; given 101 question characters or 41 answer characters, then the counter shows *101/100* (or *41/40*) and **Mulai polling** is disabled.
- **F-22.AC3:** Given the seller picks one of 1 jam, 6 jam, 24 jam, 3 hari or 7 hari, then the end time under the choices updates, e.g. *Berakhir Rab, 18 Nov 19.02*; the time left (*sisa …*) shown to buyers and the seller is worked out from our clock, not the phone's. When the end time is reached, then no vote is accepted, and anyone who opens or pulls down the page sees **Polling selesai**. Tested with a phone clock set 2 hours wrong: time left and ending stay correct.
- **F-22.AC4:** Given a follower who hasn't voted, when they open the cart page, then they see the question and answers without percentages; when they tap an answer, then the card shows each answer's % and the total, with theirs marked **Pilihan Anda**; the seller sees the higher count the next time they open or pull down Toko saya or Beranda.
- **F-22.AC5:** Given a follower has voted, when they tap a different answer before the end, then their vote moves: the total stays the same and the shares change.
- **F-22.AC6:** Given a signed-in buyer who doesn't follow the cart, when they tap an answer, then the **Ikuti & pilih** sheet opens; when they confirm, then they follow the cart (F-06) and their vote counts, both in one step: a weak signal never leaves them following without a vote, or voting without following; **Batal** does neither. Given a signed-out visitor, then sign-in comes first (D36) and they return to the same poll **without a vote cast**; they tap their answer again.
- **F-22.AC7:** Given a poll is running, when the seller opens Toko saya or Beranda, then they see each answer's count and %, the total, and time left, and no buyer names; **Buat polling** is not offered.
- **F-22.AC8:** Given a running poll, when the seller taps **Akhiri sekarang** and **Ya, akhiri**, then votes stop at once and buyers who open or pull down the cart page see **Polling selesai** with the final results; given the seller taps **Hapus** and **Ya, hapus**, then the poll and its votes are gone for buyers on their next open or pull-down, and the seller can start a new one (up to 10 a day).
- **F-22.AC9:** Given a poll ended, then buyers see the final results with **Terbanyak** on the top answer (ties: both marked) for 24 hours after the end, then the card no longer shows; the seller still sees the last result until a new poll starts.
- **F-22.AC10:** Given a followed cart has a running poll the buyer hasn't voted on, when the buyer opens Diikuti, then that cart's row shows *Polling · sisa {time}*; after they vote, the line is gone. No push is sent at the start or end (D71).
- **F-22.AC11:** Given the seller has no signal, when they tap **Mulai polling**, then nothing starts and the screen says *"Butuh sinyal untuk memulai polling"* with what they typed kept; given a buyer has no signal when voting, then *"Pilihan belum terkirim. Coba lagi saat ada sinyal."* shows and the vote isn't counted.
- **F-22.AC12:** Given a buyer taps an answer after the poll ended, then *"Polling sudah selesai"* shows and the card switches to the final results.
- **F-22.AC13:** Given the seller deleted the poll while a buyer has the cart page open, when the buyer taps an answer, then *"Polling sudah dihapus"* shows, no vote is kept and the card disappears.
- **F-22.AC14:** Given the admin switches the seller's **Tampil ke pembeli** off (F-08), then the poll disappears with the cart and any vote is refused; when switched back on, the poll shows again if it hasn't ended.
- **F-22.AC15:** Given the seller has started 10 polls today (Bali time), when they tap **Buat polling**, then *"Maksimal 10 polling per hari. Coba lagi besok."* shows and nothing starts.

---

## 8. Notifications

| Notification | Trigger | Recipient | Limit |
|---|---|---|---|
| Followed cart open (F-06) | First Buka of the day | Followers with the switch on | 1 per cart per day |
| Followed cart near (F-10) | Cart within about 500 m of the buyer or the saved spot | Followers with the switch on | 1 per cart per day |

Polls (F-22) send no push, at the start or the end (D71). Followers find them on the cart page and in Diikuti.

---

## 9. Privacy, data and consent

| Data | Rule |
|---|---|
| Seller position | Shared while Buka; stored as a trail for later insights; kept 90 days **(proposed)** |
| Seller sales (F-11) | The seller's own data. Never shown to buyers or other sellers. Later shown back to the seller in membership. Onboarding says this plainly, because sellers may worry about tax |
| Buyer position | Used only to place the map and check distance to followed carts. No history of where a buyer has been |
| Buyer searches, views, follows (F-13) | Counted per area and hour. Search words that match no dish or cart name are counted as *lainnya* and not kept. Shown later to sellers in membership as demand by area, never per person. Areas with too few counts are hidden from sellers **(proposed: under 3)**; admins see exact counts |
| Poll votes (F-22) | Stored per account so a vote can be changed and counted once. Sellers see counts only, never who voted. Votes are deleted with the poll (Hapus); not used in demand data (F-13) for now |
| Consent | Recorded at first sign-in. Indonesia's personal data law (UU PDP) applies; full compliance before the public launch |

**Consent text, outline (to be finalised with a legal check before the pilot):**
- **Buyers:** *"Kami memakai lokasi Anda untuk menampilkan gerobak di sekitar Anda dan memberi tahu saat gerobak favorit Anda dekat. Pencarian Anda dihitung secara anonim per area untuk membantu penjual tahu di mana pembeli mencari."* (We use your location to show carts near you and to tell you when a favourite cart is close. Your searches are counted anonymously by area, to help sellers know where buyers are looking.)
- **Sellers:** *"Lokasi gerobak Anda tampil di peta saat Buka. Catatan penjualan Anda hanya untuk Anda dan tidak dibagikan ke siapa pun."* (Your cart's location shows on the map while you're Buka. Your sales records are for you only and aren't shared with anyone.)

---

## 10. Configurable defaults

| Setting | Default |
|---|---|
| Nearby radius | 3 km; followed carts at any distance |
| Position update | every 5 min or 150 m |
| LIVE / STALE / hidden | ≤ 10 min / 10–30 min / > 30 min |
| Contact lost without Tutup | Hidden after 30 min; offline recorded positions can restore automatically; tracking gaps over 30 min need Lanjut Buka with a fresh position; only seller Tutup ends the shift |
| "Near" distance | 500 m **(proposed)**, tested within ±100 m; buyer position at most 30 min old |
| Saved spots | up to 2 **(proposed)** |
| Push limits | 1 "open" and 1 "near" per cart per day |
| Page view counting | 1 per buyer per cart per hour |
| Sales changes | delete, same day only (editing is P1) |
| Demand count privacy | hide areas under 3 **(proposed)** |
| Seller trail retention | 90 days **(proposed)** |
| Default map spot without location | Batu Bolong, Canggu |
| Demo simulation auto-stop | 2 hours after start |
| Poll length choices (F-22) | 1 jam, 6 jam, **24 jam** (preselected), 3 hari, 7 hari |
| Poll limits (F-22) | 1 running per shop; 10 new per shop per day; question 100 characters; 2–4 answers of 40 characters; final results shown 24 hours |

---

## 11. Mockups

Static pages in `../mockups-v3/`. Open `index.html`. The design is the GitHub app's, with the D29–D31 heading work and Manrope (D32). One Android phone per state; iOS differs only at sign-in.

| Page | Covers |
|---|---|
| `design-system.html` | App colours, type, parts; before/after of the heading fix; v2.2 parts: confirmation sheet, toast, photo picker, dish search, halal labels, sheet heights |
| `dish-list-v2.md` | Word list for demand counts only (F-13, D55); sellers no longer pick from it |
| `font-lab.html` | Q9: the Penjualan and Gerobak screens in five typefaces, same sizes and weights |
| `buyer-start.html` | F-12.AC1–AC2, iOS Apple sign-in |
| `buyer-map.html` | F-04.AC1–AC14 (07–09: sheet heights), F-03.AC3, F-13, F-12.AC4 (names on pins, card focus and the Profil button; signed-out map and the sign-in prompt) |
| `../copy/f10-copy-plain-id.md` | D61 copy table for every F-10 buyer text, both pushes and the pin labels (applies over mockup wording) |
| `round-v29.html` | F-22.AC1–AC15: seller creates a poll with the timer, confirmation, live results, end and delete; buyer cart page before and after voting, the Ikuti & pilih sheet, the ended poll, Diikuti line |
| `owner-round-v27.html` | v2.7: review sheet, numbers row and pengumuman on the cart page; Ringkasan and pengumuman in Toko saya; stock on Beranda; dated 7-day list; background notification; Nyalakan lokasi line |
| `buyer-cart.html` | F-05, F-17.AC3, F-02.AC5, F-02.AC11, F-16.AC9 (menu photos), F-03.AC3, F-06 first follow, F-10 permission and saved spot |
| `buyer-follow.html` | F-06 Diikuti and switch, F-06.AC4, F-10 "near" push |
| `seller-start.html` | F-12.AC3, F-01.AC1–AC11 (11–12: number already used, menu incomplete), F-02.AC10 (photo choice sheet, no selling area, halal choice, Jenis menu: Makanan, Minuman, Camilan) |
| `seller-home.html` | F-03.AC1/AC4/AC5/AC10–AC12, F-02, F-16.AC9 (menu photos), F-07 (AC3–AC5: Hari ini, Pengikut card; 10: new shop), F-08.AC1 seller view, F-19.AC1–AC5, F-20.AC1–AC4 |
| `seller-sales.html` | F-11.AC1–AC8, F-11.AC10, F-07.AC2 (05 and 06: a day opened per menu, and a day with no sales) |
| `seller-shop.html` | F-16.AC1–AC3, AC5–AC9, F-02.AC10, F-02.AC12 |
| `admin-sellers.html` | F-08.AC1–AC4 |
| `admin-monitor.html` | F-18.AC1–AC8 |


The frontend builds from these. Changes go through the CTO.

---

## 12. Phase 0 demo script

**Setup:**
- **Phone A:** buyer app, used by the counterpart.
- **Phone B:** seller app, Pak Made's bakso cart, used by the presenter.
- **Laptop:** admin console (Penjual, Pantau visibilitas). The simulation is running; it has no screen to start it from (D33).

**Steps:**
1. The counterpart opens the app and sees the map straight away, with carts moving around and the list within 3 km. They search "martabak". They tap a cart; the sign-in prompt appears and they sign in with Google and accept, then land on that cart page (D36).
2. They open a simulated cart's page: menu, prices, Halal label, LIVE. They tap **Ikuti** and save **Rumah**; when a simulated cart passes within 500 m, the "near" push arrives.
3. They also follow **Pak Made** from a shared link; his page shows *Tutup*. Phone B taps **BUKA** and **Ya, buka**. Within a minute Pak Made appears on Phone A's map, and Phone A gets *"Bakso Pak Made buka sekarang di Canggu. Lihat di peta."*.
4. Before the session the team set a followed simulated cart to come near Phone A. Phone A gets *"… 300 m dari Anda"*. Tapping it flies the map to the cart.
5. Phone A searches "bakso": only carts with available bakso show.
6. Phone B marks *Bakso urat* **Habis**. Phone A sees it within a minute.
7. Phone B records 3 sales (Tunai, QRIS). Beranda shows *"3 porsi · Rp …"* and *"Dilihat N kali"*, and the 7-day list fills.
8. Phone B taps **TUTUP** and **Ya, tutup**. The cart disappears from Phone A. Beranda shows **Rute hari ini** with time open and distance.
9. On the laptop, the admin switches Pak Made **off** in Penjual. Phone A's map drops him within a minute and Phone B says *Disembunyikan admin*. The admin switches him back on; Phone B can Buka again.
10. **The vision slide (not built):** the membership that sellers will pay for, with demand by area, best spots and hours.

---

## 13. Phases

| Phase | Scope | Exit |
|---|---|---|
| **0: Demo** (now) | F-01 to F-13, F-15, plus F-16 to F-22. Android only. Simulated carts plus Pak Made. No billing. Test sign-in on testing; Google where the client ID exists | Demo script passes twice in a row (G5) |
| **1: Bali pilot** | Real sellers signing themselves up with field-agent coaching in Canggu. Real Google sign-in for both apps (ADR-009). Production maps. Gerobak's own web address for share links. Both apps on the Play Store. iOS buyer app with Apple sign-in. Account deletion, privacy policy, UU PDP. P1 feature F-14, plus editing a sale, the dish list (D14, D26). Admin editing of seller details is excluded (D27). Set targets for G1–G4 | To be set after the demo |
| **2: Seller membership** (D8) | Paid plan for sellers: demand by area (from F-13), sales history and best spots and hours (from F-11 and the trail), and more. Pricing to be decided | To be set |
| **3: Later** | From v0.9: Teriak and the yes/no claim; QR ordering and QRIS; cash drawer and spending; Jadwal pintar and Rencana hari ini; Peta keramaian, the heatmap and forecast; Komunitas; Reviews, unless F-17 comes forward (Q8); sponsored Populer row and paid boosts; Pengingat by menu; juragan fleets | — |

### 13.1 Effort and cost (CTO estimate, 2026-10-28)
All numbers are **Kai's estimates**, in engineer-days, not quotes.

| F | Effort | Main risk |
|---|---|---|
| F-01 Onboarding | 3 d | Large phone photos |
| F-02 Profile and menu | 3 d | Search relies on the names sellers type (D55) |
| F-03 Buka/Tutup | **8–10 d** | Cheap Android phones stop the app in the background, so carts vanish |
| F-04 Map, list, search | 4–5 d | Free public maps can't carry the pilot |
| F-05 Cart page | 3 d | Without an own address, the link opens a web page but not the app |
| F-06 Ikuti + "open" push | 4–5 d | No street-name lookup; broad area must match the current cart position |
| F-07 Stats | 2 d | — |
| F-08 Admin | 3 d | — |
| F-09 Demo carts | 5 d | Hosting cost if left running (guarded by F-09.AC4) |
| F-10 Dekat Anda | 3 d (saved places, D59) | Buyers skip saving a place |
| F-11 Catat penjualan | 4 d | Offline sales counted twice (F-11.AC6) |
| F-12 Sign-in + consent | 5 d | Built in-house |
| F-13 Demand signals | 2–3 d | Personal details in search words (handled by D15) |
| F-19 Rute hari ini | **not estimated yet** | Positions every 5 min / 150 m make the line coarse (accepted) |
| F-01/F-16 real photos | **not re-estimated** | Needs a place to store photos (Owner cost decision O6 in the tech design) |
| F-18 Pantau visibilitas | **not estimated yet** | Needs live positions per seller; the live list and the buyer map must use the same status rules |
| F-22 Polling pengikut | **8–9 d** (server 3, seller app 2.5, buyer app 2.5, tests 1; 2026-11-17) | Reaches phones only with new builds of both apps (no over-the-air updates yet); one vote per Google account can be gamed with spare accounts. $0 extra running cost |

**Total:** about 55–65 days, including about 6 days of groundwork. D14 saves about 2–3 days. **F-18 is not in this total**; Kai has not estimated it yet.

**Running cost:** Phase 0 fits the current hosting plan of about $5 a month, with the auto-stop. **Paid items for the Owner later** (Estimated): Google Play account $25 once; WhatsApp codes only if a pilot seller can't use Google (ADR-009); own web address about $10–20 a year; Apple $99 a year for iOS.

---

## 14. Non-goals (for now)
- Payments of any kind through the app.
- Buyers calling or shouting for a cart.
- Seller tiers or billing in Phase 0 and the pilot (D1).
- Bookkeeping: spending, cash drawer, stock, profit.
- Social features: posts and comments. Polls (F-22) are fixed answers only; buyers can't write their own answer or comment on a poll. Reviews only as F-17, if Q8 brings them in.
- Delivery.
- Markets outside Bali.
- Selling data to anyone except sellers (D8).

---

## 15. Constraints
- One person, one phone at the cart: big buttons, sunlight, wet hands, at most a few taps per sale.
- Formal Indonesian ("Anda") and English; follows the phone language.
- Bali time (WITA) for every day boundary.
- Phase 0 is Android only.
- Two apps: **Gerobak** for buyers and **Gerobak Penjual** for sellers (D11).
- Phase 0 running cost stays within the current hosting plan (about $5 a month).

---

## 16. Assumptions (to validate)

| ID | Assumption | How we test it |
|---|---|---|
| A1 | Sellers will keep the app Buka for their whole shift | Share of selling hours with location in the pilot (F-18 shows it per seller) |
| A2 | Sellers will record most sales if they see their day's total | Recorded sales vs the seller's own estimate, by interview |
| A3 | Buyers will sign in before seeing anything | Drop-off at the sign-in screen |
| A4 | Buyers who follow a cart save at least one place (D59) | Share of followers with a saved place |
| A5 | 500 m is the right "near" distance | Push tap rate; buyer interviews |
| A6 | Sellers will pay later for demand and sales insights | Willingness-to-pay interviews during the pilot |
| A7 | Sellers know whether their cart is halal and answer honestly | Field agents check a sample in the pilot; buyer reports |
| A8 | *Retired in v2.4 (D55): sellers no longer pick a dish.* | — |
| A9 | The Buka confirmation stops more mistakes than it annoys | Share of sheets ended with **Batal**; seller interviews |
| A10 | "Free text" means the seller types the question and answers, and buyers pick one (D70) | Owner reads v2.9; if buyers should type their own answers, that is a different feature (comments) |
| A11 | Sellers will run polls and followers will vote without a push (D71) | Polls started per active seller per month; votes per poll ÷ followers; seller interviews |

---

## 17. Risks

| Risk | Impact | Mitigation |
|---|---|---|
| Cheap Android phones stop the seller app in the background | Carts vanish from the map; the whole product fails | Battery-limit prompt at onboarding; seller warning; test on real phones; the demo leans on simulated carts |
| Buyers skip saving a place, so few get "near" alerts (D59) | Dekat Anda reaches fewer buyers | Ask at the first follow, remind in Profil (F-10.AC5); revisit "always" after the pilot if the share is low |
| "Near" pushes arrive late when the app is closed | Buyers miss a cart that passes quickly | Accepted; measured in the pilot with A5 |
| The sign-in prompt at the first tap loses curious visitors (D36) | Fewer buyers | The map is free to view, so drop-off now sits at the first tap instead of at launch. Watch drop-off (A3) and which action triggers it |
| Sellers don't record sales at rush hour | Thin sales data for membership | 3 taps; same-day total as the reward; field agents coach |
| Sellers fear tax visibility | They refuse sign-up or stop recording | Private by default; say it plainly at onboarding |
| Cold start: few carts, so few buyers | Empty map | Hyper-local launch, field agents, simulated carts only in the demo |
| Free public maps can't be used at scale | Pilot blocked | CTO plan before Phase 1 |
| A seller-chosen **Halal** label is read as an official halal claim | Buyer trust; legal exposure under the halal product law | Wording *“Status halal menurut penjual”*, no official logo, legal check before the pilot (Q10); later a certificate number could show **Bersertifikat** (P2) |
| A seller writes an offensive or misleading poll (F-22) | Buyer trust | Same as pengumuman: the admin hides the seller with **Tampil ke pembeli** (F-08) and contacts them; no per-poll moderation in P0 |
| Spare Google accounts give one person several votes; Ikuti & pilih allows follow, vote, unfollow (F-22) | Counts can be inflated | Fine for "which new menu?"; polls are never used for prizes or anything of value in P0. Revisit if the pilot shows abuse |
| Polls reach phones only with new buyer and seller builds (F-22) | No poll on current phones (buyer v9, seller v7) until the Owner approves builds | Testing and web demo links until then; CTO suggests over-the-air updates in the next approved build (later ADR) |
| Few votes because polls send no push (D71) | Sellers find polls useless | Diikuti line and cart page card; measure A11; a push at the start is the first fix to try |
| Real photos cost storage and can be inappropriate | Running cost; a bad photo on the map | App shrinks photos; admin hides the seller with **Tampil ke pembeli** (F-08); cost decision with the CTO (O6) |

---

## 18. Open questions

| ID | Question | Owner | Status |
|---|---|---|---|
| Q1 | Can buyers browse without signing in? | Owner | **Closed:** yes for the map, list and search; no for any action (D36) |
| Q2 | Demo first, or straight to a pilot? | Owner | **Closed:** demo first |
| Q3 | Who buys the historical data? | Owner | **Closed:** sellers, through membership (D8) |
| Q4 | Membership price and what's in it | Owner | Open; decide during the pilot |
| Q5 | One app with a seller mode, or two apps? | CTO and Pia | **Closed:** two apps (D11) |
| Q6 | Consent wording legal check | Owner | Open; before the pilot |
| Q8 | Reviews (F-17): P1 for the pilot, or P0 so the counterpart sees them in the demo? | Owner | **Closed:** reviews show on the cart page from Phase 0, with example data; writing them stays P1 (D35) |
| Q7 | Keep "always" location for buyers (D3), or saved places now and "always" later? | Owner | **Closed:** saved places now (D59, 2026-11-12) |
| Q9 | Typeface: keep Plus Jakarta Sans, or switch? | Owner | **Closed:** Manrope (D32) |
| Q10 | Legal check of the Halal / Non-halal wording before the pilot | Owner | Open; does not block the demo |

---

## 19. Decision log

| ID | Date | Decision | Why | Cons accepted | By |
|---|---|---|---|---|---|
| D0 | 2026-10-28 | Gerobak v1 is a visibility app; hard day-one features removed | The core value is seeing carts; ship it simply | Less "wow"; no buyer-to-seller call | Owner |
| D1 | 2026-10-28 | Everything free in Phase 0 and the pilot; no tiers | Need sellers before charging | No revenue yet | Pia |
| D2 | 2026-10-28 | Buka is one tap, never blocked by a form | Never block the core action | No opening cash count | Pia |
| D3 | 2026-10-28 | *Superseded by D59.*  "Near" uses the buyer's live location by default, with saved spots as the fallback | Feels like magic for those who allow it | Harder to build, store review risk, more refusals. Pia objected once | Owner |
| D4 | 2026-10-28 | Buyers must sign in before the map | Data is the key asset | Loses some curious buyers. Pia leaned the other way | Owner — **superseded by D36, 2026-11-01** |
| D5 | 2026-10-28 | Sellers record sales by hand (F-11) | Builds sales history for membership | Depends on sellers' discipline | Owner |
| D6 | 2026-10-28 | Count searches, views and follows by area and hour (F-13) | Demand data without shouts, no extra typing | Needs clear consent | Pia |
| D7 | 2026-10-28 | One global alert switch; no per-cart switches | Simpler | Can't silence one cart without unfollowing | Owner |
| D8 | 2026-10-28 | Data is sold back to sellers through a membership (Phase 2), not to outside buyers | Clear value, simple consent | Smaller data revenue for now | Owner |
| D9 | 2026-10-28 | Followed carts are shown at any distance; others within 3 km | Regulars want their cart wherever it is | Followed list can grow long | Pia (kept from v0.9) |
| D10 | 2026-10-28 | *(Replaced by D19)* The mockups continue the existing app's design system; no new visual language | The demo must look like the product the counterpart already saw; the frontend can reuse the app's tokens | Some app tokens are sampled, not copied, so a few shades may shift in the build | Pia |
| D11 | 2026-10-28 | Two apps: buyer and seller | Play allows one "location while closed" feature per app; the seller app needs it for Buka. Matches the mockups | Two store listings to maintain | Pia, on CTO advice |
| D12 | 2026-10-28 | Share links use a free temporary address in Phase 0; own address from the pilot | No purchase needed for the demo | In the demo, the link opens a web page, not the app | Pia |
| D13 | 2026-10-28 | Tunai is preselected when recording a sale | Keeps a sale at 3 taps; cash is the common case | A QRIS sale needs 1 more tap; a seller may forget to switch | Pia |
| D14 | 2026-10-28 | Editing a sale and editing the dish list move to P1 | Neither shows in the demo; saves 2–3 days | A wrong sale is deleted and re-entered | Pia |
| D15 | 2026-10-28 | Searches count where the buyer is; only dish and cart names are kept, others as *lainnya* | Real demand, with no personal details stored | Unusual searches lose their words | Pia, on CTO advice |
| D17 | 2026-10-29 | Sellers edit their own photos, description and menu (F-16), P0 | Owner request; sellers keep their page fresh without an agent | Some photos or prices may be wrong; seller corrects them after admin contact (D27) | Owner, shaped by Pia |
| D18 | 2026-10-29 | Reviews only from buyers who were near the cart while Buka; sellers reply and report but can't delete | Keeps reviews honest without purchases in the app | Some real buyers can't review; regulars who never came near can't either | Pia |
| D19 | 2026-11-01 | The mockups follow the current app's blue colours; replaces D10's cream and coral | Owner's call: one look across the app and the mockups, with no restyle of the app needed | The cream and coral look is dropped | Owner |
| D20 | 2026-11-01 | *(Withdrawn; Owner kept blue, see D21)* New design system "Hitam, putih, satu sinyal": black and white, flat, one lime signal colour for "open now", greyscale map | Owner asked for clean, modern, minimalist and original; no Indonesian super-app uses black plus lime (Assumption, unchecked), and black on white reads best in sun | Kai's demo app must be restyled; lime is pale on white, so it is only ever a fill behind black text | Owner brief, Pia's design |
| D21 | 2026-11-01 | Keep the blue; revamp layout and sizing: 360 × 780 screens, type scale with nothing under 12 px, one-line list rows, 8-point spacing, 44–52 px tap targets | Owner: the problem is layout and sizing, not colour | Less fits on one screen; long names and dish lists are cut with "…" in lists (shown in full on the cart page) | Owner, Pia's design |
| D22 | 2026-11-01 | Design redone from research: one design, two native skins (Android Material 3 habits, iOS HIG habits), system fonts, real screen sizes; blue brand kept | Owner asked for a from-scratch revamp for Android and iOS; users expect their platform's own controls | Two sets of screens to keep in step; the frontend builds platform-specific bars and controls | Owner request, Pia's design |
| D23 | 2026-11-01 | Seller home: status card in words + one full-width 64-high BUKA/TUTUP button at the bottom (replaces the round disc); Habis is a switch per item; third seller tab is Toko saya (account settings inside it) | Thumb reach, status not by colour alone, native on/off control | The round disc's character is gone; account settings are one level deeper | Pia |
| D24 | 2026-11-01 | Solid white header bars with a divider; content grouped on outlined white cards; corners cut to 4–10 (sheets 16) | Owner: content blended into the background and corners were too round | Looks a little more boxed than stock iOS | Owner feedback, Pia's design |
| D30 | 2026-11-01 | Every heading gets its own white surface (header band, sheet head, cart title block, admin title bar); titles 24–28 px | Owner: headings still blended in; the cause was the shared grey ground, not the text colour | More white at the top of each screen; slightly less map visible under the sheet head | Owner, Pia (Kai diagnosis) |
| D29 | 2026-11-01 | Mockups follow the existing GitHub app design; only headings, titles and labels get stronger weight and darker colour. Replaces the visual parts of D22–D24 and D28 | Owner: the GitHub design is much better; its only problem is headings blending into the background | The round BUKA disc and Habis buttons come back; the v2 and OpenDesign work is kept only as history | Owner, Pia |
| D28 | 2026-11-01 | New OpenDesign product-system proposal; blue remains, hierarchy and layouts redesigned | Owner requested OpenDesign and chose Create a new system | Visual proposal needs review; illustration data does not verify working app behaviour | Owner direction, Pia design |
| D27 | 2026-11-01 | Sellers supply and maintain all shop information; admin reads it and changes buyer visibility only. Setup is in the seller app, not the console | Owner clarification: all details come from seller information first | Admin must ask the seller to correct errors; onboarding effort needs a revised CTO check | Owner |
| D26 | 2026-11-01 | Remove the admin **Daftar menu** page, editing sellers on their behalf and the separate Nonaktifkan flow; one **Tampil ke pembeli** switch per seller; the dish list is fixed in Phase 0 | Owner: keep it simple, just enable or disable from the buyer view | No admin-side menu fixes before the demo, so a wrong dish goes through Pia or Kai; hiding is a blunt tool (no reason field yet) | Owner request, Pia's design |
| D36 | 2026-11-01 | **Peta opens without an account.** Map, list and search work signed out; opening a cart, Ikuti, ulasan, saved places and alerts ask for sign-in once, on top of the same map. Supersedes D4 | Owner: the map is the product, so a visitor should see it before filling in anything. Sign-in still comes before any action that creates data | Guests see cart names and positions; reviews and cart details sit behind sign-in, so they reach fewer people; more first sessions end in a sign-in prompt | Owner |
| D35 | 2026-11-01 | **Reviews show on the cart page in Phase 0** (average, count, tags, latest two, "Ulasan baru" under 3). Writing them stays P1. Q8 closed | Owner: reviews are the reason a buyer walks over, and the counterpart should see them in the demo; writing needs proof of a visit and moderation | Phase 0 reviews are example data; a cart with no reviews looks empty | Owner |
| D34 | 2026-11-01 | **7 hari terakhir opens per day**: which menu sold, portions and takings per dish, highest portions first; zero days say "Tidak ada penjualan hari itu." | Owner: a seller needs to know what actually sold, not only the day total | The list gets longer when a day is open; the numbers only add up if every sale stores its items (F-11 already does) | Owner |
| D33 | 2026-11-01 | **No demo page in the admin console.** The admin has Penjual and Pantau visibilitas only; the Phase 0 simulation is turned on by the team before the demo, with no UI for it | Owner: a demo panel in the live console is a risk and adds a screen nobody uses after the demo | The team needs another way to start the simulation; presenter must remember it before each session | Owner |
| D32 | 2026-11-01 | **Manrope** is the app typeface, replacing Plus Jakarta Sans. Sizes, weights, colours and spacing stay as they are | Owner chose it from five options drawn on the real screens; it carries the 18 px heading weight with more character than Jakarta and keeps prices and times crisp | Long names run a little wider; the app must bundle one new font file | Owner |
| D31 | 2026-11-01 | Section headings get their own white bands joined to their content; **Hari ini** becomes a heading with the totals on the next line; headings inside a card use a divider instead of a second surface | Section headings still read as background under the D30 screen-title fix | More white on screen; two heading treatments to keep straight | Pia, after the Owner's request |
| D25 | 2026-11-01 | Add F-18, an admin visibility monitor, as P0; admins message sellers by hand via WhatsApp, no automatic alerts yet | Owner: quality control, for now done by people; protects the core promise that open carts are on the map; also measures A1 | Someone must check the page each evening; reasons are best guesses | Owner request, Pia's design |
| D16 | 2026-10-28 | The demo simulation stops on its own after 2 hours | Keeps hosting within about $5 a month | The presenter restarts it for long sessions | Pia |

---

## 20. Glossary

| Term | Meaning |
|---|---|
| **Gerobak** | Street-food cart (push cart or motorbike cart); also the product name |
| **Buka / Tutup** | Open / closed: the seller's switch for being on the map |
| **Habis** | Sold out |
| **Halal / Non-halal** | Permissible / not permissible for Muslims; here as declared by the seller |
| **Lama buka / Jarak** | Time open / distance travelled (F-19) |
| **Ikuti / Diikuti** | Follow / followed |
| **Dekat Anda** | "Near you": the alert when a followed cart is close |
| **Di sekitar Anda** | "Around you": the list of carts within 3 km |
| **Catat penjualan / Penjualan** | Record a sale / Sales tab |
| **Tunai / QRIS** | Cash / Indonesia's standard payment QR. Here only a label for how the buyer paid |
| **LIVE / STALE** | The cart's position is fresh / a bit old (dimmed) |
| **WITA** | Central Indonesia Time (UTC+8), Bali's time zone |
| **Field agent** | Team member who helps sellers sign up in person |
| **Membership** | The future paid plan for sellers (Phase 2) |
| **Polling / suara** | Poll / vote (F-22) |
| **Ikuti & pilih** | Follow and vote: one tap for a non-follower to join a poll |


D31 · 2026-11-01 · Owner requested clearer section headings. White section bands and a separate sales summary extend D30. Accepted trade-off: slightly more vertical space in exchange for clearer grouping. No scope change.

D32 · 2026-11-01 · Owner: “explore alternative fonts”. Five typefaces (Plus Jakarta Sans, Inter, Manrope, DM Sans, Nunito Sans) were set on the real Penjualan and Gerobak screens at mockups-v3/font-lab.html, with a script-free Typeface switch on every page. Owner chose Manrope. Accepted trade-offs: long names run slightly wider; the app must bundle one new font file. Sizes, weights, colours and spacing unchanged, so no acceptance test changed and no feature or priority changed.

| D37 | 2026-11-01 | Aligned sales columns | Seller can scan amounts quickly | Longer names truncate in narrow rows | Owner |
| D38 | 2026-11-01 | Denser type and spacing, larger map viewport | More map visible on a phone | Less room for verbose copy | Owner |
| D39 | 2026-11-01 | Diikuti Buka/Tutup tabs with search | Faster access to relevant carts | Extra tap to see the other status | Owner |
| D40 | 2026-11-01 | Two-step seller setup: identity and location, then menu | Less crowded form | One more transition | Owner |
| D41 | 2026-11-01 | Fixed or variable price per item; amount entered at sale | Supports products priced by order | Variable sale needs extra input | Owner |
| D42 | 2026-11-01 | Missing updates hide stale positions without treating them as seller-initiated Tutup; recovery uses recent offline-recorded points automatically; a phone tracking gap over 30 min requires seller confirmation and a fresh position; only seller Tutup ends a shift | Buyers do not travel to an old pin, and sellers can recover without rebuilding the shop | A seller with a dead phone cannot be warned until they return | Owner request, Pia decision |
| D43 | 2026-11-01 | Opening alert uses the cart name and current broad area, with Lihat di peta; no street names or address lookup | A buyer gets enough context without a fragile street guess; map supplies the precise pin | Area can be omitted if unavailable | Owner |
| D45 | 2026-11-03 | Real photo upload from camera or gallery for the cart (1 required, up to 5) and each menu item (optional); stand-in pictures removed | Owner: the app can't upload photos; buyers recognise a cart by its photo | Storage cost and a CTO effort check; a photo can wait on weak signal | Owner request, Pia |
| D46 | 2026-11-03 | Remove **Biasa berjualan di** from setup and Toko saya | Owner: not needed; the live position while Buka is what buyers use, and no screen used the field | Admins lose a hint of where a new seller works; can be derived from Buka history later (P2) | Owner request, Pia |
| D47 | 2026-11-03 | *Superseded by D55.* Jenis masakan becomes a search over a list of about 190 dishes with other names; **Lainnya** when nothing fits | Owner: pills don't scale and the list was thin (also the CTO's F-02 risk) | Typing on a phone; the list needs upkeep from Lainnya picks | Owner request, Pia |
| D48 | 2026-11-03 | Replace the per-item pork flag with one **Halal / Non-halal** choice per cart, shown as declared by the seller, no official logo | Owner: halal is what Muslim buyers look for; a per-item flag says too little because the kitchen is shared | Relies on the seller's honesty; wording needs a legal check (Q10); a per-item view is lost; long cart names in list rows are cut a little sooner to fit the tag | Owner request, Pia |
| D49 | 2026-11-03 | BUKA and TUTUP ask for confirmation in a sheet; refines D2 | Owner: prevent misclicks; a wrong Buka alerts every follower and cannot be undone | Two taps instead of one at the start and end of each shift | Owner request, Pia |
| D50 | 2026-11-03 | New F-19 **Rute hari ini** on seller Beranda: route map, time open, distance; seller only | Owner: sellers want to see their day; also a step towards membership insights | More work on Beranda; distance is approximate | Owner request, Pia |
| D51 | 2026-11-03 | New F-20: toasts sit at the bottom above the tab bar, leave after 4 s (6 s with a button), one at a time; lasting conditions are banners | Owner: the toast floated over the BUKA button and never went away | A seller who looks away may miss a toast; anything important is a banner instead | Owner request, Pia |
| D52 | 2026-11-03 | Di sekitar Anda sheet has three heights: Kecil, Sedang, Penuh | Owner: the list should extend upwards | At Penuh the map is hidden; one more control to learn | Owner request, Pia |
| D53 | 2026-11-04 | *Superseded by D55.* Jenis masakan is a dropdown: a ▾ field that opens the whole grouped list, with optional search; the list grows to 264 dishes in 16 groups; refines D47 | Owner: wants a dropdown and more choices. Options weighed: (a) plain phone dropdown, a flat list of 264 rows, too long to scroll; (b) two dropdowns, group then dish, an extra step and sellers must guess the group; (c) one dropdown with group headings and optional search, chosen: works for sellers who scroll and those who type | A tall list to scroll; the added dishes are assumptions until field agents check them (A8) | Owner request, Pia |
| D61 | 2026-11-12 | F-10 buyer texts rewritten in plain everyday Bahasa Indonesia (copy table); coordinates and compass buttons removed from view | Owner: wording too technical for warung customers | Some precision is lost in wording ("dekat" instead of exact rules); copy must now be kept in one table | Owner request, Pia |
| D68 | 2026-11-13 | Show the rating average from the first review, always with the count, in Ringkasan, the cart page and every cart card; replaces the "Ulasan baru until 3" rule of D35 | Owner: the rating seemed missing and should be visible on the shop page and cards. The count beside it lets buyers judge a 5,0 from one review | A single harsh review weighs heavily on a new cart; admin hiding (D63) is the safety valve | Owner request, Pia |
| D69 | 2026-11-13 | A Buka shift with no position for 60 minutes closes automatically at the time of the last position; the seller sees why on reconnect; supersedes D42's "only the seller's Tutup ends a shift" and F-03.AC9 | Owner: a lost cart should not stay open; clean Lama buka, route and admin data | A seller still selling in a dead zone or with a phone that stops the app drops off and must tap BUKA again; Pia raised this once, the reconnect banner and the existing battery prompt are the mitigations | Owner request, Pia |
| D63 | 2026-11-13 | Buyers write reviews from the cart page (stars, tags, note); any signed-in buyer, one per cart, not the shop's own account; admin can hide; proximity rule dropped | Owner: no way to review. The 100 m rule needs location history we don't keep and blocks real customers who didn't open the app | Fake or unfair reviews are easier; admin hiding is the safety valve; revisit if abused in the pilot | Owner request, Pia |
| D64 | 2026-11-13 | Pengikut, Nilai and Ulasan shown as one numbers card in Toko saya and one row on the cart page | Owner: the profile isn't clear; numbers should be visible at a glance | One more card above the menu | Owner request, Pia |
| D65 | 2026-11-13 | The seller's background notification reads "Gerobak Anda tampil di peta", stays while Buka and goes at Tutup; no Tutup button in it (Tutup keeps its confirmation, D49) | Owner asked whether the app runs in the background; Android requires this notification anyway, and the seller must know they are still visible | One extra tap to Tutup from the notification | Owner question, Pia |
| D66 | 2026-11-13 | New F-21 Stok hari ini: optional per item, lowered by recorded sales, auto-Habis at 0, buyers see "Tinggal n" only at 5 or fewer, clears at midnight | Owner: sellers need a stock counter. Optional so busy sellers aren't forced; low-only display because counts depend on recorded sales | Counts drift if sales aren't recorded; one more field on Beranda | Owner request, Pia |
| D67 | 2026-11-13 | F-15 Pengumuman moves to P0: one line, 80 characters, cart page and Diikuti, 24 hours, no push | Owner: sellers want to tell buyers something; 24 hours stops stale messages like "sampai jam 21.00" | Seller must renew daily | Owner request, Pia |
| D62 | 2026-11-12 | The buyer's Rumah and Kantor show as pins on Peta, a Profil mini-map and faded in the picker | Owner: buyers should see where their saved places are; replaces the coordinates | A busier map; pins must never be mistaken for carts | Owner request, Pia |
| D60 | 2026-11-12 | Skip a near push for a cart if its buka push reached the buyer in the last 15 minutes | Two pushes about the same cart within a minute feels like spam and pushes buyers to turn alerts off; the buka push already tells them the cart is out | A buyer whose cart opens right by Rumah isn't told the distance; they see it on the map | Pia, raised by Kai |
| D59 | 2026-11-12 | Dekat Anda uses saved places (Rumah/Kantor) and the buyer's position while the app is open; the buyer app never asks for "always" location; Q7 closed; supersedes D3 | Owner chose option B: the demo looks the same, about 4–5 days saved, no Google Play background-location review for the buyer app, fewer refused permissions, less battery | No alert when the buyer is somewhere new with the app closed; relies on buyers saving a place | Owner, Pia |
| D58 | 2026-11-10 | One Google account = one Gerobak account, used by both the buyer and seller apps; the shop is a role on that account, not a separate login; admin access stays separate | Owner question. Options: (a) separate seller and buyer accounts: sellers need a second Gmail to buy, and their own views can't be recognised; (b) one account, two roles, chosen: simplest for people and keeps F-07.AC1 reliable | A seller's buyer activity (follows) sits on the same account as their shop; it stays private and never shows on the shop | Owner question, Pia |
| D56 | 2026-11-05 | Each setup step is checked before moving on: Lanjut ke menu checks all of step 1 including whether the WhatsApp number is taken; + Tambah menu checks the current menu | Owner: the number error only showed at the end; fixing a mistake should happen where it was made | One more check (and a short wait) on Lanjut; without signal the number is checked at the end instead | Owner request, Pia |
| D57 | 2026-11-05 | Pengikut becomes a Beranda card: total, new this week, 7-day bars of new followers, who gets the Buka alert; replaces the one-line text | Owner: the follower section was only a sentence; sellers should see their following grow | One more card on Beranda, so the menu sits lower; counts only, never names (privacy) | Owner request, Pia |
| D55 | 2026-11-05 | **Jenis menu** is one of three: Makanan, Minuman, Camilan, per item, required; menu grouped by these on the cart page; the dish list stays only for demand counts; replaces D47 and D53 | Owner: simplify. Three big buttons are one tap for every seller, need no reading or scrolling, and no item is left as Lainnya | Search by another dish name (*terang bulan* → *Martabak manis*) is lost; demand by dish is read only from buyers' searches, not from what sellers sell; yesterday's dropdown work is dropped | Owner request, Pia |
| D54 | 2026-11-04 | A menu item's photo shows wherever the item is listed (seller Beranda, Toko saya, Catat penjualan, buyer cart page); the placeholder only when there is no photo | Owner: menu photos didn't show; sellers need to see the photo they uploaded is in use | Slightly more data on the seller's phone for small thumbnails | Owner request, Pia |
| D44 | 2026-11-02 | Carts are named on the map; a list card focuses that cart's pin; each card has a Profil button to the cart page | Owner: a buyer should recognise a cart on the map without matching pins to rows, and the list should steer the map. One explicit button keeps the profile reachable when the card now moves the map | The map is busier and its labels take space over the pin; reaching the profile takes two taps instead of one; cards get narrower for the name | Owner request, Pia's design |
| D70 | 2026-11-17 | New F-22 **Polling pengikut** (P0): the seller types one question and 2–4 answers, picks a length (1 jam to 7 hari, 24 jam default), one poll at a time; followers vote once and may change it; non-followers are offered **Ikuti & pilih**; buyers see results after voting; seller sees counts, never names; no editing after start; final results show 24 hours | Owner: sellers need a way to let followers vote, free text for now, with a timer. Options weighed: (a) seller writes the answers, buyers pick one, chosen: real counts a seller can act on, simplest to read on a phone; (b) buyers type their own answers: rich but uncountable and needs moderation, it's comments, not voting; (c) answers picked from the seller's menu: tidy, but can't ask about places or times. Fixed lengths instead of a date picker: one tap, no wrong dates. Follow-to-vote turns the poll into a reason to follow (G2) | Sellers can't ask open questions; a typo means delete and restart, losing votes; non-followers can't vote without following | Owner request, Pia |
| D71 | 2026-11-17 | Polls send no push at the start or the end; they show on the cart page and in Diikuti | Notifications were cut from 16 kinds to 2 (v1.0) and buyers have one switch for all of them (D7); a third kind risks buyers turning alerts off, which costs the "open" alert, the core of G3. Same reasoning as pengumuman (D67) | Fewer votes, mainly from buyers who open the app anyway; counts are only as fresh as the last open or pull-down; revisit with A11 in the pilot | Pia |

D33–D36 · 2026-11-01 · Owner asked for four changes: no demo in admin, 7-day sales opened per menu, reviews on the cart page, and Peta open without an account. Accepted trade-offs: the simulation needs another way to start; a day opened makes the sales list longer; Phase 0 reviews are example data; guests see less of a cart until they sign in, and D4 no longer applies. No other requirement changed.
