![]() At a high level, it connects third-party embedded apps with the first-party host document. ![]() It provides UI components such as buttons and colors, handles layout, enforces permissions, and provides an interface to data. Now let's talk about the library code and the app instance data. App instance data: A way for an app instance to store long-lasting data in Quip, such as specific poll options and votes.Library code: Quip code to handle communication with the surrounding document.App code: JavaScript, CSS, and other assets to render the app into the iframe.Configuration data: The name of the app, required API version, toolbar color, and so on.Build a platformīack in Part 1, we separated the platform into four pieces and walked through the first two. ![]() Then we'll end by showing a few powerful collaboration components built into the platform. We'll discuss how we support communication between the app and the Quip document, as well as how we enable apps to store long-lasting, syncing, custom data that works online and offline. This post will cover the second part of building a platform.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |