Glitchy, but real
A developer frustrated with Adobe rebuilt seven of its applications, then started on Office. Testers found the results immature. They also found them far more functional than they had any right to be.
A developer became frustrated with Adobe — and responded by rebuilding it. Brandon Thomas, the Atlanta-based founder of ArtCraft, says he “got bit by the dark pattern ‘cancellation fee’ one too many times.”
Not literally, and certainly not completely. But in under three days from first commit to release, ArtCraft published seven free, open-source applications modelled on Photoshop, Illustrator, Premiere Pro, Lightroom, Acrobat, After Effects and InDesign. Then it began doing the same to Microsoft Office, and then to AutoCAD and Pro Tools.
PhotoCraft, the Photoshop-style flagship, was created on 30 September. By 10 October it had accumulated more than 39,000 GitHub stars and 5,700 forks, along with 1,393 pull requests and 1,190 issues — an extraordinary response for software that its own maintainers describe as early alpha, and “not yet a Photoshop replacement for daily professional work.”
Gizmodo reports that Thomas built the suite with Claude Opus 5.5, in Rust; he told Hacker News, “We’re using vanilla Claude Code for ArtCraft apps.” The README calls the work clean-room: “implemented from public specs and observed behaviour only. No proprietary code, shaders or assets.” That is ArtCraft’s description of its own method, not an independent legal judgement.
Twelve reimplementations, four vendors, ten days
GitHub stars for every ArtCraft application published between 30 September and 10 October, with the product each is modelled on and the day its repository was created. Snapshot taken 10 Oct 2026, 15:32 UTC.
Independent testers did not find fully formed Adobe replacements. They found something more provocative: software that was visibly immature, yet far more functional than it had any right to be.
Gizmodo’s Mike Pearl, who uses Photoshop “twice a year”, found that lasso, feather, paste, transform, levels and colour “were all where I expected them to be”. In his words, “it feels like using glitchy, but real, Photoshop.” Free Transform, though, was “an unpredictable mixed bag”.
The maintainers are blunter still. The README lists the biggest gaps as AI and generative features, about twenty missing tools, depth in typography and professional workflows, and plug-in compatibility. Every Photoshop menu item is wired to a command, “but that measures wiring, not behaviour.” The roadmap’s own assessment puts real parity “still well below 50%”, and scores whether “a professional could switch for daily work” at roughly 25–35%.
This is not evidence that Adobe has been replaced.
It is evidence that the distance between absurd idea and credible prototype has collapsed.
The story expanded almost immediately. ArtCraft also published WordCraft, GridCraft and DeckCraft: early attempts to recreate Word, Excel and PowerPoint. Paul Thurrott notes that they “aren’t as far along as the Adobe-inspired apps.”
The FUTC channel tested all three rather than relying on screenshots:
WordCraft
Looked convincingly familiar, but struggled with basic formatting and image layout.
GridCraft
Recalculated its charts automatically and, through its built-in MCP server, took instructions from Claude to add a sheet and a chart. Several controls were buggy.
DeckCraft
Created and edited slides through both the interface and Claude, but lagged throughout and crashed once on Present.
The reviewer’s advice for real work was mature LibreOffice, which “is going to get you a lot farther than downloading some vibecoded app that’s only a few days old.” He still called it “a pretty cool project”, and was impressed by how quickly the applications had become recognisable and agent-operable. A YouTube demonstration is a practical observation, not a technical audit — but it is a better test than a screenshot.
That is the right balance: do not confuse breadth with readiness — but do not confuse immaturity with irrelevance.
Adobe declined to comment to The Register; Microsoft acknowledged the inquiry and offered no further response. As of 10 October every repository is still live, and no takedown notice appears in GitHub’s public DMCA log.
The legal position is unsettled rather than hopeless. Andres Guadamuz, writing on TechnoLlama, concludes “very tentatively that ArtCraft may be on the right side of the law in the US”; the exposure he sees is in licence terms, patents and trademarks. Ars Technica adds trade dress — an interface that mimics Adobe’s too closely. And the lawyer Neil Brown told The Register it could still be “litigated, when the party most likely to feel aggrieved has deep pockets.”
If software functionality becomes easier to reproduce, every organisation should ask what it is actually paying for.
| Previous assumption | Generative question |
|---|---|
| Complex software is inherently scarce | Which parts are now inexpensive to regenerate? |
| The application is the product | Is the application merely an interface over deeper capabilities? |
| Feature breadth creates defensibility | Which features cannot be recreated from observable behaviour? |
| Users operate software | Will agents become its primary operators? |
| Interfaces remain stable for years | Could interfaces be generated for each role, task or moment? |
| Buying software transfers capability | Is the organisation really buying trust, support and accountability? |
| Application portfolios are permanent assets | How much of the portfolio records what was historically too expensive to rebuild? |
This is not simply another build-versus-buy decision. It introduces a third option.
- If an application’s features can be reproduced, what is the customer really paying for?
- What percentage of today’s application estate exists because replacement used to be too expensive?