Welcome to the Flagship Flutter SDK documentation!
The following article will guide you through the steps to get Flagship up and running on your Flutter app using our client library with preconfigured methods to implement the Decision API.
Wants to have a look at the GitHub repo? Link here.
Feel free to contact us if you have any questions regarding this documentation.
Tracking manager feature - Preventing from a data lost and bandwidth hogs.
Config Tracking Manager
Visitor cache feature - Dealing with offline mode.
Managing visitor cache
Customisable interfaces IVisitorCacheImplementation & IHitCacheImplementation to control data. A default implementation is provided by the SDK.
- onVisitorExposed callback in SDK configuration
- Deprecate userExposed(). Use visitorExposed() instead
- visitor_consent key in body of the campaign request
- Bucketing Mode
- Experience Continuity
- Predefined context
- VisitorBuilder class to manage options
- ConfigBuilder class to create a FlagshipConfig instance and manage options
- Flag class to manipulate Flag
- synchronizeModification is now deprecated, use fetchFlags function through the visitor instance
- getModification / getModificationInfo / activateModification are now obsolete and have been replaced by Flag class
- Callback (status listener), called when SDK status has changed
- Improve FlagshipConfig class and manage listener status
- Improve the synchronize modification
- Improve the Logs
- Fix configuration when the current visitor is not Set
- Add unit tests and secure code
- Visitor consent management
- Add logManager to manage logs
- Add FlagshipConfig object to customize the timeout and the logger
- Implement Panic Mode
- Refactor naming of classes & enums (remove FS prefixes)
- Implement the minimal functions to run Flagship:
-- Visitor management
-- Modifications synchronization
-- Modification getter
-- Hit tracking
Updated 13 days ago