IssueTracker

I've came accross an article showing how you can rename your "build.gradle" file
http://www.developerphil.com/renaming-your-gradle-build-files/

I empathise for the underlying need behind this article.

Wasting time editing the wrong build.gradle file is one of the most wasteful things of a poor dev life.

But as I commented, there are no bonus points for customizing trivial aspects of your build system.

The real problem is an UX problem. And more precisely an Android Studio UX problem

Bash has a fine UX in this case, it's obvious which file you want to edit

$ fd build.gradle
android/build.gradle
build.gradle
common/build.gradle

But Android Studio makes all those different files looks the same

Gradle Scripts

This is an obviously wrong UX choice (different things should look different)
And one hour invested here would save thousands of hours of confusion on hour side.

A simple solution is to invert the display

Gradle Scripts
> **:android** (build.gradle)
> **Project** (build.gradle)
> **:common** (build.gradle)

Also please put Gradle Scripts the first node of the "Android" hierarchy. If something is wrong in the build system, nothing works. So hiding it after a potentially a very large number of files is not a good idea either