do you think we should simply set minSdk to that for this module?

I don't think so, it will force clients to upgrade their application's minSdk for using profiling feature. But actually we expect that anyone can import profiling feature, and they are able to enable it only for end user's device above SDK 35

Good question.

If you try (change minSdk of a module to 30 and compile the sample), you have something like this:

Manifest merger failed : uses-sdk:minSdkVersion 23 cannot be smaller than version 30 declared in library [:integrations:dd-sdk-android-sqldelight] /Users/aleksandr.gringauz/projects/dd-sdk-android/integrations/dd-sdk-android-sqldelight/build/intermediates/merged_manifest/debug/processDebugManifest/AndroidManifest.xml as the library might be using APIs not available in 23
	Suggestion: use a compatible library with a minSdk of at most 23,
		or increase this project's minSdk version to at least 30,
		or use tools:overrideLibrary="com.datadog.android.sqldelight" to force usage (may lead to runtime failures)

I'm almost sure it will be the same for the library when it isn't compiled, but downloaded. Because it is manifest merging.

The customer will have to use flavors (like this) to use the profiling module.

But the question is - how to deal with these flavors when uploading to google play. I currently don't know, research needed.

This is important point indeed, thanks for bringing it.

Let's add TODO item for now.

What's the thing to do here? do we want to bump the minSdk for this?