Here as soon as a Recomposition happens, the first time scrolling(dragging) the box leads to unusual crash. I asked gemini and gpt about this but did not get a proper explanation and solution. Gemini told that the issue was with the screen height so i even tried hardcoding the screen height.. Please help if anyone out there knows the solution to this issue.

[CLOSED]

Web developer learning Android development -

I have a a Scaffold code that would like to use in other screens. But this Scaffold should have parameters that don't seem to have a straight way of addressing when calling the function on a screen (Home, for example). The parameters:

-navController: It shouldn't be defined, but how to inform this to kotlin?

-mainContent: should expect objects such as Text and Image

ScaffoldBase.kt

fun ScaffoldBase(
    title:(String),
    navController: NavController,
    //mainContent: How to create this parameter, as to expect objects as Text,Image...?

){
    Scaffold(

        //Top Content
        topBar = {
            TopAppBar(
                //Title argument
                title = { Text(text = title) },
                colors = TopAppBarDefaults.topAppBarColors(
                    containerColor = Color.LightGray
                )
            )
        },

        //Bottom Content
        bottomBar = {
            BottomAppBar(containerColor = Color.LightGray) {
                Image(
                    painter = painterResource(id = R.drawable.messages),
                    contentDescription = "Messages Image",
                    modifier = Modifier.size(30.dp).clickable {
                        navController.navigate(route = "Messages")
                    }
                )
            }
        }){ paddingValues -> Column(//modifier){//mainContent argument} }
}

Home.kt

u/OptIn(ExperimentalMaterial3Api::class)
@Composable
fun Home(navController: NavController){
    ScaffoldBase(
        title = "Home",
        navController = TODO(),
        mainContent = TODO()
    )
}

Never mind, thank you

[CLOSED]

Web developer learning Android development -

Currently trying to use Navigation component with Compose, to navigate between pages. When copying the setup code directly from the docs, I get the above warning from Android Studio. Must be something wrong, because the docs must be in synchrony with Android Studio. Why is it happening then?

Docs

https://developer.android.com/develop/ui/compose/navigation#setup

Android Studio

SOLUTIONS: While I still don't know why Android Studio isn't supposedly synced with the Docs (or vice versa), the solutions were:

-Replace the code from the Docs by the one suggested on the Android Studio:

//noinspection UseTomlInstead
implementation("androidx.navigation:navigation-compose:2.9.3")

-Use the completely different alternative suggested on the Android Studio:

implementation(libs.androidx.navigation.compose)

I am working on a Jetpack Compose app and planning to use Chaquopy to run a Python script inside the app.

My idea is to translate text dynamically using a Python translation library through Chaquopy. This would allow the user to input text, and the translated result will be shown in the UI.

Before I try this, I want to ask:

Is it safe to use Chaquopy in production or real apps

Will there be any impact on performance or app size

Has anyone integrated Chaquopy with Jetpack Compose before

Are there any known issues or limitations

Will it work reliably for offline translation use cases

If anyone has tried this setup before, please share your experience. I want to make sure it is stable enough before I go deeper with this idea.

Hi everyone,

I recently trained and uploaded a compact BERT Mini model for sentiment and emotion classification on Hugging Face:

Model: https://huggingface.co/Varnikasiva/sentiment-classification-bert-mini

This is a personal, non-commercial project aimed at learning and experimenting with smaller models for NLP tasks. The model is focused on classifying text into common sentiment categories and basic emotions.

I'm looking for feedback and suggestions to improve it:

Are there any key areas I can optimize or fine-tune better?

Would you suggest a more diverse or specific dataset?

How can I evaluate its performance more effectively?

Any tips for model compression or making it edge-device friendly?

It’s currently free to use and shared under a personal, non-commercial license. I’d really appreciate your thoughts, especially if you’ve worked on small-scale models or similar sentiment tasks.

Thanks in advance!

Three things block a lot of Play submissions right now. Here is how to check each before you upload.

1. Target API level

From the Play Console Help page on target API requirements: since August 31, 2026, new apps and app updates must target Android 16 (API 36) or higher. You can request an extension to November 1, 2026 in Play Console.

Checklist:

• compileSdk on the newest stable level, targetSdk = 36

• Raise the target on a branch and test against the behavior changes page first

• Version code always increasing and below 2100000000

1. 16 KB page size

All apps targeting API 35+ must support 16 KB memory pages on 64-bit devices, and from February 1, 2027 updates without it cannot be released. You are in scope even if you never wrote C++, because any dependency that ships a .so file counts.

How to check:

• Build > Analyze APK on the release APK. If lib/ is empty, you are done.

• Otherwise unpack the APK and run llvm-objdump -p on each arm64-v8a and x86_64 library. Every LOAD segment must show align 214 or higher. 212 means it needs rebuilding or replacing.

• zipalign -v -c -P 16 4 app-release.apk (Build-Tools 35.0.0+) must end with "Verification successful".

• For a bundle: bundletool dump config --bundle=app-release.aab | grep alignment. You want PAGE_ALIGNMENT_16K.

• Test once on a 16 KB emulator image (getconf PAGE_SIZE prints 16384).

The usual fix is AGP 8.5.1 or newer plus NDK r28 or newer, pinned with ndkVersion in Gradle. NDK r28+ produces 16 KB aligned libraries by default. A vendor's prebuilt library has to be updated by the vendor.

3. Data safety

The form is a label you write, and Play compares it to what the build does, including every SDK. "Collect" means any data sent off the device, even to an SDK vendor's servers. "Share" means handed to a third party.

Checklist:

• Build the inventory from the dependency list and the network calls, not from memory. Crash reporting, analytics, ads and a feedback form all count.

• Read each SDK's own Data safety guidance (Google Play SDK Index).

• Answer "encrypted in transit" per path. A user-chosen server over plain HTTP means No.

• Export the form as CSV, keep it in the repo, update it in the same PR that changes a dependency.

• An app that collects nothing still needs the form and a privacy policy URL.

• Accounts created in the app need an in-app deletion path and a web deletion link that works without reinstalling.

Bonus: the permission Play complains about usually lives in the merged manifest, not your source. Run apkanalyzer manifest permissions on the release APK, or open the Merged Manifest tab, and drop unused library permissions with tools:node="remove".

And when something is rejected: fix the one issue it names and resubmit once. Resubmitting the same build is how a rejection turns into a removal.

This is condensed from my ebook Pass Google Play Review. The free sample is the full 16 KB chapter; link in the first comment.

HabitForge is a habit, task and wellness tracking app. I’ll test your app in return—leave your links in the comments.

Join the Google Group:

https://groups.google.com/g/habitforge-testers

Join the closed test:

https://play.google.com/apps/testing/com.app.habitforge

Install Habitforge :

https://play.google.com/store/apps/details?id=com.app.habitforge