Milestone 01 / care = love
Returning to the reason I wanted to build it.
August 17–October 5, 2026: from Inventory and Mirror to a clearer place for my products, routines, and personal memory.
What I wanted to keep
I wanted one place to keep my skincare, haircare, and body care products. What do I currently own? What have I bought? What did I actually think of it? And when I’m considering buying something again, which products did I try and love?
I’m the user and the only user tester at this stage. That matters. The app needs to be useful in my own life before I can make claims about anyone else’s experience.
The first foundation
The earliest repository baseline, from August 17, was called Inventory + Mirror. Inventory held products and personal impressions. Mirror held observations and explicit connections to products. A personal observation wasn’t a diagnosis, and linking a product to a moment didn’t establish that it caused anything.
The native prototype kept records locally, with cloud synchronisation disabled. Its first boundaries excluded photos, automated analysis, routines, commerce, and gamification. Those were limits of that version, rather than a permanent definition of the app.
Giving the collection its own world
Inventory and Mirror became Pouch and Pond. Botanical shapes, jelly-like materials, mesh, resin, and water gave the collection a visual world. Practical capture also developed: photos, on-device text and barcode recognition, manual search, and reviewable public catalog matches. Sourced product information and my own experience needed to remain distinct.
By September, the native design notes described cream paper, olive ink, restrained ochre, and fine grain. Home offered a quick note, products in rotation, and the latest observation. A separate private web companion explored similar records, but used its own store. The retained build and deployment notes are historical records, not a check of its current hosted state.
Looking at Home again
On October 4, I looked at the actual Home screen. “How’s your skin feeling?” and “Add a note” made observation the main activity. Morning and night routines weren’t visible. The rotation card said “3 products,” showed two faint placeholders, and named one mask. It took up a lot of space without making the collection easy to understand.
The skin-focused wording also left hair and body care out of the picture. This was my design review, not evidence that other users had struggled. It was enough to make me restate the purpose: an inventory and purchase memory I could consult through my own experience.
Putting the collection and rotation first
The starting point should be what I’m actually using, including morning and night routines. A shared routine needs to be possible too. The complete collection still matters, including occasional products and the things I’ve set aside or finished.
My notes can be small. Tags, quick comments, and reviews should accumulate around the product. Buying another bottle shouldn’t create a disconnected review. The October 5 source review recorded progress on routine assignments, collection filters, personal reviews, repurchase intent, and repeat-purchase records. It did not establish that all of those flows had been visually tested.
The follow-up screens
The follow-up screenshots supplied after the written log make the newer direction visible. Greenhouse shows morning and night rotation with skincare, hair care, and body care categories. Basket shows recognisable product photos, search, and filters for In rotation, Loved, and Buy again. Pond keeps the care profile and journal, while Meadow holds reading.
The light and dark screenshots document this iteration. They also introduce Basket, Greenhouse, and Meadow where earlier work used Home, Pouch, and Garden. They show the interface as captured; they don’t settle every naming decision or prove that the complete experience works in daily use.
What remains open
Personalised product suggestions remain a larger piece of work. A reading library and a budget estimate alone don’t make a recommendation system. Product and price sources, personal context, and the uncertainty behind a suggestion still need careful treatment.
The next meaningful review is practical: can I find what I’m using, add a purchase without duplicating a product, leave a quick thought, and later retrieve what I loved? The October review brought me back to the reason I wanted to build the app—and gave the next version a more concrete job to do.
care = love is being developed with AI-assisted coding. This log draws on the August–October development record and the supplied before-and-after screenshots. Historical implementation and test details are attributed to that record; the follow-up images add visual evidence, not broader user validation.