Objective

To discuss and identify any specific requirements for testing the Firebolt Connect apps on RDK7-certified devices.

Opportunity

RDK deployed operators require the Firebolt Apps to be integrated with their deployed solution. 


Discussion Points

  1. RDK7 Continue to use the RDKShell component for window management, Key-handling, and App management - Does this have any impact on the Firebolt Connect app tests and certification
  2. Are there any specific requirements on event handling for FB apps from the RDK7 stack 
  3. How the events/crashes of the app updated back to the Device stack
  4. Is there are requirements for  lifecycle management and bidirectional event transport with RDK7
  5. Is there any need for keeping the app session id - If yes how to handle this


Component versions in RDK7 Release

Ripple 1.16.x

Firebolt 1.4.x.

RDKServices 7.5.2


Updates expected with Firebolt 2.0

Lifecycle 2.0 - https://github.com/rdkcentral/firebolt-apis/blob/major/lifecycle-improvements/requirements/specifications/lifecycle/index.md

Bidirectional Event transport (Ripple 1.17 onwards, bidirectional event transport (BET) support is available for Firebolt client applications.)

Provider Patters - https://wiki.rdkcentral.com/display/ASP/JSON-RPC+usage+pattern+in+firebolt


RDK7 Arch diagram ( For FB apps)


  • No labels

DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.