A molecular modeling task rarely stays inside one tool. You may need to prepare a structure, run an existing program, connect to a web service, or bring a specialized capability into your working environment. The challenge is not only finding a tool—it is figuring out where it fits, how to access it, and whether you need an app or another kind of extension.
SAMSON apps are one way to add workflows to the platform. An app might connect SAMSON to an external executable or web service, wrap existing code, or provide functionality built with the SAMSON Application Programming Interface (API). In practical terms, apps can help bring different kinds of computational work into the same molecular design environment.
Start with the task, not the app name
Before browsing for an app, describe the step that is slowing you down. Are you trying to use an external program from within your workflow? Do you need a connection to a web service? Are you looking for a particular capability that could be provided by code built on the SAMSON API? These questions help you search with a purpose instead of browsing a list without knowing what to look for.
It is also useful to identify what goes into the step and what you need out of it. For example, note the kind of input your workflow has, what result you are hoping to obtain, and whether the step depends on an existing executable, a service, or custom functionality. This is a way to clarify your requirements—not a guarantee that a particular app supports a specific file, operation, or integration. Check the app’s own information before relying on it for a project.
Find apps in SAMSON
Apps are available from Home > Apps. SAMSON provides a set of apps by default, and additional apps can be added from SAMSON Connect. SAMSON Connect is also the place to manage Marketplace access and installed extensions.
When evaluating an app, use your workflow requirements as a checklist. Does its stated purpose match the step you need to perform? Does it connect to an external program or service, or provide a capability within SAMSON? Is it the right extension family for the job? Confirm details from the app’s documentation or description rather than assuming that every app handles the same inputs or produces the same outputs.
Know when to look beyond apps
Apps are part of the broader SAMSON Extensions ecosystem, but they are not the only extension family. If your main need is to work with a particular data format, the documentation also has dedicated references for Importers and Exporters. For interactive tools within the platform, see Editors.
This distinction can save time. If you are trying to add a workflow or connect functionality, start with apps. If your problem is specifically bringing data into SAMSON or sending it out, check the importer and exporter references too. The right category depends on the task you need to solve.
Building a capability instead of finding one
If you cannot find an app that meets your needs, the documentation points developers toward the SAMSON Extension Generator and the Documentation center. That is a useful next step when you want to explore creating an extension rather than adapting your workflow around an existing one.
A simple habit makes app discovery more effective: define the workflow gap, identify the kind of integration you need, check the relevant extension family, and then review available apps in SAMSON or SAMSON Connect. That keeps the search tied to a real modeling task—and makes it easier to decide whether an existing app, another extension type, or development is the appropriate path.
For the full reference, visit the SAMSON Apps documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.