Skip to main content
Supported on: Android SDK 1.0.33+

Overview

Server-driven screens let growth teams design and deploy native screens from the AppDNA console — no app release needed. The SDK renders screens from JSON config fetched via Firestore. Screens combine content blocks from any SDK module (onboarding, paywalls, surveys, messages) into a single composable surface. You can build feature announcements, upgrade prompts, referral screens, guided tutorials, and more — all without writing native UI code.

Show a Screen

AppDNA.showScreen("upgrade_prompt") { result ->
    Log.d("Screens", "Screen dismissed: ${result.dismissed}")
    Log.d("Screens", "Responses: ${result.responses}")
}

Show a Multi-Screen Flow

AppDNA.showFlow("onboarding_v2") { result ->
    Log.d("Screens", "Flow completed: ${result.completed}")
    Log.d("Screens", "Screens viewed: ${result.screensViewed}")
}

Dismiss

AppDNA.dismissScreen()

Screen Slots (Inline Content)

Place named slots in your Compose views. The console assigns screens to slots.
@Composable
fun HomeScreen() {
    Column {
        AppDNAScreenSlot("home_hero")
        // ... your app content ...
        AppDNAScreenSlot("home_bottom")
    }
}
  • Empty slots render nothing (no visual impact)
  • Content updates on next config refresh
  • Supports audience targeting per slot
Automatically inject screens between app navigations:
// Enable (one-time setup)
AppDNA.enableNavigationInterception()

// Or for specific screens only
AppDNA.enableNavigationInterception(forScreens = listOf("SettingsActivity", "Premium*"))

// Disable
AppDNA.disableNavigationInterception()

Debug Preview

Test screens from raw JSON without publishing to Firestore:
if (BuildConfig.DEBUG) {
    val json = """
    {"id":"test","name":"Test","presentation":"modal",
     "layout":{"type":"scroll"},"sections":[...]}
    """.trimIndent()
    AppDNA.previewScreen(json = json)
}

Screen Delegate

The delegate fires for every screen lifecycle event. Result and action payloads are delivered as Map<String, Any?> for forward-compat with new fields the SDK adds (e.g., last_action, duration_ms):
import ai.appdna.sdk.screens.AppDNAScreenDelegate

class MyDelegate : AppDNAScreenDelegate {
    override fun onScreenPresented(screenId: String) { }

    override fun onScreenDismissed(screenId: String, result: Map<String, Any?>) {
        val dismissed = result["dismissed"] as? Boolean ?: false
        val responses = result["responses"] as? Map<String, Any?>
        val lastAction = result["last_action"] as? String
    }

    override fun onFlowCompleted(flowId: String, result: Map<String, Any?>) {
        val completed = result["completed"] as? Boolean ?: false
        val screensViewed = result["screens_viewed"] as? List<String> ?: emptyList()
        val responses = result["responses"] as? Map<String, Any?>
    }

    override fun onScreenAction(screenId: String, action: Map<String, Any?>): Boolean {
        val type = action["type"] as? String
        // Return true to let the SDK apply default handling, false to suppress it
        return true
    }
}

AppDNA.screenDelegate = MyDelegate()
The top-level AppDNA.showScreen(...) / AppDNA.showFlow(...) callbacks DO use the typed ScreenResult / FlowResult data classes (see API Reference) — only the delegate uses untyped maps.

Presentation Modes

Screens support the following presentation modes configured in the Console:
ModeDescription
fullscreenFull-screen modal covering the entire screen (default)
modalSheet that doesn’t cover the full height (iOS pageSheet-style on Android)
page_sheetAlias of modal on Android — same rendering
bottom_sheetDraggable bottom sheet
Unrecognized values fall through to fullscreen.

Section Types

Screens are composed of ordered sections. The unified section registry includes content from all SDK modules:
CategorySection Types
Genericcontent_blocks, hero, spacer, divider, cta_footer, sticky_footer
Onboardingonboarding_step, progress_indicator, navigation_controls
Paywallpaywall_header, paywall_plans, paywall_cta, paywall_features, and more
Surveysurvey_question, survey_nps, survey_csat, survey_rating, survey_free_text, survey_thank_you
Messagemessage_banner, message_modal, message_content
Mediaimage_section, video_section, lottie_section, rive_section

Auto-Tracked Events

EventWhen
screen_presentedScreen appears
screen_dismissedScreen disappears
screen_actionUser taps a CTA
flow_startedFlow begins
flow_completedFlow finishes
flow_abandonedFlow dismissed early
slot_renderedSlot displays content
slot_registeredSlot first renders
interception_triggeredNav interception fires

Full Example

import ai.appdna.sdk.AppDNA
import ai.appdna.sdk.screens.AppDNAScreenDelegate

class ScreenCoordinator : AppDNAScreenDelegate {

    init {
        AppDNA.screenDelegate = this
    }

    fun showUpgradePrompt() {
        AppDNA.showScreen("upgrade_prompt") { result ->
            // top-level callback uses the typed ScreenResult data class
            if (result.responses["purchased"] == true) {
                unlockPremium()
            }
        }
    }

    fun startFeatureTour() {
        AppDNA.showFlow("feature_tour_v2") { result ->
            Log.d("Screens", "Tour completed: ${result.completed}")
        }
    }

    // AppDNAScreenDelegate (maps)

    override fun onScreenPresented(screenId: String) {
        Log.d("Screens", "Screen shown: $screenId")
    }

    override fun onScreenDismissed(screenId: String, result: Map<String, Any?>) {
        val dismissed = result["dismissed"] as? Boolean
        Log.d("Screens", "Screen $screenId dismissed=$dismissed")
    }

    override fun onFlowCompleted(flowId: String, result: Map<String, Any?>) {
        val screens = result["screens_viewed"] as? List<String> ?: emptyList()
        Log.d("Screens", "Flow $flowId completed, screens=$screens")
    }

    override fun onScreenAction(screenId: String, action: Map<String, Any?>): Boolean {
        // Return false to prevent default action handling
        return true
    }

    private fun unlockPremium() { /* ... */ }
}
Screens are rendered using Jetpack Compose. The SDK handles the full UI lifecycle. Screens are delivered via the same Firestore config bundle as other SDK modules.