Context data & feeds
Related links:
- Sharing data between slides
- Working with API data guide
- Context and feeds testing guide
- Importing dummy data into the CDK
- Bridge.Context API reference
- Bridge.Feed API reference
Context
An appointment's context is a source of data that holds information specific to the appointment. This information is a combination of data provided by the app and by the user creating the presentation, that is initially compiled when an appointment is created. This data can then be queried and used by your slides, as well as updated by them throughout a presentation.
The context is initially written when an appointment is being created. Its most common uses are storing information about the selected customer(s) and attendee(s) for the presentation, and saving a begin/created date for display on a welcome slide.
Some more complicated examples include saving the results of an image/spreadsheet upload - specific to that presentation, for use in product slides, or storing the results of a suburb search that is later used to filter a feed and render graphs in a data slide.
Slide content can also provide an interface for the user to edit the context. This is useful in any scenario where the deck will be viewed again later, and must preserve a state from an earlier viewing. For example, the user presents their client with a calculator or questionnaire that they fill out together. The selections and results are saved to the context and displayed pulled back in when the user shares an OnlinePreso with their client proceeding their meeting.
Feeds
A feed is a source of data which is periodically downloaded by LivePreso for use in your deck. Your deck can have one or more feeds. Within a slide, you can query data from the feed and use it, for example, to display graphs which are relevant to the viewing user.
When a user makes a preso using a deck which has feeds, the contents of the feeds are synced to the user's device, where they're then available to your slides. This means that for data which can change over the time (for example, stock prices), it's important to note the feeds are not re-fetched every time the preso is viewed; only after it has been created. In addition, the feeds will be re-fetched if the preso is updated or rescheduled.