Meet
07/16/2025, 7:32 AMDocuments folder, mostly used by Android/Kotlin development folders like .gradle, .android, .konan, and old project builds.
The .gradle folder alone was 44GB. We usually delete it to clear space, but then opening different projects means those dependencies just get downloaded again — wasting both time and bandwidth. And sometimes, projects even break due to missing versions.
This led me to two tool ideas that could save both time and storage:
1. Smart Gradle/Cache Cleaner Tool
A tool that scans all your Android/Kotlin projects, checks which libraries are in use, and removes only the unused cache — from .gradle, .android, .konan, and even project-specific build folders. It could keep shared dependencies, offer a dry-run preview, and maybe even auto-clean monthly. This could easily save 20–50GB for active devs.
2. Kotlin/Gradle/AGP Version Prompt in IDE
Every time a project opens, before syncing, the IDE shows a popup comparing the project’s Kotlin, AGP, and Gradle versions with what’s already installed. It lets you choose to update, keep, or cancel — no more unexpected sync failures or unnecessary downloads.
As someone who regularly switches between client and personal projects, I’ve faced these issues more than I can count. I’m curious:
• Would tools like this help your workflow?
• What would you improve or add?
Drop your thoughts or reactionsMeet
07/16/2025, 7:33 AMtapchicoma
07/16/2025, 8:07 AMMeet
07/16/2025, 8:23 AMStefan Oltmann
07/16/2025, 12:37 PMrm -rf my .gradle , .m2 , .konan etc. - especially after I updated a lot of libs at once.
These are all caches, so I won’t use anything.