WeChat mini program for short-lived neighborhood tasks.
Nearby short-lived information should be easy to confirm, update, and close.
The app has no fixed service area. Users can browse and publish tasks from any current location.
- Map-first task browsing around the user's current location and visible map region.
- Location-agnostic identity on the map, publish, profile, and admin surfaces.
- "Find one" discovery action for sparse maps, jumping to a random nearby post.
- Publish flow with category-specific guidance, lost/found direction, place, coordinate, and expiry controls.
- Publish-success sharing prompt and detail-page share metadata.
- Task detail page with comments, confirm, stale, resolve, and report actions.
- Client feedback plus server-side deterministic duplicate prevention for repeated trust actions.
- Local profile UI with an admin-only management tab authorized by
getMyRoleV2and theadminscollection. - Management console for search, risk filtering, reported/stale/hidden review, user feedback, and hide/close actions.
- CloudBase V2 posts, reactions, comments, feedback, attribution, account consent, rate limits, upload sessions, counters, retention, and admin checks. Local mock storage is available only when CloudBase is disabled and explicit development mock mode is enabled; production failures do not silently fall back.
- Open this folder in WeChat DevTools.
- Use
project.config.json; the placeholder appid istouristappid. - Run
npm run checkfor JSON, knowledge, package-boundary, frontend and backend readiness checks.
For shared user data, deploy postsV2, getMyRoleV2, and timer-only dataRetentionV2; create the 10 collections and indexes documented in CLOUDBASE_DEPLOY.md. Legacy functions must remain client-invocation disabled.
Posts with images require CloudBase Storage. Storage is READONLY to clients: the V2 function receives a restricted base64 payload, validates actual JPG/PNG signatures and dimensions, performs content safety, uploads to a random managed path, and saves only cloud:// file IDs. Cloud upload, safety, or entity creation failures remain explicit.
The current version intentionally keeps the product focused: map, publish, detail, structured trust actions, and admin-lite moderation. Deferred items are tracked in TODOS.md.