When a software company stops developing an application, the usual advice is to move on. That sounds simpler when the application contains none of your work.
For a long-term user, moving on can mean learning a different editing model, converting an archive, repairing typography, and replacing an environment that has become part of professional practice.
FreeHand’s users made those costs unusually visible. Some organized around an effort to preserve the product’s future. The resulting Free FreeHand campaign eventually reached federal court.
From product disappointment to collective action
The wider FreeHand history explains Adobe’s acquisition of Macromedia and the 2007 announcement ending further development. The campaign belongs to the next stage: users trying to affect what would happen to the application and their work.
A contemporary Libre Arts account traces the organization, its attempts to engage Adobe, and the move toward litigation. It also describes the subsequent search for another development path.
The campaign’s existence does not mean all former users shared its approach. It does show that dissatisfaction extended beyond casual nostalgia. People were willing to organize around an application whose development had already stopped.
What the lawsuit alleged
Free FreeHand and an individual plaintiff brought claims against Adobe concerning its acquisition and treatment of the application. Their allegations connected the loss of a competitor with the market for professional illustration software.
The essential distinction is between an allegation and a finding. A complaint records the plaintiffs’ case. It does not, by itself, prove that the defendant violated the law.
The February 10, 2012 order provides a primary account of the claims and Adobe’s motion to dismiss. It is a better source for the procedural position than a headline saying users had already won or lost the entire argument.
What the court decided at that stage
Judge Lucy Koh granted Adobe’s motion as to the Cartwright Act claim with leave to amend and denied it as to the other claims. That allowed most of the case to proceed past the motion-to-dismiss stage.
It was not a final determination that the allegations were true. Allowing a claim to proceed and deciding liability after a full adjudication are different events.
That distinction also prevents the case from being used as a shortcut in the FTC history. The earlier merger proceedings and this later private lawsuit are separate records.
The resolution did not release FreeHand’s source
The August 2012 Libre Arts report says the litigation was resolved and dismissed without release of FreeHand’s source code. It reports discounts for participating users and discussion of Illustrator improvements, while noting that the exact resolution could not then be publicly stated.
Those reported details should not be expanded into a complete public settlement contract. The meaningful product outcome for this story is narrower: the campaign did not produce a newly open FreeHand codebase for independent continuation.
That left a different question. If the original application could not be revived through access to its source, could another application recover enough of its experience?
A successor still needed a viable project
The community’s search led toward Stagestack, previously called Expressive. A later developer interview published by Libre Arts in January 2013 reported funding difficulties and discussion of releasing source code.
That history should not be used to claim that a finished open-source FreeHand successor was delivered. Discussing a release is not the same as completing one.
It does expose a recurring problem for revival projects. Strong enthusiasm can establish that people care. It cannot, on its own, finish an importer, maintain text layout, support operating systems, or finance years of development.
What a new revival should learn
The useful lesson is to make the path from affection to dependable work explicit.
A prospective user needs to know which jobs the new application can complete, which documents it can safely preserve, what is still experimental, and what happens to their work if development slows.
A mailing list can help identify the audience and gather experience. It should not be presented as evidence that those engineering questions have been solved. A prototype can demonstrate intent. It should not be described as a production replacement merely because it looks familiar.
For Backhand, that means showing real implemented workflows and stating their boundaries. It also means paying attention to the quiet requirements: saving, recovering, exporting, and explaining limitations before they become a user’s surprise.
The campaign belongs in software history because it reveals how deeply a tool can become part of somebody’s working life. The best tribute is not another promise that a beloved program will return unchanged. It is a clear account of what a useful revival actually requires.
