2.0 KiB
Web QR Login Simplification — 2026-05
Session learning from BOSS refining the xianyu-hunter Web login UX.
User preference
BOSS found the login panel too busy after adding QR login and account status. For this project, the preferred Web login UX is deliberately minimal:
- Keep only 获取/刷新登录二维码 and 刷新账号状态 in the visible login modal.
- Do not expose legacy/backup actions as primary UI buttons:
- 打开闲鱼登录窗口
- 等待并检测
- 上传 Cookie JSON
- 关闭登录浏览器/关闭登录会话
- Keep backup APIs/functions available if useful for troubleshooting, but hide them from the normal Web UI unless BOSS explicitly asks for advanced controls.
- Simplify help text to the QR-first flow: get QR → scan → refresh status → cookies persist in
browser-data/.
Implementation shape used
In /Users/chick/.Hermes/workspace/research/xianyu-hunter/public/index.html, the login actions block should be:
<div class="login-actions">
<button class="btn btn-primary" onclick="fetchLoginQr()">获取/刷新登录二维码</button>
<button class="btn" onclick="checkLoginStatus()">刷新账号状态</button>
</div>
The help text should avoid mentioning JSON import or manual browser opening in the normal flow.
public/app.js may still contain openLoginWindow(), waitLoginStatus(), importCookieFile(), and closeLoginBrowser() as hidden troubleshooting utilities, but no visible element should call them in the standard modal.
Verification commands
cd /Users/chick/.Hermes/workspace/research/xianyu-hunter
node --check public/app.js
node --check server.mjs
node --check lib/login.mjs
PORT=3000 node server.mjs
curl -sS http://127.0.0.1:3000/ | grep -E '获取/刷新登录二维码|刷新账号状态|上传 Cookie JSON|打开闲鱼登录窗口|等待并检测|关闭登录会话'
Expected UI marker result: only the two kept buttons and QR/status help text should appear; no legacy button labels should appear.