About Satin
People shouldn’t have to relearn software. Software should fit the person using it.
Satin is pre-launch. OwnUX is an open specification, started by the Satin team in 2026.
Places to learn: 3
Same four jobs, a different place in every app. Each one has to be learned again. Illustrative apps.
Why Satin exists. Every app makes you relearn the same jobs. That should be the software’s problem.
01 · The problem
The same jobs, a different journey in every tool.
Find my task, change its status, set a date, see what’s blocked. Many people work in tools they didn’t choose, and products are designed for an average user, so beginners and experts share one crowded default.
02 · The bet
Your way of working should carry over.
We think people want their own way of working to come with them, not every app to look the same. OwnUX translates the interface for each person, while every app keeps its data, permissions and truth.
03 · What we must prove first
- 1People finish everyday tasks measurably faster in Satin, and keep using it every week.
- 2At least one product sees better activation with OwnUX than its holdout group does.
- 3One founder can keep the integrations with each app reliable.
Until these are shown, we claim no universal compatibility and call OwnUX a proposed technology, not an established standard.
Who feels it most
- Contractors and agencies in each client’s tracker
- Designers and PMs pulled into engineering tools
- People living through a tool change
- New joiners
- People whose accessibility needs default layouts serve poorly
The founder
Founded by Pranav Goswami, who edits the OwnUX specification.
OwnUX is an open specification, started by the Satin team in 2026. It builds on decades of research into adaptive and accessible interfaces, cited openly, and anyone can read it, implement it or help shape it.
- Text under CC BY 4.0, reference code under Apache 2.0
- The planned OwnUX Ready badge is reserved for products passing conformance
- Satin is building the first implementation of OwnUX
How to cite
OwnUX Specification · working draft v0.1
23 Oct 2026
“OwnUX Specification v0.1 (working draft). Satin, 2026.”
Text licensed CC BY 4.0. Quote it, share it, build on it.
The principles we build by. Nine rules that hold for people and for products. Hover over one for detail.
What’s happened, and what’s next.
An honest record. Each phase ends with a go or no-go checkpoint. We promise no dates before the results are in.
22 October 2026
DoneThe product is defined
The first product document sets the scope: a task-first experience layer for two supported apps. The same day, Satin becomes two-sided.
23 October 2026
DoneOwnUX gets its name
A naming check retires the earlier working names. OwnUX becomes the technology, with Jira Cloud and Linear as the first apps.
23 October 2026
DoneThe platform audit
We read the official documentation for Jira Cloud, Linear, Asana and the Chrome Web Store: sign-in, scopes, rate limits and admin controls.
23 October 2026
DoneThe company becomes Satin
The product and company take the name Satin, and usesatin.com is registered. OwnUX, the technology, keeps its name.
23 October 2026
DoneOwnUX Specification v0.1
The first public working draft: definition, architecture, Interface DNA, verified actions, data and security model, conformance levels. Proposals and comments are welcome.
Now
In progressBuilding both sides
The OwnUX SDK is an alpha in our Reference App; ownux test exists as v0. Satin for People is in development, Jira Cloud first.
Next
PlannedA second app, and portable DNA
For people: the Linear adapter, Familiar mode and DNA sync. For products: a design partner’s integration in staging, and DNA Share.
Then
PlannedThe closed beta
Twenty to thirty invited people on Jira Cloud and Linear, and a design partner in production with a holdout group.
If the gates pass
Planned, laterThe public beta
A Chrome Web Store listing, a developer portal, the first paid plans for products and specification v0.9.
Later
Planned, laterThe platform
Teams, the cross-app view and presets for people. A public SDK, L3 conformance and specification v1.0 for products.
How Satin is built
One founder, and an engineering agent. Satin is built with Claude Code, working spec-first.
Pranav sets the product direction. Claude Code, Satin’s engineering agent, works from the product document, writes acceptance tests before code, and records its decisions with reasons.
- Every change traces to a requirement and an acceptance test
- Safety cases are tested: wrong task, no permission, source down
- Money, legal, brand and direction calls stay with the founder
01 / 05
Requirement
Product document
Start from the specification
Every change begins with a requirement ID in the product document. If it isn’t written down, it isn’t built.