Multi-platform design management and deployment
Abstract
A design management and distribution system can include a design system configured to generate an update to a UI design comprising components, variables, and variants. A design pipeline can be configured to tokenize the components, variables, and variants of the UI design to generate tokenized code stored in a structured data format in a design repository. The system can include an application pipeline configured to translate the tokenized code into a first platform-specific package compatible with a first client device and into a second platform-specific package compatible with a second client device. The first platform-specific package and the second platform-specific package implement the UI design. A first application repository may receive the first platform-specific package from the application pipeline for distribution to the first client device, and a second application repository may receive the second platform-specific package from the application pipeline for distribution to the second client device.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . An automated process, comprising:
detecting, by a design pipeline, a new version of a user interface (UI) design generated by a design system, the new version of the UI design comprising components, variables, and variants; tokenizing, by the design pipeline, the components, variables, and variants of the UI design to generate tokenized code stored in a structured data format in a design repository; translating the tokenized code into a first platform-specific package and a second platform-specific package, wherein the first platform-specific package implements the new version of the UI on a first platform, wherein the second platform-specific package implements the new version of the UI on a second platform; distributing the first platform-specific package to a first client device of the first platform; and distributing the second platform-specific package to a second client device of the second platform.
2 . The automated process of claim 1 , wherein the translating the tokenized code further comprises applying a first script to parse the tokenized code and generate the first platform-specific package, and applying a second script to parse the tokenized code and generate the second platform-specific package.
3 . The automated process of claim 1 , wherein the tokenized code comprises a primitive token, a semantic token, a component token, and an experience token.
4 . The automated process of claim 3 , wherein the tokenized code comprises a motion token that defines an easing curve for motion in the new version of the UI.
5 . The automated process of claim 1 , wherein the new version of the user interface comprises a first native theme and a second native theme.
6 . The automated process of claim 5 , further comprising:
applying, by the first client device, the first native theme in the first platform-specific package to render a first UI of the UI design with a first branding; and applying, by the first client device, the second native theme in the first platform-specific package to render a second UI of the UI design with a second branding.
7 . The automated process of claim 1 , wherein the translating further comprises:
making, by the design pipeline, an application programming interface (API) call to retrieve data related to the components, variables, and variants; and encoding the data related to the components, variables, and variants into the structured data format.
8 . A design management and distribution system, comprising:
a design system configured to generate an update to a user interface (UI) design comprising components, variables, and variants; a design pipeline configured to tokenize the components, variables, and variants of the UI design to generate tokenized code stored in a structured data format in a design repository; an application pipeline configured to translate the tokenized code into a first platform-specific package compatible with a first client device and into a second platform-specific package compatible with a second client device, wherein the first platform-specific package and the second platform-specific package implement the UI design; a first application repository that receives the first platform-specific package from the application pipeline for distribution to the first client device; and a second application repository that receives the second platform-specific package from the application pipeline for distribution to the second client device.
9 . The design management and distribution system of claim 8 , wherein the first platform-specific package is incompatible with the second client device.
10 . The design management and distribution system of claim 8 , further comprising a package registry configured to publish the tokenized code to the application pipeline.
11 . The design management and distribution system of claim 8 , wherein the application pipeline translating the tokenized code includes:
applying a first script to parse the tokenized code and generate the first platform-specific package; and applying a second script to parse the tokenized code and generate the second platform-specific package.
12 . The design management and distribution system of claim 8 , wherein the tokenized code comprises an experience token that implements an accessibility mode.
13 . The design management and distribution system of claim 8 , wherein the tokenized code comprises a motion token that defines an easing curve for motion in the first platform-specific package and in the second platform-specific package.
14 . The design management and distribution system of claim 8 , wherein the first client device is configured to apply a first native theme in the first platform-specific package to render a first UI of the UI design with a first branding, and wherein the first client device is configured to apply a second native theme in the first platform-specific package to render a second UI of the UI design with a second branding.
15 . The design management and distribution system of claim 8 , wherein:
the design pipeline is configured to make an application programming interface (API) call to retrieve data related to the components, variables, and variants; and wherein the design pipeline is configured to encode the data related to the components, variables, and variants into the structured data format.
16 . A process, comprising:
generating a new version of a user interface (UI) design comprising components, variables, and variants; tokenizing the components, variables, and variants of the UI design to generate tokenized code; translating the tokenized code into a first platform-specific package and a second platform-specific package that implement the new version of the UI; distributing the first platform-specific package on a first platform; and distributing the second platform-specific package on a second platform incompatible with the first platform-specific package.
17 . The process of claim 16 , wherein the translating the tokenized code further comprises:
applying a first script to parse the tokenized code and generate the first platform-specific package; and applying a second script to parse the tokenized code and generate the second platform-specific package.
18 . The process of claim 16 , wherein the tokenized code comprises a motion token that defines an easing curve for motion in the new version of the UI.
19 . The process of claim 16 , further comprising:
applying, by a first client device of the first platform, a first native theme in the first platform-specific package to render a first UI of the UI design with a first branding; and applying, by the first client device of the first platform, a second native theme in the first platform-specific package to render a second UI of the UI design with a second branding.
20 . The process of claim 19 , wherein translating the tokenized code further comprises:
calling an application programming interface (API) to retrieve data related to the components, variables, and variants; and encoding the data related to the components, variables, and variants into a structured data format.Join the waitlist — get patent alerts
Track US2026079681A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.