We're excited to announce Flagship SDK v5.0.0, featuring significant improvements in performance, capabilities, and developer experience across all supported runtime environments.

Added

• Emotion AI Integration — Utilize powerful emotion analysis capabilities to understand user reactions and tailor experiences based on emotional responses, enabling more empathetic and responsive applications.
• Batch Limit for Activate Hits — Implemented a fixed maximum limit on activate hits per batch, significantly reducing network overhead while maintaining analytics accuracy.
• reuseVisitorIds pros which controls whether the SDK saves visitor IDs in local storage for reuse across sessions.

Improved

• Enhanced Tree Shaking — Reduced bundle size through improved code splitting and dependency management, ensuring you only load what you need for your specific implementation.

Changed

• Contextual Segment Hits — In bucketing mode, segment hits are now only sent when the visitor context has been updated, reducing unnecessary network requests and improving performance.
• Naming Clarity — Renamed FetchFlagsStatus to FlagsStatus for improved API clarity and consistency throughout the SDK.

For migration assistance and detailed documentation, please refer to our official documentation.

Add

• Emotion AI
• Limit the maximum number of activate hits per batch
• reuseVisitorIds props. If it is set to true, the SDK will save the visitor ID and/or anonymous ID and reuse it for the next session if visitorId is not set, to maintain cross-session visitor experience.

Change

• The Flagship.start method is now asynchronous
• Segment hits in bucketing can be sent only when the visitor context has been updated

Fixed

• Visitor multiple authentication

Add

• QA assistant tool
• Visitor Status
• Flag status
• Visitor.getFlags method
• The onSdkStatusChanged props of FlagshipProvider

Change

• useFsFlag hook
• visitor.getFlag method signature
• Flag.getValue method signature
• ThehasConsented key of visitorData props is now mandatory
• SDK status enum

Remove

• From visitor instance (modifications, getFlagsDataArray, getModificationsArray, getModification, getModificationSync, getModificationInfo, getModificationInfoSync, synchronizeModifications, activateModification, getAllFlagsData, getModificationsForCampaign, and getFlatsDataForCampaign)
• From FlagshipProvider (enableClientCache and statusChangedCallback)

Improved

• Usage data collection process

Fixed

• Fixed a typo error in the DecisionMode property value of the usage tracking hit.
• Fixed Intl property error

Updated

• @flagship.io/react-sdk dependency to version 3.3.2

Fixed

• Usage tracking collection issue

Updated

• @flagship.io/react-sdk dependency to version 3.3.1

Added

• Collecting developer usage tracking data:
  • The SDK now collects troubleshooting data, which will help us find implementation issues
  • The SDK now collects usage data, which will help us improve our product
• disableDeveloperUsageTracking property in config object.
• Experience continuity in bucketing mode

Updated

• @flagship.io/react-sdk dependency to version 3.3.0

Added

• campaignName, variationGroupName and variationName in Flag metadata

Updated

• @flagship.io/react-sdk dependency to version 3.2.4

Added

• fetchFlagsBufferingTime props in config object.
• trackingManagerConfig props in config object.
• New warning logs

Deprecated

• trackingMangerConfig props of config object.

Updated

• @flagship.io/react-sdk dependency to version 3.2.3

Added

• qt field in activate batch. It represents the time delta (in milliseconds) between when the hit being reported occurred and the time the hit was sent.

Updated

• @flagship.io/react-sdk dependency to version 3.2.2