<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: fenghui2 yang</title>
    <description>The latest articles on DEV Community by fenghui2 yang (@fenghui2_yang_3635dfe77c9).</description>
    <link>https://dev.to/fenghui2_yang_3635dfe77c9</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4059204%2F377e5b84-15c4-4eb3-886d-550d7a38417a.png</url>
      <title>DEV Community: fenghui2 yang</title>
      <link>https://dev.to/fenghui2_yang_3635dfe77c9</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/fenghui2_yang_3635dfe77c9"/>
    <language>en</language>
    <item>
      <title>Building ShopMemo as a solo developer: giving AI a memory for ecommerce content</title>
      <dc:creator>fenghui2 yang</dc:creator>
      <pubDate>Sun, 02 Aug 2026 14:25:41 +0000</pubDate>
      <link>https://dev.to/fenghui2_yang_3635dfe77c9/building-shopmemo-as-a-solo-developer-giving-ai-a-memory-for-ecommerce-content-2a7</link>
      <guid>https://dev.to/fenghui2_yang_3635dfe77c9/building-shopmemo-as-a-solo-developer-giving-ai-a-memory-for-ecommerce-content-2a7</guid>
      <description>&lt;p&gt;I built ShopMemo because AI content tools kept forgetting the useful parts&lt;br&gt;
I have tried a lot of AI writing tools while working on ecommerce ideas. Most of them can produce product descriptions, social posts, ad copy and emails in seconds.&lt;br&gt;
That part already works. The part that kept bothering me was what happened after publishing.&lt;br&gt;
A seller would test a hook, adjust the angle, find a better way to describe the product, learn something from the numbers, then lose that learning inside a chat history, a spreadsheet, or their own head. A month later, the next content task started from an empty prompt again.&lt;br&gt;
That is why I started building ShopMemo.&lt;/p&gt;




&lt;p&gt;The problem I saw in ecommerce content workflows&lt;br&gt;
A simple ecommerce content workflow looks like this:&lt;br&gt;
Find a product&lt;br&gt;
    ↓&lt;br&gt;
Create content&lt;br&gt;
    ↓&lt;br&gt;
Publish&lt;br&gt;
    ↓&lt;br&gt;
Check performance&lt;br&gt;
    ↓&lt;br&gt;
Repeat&lt;br&gt;
Experienced sellers pick up a lot along the way. They learn which hooks get attention, which product angles convert, which tone fits their audience, and which formats are worth repeating.&lt;br&gt;
Most of that knowledge never becomes part of the next AI run. It stays scattered across notes, screenshots, analytics pages and half-remembered decisions.&lt;br&gt;
As a builder, this felt like the wrong place to stop. If AI can help create content, it should also help preserve the reasons a piece of content worked.&lt;/p&gt;




&lt;p&gt;Most AI content workflows start too clean&lt;br&gt;
The usual AI workflow looks like this:&lt;br&gt;
Product information&lt;br&gt;
        +&lt;br&gt;
Prompt&lt;br&gt;
        ↓&lt;br&gt;
Generated content&lt;br&gt;
That is fine for a first draft. It is weak for a real seller who has already run campaigns, talked to customers and learned from past posts.&lt;br&gt;
The AI usually does not know that last month a certain headline style worked better, that buyers in this niche respond to a specific angle, or that the brand should avoid a certain voice.&lt;br&gt;
So the seller keeps teaching the same lessons again. I wanted ShopMemo to reduce that repetition.&lt;/p&gt;




&lt;p&gt;The idea behind ShopMemo&lt;br&gt;
ShopMemo tries to save the strategy behind good content. The final text is only one artifact from the work.&lt;br&gt;
When a seller finds a post that worked, I do not want the tool to store it as “a good post” and move on. I want it to pull out the useful parts:&lt;br&gt;
Audience:&lt;br&gt;
Who was this written for?&lt;/p&gt;

&lt;p&gt;Hook:&lt;br&gt;
Why did someone stop scrolling?&lt;/p&gt;

&lt;p&gt;Angle:&lt;br&gt;
What made the product feel relevant?&lt;/p&gt;

&lt;p&gt;Structure:&lt;br&gt;
How was the message arranged?&lt;/p&gt;

&lt;p&gt;Brand voice:&lt;br&gt;
Why did it sound right for this store?&lt;/p&gt;

&lt;p&gt;Feedback:&lt;br&gt;
What happened after publishing?&lt;br&gt;
Once those pieces are saved, the next content draft can start with memory instead of guesswork.&lt;/p&gt;




&lt;p&gt;How I approached the first version&lt;br&gt;
I kept the first version small on purpose. I did not want to build a general AI assistant with a vague promise. I wanted one workflow that I could test with real ecommerce content.&lt;br&gt;
Analyze successful content&lt;/p&gt;

&lt;p&gt;↓&lt;/p&gt;

&lt;p&gt;Extract the strategy&lt;/p&gt;

&lt;p&gt;↓&lt;/p&gt;

&lt;p&gt;Save the pattern&lt;/p&gt;

&lt;p&gt;↓&lt;/p&gt;

&lt;p&gt;Generate new content using past experience&lt;/p&gt;

&lt;p&gt;↓&lt;/p&gt;

&lt;p&gt;Learn from feedback&lt;br&gt;
The feedback loop matters most. Good content usually comes from experiments: publish, observe, adjust, repeat. ShopMemo is my attempt to make those experiments easier to reuse.&lt;br&gt;
I am still early. Some parts are rough, and I am learning where memory helps and where it gets in the way. That is part of the reason I want to write about the build process in public.&lt;/p&gt;




&lt;p&gt;What I learned while building it&lt;br&gt;
AI makes production cheaper. That changes the value of experience.&lt;br&gt;
Before AI, a seller might ask: can I create enough content? Now the better question is: can I create content based on what my store has already learned?&lt;br&gt;
Anyone can ask a model to write another post. The advantage comes from the context around the post: customer feedback, past winners, failed angles, brand rules and small details from the business.&lt;br&gt;
That context is where a personal tool can beat a generic tool.&lt;/p&gt;




&lt;p&gt;The direction I am exploring&lt;br&gt;
I think more AI apps will move from “generate this for me” to “help me work with what I already know.”&lt;br&gt;
For ecommerce sellers, that means AI should remember the store, the audience, the past campaigns and the lessons from previous content. It should make the next draft feel less like a blank page.&lt;br&gt;
ShopMemo is my attempt to build in that direction. I am starting with ecommerce content because the feedback loop is clear: sellers publish, the market responds, and the tool can learn from that response.&lt;/p&gt;




&lt;p&gt;About ShopMemo&lt;br&gt;
ShopMemo is an early-stage project for ecommerce sellers who want to turn their own content experience into reusable AI memory.&lt;br&gt;
I am building it step by step and sharing what I learn along the way.&lt;/p&gt;

&lt;p&gt;Website: &lt;a href="https://shopmemo.app" rel="noopener noreferrer"&gt;https://shopmemo.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>buildinpublic</category>
      <category>saas</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
