A customer would buy a tool, download a zip, then follow nit-picky instructions. “These two files go into the Plug-Ins folder, unless you’re on Windows, in which case it’s over here, and it’s four things, and if you have two InDesign versions, do it twice.”
Then Adobe would release a new version, the folders would change, and the support emails would start.
“Put the .jsx in the Scripts Panel folder” sounds simple until you try to explain where that folder is.
I am sure I lost a fair number of potential sales to the friction of just getting these things installed.
What it is
PluginInstaller is a free app for Mac and Windows. You open it, see a list of tools, pick one, and click an install button. Done.
It works out which Adobe apps and versions you have and puts each piece where it belongs. Updating and removing are one click too.
It doesn’t care how a tool was cooked up. Old-style ExtendScript, CEP panels, UXP plug-ins and C++ plug-ins all install the same way. That matters, because a lot of good, working automation is still plain ExtendScript, and there isn’t a decent place to get it from.
Along the way I made a few conscious decisions, which should explain some of the seemingly odd details about PluginInstaller:
– No account to install. Free tools and trials just install. You only need to register when you buy something.
– No subscriptions. A paid licence runs for a year and then stops. Nothing renews itself and nothing charges your card again. When you need the tool again, even years later, you buy new. No yearly upkeep.
– Prices up front. Every paid tool shows its yearly price on its card.
– No tracking.
– Signed packages. Every package is code-signed and optionally encrypted, so you can verify who made it and that it wasn’t changed along the way.
Signing protects the customer (be reassured the code comes from a trusted source).
Encryption protects the developer (be reassured the code is not easy to inspect or copy).
Why it took five years
PluginInstaller sits on top of Tightener, a framework I’ve been building since 2021 to automate work around various apps, including Adobe® Creative Cloud® apps. To install an add-on properly I used many of the features built into Tightener: licensing, code encryption and signing, inter-app communication, machine GUIDs, user GUIDs, developer GUIDs, public/private key management, a product and developer registry that deliberately keeps no personally identifiable data about customers and developers…
On top of that came a lot of testing on Macs and PCs with different setups. 1.0 is the first release where all of it fits together.
What’s in it now
To start with: 25 tools, most of them free, mostly for InDesign, plus a free Scripts panel for Illustrator, Photoshop and other Adobe apps that don’t have a usable one. And more tools on the way…
Go and have a look at these:
SmartRelink PL: finds missing images and relinks only what you approve.
TextStitch: threads Data Merge output into one story.
Scripts Panel NT: a real Scripts panel for Photoshop.
You can download PluginInstaller here:
A 90-second walkthrough video: https://tur.nz/4m
For developers
If you write scripts or plug-ins for Adobe apps, PluginInstaller can deliver them for you as a signed, one-click install. I will gradually be opening this up to other developers in 2027, step by step, starting with free and donationware tools. If you’ve got something you’d like to distribute, tell me what it is. More details will follow soon.
For companies
Rorohiko’s main business is custom work: plug-ins and automation of Adobe® Creative Cloud® apps for publishers, printers, catalogue teams… If there’s a step in your workflow that eats hours every week, I’d like to hear about it.
Also, long term I have far-reaching goals for PluginInstaller. Does your IT team hand out its own scripts and templates? PluginInstaller can be customized to deliver those too, from a catalog on your own server. If that sounds useful, get in touch.
Kris Coppieters –