External third-party products are managed through the existing product proxies architecture in FxFactory. The
FxProxy project format has been extended to recognize external applications.
Developers are not responsible for the set-up and configuration of proxies. We build and provide a proxy for your product to help in testing all functionality before the product is distributed to the public. That same proxy, with further modifications, is then pushed to end-users through our servers when your product goes live.
Proxies are the means by which FxFactory displays basic information about products that are not installed on the system. Proxies also specify product requirements and instruct our application on how to download or upgrade the product.
Every product in FxFactory is assigned a unique ID. This UUID survives name-changes, upgrades, etc. and gets changed only when a new version of the product must be treated as a different entity by FxFactory’s ecosystem (application, runtime and online store). In most cases the UUID never changes through the lifetime of a product.
If you maintain multiple products through a single codebase, UUIDs make it easy to interact with FxFactory through a single entry point. As long as you use the correct UUID for the specific product you happen to be building, the code that check licensing status can be easily shared among all your products.
Once a proxy linked to your product via UUID is available to FxFactory, some basic changes need to be made to your code:
All of the above functionality is available through the simple APIs exposed by the FxFactory Framework.