跪拜 Guibai
← Back to the summary

A WeChat Mini-Program MVP Replaces Nagging with a Little Red Flower

Recently, while checking the mini-program backend, I noticed that some users have been using it continuously.

Not test accounts, not clicks from myself, and not clicks from friends helping out.

That moment felt quite subtle. Although there is no revenue, the feeling that something I made has genuinely helped some families was very comforting.

image.png

Because this project was never a "grand narrative" product from the start, nor did it have a particularly complex business model. It is just a very small family growth tool: helping parents record their children's daily small goals, small progress, and small rewards.

But when you see real users starting to use it, you suddenly realize:

As long as a product truly solves a little bit of a real problem, it has a reason to keep going.

Project Background

The core scenario of this mini-program is very simple:

In many families, parents repeatedly urge their children every day to:

None of these things are big on their own, but repeating them daily easily turns into parent-child conflict.

So from the beginning, I didn't want to make a "task management tool," but rather a gentler family growth incentive system.

Its core is not:

Managing children

but rather:

Seeing a child's small progress and giving positive feedback

Parents no longer just verbally urge, but turn requirements into clear small goals.

After completing them, it's not just "done" for the child, but they can see their efforts being recorded.

After the parent confirms, a little red flower is awarded. This action is actually very important. It is not just a simple points system, but a kind of "I see you" feedback.

Why Use "Little Red Flowers"

The "little red flower" concept is very traditional, but also very intuitive.

For children, it is easier to understand than abstract growth values, points, or experience points.

For parents, it is also low-cost enough and doesn't require much explanation.

So I didn't design a complex system of levels, badges, or leaderboards from the start, but kept the simplest positive feedback first:

Complete a small goal, get a little red flower.

Levels, badges, and growth records can be expanded later, but the first version cannot be slowed down by these enhancement features.

For a personal project, the most important thing in the first stage is not how beautiful the architecture is, but whether the real user path loop can be run through.

Recently Added Direction: Growth Resource Library

While working on the mini-program, I also gradually realized a problem:

A pure tool might take users time to understand.

But many parents actually have very direct needs:

So recently I started testing a new module: a Growth Resource Library.

It is still in the testing phase, with plans to first put up some materials that parents can use directly:

The positioning of this module is not a "resource download station," but to help parents start using this growth mechanism at a lower cost.

If users don't know how to create goals for the moment, they can first download a plan template.

If parents don't know how to accompany their children in execution, they can first look at a communication script template.

Current Phase Iteration Focus

Next, I will focus on a few things:

1. Optimize the Child Mode Experience

Keep the child mode as pure as possible, only retaining content directly related to the child, such as goals, check-ins, little red flowers, and rewards.

Content like the resource library will be placed on the parent side and will not enter the child mode.

2. Improve the Growth Resource Library

The resource library is currently in the testing phase, first verifying whether parents are willing to browse, download, and use these materials.

If the data is good, then continue to supplement resource categories and backend statistical capabilities.

3. Add Data Statistics

Including resource page views, downloads, number of growth goals created, check-in counts, parent confirmation counts, etc.

Personal projects also need data feedback, otherwise it's easy to iterate based on feeling.

4. Optimize the First-Time User Path

Many products don't lack features, but users don't know what to do when they first enter.

Later, I will continue to optimize templates, empty states, and new user guidance to help parents complete their first creation faster.

A Little Retrospective

Seeing that there really are people using it in the backend this time, my feeling is:

An MVP doesn't have to be very complete, but it must have a real closed loop.

For this project, the closed loop is not the number of pages or the feature list, but:

A family can truly use it to complete a growth interaction.

Parent creates a goal, child completes the check-in, parent confirms, child gets a little red flower.

As long as this process holds true, the subsequent features have meaning.

Final Words

This project is still very early and has many imperfections.

But I will continue to polish it in one direction:

Not managing children,
but growing together with them.

If you are also working on independent products, mini-programs, family tools, or education-related projects, you should understand this feeling:

When real users first appear in the backend, even if the numbers are small, it's enough to make you take another step forward.

Mini-Program Experience:

Snipaste_2026-06-27_12-47-58.png