[Android] Expose view

[kiftio]

What changes are you making?

Introduces CheckoutView, a new public FrameLayout subclass that lets host apps embed Shopify checkout inside their own presentation container (e.g. a Jetpack Compose ModalBottomSheet) rather than relying solely on the imperative ShopifyCheckoutKit.present API.

CheckoutView owns the

• checkout header,
• close control,
• loading indicator,
• WebView, back-navigation handling,
• protocol connectivity.

The host retains full control over sheet geometry, scrim, drag handle, snap points, and dismissal gestures. The view can be constructed directly for View-system and Java hosts, or created via the CheckoutView.create Kotlin builder that accepts the same CheckoutPresentation DSL used by present.

Key behavioral details:

• onCancel is invoked by the close button and system back (which navigates WebView history first when possible); the host is responsible for routing sheet-gesture dismissals through the same cancellation path.
• onFail asks the host to remove its presentation rather than attempting to dismiss an unknown parent.
• When the underlying WebView is unsupported, onFail is invoked and the view remains inert instead of crashing.
• destroy() is idempotent and must be called when the view is permanently removed. AndroidView.onRelease is the recommended Compose integration point. The view also destroys itself when its nearest LifecycleOwner is destroyed.
• Callbacks and the protocol client are fixed at construction time; a new CheckoutView must be created for a new checkout URL.

---

Checkout chrome (toolbar, progress bar, loading background, close button) is extracted from CheckoutBottomSheet into a new checkout_view_content.xml layout owned by CheckoutView.

CheckoutBottomSheet now hosts a CheckoutView inside a plain FrameLayout container, removing duplicated chrome logic.

CheckoutWebView.checkoutViewFor is refactored to run on the calling thread (must be main) and transport attachment is moved out of the constructor so a failed feature check can cleanly destroy the partially constructed WebView. CheckoutBottomSheet.start() now returns a Boolean indicating whether presentation succeeded, allowing ShopifyCheckoutKit to clean up its lifecycle observer on failure without relying on a caught exception.

The demo app's cart screen is updated to demonstrate the embedded flow using ModalBottomSheet + AndroidView, and CartViewModel.checkoutConfiguration is extracted so the same callback block can be shared between the imperative and embedded paths.

How to test

1. Build and run the demo app (CheckoutKitAndroidDemo).
2. Add items to the cart and tap Checkout — the cart screen now presents checkout inside a ModalBottomSheet via CheckoutView.
3. Verify the checkout header, close button, loading indicator, and WebView render correctly inside the sheet.
4. Tap the close button or swipe to dismiss — confirm onCancel is invoked and the sheet closes.
5. Press system back while on the first checkout page — confirm the sheet closes. Press back on a page with WebView history — confirm it navigates back before closing.
6. Confirm the existing ShopifyCheckoutKit.present flow (used elsewhere in the app) continues to work unchanged.
7. Run the unit tests: ./gradlew :lib:test — new CheckoutViewTest and updated InteropTest cover construction, preload consumption, lifecycle destruction, back navigation, cancel deduplication, and Java interop.

---

Before you merge

Important

• I've added tests to support my implementation
• I have read and agree with the Contribution Guidelines
• I have read and agree with the Code of Conduct
• I've updated the relevant platform README (platforms/swift/README.md and/or platforms/android/README.md)

---

Releasing a new Swift version?

• I have bumped the version in ShopifyCheckoutKit.podspec
• I have bumped the version in platforms/swift/Sources/ShopifyCheckoutKit/ShopifyCheckoutKit.swift
• I have updated the SwiftPM/CocoaPods version snippets in platforms/swift/README.md (major version only)

Releasing a new Embedded Checkout Protocol version?

• I have bumped embeddedCheckoutProtocolAndroid in platforms/android/gradle/libs.versions.toml
• I have updated protocol/languages/kotlin/embedded-checkout-protocol/api/embedded-checkout-protocol.api if the public API changed

Releasing a new Android version?

• I have bumped checkoutKitAndroid in platforms/android/gradle/libs.versions.toml
• I have updated the Gradle/Maven version snippets in platforms/android/README.md

Tip

See the Contributing documentation for the full release process per platform.

[kiftio]

• dk/app-owned-sheet-sample #452
• [Android] Expose view #446 👈 (View in Graphite)
• [Android] Replace JavascriptInterface with WebMessageListener #424 : 1 other dependent PR (#456 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[kiftio]

CheckoutView intentionally lacks Android’s standard XML-inflatable constructors:

• View(context)
• View(context, attrs)
• View(context, attrs, defStyleAttr)

CheckoutView instead requires runtime state immediately:

CheckoutView(context, checkoutUrl, listener, protocolClient)

Without the suppression, lint warns because subclasses of View are normally expected to support XML inflation.

The practical consequence is that this will not work:

<com.shopify.checkoutkit.CheckoutView ... />

But direct construction and Compose’s AndroidView(factory = …) work normally. The annotation only silences that specific static-analysis warning; it changes no runtime behaviour.

[kiftio]

This is internal..

The responsibility is on the caller to run call on the main thread.

Rationale - the whole CheckoutView is UI construction. The whole thing should be on the UI thread, not just this internal WebView creation part.

Annotating the constructors for the View with @mainthread

Compose's AndroidView.factory already runs on the UI thread

[kiftio]

small refactor to avoid the non-null assert