Cross-app view. All your tasks in one list. Planned for later.
Planned for later · Needs a second supported app first
acme.atlassian.net
Studio workspace
Illustrative. Cross-app view is planned for later, once Linear is supported.
One model, many apps
The same task, whatever app it lives in.
Satin maps every supported app onto one shared set of tasks and actions, so a Jira issue and a Linear issue due today sit in the same Today.
- Five core tasks, each mapped to every app’s official API
- Grouping uses the shared model, not one app’s quirks
- Each change is made and checked in the task’s app
Satin capability
task.list_assigned
The bindings Satin uses, from its platform audit. The Linear adapter is planned for a later phase.
Where it is today. Planned for later. It needs a second supported app first; Linear is next.
- 1
- 2
- 3
- 4
No dates yet. Everything after step one is a plan, not a promise.
Built on the same rules. It changes what you see, not who owns your work or where it’s kept.
In place stays the core. Satin meets you inside the tool you’re sent to. Cross-app view is an addition.
Every task keeps its source. A chip names the app it lives in, and one click opens it there.
Changes go home. Changes use the app’s official API and are read back before Satin says it’s done.
Combined on your device. Tasks are combined in your browser and never reach Satin’s servers.
One set of shortcuts. The same keys and the same steps, whichever app a task came from.
Each app’s rules apply. Each app still decides what you can see and change. Satin never carries access between apps.
Part of Pro, when it arrives. Free keeps two supported apps, each in place. Pro adds the view across them.
PlannedCross-app view is planned for later. Prices are planned launch prices, subject to change.
Questions about cross-app view.
It’s planned for later, after Linear support, because it needs two supported apps to combine. We’ll share timing when we’re confident in it.