Really excited about Gemini 3.5 Flash, can't wait to try it out...

https://preview.redd.it/dkl2rvhc152h1.png?width=816&format=png&auto=webp&s=4e4ae5c878fcbc749bfc6b957800f702dfb13688

No matter what I'm doing I can't get rid of this warnings. My last attempt was to bump material and activity ktx libraries. The second warning might be caused by Bottom Sheet library but honestly, I've no idea at this point.

I also cross-checked with Opus 4.6:

Your implementation is correct. No stupid mistakes found. Here's the breakdown:

✅ What's done right

Area	Status
enableEdgeToEdge() before super.onCreate()	✅ Correct
Root Scaffold uses contentWindowInsets = WindowInsets.safeDrawing	✅ Correct
NavHost applies .padding(paddingValues).consumeWindowInsets(paddingValues)	✅ Correct — this is exactly the pattern that prevents double-insetting in nested Scaffolds
Nested Scaffolds use default contentWindowInsets	✅ Fine — because the parent already consumed safeDrawing, the nested Scaffolds inherit WindowInsets(0) automatically via consumeWindowInsets. No manual zeroing needed
All nested Scaffolds apply paddingValues to content	✅ Every screen applies Modifier.padding(paddingValues)
No fitsSystemWindows in XML layouts	✅ Clean
No manual systemBarsPadding/statusBarsPadding calls	✅ Clean
No statusBarColor/navigationBarColor in themes	✅ Clean
Compose theme has no system bar manipulation	✅ Clean
ModalBottomSheet usage (TagCreationSheet, SmartPantry)	✅ Material3 Compose — not affected by the Material view-layer deprecation

https://preview.redd.it/lze098vky42h1.png?width=2262&format=png&auto=webp&s=57bae67ca86ae933e115d97452c6bdf43b92c97e

Frankly, I'm losing it at this point. Any tips, have you guys won the fight with edge to edge? I can link the app to prove that edge-to-edge actually works correctly.

I also wonder whether this warnings influence play store algo and ultimately my organic traffic.

I've been an Android developer for about 5 years. There have been different phases of learning and sharpening my skills. However, I feel it has all slowed down since ai assisted coding became a thing. Of course there have been plenty of other things to learn regarding that, but I'm talking about artisanal software development specifically.

I'm curious whether it's just me or do you guys share this view?

I'm interested to hear stories about impact of localisation on revenue. I'm talking about in app localisation as well as store localisation.

I've got this 50k downloads app 200 euro MRR. App is in English but got a few requests to provide translations.

What's your take? I'm trying to assess roi.

I've got an app that has about 5k active devices, 60k downloads, makes 100-200€MRR. I started to localise app after repeated requests - mainly from Indonesia but also Spain.

Should I care about play store localisation too?

I've got an app that has about 5k active devices, 60k downloads, makes 100-200€MRR. I started to localise app after repeated requests - mainly from Indonesia but also Spain.

Should I care about play store localisation too?