A molecular modeling task rarely fits neatly into one tool. You may need to connect an external program, use a web service, or bring existing code into your working environment. The challenge is not only finding a tool—it is knowing where it fits and how to find it without confusing it with other kinds of extensions.
In SAMSON, apps are one extension family designed to add workflows. An app may connect to an external executable or web service, wrap existing code, or provide functionality built with the SAMSON Application Programming Interface (API). That makes “app” a useful category to check when you want to extend what you can do in SAMSON, rather than simply import or export a file.
Start with the task, not the extension name
Before looking through available apps, describe the missing step in your workflow. For example:
- Does the step depend on another program? Look for an app that may connect SAMSON with an external executable.
- Does it rely on an online service? Apps can provide connections to web services.
- Do you need to reuse existing code? An app may wrap code so it can contribute a workflow in SAMSON.
- Are you looking for new platform-specific functionality? Apps can also be built using the SAMSON API.
These possibilities describe what apps can do as a family; they are not a guarantee that a particular app supports a particular program or task. Check the details of an individual extension before relying on it in a project.
Where to look
Apps are available in SAMSON under Home > Apps. SAMSON includes a set of apps by default, and more can be added from SAMSON Connect. If you are trying to understand available extensions or manage what is installed, the Extending SAMSON guide is the relevant companion reference.
The example above shows an app from the SAMSON ecosystem. Treat examples as a starting point for exploration: the right choice depends on the workflow you need, not simply on an app’s name or category.
Apps are not the only extension family
A common source of confusion is treating every extension as an app. If your immediate need is to bring a structure or other data into SAMSON, consult the Importers reference. If you need to produce files for use elsewhere, look at Exporters. For tools that support working with content inside the platform, the Editors reference may be more relevant.
A practical way to narrow the search is to ask: “Am I trying to add a workflow, bring data in, send data out, or work with data in SAMSON?” Apps are a sensible place to start for the first case; the other extension families may fit the others better. This small distinction can save time when you are browsing a growing collection of tools.
If you want to build an app
If the workflow you need is not available, SAMSON’s documentation points developers toward the SAMSON Extension Generator and the Documentation center. The key takeaway is that apps belong to the broader SAMSON Extensions ecosystem: learning how extensions are developed and managed is the next step beyond browsing existing apps.
To explore the app category and its related references, see the SAMSON Apps documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.