Skip to main content
SDK Version

Getting Started

Using the Actito Ionic Native library will allow you to quickly implement remote notifications, use actionable analytics or display content in your app.

Requirements

Understanding the environments​

Applications commonly operate across two primary environments: development and production.

  • The development environment is used for feature implementation, debugging, and internal testing.
  • The production environment represents the live deployment accessed by end users.

It is strongly recommended to assign distinct bundle identifiers to each environment (for example, com.example.app.dev for development and com.example.app for production). Maintaining separate identifiers allows both versions to coexist on the same device, ensures each build connects to the appropriate Actito environment, and prevents data or configuration conflicts.

In most configurations:

  • The development environment corresponds to the debug build type.
  • The production environment corresponds to the release build type.

Establishing a clear separation between environments minimizes the risk of deploying builds that target incorrect services.

Environments

Important

Please ensure you configure distinct environments, as this separation is required for remote notifications to function correctly.

An overview of the library​

The Actito SDK is composed of multiple modules designed to integrate seamlessly with your application.

The core Actito module is required and provides the foundational functionality necessary for all Actito integrations.

Additional modules are optional and can be included as needed to extend the SDK's capabilities — for example, in-app messages or an inbox.

Overview of the library

This modular structure allows developers to include only the components relevant to their use case, ensuring optimal performance and reduced application size. In the package.json your application, add the dependencies that you need:

# Required
npm i capacitor-actito

# Optional modules
npm i capacitor-actito-assets
npm i capacitor-actito-in-app-messaging
npm i capacitor-actito-inbox
npm i capacitor-actito-push
npm i capacitor-actito-push-ui
npm i capacitor-actito-user-inbox

Setting up the configuration file​

To establish a connection between your application and Actito, you must download a configuration file for each environment your application supports. In most cases, this includes both development and production configurations.

Once downloaded, place each file in the following locations within your project:

  • Production configuration: <project>/android/app/actito-services.json
  • Development configuration: <project>/android/app/src/debug/actito-services.json
note

This approach uses Android's build configuration to determine which configuration file to use. You can read more about this approach in the Android documentation.

To make the values in your actito-services.json configuration file accessible to the Actito SDK, you need the Actito Services Gradle plugin (actito-services).

In your root-level (project-level) Gradle file (<project>/android/build.gradle), add the Actito Services plugin as a dependency:

buildscript {
    dependencies {
        classpath 'com.actito.gradle:actito-services:1.0.0'
    }
}

In your module (app-level) Gradle file (<project>/android/app/build.gradle), add the Actito Services plugin:

apply plugin: 'com.actito.gradle.actito-services'

Launching Actito​

Before using any Actito features, the SDK must be initialized by invoking the Actito.LaunchAsync() method. This process ensures that the Actito SDK is fully set up and ready to operate. Most SDK functionality will remain unavailable until this initialization occurs.

It is recommended to invoke the launch within when the main application component initialises its state:

useEffect(() => {
  (async () => {
    // Launch Actito! 🚀
    await Actito.launch();
  })();
}, []);

Launching the SDK automatically registers the device with Actito. If your application requires user consent before collecting or registering device information, you may delay the initial launch until consent is granted.

Otherwise, ensure that launch() is called during the application's initialization phase to avoid missing important updates — particularly when the app is created in the background.

Unlaunching Actito​

If your application needs to permanently disable Actito functionality, you can invoke the unlaunch() method. This method completely removes all Actito-related functionality and deletes any previously registered device information, both locally and remotely.

While this action is generally discouraged, it may be required in certain cases — such as when a user requests permanent account deletion or data removal — to ensure compliance with privacy and data protection regulations.

await Actito.unlaunch()
Important

Once unlaunch() is invoked, all associated data is permanently destroyed and cannot be recovered. Any subsequent calls to Actito APIs will fail until the SDK is reinitialized using the launch() method.