恋爱积分簿 · Love Points Tracker 💕
A private score-keeping app for two people. Log the small things you do for each
other — cooking, chores, a letter, a photo — and watch them add up: into points,
into a shared goal, into a pet that grows, into a room you decorate together.
Built as vanilla JS + HTML + CSS against a ServiceNow Scripted REST API.
No framework, no bundler, no build step. index.html is the app.
📖 用户使用指南 (User Guide) · 🐣 小窝设计文档 · 🛠 Engineering rules
📋 Changelog · 🏗 System design · 🗂 Migration record
What it does
Scoring
- Two accounts, one shared ledger. Each partner has their own score; both see every entry.
- Custom categories with emoji and point values; 奖励模式 / 惩罚模式 with a monthly target.
- 月末结算 archives the month to history and starts fresh. Past months are swept
automatically; the still-running month is opt-in.
Together
- 共同目标 — a joint points target you both feed (a trip, a nice dinner).
- 情书 — a private letter arrives as a sealed envelope until your partner opens it.
- 回忆相册 — photos with captions, played back as a Ken Burns slideshow.
- 成就徽章 — 16 badges derived from real activity, so they can never be wrong.
- 年度回顾 — a yearly recap with your best month, top category and that year's photos.
- 对方的天气 — each phone publishes its own weather so you can see their sky.
恋爱小窝 (the pet game)
- Adopt one of 4 species; it grows from your activity, starting at 0 EXP.
- 小窝币 come from the pet's growth, never from your love points — furniture never
competes with real rewards.
- 32 hand-drawn SVG pieces, freely placed, dragged, resized. The room is shared:
move a sofa and your partner sees it within seconds.
- 10 seasons and festivals with their own palette, sky, particles and pet outfit.
- Year-locked keepsakes — one piece per festival per year (2026–2028 pre-drawn).
Miss it and it's gone; buy it and it's yours forever.
The whole app follows your phone
- 早晨 · 白天 · 黄昏 · 夜晚 — palette and sky follow the local clock; night goes dark.
- The moon is the real moon, computed from the lunar cycle — a full disc on 农历十五.
- Real local weather falls over the page and against the pet-room window.
Architecture
iPhone / laptop browser
├── index.html all markup + CSS (4.7k lines)
└── app.js all logic — state, render, API, SVG art (6.1k lines)
│
│ HTTPS · apikey + Authorization: Bearer <access token>
▼
Supabase yvllstktmjoedfsgojgs.supabase.co
├── /functions/v1/* 27 Edge Functions — every business rule
├── Postgres 12 tables, row-level security on all of them
├── Auth hashed passwords, JWT + refresh
└── Storage private "photos" bucket, served as signed URLs
Only a function may write. RLS is SELECT-only for clients, so a session token
alone cannot change a row; functions hold the service-role key and bypass RLS. The
upside is that every rule lives in one place. The cost is that there is no second
line of defence behind it — a missing check in a function is simply missing.
No build step: node --check app.js is the whole toolchain. The frontend
auto-deploys from main via GitHub Pages; functions deploy with
npx supabase functions deploy <slug>. Deploy the function first when a change
spans both, or the pushed app calls an endpoint that doesn't answer yet.
Ran on a free ServiceNow PDI until 2026-09-11. servicenow/ is kept as history
— those scripts are the source this was ported from and are no longer deployed.
See the changelog.
Data model
Everything shared is scoped by match_id (the couple). bag is also scoped by
char, because an unredeemed reward belongs to one partner. Row-level security
enforces both in the database: a cross-couple read returns empty, a cross-couple
write 404s.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
