One of the more difficult concepts to communicate has been around the value and pervasiveness of app integrations. A while ago, we assembled the App Action Contribution Reference as a single source for information on all the locations where developers can weave app experiences into Jive. One thing that was missing in this was a bit of the glue that brings it all together, such as understanding exactly how apps understand the core tenants of rendering a "contextual experience", such as:
- Who is the Viewer?
- What is my app context?
- Where is my app being viewed?
- How is my app being displayed?
- How to target app delivery to only key points in the Jive UX?
[Enter, Stage Left] Jive Developer App Reference "App"
Overview of Features
- Implements every action contribution in the App Action Contribution Reference, including distinct actions for "All Places", "All Content" and their individual content/place type specifics.
- 1 app.xml, 1 canvas.html, 1 main.js, and 1 main.css
Includes sample code implementations for:
- Who is the current viewer?
- What is my current view name & context?
- What is my current action name & context?
- Get/Setting View Params for in-app linking.
- !app artifact creation
- Simple App Links to initiate in-content contextual app-views
- Simple HTML Markup (instead of App Link)
- Canvas View
- Group Tab View w/Params
- Content Action View
Give it a Try for Yourself
We've updated the Getting Started > Creating an App with the Jive Node SDK tutorial with details on how you can generate this app for yourself to get started on your own.
- jive-sdk create app
- jive-sdk build --apphosting="jive"
- Upload the extension.zip to the Developer Sandbox
As always, I hope this helps ... and enjoy!