Application builder with automated data objects creation
US-2017115968-A1 · Apr 27, 2017 · US
US10901707B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10901707-B2 |
| Application number | US-201816138094-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 21, 2018 |
| Priority date | Sep 21, 2018 |
| Publication date | Jan 26, 2021 |
| Grant date | Jan 26, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An application builder system includes an application builder server and a client-side application builder. The application builder server may receive, from a tenant user device, a request to store a data structure corresponding to a container component. The application builder server may identify one or more attributes of the data structure corresponding to a declarative use feature of the server. The application builder server may determine whether the data structure satisfies the declarative use feature of the server based on the attributes. The application builder server may expose the container component on the user interface based on the declarative use feature of the server. As such, a developer may upload a custom container component for use in an application builder application. Other users may download the custom container components and use the custom container component on the application builder application.
Opening claim text (preview).
What is claimed is: 1. A method for editing components of a user interface, comprising: receiving, at a server and from a tenant user device, a request to store a data structure corresponding to a container component; identifying one or more attributes of the data structure corresponding to a declarative use feature of the server; determining the data structure satisfies the declarative use feature of the server based at least in part on the one or more attributes; and exposing the container component on the user interface using the declarative use feature of the server. 2. The method of claim 1 , further comprising: identifying a droppable region of the container component based at least in part on the one or more attributes of the data structure. 3. The method of claim 1 , further comprising: receiving, from the tenant user device, a package of components comprising the data structure corresponding to the container component. 4. The method of claim 1 , further comprising: restricting a type of component from being contained by the container component based at least in part on the one or more attributes. 5. The method of claim 1 , further comprising: receiving, at the server and from the tenant user device, a second request to store a second data structure corresponding to a non-container component; and exposing the non-container component on the user interface using the declarative use feature of the server, wherein the non-container component is contained by the container component. 6. The method of claim 1 , further comprising: identifying a set of default components contained by the container component, wherein the set of default components is exposed on the user interface within the container component. 7. The method of claim 1 , wherein the container component comprises a third-party-developed container component configured for the declarative use feature of the server. 8. The method of claim 1 , wherein a component array attribute of the one or more attributes of the data structure indicates the container component is configured to contain other components. 9. The method of claim 1 , wherein the declarative use feature of the server comprises a drag and drop feature, and the container component is configured for the drag and drop feature. 10. The method of claim 1 , wherein the user interface is for a web development platform. 11. The method of claim 1 , wherein the container component contains one or more non-container components. 12. The method of claim 1 , wherein the container component comprises one or more features modifiable by an administrator of the tenant user device based at least in part on the declarative use feature of the server. 13. An apparatus for editing components of a user interface, comprising: a processor, memory in electronic communication with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receive, at a server and from a tenant user device, a request to store a data structure corresponding to a container component; identify one or more attributes of the data structure corresponding to a declarative use feature of the server; determine the data structure satisfies the declarative use feature of the server based at least in part on the one or more attributes; and expose the container component on the user interface using the declarative use feature of the server. 14. The apparatus of claim 13 , wherein the instructions are further executable by the processor to cause the apparatus to: identify a droppable region of the container component based at least in part on the one or more attributes of the data structure. 15. The apparatus of claim 13 , wherein the instructions are further executable by the processor to cause the apparatus to: receive, from the tenant user device, a package of components comprising the data structure corresponding to the container component. 16. The apparatus of claim 13 , wherein the instructions are further executable by the processor to cause the apparatus to: restrict a type of component from being contained by the container component based at least in part on the one or more attributes. 17. The apparatus of claim 13 , wherein the instructions are further executable by the processor to cause the apparatus to: receive, at the server and from the tenant user device, a second request to store a second data structure corresponding to a non-container component; and expose the non-container component on the user interface using the declarative use feature of the server, wherein the non-container component is contained by the container component. 18. The apparatus of claim 13 , wherein the instructions are further executable by the processor to cause the apparatus to: identify a set of default components contained by the container component, wherein the set of default components is exposed on the user interface within the container component. 19. A non-transitory computer-readable medium storing code for editing components of a user interface, the code comprising instructions executable by a processor to: receive, at a server and from a tenant user device, a request to store a data structure corresponding to a container component; identify one or more attributes of the data structure corresponding to a declarative use feature of the server; determine the data structure satisfies the declarative use feature of the server based at least in part on the one or more attributes; and expose the container component on the user interface using the declarative use feature of the server. 20. The non-transitory computer-readable medium of claim 19 , wherein the instructions are further executable to: identify a droppable region of the container component based at least in part on the one or more attributes of the data structure.
Related publications grouped by family.
Answers are generated from the same data shown on this page.