Molecular modeling often involves more than building or examining a structure. You may need to connect a workflow to an external tool, use a web service, or bring existing code into your work. The challenge is not always a lack of tools; it is knowing where to look and which kind of SAMSON extension might fit.
In SAMSON, apps are one family of extensions that can add workflows to the platform. An app might connect to an external executable or web service, wrap existing code, or provide new functionality using the SAMSON Application Programming Interface (API). That range matters: an app is not limited to one kind of workflow or one way of being built.

AutoDock Vina Extended App is an example shown in the SAMSON apps reference.
Start with the task, not the extension name
When choosing what to explore, describe the task you want to accomplish in plain language. For example: Do you need a workflow that connects SAMSON to another program? Are you looking for a way to use an existing service or code within your molecular design process? Or are you trying to add functionality based on the SAMSON API?
These questions help you judge whether an app is a sensible place to start. They also give you a clearer way to search for a relevant extension than browsing a list without a specific need in mind. An app may support a complete workflow, or it may provide one part of a larger process; check the information for the particular extension before relying on it for a task.
Where to look in SAMSON
To find apps in the platform, go to Home > Apps. SAMSON provides some apps by default, and you can add more through SAMSON Connect. This gives you a simple starting point: first check what is available in your installation, then consult SAMSON Connect if you need to find or manage additional extensions.
If you are unsure whether an app is the right extension family, compare it with the other categories described in the documentation. Editors, Importers, and Exporters are separate extension families. The apps reference points to these pages as a way to compare categories; use the relevant page to learn about a specific family rather than assuming that all extensions serve the same purpose.
If the workflow you need is missing
Not finding a suitable app does not necessarily mean the workflow cannot be brought into SAMSON. Apps can be built around external executables, web services, existing code, or the SAMSON API. If you are considering creating one, the user-facing apps reference directs developers to the documentation on generating SAMSON Extensions and to the Documentation center.
For most users, a useful sequence is: identify the task, check Home > Apps, look on SAMSON Connect if needed, and compare extension families when the fit is unclear. For developers, the next step is to follow the extension-generation documentation. This keeps the search focused on the workflow you need, instead of on the assumption that every molecular modeling task requires the same kind of tool.
For the app overview and its related references, visit the SAMSON apps documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON at www.samson-connect.net.
