A molecular modeling task rarely stays in one lane. You may need to connect a tool, reuse existing code, or add a capability to your working environment—and it is not always obvious where to look first. In SAMSON, apps are one way to add workflows. Knowing what they are, where to find them, and how they differ from other extension types can make it easier to choose a sensible next step.
What an app can do
A SAMSON app can add a workflow to the platform. Depending on the app, that may mean connecting SAMSON to an external executable or web service, wrapping existing code, or providing functionality built with the SAMSON Application Programming Interface (API). These are different ways of bringing a task into your molecular design environment; the documentation does not imply that every app does all of them.
This is useful when you have a specific workflow in mind but are unsure whether you need to build something from scratch. First, check whether an existing app already provides a relevant connection or wraps functionality you want to use. If it does, you may be able to work with that app rather than starting with development. If not, the developer documentation is the place to explore how to generate an extension.
Where to look in SAMSON
To browse apps available in your environment, go to Home > Apps. SAMSON includes a set of apps by default, and you can add more from SAMSON Connect. This gives you a practical first check: look at the apps already available, then use Connect to explore and manage extension access when you need more.
When evaluating an app, start with the job you need done. Are you trying to connect to another tool or service? Reuse existing code? Add functionality based on the SAMSON API? Those questions help you search with a clear purpose instead of browsing a list without knowing what would fit.
App or another extension?
Apps are part of the wider SAMSON Extensions ecosystem, but they are not the only extension family. The documentation also lists Editors, Importers, and Exporters. If your need is specifically about bringing data into SAMSON, taking data out, or working through an editor, those reference pages may be a better starting point than the apps page.
A simple way to choose is to describe the outcome, not the software you think you need: “I want to add a workflow,” “I need to import a file,” or “I need to export data.” Then use the matching extension reference to investigate. If you are unsure, begin with Extending SAMSON, which covers adding, removing, and developing extensions.
When you want to build an app
If browsing existing apps does not solve the problem, SAMSON provides a development path. The documentation points to generating SAMSON Extensions and the Documentation center for those getting started with extension development. This keeps the decision grounded: first identify the workflow, then check available extensions, and only then move toward building what is missing.
For an overview of SAMSON apps and related references, learn more in the Apps documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON at samson-connect.net.