跪拜 Guibai
← All articles
Frontend · Backend · WeChat Mini Program

One Page Per Person: AI Built a Private WeChat Memory Book in 24 Days, and Three Walls Held

By 好市民_ ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

AI-assisted solo development compressed a quarterly timeline into 24 days, but the bottleneck moved from execution to judgment: every ten lines of generated code gets reviewed, and the product's entire shape is a compliance ruling WeChat handed down. Western developers leaning on AI for a real shipped product face the same ceiling: review capacity, not code generation.

Summary

A phone call about a relative's child exposes the gap: a face remembered, a name gone, ten minutes of scrolling a dormant group chat. 相识簿 is the fix. Not a contacts app, not a CRM, no friend requests, no public profiles. One page per person, a book only its owner can open.

The build runs 24 days from first commit. Front end is a native WeChat Mini Program, 16 pages and 30+ custom components at 13,000+ lines of WXML/WXSS/JS/JSON. Back end is Spring Boot 2.7 at 10,000+ lines with MySQL, Redis, JWT, and images direct to OSS. AI absorbs the tedious volume: lunar calendar conversion with leap months, unified API wrappers, 80rpx buttons, BEM class names. It even argues a feature down, scoring the relationship graph against replaceability and usage frequency, and the long-image export wins.

Three walls stop the AI cold. It copies birthday phrasing onto death anniversaries, so wording gets rebuilt manually as 诞辰 and 忌日 with grayscale avatars. It can't read compliance: a public memorial page would reclassify the app as social-notes, a category individual WeChat accounts cannot open, so privacy rules are mandatory, not aesthetic. During integration it invents endpoints and fields, turning the human into an acceptance tester: review ten lines, run, send back.

Takeaways
— The build ran 24 days from first commit: a native WeChat Mini Program with 16 pages and 30+ custom components at 13,000+ lines of WXML/WXSS/JS/JSON, plus a Spring Boot 2.7 back end at 10,000+ lines with MySQL, Redis, and JWT.
— Lunar birthdays store three fields (birthday, birthday_calendar, birthday_leap_month), and zodiac derives from the Gregorian date, not the lunar calendar.
— WeChat compliance forced the privacy design: individual account holders cannot open the social-notes category, so user interaction and public profiles are structurally impossible.
— The first version stored phone numbers and WeChat IDs in plaintext with only column-length headroom; this stayed as acknowledged unpaid debt.
— AI scored candidate features on three criteria (replaceability by a notes app, development cost, usage frequency), and the relationship graph lost to long-image export.
— Death anniversaries use memorial wording (诞辰/忌日), grayscale avatars, and 'time frozen' on exports instead of any celebration tone.
— Long-image export renders entirely on-device via off-screen canvas; no image touches a third-party server.
Conclusions

AI proved useful by absorbing the tedious volume that grinds solo development to a halt: boilerplate pages, uniform styling, repeated API wrappers, and it never got tired.

Compliance reshaped this product into something more deliberate: privacy isn't a marketing line here, it's the only configuration WeChat allows an individual account to run.

Plaintext phone numbers flagged as known debt show how AI-paced development shifts priorities: feature velocity outruns security hardening, and the boring fix lands on an unwritten roadmap.

With AI hallucinating endpoints and fields during integration, the human role collapses to acceptance testing, which means reading generated code fluently is the real skill constraint, not writing it.

Concepts & terms
WeChat Mini Program
A lightweight application that runs inside WeChat, built with WXML/WXSS/JavaScript. Approval categories constrain what features are allowed; individual (non-company) accounts cannot open the social-notes category, which forces any user-interaction or public-profile feature off the table.
Lunar calendar (农历)
The Chinese lunisolar calendar used alongside the Gregorian one for birthdays and festivals. It inserts leap months roughly every 2-3 years and has months of 29 or 30 days, so converting to and from Gregorian dates requires per-year rules, and software must carry a leap-month flag for birthdays.
Social-notes category (社交-笔记)
A WeChat Mini Program approval category for apps featuring user interaction, public profiles, or social content. Only company-registered accounts can open it, which is why personal apps with user-generated sharing are effectively forced to stay completely private.
From the discussion
Featured comments
aspray

Why not add the address book? Don't waste tokens in the future (facepalm)

好市民_

The address book is primarily for communication.

See top comments, translated →
Source: juejin.cn ↗ Google Translate ↗ Backup ↗