Build utility plugins for the Compositor Mac app
Develop small Swift plugins that add missing features to the new Compositor image editor for Mac.
Open NuviFlux for the evidence, open questions, and first test.
THE OPPORTUNITY, IN CONTEXT
Explore file-based utilities for Compositor
The business model
Preparing images and composition files can take time away from creative work. A utility for Compositor could automate a repeated preparation task and produce files the editor can read, using its documented file interface.
What has been observed
Compositor's writing guide explicitly describes an external file interface, with no plugin or API involved. Scripts can write .comp packages containing images and a manifest for live reload. The documented opportunity is therefore a file-writing utility, rather than a confirmed native plugin system.
Entry conditions and costs
Costs include a compatible Mac, development time and testing against the target app version. Naming, write order and unsaved changes affect the integration. Protect existing projects and account for the work needed to maintain compatibility.
The key question
Does the utility remove enough repetitive work to justify its price and upkeep?
Common questions
Is there a documented native plugin API?
The reviewed guide describes file-based integration and explicitly says no plugin or API is involved.
What could a useful utility deliver?
A correctly structured composition package for one repeatable asset-preparation task.
A CLOSER LOOK
From image assets to a composition package
Compositor can read composition packages written by external scripts. Developers could sell a utility that handles a repeated asset-preparation task through that file interface.
