Managing App Session in DFINERY SDK
Introduction
When you integrate with DFINERY SDK you will have an app start event (abx:start_session), and an app stop event (abx:end_session). This article is about how DFINERY SDK manage the app start and stop event.
How do DFINEY SDK know App start or stop
Each Android and iOS has the method that alert the developer to the app is started or stop. Using this method DFINERY can identify what happened on your app. If DFINERY SDK identify the app is started, SDK will call abx:start_session event or the app is stoped, SDK will call abx:end_session.
Android AppLifecyle [Android Developer]
Android has a app lifecycle like this. Each lifecycle has its own method. Based on this app lifecycle SDK will call abx:start_session on the app start(onResume()), and will call abx:end_session when app is stoped(onPause()).
iOS App Lifecycle [Apple Developer]
iOS also has a similar app lifecycle. Based on this lifecycle, if the app is started (Active) DFINERY SDK will call abx:start_session, and if the app is stoped (InActive) DFINERY SDK will call abx:end_session.
abx:start_session
abx:start_session event will call on number of app event is on.
- User installs the app and start the app.
- User restart the app after 60second the app is stoped (60 second Rule)
- User start the app using deeplink via a DFINERY tracking link.
abx:end_session
abx:end_session event will call on number of app event is on.
- User exit the app using a home button or multitasking mode. After 60second abx:end_session will call. (60 second Rule)