One Page Per Person: AI Built a Private WeChat Memory Book in 24 Days, and Three Walls Held
I Used AI to Build Another Mini Program: 24 Days, Recording Everyone I've Known in My Life
Last month my mom called and asked whether the kid in Uncle Sanjiu's family was taking the college entrance exam this year.
I opened my mouth, the name was right there, and I couldn't say it. It took ten minutes of scrolling through WeChat before I found his name in a group chat nobody had spoken in for ages.
That hit hard. I clearly knew all these people — we'd eaten together, they called me 'big brother,' we'd toasted. But apart from a blurry face, nothing was left.
I tried keeping it in my memo pad. Thirty-odd entries in and it was chaos: this one is for Old Wang, that one is a college roommate, search 'hotpot' and you get a crowd. WeChat chat history doesn't work either — it only keeps what was said, not 'this person has a weak stomach, can't eat spicy.'
What I actually wanted was simple: one page per person. Their birthday, how we met, what we've done together over the years — something to flip through when I need it.
This isn't my first mini program. I built an electronic class yearbook before, for graduation season — everyone scanned a QR code and wrote their own page.
But a yearbook only holds one graduation. Three, five years out, those people drift apart year by year, and I can barely remember their names anymore.
So I started another one. The same 'one page per person' idea, but instead of recording one graduation, it records everyone you've known in a lifetime.
Except 'simple things' can't be built by one person. Design — I can't draw, so it would come out ugly. Front end and back end to write. A server to buy, a domain to configure. And the mini program has to pass review. Normal pace is measured in quarters, and I know myself too well — I'd quit halfway. The last project ended exactly like that: it ran, and then there was no 'and then.'
This time I didn't quit. 24 days, from the first commit to how it looks now.
First, what AI actually made easier
Not 'it can write code.' People who can write code are everywhere; that's not worth anything.
What actually felt different was a few things below.
First, it turned one sentence of plain language into something shippable.
I told it: birthdays need to support the lunar calendar, and you have to handle leap months. Leap April and regular April aren't the same day. Don't get it wrong.
Its solution was three fields: birthday stores the date, birthday_calendar stores the calendar system, birthday_leap_month stores the leap-month flag. Then it added: don't auto-calculate zodiac signs from lunar birthdays, because zodiac is a Gregorian concept.
That last sentence was something I hadn't thought of. I could have thought of it myself, but I'd probably have found out after entering a hundred records — and changing it then would be a disaster.
Front end and back end each got their own lunar conversion (the homepage needs to calculate 'how many days left' client-side, the server needs it for reminders), and leap months and variable month lengths (first month/twelfth month, first day/thirtieth day) all have to be right. This kind of thing isn't hard, but it's tedious — exactly what you throw at it.
Second, it never gets annoyed.
The final version is 16 pages and about thirty custom components; front-end wxml/wxss/js/json totals 13,000-plus lines, and the Spring Boot back end is 10,000 lines and change.
Every page needs the four-file set, button heights have to be a uniform 80rpx, card corner radius 20rpx, style class names have to be BEM, APIs have to be uniformly wrapped, and pages with login state have to await wx.$onLogined first.
None of these tasks has any technical content. But added together, they're enough to grind a passionate person down.
AI doesn't get annoyed. Ask it to change something a seventh time, and it won't roll its eyes.
Third, it filled in the part I would have skipped entirely: aesthetics.
I described it: Kodak film, darkroom smell, old photo album — no sticker-and-stamp scrapbook vibe.
It started with a dozen-plus HTML previews for me to pick from, and we settled on: rice paper background #F7F5F0, burnt caramel amber #92400E, serif headings, dates in monospace like machine-stamped archive numbers.
I went through many rounds of changes, but each round was me saying 'make this older' or 'this is too flashy,' and it produced, and I picked.
Without AI, I would have skipped this whole step and made a white-background-blue-button utility that I wouldn't want to open a second time.
Fourth, and what surprised me most: it had the guts to cut my requirements.
I really wanted a 'relationship graph' at the start — a web of everyone I know, A and B went to school together, that would look great.
It didn't just agree. It made a table, scored each candidate feature against 'can a notes app replace it,' 'how much does it cost to build,' 'how often will I use it,' and told me: we can do it, but it goes last. Build the long-image export and quick import first.
I did. In hindsight it was right — the graph looks nice, but I wouldn't open it once a month myself; 'export a long image' is the only thing I'd show someone else.
But AI genuinely fails too, and I hit all three of these
One: human-situation common sense. It doesn't have it.
There's Uncle Zhang next door. When I was a kid I used to do my homework at his doorstep. He passed away last winter. The reminder module was copied from birthdays, and the wording came with 'wish you.'
I changed it to 'memory of birth' and 'death anniversary,' turned the avatar on the person card grayscale, and the exported long image says 'time frozen' — no celebratory tone at all.
You can't write this kind of thing into a requirements doc. And AI won't volunteer the question 'is this person still alive?'
Two: the compliance line. It doesn't care.
I'd planned a 'public memorial page' — thought the reach would be better. After checking the rules: an individually-registered mini program, the moment it has user-to-user interaction or a public profile page, the category becomes social-notes, which individual accounts can't open at all.
So this product has a hard red line: private to yourself, no adding friends, no reading your contacts, no public content at all. Except you, nobody can open your book.
And one debt I still owe: phone number and WeChat ID fields are documented as encrypted in storage, but the first version stores them in plaintext, only leaving headroom in the column length. I know this debt is on me.
Three: it will invent with total confidence.
During the front-end/back-end integration days, field names didn't match, endpoints didn't exist, and it fabricated them more naturally than the real thing.
So by the late stage, my job turned into acceptance testing: it writes ten lines, I read ten lines, run it once, and if it's wrong send it back to redo.
That's not bad news — acceptance is way faster than writing from zero. But it means one thing: if you don't understand at all, you can't accept. AI amplifies your judgment; it doesn't replace it.
So what does this thing actually look like
It's called Acquaintance Book (相识簿). One line: a personal book of people, written only for yourself.
Not a contacts app, not a CRM, no friend requests, no 'network management.' It does one thing: gathers what's scattered across chat history and memory, stacked by person.
The images below are from a freshly registered empty account. I deliberately screenshotted an empty one — the book holds other people's stories, so posting them wouldn't be appropriate.
The homepage doesn't do work. It just makes you remember.
With content, this page is one line for today, the nearest memorial date, what you did this day that year and with whom, who you've eaten with recently, and a section for 'people you haven't been in touch with in a while.'
An empty account opens to the image above: a sample card, three scene hooks, and a 'record the first person' button. I redid this many times and kept 'one dedicated page per person, written only for yourself' because it's the one thing this product can't give up.
One page per person.
The person list is in the image. The search box searches by nickname and real name, tags are tappable (family, classmate, relative, friend, colleague), sortable by most recent record or how long you've known them, and 'by group' is a separate view.
Tap through and it's that person's page: how you met, how many years you've known them, birthday (Gregorian or lunar both work, leap months selectable, zodiac auto-calculated), phone, WeChat, QQ (only you can see them). And a 'profile summary' section for personality, dietary restrictions, social taboos — for my mom's page I wrote 'don't bring up stuff at her workplace.'
Record an entry.
Date, one sentence, one photo, location, pick from 12 moods. No essay required — one sentence is enough: 'Had hotpot today, he said next time he'll bring his daughter.'
Album import.
Up to 20 photos at once, one caption per photo, generates 20 records in one shot. Photos sitting in your phone for years finally have a place to go instead of living at position 4,000 in the album.
Reminder hub.
Birthdays, death anniversaries, knowing-day anniversaries, lunar (calendar) included. The header line 'small reminders you only see when you open the app' isn't copywriting, it's fact: there are no push notifications here.
I know this is a product flaw — follow-up depends on you remembering to look. But to avoid the 'follow our official account to get reminders' routine, this is how it stays for now.
Export long image.
Pick up to 10 records, compose a 'time film strip' long image, footer has the mini program QR code. Save to album, print and tuck into a physical album, or post to moments.
I won't show the long image — it's all other people's business. The whole image is drawn locally on your phone with canvas; no image is uploaded to third parties.
Invite the other person to fill in their own page.
The entry is in 'Mine,' the first item: 'Invite TA to complete their profile.' An old classmate not seen in ten years, I don't know what city he's in now, I can send him the card directly and let him fill it in himself.
When he's done, it only saves to my book, only I can see it; if he wants to change something, he clicks the same link to redo. No registration, no verification code, and no second record gets created.
You can also see the line I drew for myself in this image: the bottom of the page says 'no public leaderboards, no reading contacts for friend suggestions,' and the stats are four numbers — people you know, records of moments together, photo evidence, days since joining. No followers, no interactions, no number you have to maintain.
Groups.
A class, a family, a team — collect them into a group, tap through to a wall of avatars. The class from your yearbook is one group here.
People no longer here, recorded properly too.
Avatar goes grayscale, death anniversary gets its own entry, tone is remembrance not celebration. After I created Uncle Zhang's card, I rewrote that death-anniversary caption three times; no wording ever felt quite right.
Quick tech stack for the practitioners: native mini program (no framework) + Spring Boot 2.7 + MySQL + Redis + JWT, images uploaded directly to OSS with only URLs in the database. Mini program QR codes are generated on the back end and returned as base64 without persistence, saving an entire storage setup for one code. Long images are composited purely client-side via off-screen canvas — zero server-side rendering cost.
24 days, and a little selfishness
From the first commit on October 27 to today, 24 days.
Most of the time I wasn't writing code, I was making decisions: what to build, what not to build, how to phrase this line, whether this button goes left or right. AI pushed the cost of 'doing' down to near zero, and what's left is 'thinking clearly.'
This is what I most want to say after finishing:
AI's strength isn't 'writing code,' it's 'if you can say it, it will do it.'
And what ordinary people most lack isn't usually execution — it's 'knowing what you want' and 'knowing what you shouldn't want.'
I'm still filling it in. Last week I made a card for my college roommate, dug out photos from climbing a mountain together in 2016, and laughed for a while seeing how thin I was back then.
It doesn't solve loneliness, and it doesn't maintain relationships for you. It just gives you a place to look when you can't remember.
The mini program is called Acquaintance Book. My second mini program, and the first one I finished that I still use. It doesn't have many features, the relationship graph isn't built yet, data backup and complete deletion are still owed, and questions are welcome.
If you have a few people you've always wanted to seriously record but never quite bothered to start, give it a try.
Acquaintance Book · Memory time journal for people — one page per person, written only for yourself.
No registration, no phone number required, it opens to an empty book. Scan with WeChat, or search directly for 'Acquaintance Book.'
If you could only record one person, who would you record first?
Top 2 of 3 from juejin.cn, machine-translated. The original thread is authoritative.
Why not add the address book? Don't waste tokens in the future (facepalm)
The address book is primarily for communication.
Check out mine.