user explicitly controls permissions

can connect cards to DAs? the DAs can see these cards (or all)

A way to schedule cards to be posted to twitter/instagram?

[no ui example?] get urls of trello/etc from bitbucket: when card checked, complete the task on the source url (unito.io)

what kinopio features can i build using only DAs (the same tools that I present to third parties)

custom card fields

custom fields that do computation on dataentry, and present results

if space DAs: only see the DAs you set up, or all users of the space see the DA of a space and it’s state?

DAs are bound to user or space??

can only push? (what scenarios do they need to know state for?)

child iframes should have no access to LS

long-term planning

how to add DAs? a directory like Explore that apps can be submitted to?

supply basic CSS framework for ppl who want a native look

DAs can have arbitrary gui, can talk to parent space via pre-approved postmessages?

use cases:

what’s hot on trello/figma/etc.

... t. what integrations/plug ins would you want?

lives inside a kinopio window chrome w max bounds and a close button

Desk accessories are hard to write because they’re constructed so differently from the host programs they depend on. They’re written as device drivers - which means, among other things, that they are table-driven, that they have to be small

and that they have to be very careful not to alter the environment they work in

A desk accessory (DA) in computing is a small transient or auxiliary application that can be run concurrently in a desktop environment with any other application on the system https://en.wikipedia.org/wiki/Desk_accessory