On 12 November 2026, a Show HN post passed 300 points on Hacker News. Its title says the poster’s $300 embroidery machine needed a subscription, so they built their own app. The project is called ZigZag, and it is on GitHub under the name simpsoka.
The repository describes ZigZag as free, open-source embroidery software for Mac and Windows, licensed Apache-2.0. It is built around the Brother Skitch (PP1) and sends designs to the machine over Bluetooth. It imports SVG artwork and converts it to stitches. It has a visual editor, text and lettering, image tracing for logos, and a stitch preview. It exports to five common embroidery file formats. The README says it was tested on a real PP1.
What the post claims, and what the repository shows
The excitement is easy to guess. One person got tired of paying for the software that runs their machine and made their own. If that is possible, every subscription utility is at risk.
I checked what the repository actually says. It does not name the subscription. It mentions Brother’s Artspira app only as software that must be closed while ZigZag talks to the Skitch. The subscription story comes from the post title. The README also doesn’t say how the software was built, so I won’t claim it was vibe coded.
The limits are listed plainly. Only the PP1 is tested. The machine protocol is reverse-engineered, and the page advises avoiding firmware updates. Writing machine settings is not supported. Gradient fills, cutwork, built-in fonts, monogramming and multi-hooping are all listed as “not yet.”
So this is a capable tool with clear gaps, built for one machine. That is fine. It was never meant to serve everyone.
Personal tools are where the shift is real
My view of vibe coding is narrow. It collapses the distance between an idea and working software. That is the only distance it collapses. Real-world testing, user feedback, marketing and getting customers are all still there.
Personal tools are the exception, because those steps barely matter. The builder is the only user. The tool handles the builder’s own data, on the builder’s own machine. If it breaks, one person is inconvenienced and fixes it that evening. A normal person can now build fairly competent software for their own use. I replace many tools and scripts with ones I build this way.
ZigZag fits that pattern. The owner knows exactly what they need from an embroidery app. They have a machine to test on every day. Nobody else’s data is at stake.
Consumer utility software will be hit hard
The same logic points at consumer utility software. These are single-purpose apps that sit between a person and their own files or device. Think converters, companion apps, trackers and format tools. Many charge a small monthly fee for something a motivated owner can now build. Not every customer will build their own. But the price they will tolerate drops once a free alternative exists and anyone can point to it.
If you sell a small utility to individuals, ask whether your product does anything beyond handling a user’s own data. If it doesn’t, expect the pressure to grow.
Why this doesn’t carry over to B2B
It would be wrong to read ZigZag as a sign that business software is next. A business tool handles other people’s data. It needs security review, access control and an answer for when something breaks at 9am on a Monday. Every build still needs back-and-forth on alignment, strategy, approach and security. AI can’t supply those without human context and experience, and you don’t get them from a single prompt.
There is also a part no code covers. Take a shop that takes payments and ships orders. Its software has to connect to local payment processors and logistics partners. Those are relationships and integrations that each market sets up separately. This is part of why I build AeroChat the way I do. You can’t vibe code your way into those relationships.
What a business should do
If you run a service business or a shop, check your own subscriptions first. List the ones that only handle your own files or your own data on one device. A design converter, a label tool, a file formatter. Those are candidates for replacing with something you or a staff member builds. Keep the build small and test it on real work before you cancel anything.
Leave the tools that touch customers, payments, stock or staff records alone. Those need a vendor who carries security and integrations, and who answers when something fails.
If you sell software, work out which side of that line your product sits on. If a user’s own data is all it touches, the price pressure is coming. If you hold the integrations and the responsibility, build on that.
Source: Hacker News: Show HN: My $300 embroidery machine needed a subscription, so I built my own app