A modern programming language that makes developers happier.

kotlinlang

When building an android library that ships full screens in the library (we basically have a payment library we're working on and we ship full payment screens as part of this library), whats the best practice for supporting edge-to-edge in a compose android library? im sorta lost on whether or not we should pull the plug and just use the e2e apis everywhere in our library and therefore force our consumers. Anyone have strongs thoughts or opinions?

maybe do exactly as what stripe does <https://docs.stripe.com/payments/mobile/payment-sheet|docs.stripe.com/payments/mobile/payment-sheet>

<@U011HA9T9SA> any chance you have opinions on this?

screenshot_2026-07-27_15.44.15.png

I recently published an android library and the google play console will give you warnings if your app targets sdk 35 but doesn’t use the proper edge-to-edge apis.
even recently this list had revenuecat but looks like their newer updates fixed it.

may be relevant: <https://github.com/RevenueCat/purchases-android/issues/2026|github.com/RevenueCat/purchases-android/issues/2026>