Intent
Need to create an interface for enabling Access to Content on Sunbird across different apps like Read Along,Games etc.
Note: Assumption of this specification is based on the apps being able to support these intents as part of their implementation.
Documentation is categorised into multiple sections:
Approaches
Technical Specification for third party apps
Param Data Supported
Data Sharing Table
Summary Event Spec
API Documentation
Intent Handling
Vendor Registration of Apps to Sunbird
Global Vendor Registration API
Local Vendor Registration by Deep Linking
Approaches
Technical Specification for Third Party Apps
Vendor registration of Apps to Sunbird
Global Vendor Registration API
Each Vendor can be registered as part of Global Configuration for Sunbird to have app links being enabled.
{ identifier: "", name: "", logo: "", appName: "", packageId: "", mimeType : [], preferredOrgIds : [], vendorDetails: { company: { name: "<name-of-parent-company>", year: "" },... }, vendorCode: "This is assigned by Sunbird as unique key to identify", createdDate: Date, updatedDate: Date, enabled : boolean, validUpto: Date }
Vendor CRUD API (or) Form Configuration Supported.
Local Vendor Registration by Deep Linking
Enabling of Deep link in Sunbird for local registration restricted to device.
Device hears for deep links to register vendor apps locally (Restricted to particular device).
StepsVendor app needs to call a deep link of Sunbird app.
Sunbird App as part of handling deep link will try to persist vendor information locally on app’s data.
Any subsequent invocation of intent from Sunbird will show globally registered apps for Sunbird along with locally registered apps in devices.
deeplink Url :
diksha://register?name: "", logo: "", appName: "", packageId: "",mimeType:””
Parameter | DataType | Description |
---|---|---|
name (M) | String | |
logo (M) | String | |
appName (M) | String | |
packageId (M) | String | |
mimeType (O) | String |