iOS SDK 15.6.5,
Android SDK 15.5.1,
Hello Screen Dynamic States,
Bluedot Cordova plugin 4.0.1,
Bluedot Xamarin Android Wrapper 15.4.1,
Bluedot Xamarin iOS Wrapper 15.6.0,
Bluedot React Native wrapper 2.2.0,
To get started with Tempo, you’ll first need to integrate the Point SDK in your mobile app. You can find step-by-step integration guides here:
During SDK integration, there are 4 important stages that align with your customer’s experience.
/** * Start Tempo Tracking. * @param destinationId - destinationId of the Zone for tracking. * @param statusListener - implementation of Tempo status callbacks to receive Tempo lifecycle events and errors. */ public void startTempoTracking(@NonNull String destinationId, @NonNull TempoStatusListener statusListener) /** * Stop Tempo Tracking * TempoStatusListener#tempoStopped() will be called once tracking has ceased. */ public void stopTempoTracking()
You’ll find comprehensive Android implementation detail here.
/** * Start Tempo Tracking for destination id provided * * @note An error will be returned if your App does not have Always location permission. * @param destinationId The destinationId to be tracked * @param completion A mandatory completion handler called once Start Tempo processing completed. If the Tempo is started successful, error will be returned as nil. However, if the Start Tempo fails, an error will be provided. */ - (void)startTempoTrackingWithDestinationId: (NSString * _Nonnull)destinationId completion: (void (^ _Nonnull)(NSError * _Nullable error)) completion; /** * Stop Tempo Tracking * * @param completion A mandatory completion handler called once Stop Tempo processing completed. If the Tempo is stopped successful, error will be returned as nil. However, if the Start Tempo fails, an error will be provided. */ - (void)stopTempoTrackingWithCompletion: (void (^ _Nonnull)(NSError * _Nullable error)) completion;
You’ll find comprehensive iOS implementation detail here.
In iOS, to receive Tempo related callbacks, implement the BDPTempoTrackingDelegate protocol
Tempo will timeout after 30 minutes if the device hasn’t arrived at the destination. This expiring time is customizable; check with your CX representative if you’d like to update it.