Getting Started

The GluedIn SDKs provide seamless integration with your existing app or function as a standalone video community platform. Our UI SDK includes a comprehensive interface, enabling easy theme customization and a quick launch with minimal configuration. For greater flexibility, the Core SDK offers all essential methods to build a fully customized UI/UX.

Key Decisions Before Integration

Before beginning the integration process, please consider the following essential prerequisites:

  1. Define Entry Point

    Clearly establish the entry point for integration, ensuring alignment with your app’s functionality and goals.

  2. Integrate it in existing app vs launching a new app

    Below are the key points outlining the differences between these two approaches:

    • Objective: Integrating into an existing app enhances the current application by embedding community features, while launching as a new app deploys a standalone community platform.

    • User Experience: Integration within an existing app offers a seamless experience, making the community features appear native, so users are unaware of an additional SDK. In contrast, launching as a new app provides users with a dedicated community experience in a separate application.

    • Branding: Integration maintains consistency with the current app’s branding, while launching as a new app offers complete branding control, allowing for a unique brand identity.

    • Maintenance: When integrated into an existing app, updates and new functionalities are managed within the app itself. In a standalone launch, however, updates and maintenance need to be handled independently, separate from other applications.

  3. UI+ SDK vs Core SDK

    Below are the point which helps to differentiate between the UI+ SDK and Core SDK, making it easier to select the appropriate option based on project requirements.

    • Objective: UI+ SDK, provides out-of-the-box solution with minimal configuration however Core SDK, Provides foundational methods, allowing developers to build a fully customized UI/UX that aligns with specific app design and branding needs.

    • Customization: UI+ SDK, offers limited customization; ideal for quick deployment with standard features and pre-built UI components however Core SDK, maximum customization flexibility, allowing integration of only the required functionalities and building a tailored user interface from scratch.

    • User Experience: UI+ SDK, Includes a pre-designed interface, delivering a consistent, streamlined user experience with minimal development effort however Core SDK, enables complete control over the user experience, giving developers the freedom to design a unique look and feel within the existing app environment.

    • Development Effort: UI+ SDK, minimal development required; ideal for teams seeking a quick and straightforward integration of community features however requires more development resources to build and style the interface according to custom specifications.

    • Maintenance: UI+ SDK, managed updates are provided as part of the SDK, with built-in compatibility and less maintenance overhead however Core SDK, maintenance responsibility falls on the development team, as custom code and UI elements may need updates when SDK versions change.

  4. PGC (Professionally Generated Content) or UGC (User Generated content)

    Lets find out in which use case your business requirement falls:

    • PGC(Professionally Generated Content): Businesses that want to include short video experiences in the existing app when you already have content they want to monetize or use for engagement. One Click configuration to restrict the content creation by the end users from the console. Read more about PGC

    • PGC + UGC: Businesses have flexibility to start with PGC and move it on UGC with a controlled environment using our inbuilt AI + Manual moderation layer. Enable and disable the UGC feature from the console whenever needed. Read more about PGC+UGC

  5. Vertical vs Card Feed

    We support two types of feed in GluedInSDK, 1) Vertical and 2) Card Type. Businesses can choose while creating a project on the GluedIn console. If the content is available in multiple formats i.e. video, image, and text. should choose a card based feed however if the content is only video and available in 9:16 format ideal feed type is vertical.

  6. Platform Pre-Requisites

    • If Android studio is not installed on your machine, please download from here and install.

    • Min Requirements for Gluedin Android SDK

    • minSdkVersion – 24

    • targetSdkVersion – 34

    • compileSDK - 34

    • Min Java Version – 11.0

Quick Integration Steps

To get started, here’s a brief overview of the primary steps:

  • Step 1: Create API & Secret Key: Generate the required keys from the console to start your integration.

  • Step 2: Integrate Dependency: Add GluedInSDK dependency in to your app for streamlined dependency management.

  • Step 3: Entry Point Configuration: Set up the main entry point to initialize the SDK.

  • Step 4: Project Configuration: Adjust your project’s Info.plist settings for proper integration.

  • Step 5: Feed & Callback Setup: Select the feed format and configure necessary callbacks.

  • Step 6: Run the App: With these steps complete, run your app to see the SDK in action.