Now let's place Apps in the bigger picture. Apps don't work in isolation. They sit alongside several other parts of Tines, and understanding how they relate will help the whole platform make more sense.
Apps live in the top navigation bar in Tines. From the Apps section, you can see a list of any Apps you've already created, or start a new one.
UI location to access the Apps tab.
From there, an App connects to the rest of Tines in a few key ways:
Stories. Stories are the workflows that do the actual work in Tines: moving data, making decisions, and taking action across your tools. An App connects to one or more stories through endpoints, so the stories do the work while the App gives people a way to interact with it.
Workbench. Workbench is the Tines AI assistant, and it's what powers the App builder. You describe what you want in natural language, and Workbench generates the React application for you, and can even create the endpoints that connect your App to your stories.
Pages. Pages let you expose simple web pages connected to your stories, often used to collect input through forms or build requester and approver flows. Apps take the idea of a workflow front end further: rather than assembling page elements, you describe what you want and get a fully customizable React application, with complete control over the interface, styling, and code.
Cases. Cases are where teams track and manage work in Tines. You can add an App directly to a case through a case action, and the App can automatically pick up the case it's opened from, giving people a tailored, interactive view right inside the case.
Collections. Apps can be added to Collections, which bring multiple Apps together into a single, organized view for your team. It's a handy way to group related Apps so people can find them in one place.
This is what makes Apps so useful. A single App can pull together data and actions from across your tenant into one coherent experience. For example, a finance team could build an App that surfaces invoice data from one story, vendor details from another, and an approval action from a third, all in a single, tidy interface.