I wanted to enquire if there might be plans in the works, or an argument for, Jibo launching with a notification system including an API allowing outside apps to use Jibo’s notifications, without using a skill.
I’ve included an argument for Jibo Inc to consider adding a standard notification system in the SDK with an external API.
A Jibo Notifications API would allow Jibo to uniquley communicate outside notifications from any existing apps that are owned by a Jibo owner.
Imagine Jibo receiving a text message with settings that could produce a unique, display of motion, selected sounds or perhaps entire .key files. These .key files could be developed from yet other Jibo skill developers and sold in a ‘Notifications’ section of the Jibo skill store, for those who only learn to create .key files. (like selling ring tones to developers for their notifications)
Yes, any one of us could try to build this and sell it as a skill, but rather than Jibo Notifications being a purchasable skill, other Jibo skill writers could still benefit while creating standardization if Jibo Inc created the standard and kept it open.
If managed well from the API, outside internet apps could sign up to use this notification channel. Jibo Inc would have produced another avenue to connect Jibo to the outside world from the start; while Jibo skills are being developed and using this tool as well.
Apps that send notifications can then code JIBO personality into their notifications, without learning Jibo skills, just the registration and use of the Jibo Notification API.
If provided by Jibo Inc a notifications system would be a fast way for people to adapt their existing notifications code in other apps to a unique, select, Jibo personality specific, elements that enhance their, and I repeat, ‘existing notifications’, and add future notifications for all Jibo owners.
What do the other developers think about this? Is anyone already working on it?