Lombok is pretty much the same amount of trouble as using a different JVM language, IME. (Though by the same token I'd always pick Scala over Kotlin: if you're going to go to the effort of using another language, you might as well pick the one that offers the most power rather than using the equivalent of CoffeeScript)

Lombok? My first encounter with it was years ago with some annotation called sneaky throws. shudders

You can very selectively disable features and behavior of Lombok. While I've never used the annotation in my current project I can see the use of it in cases where Java's forcing of exception annotation is in your way or forces unnecessary verbosity.

Do you recommend using Lombok now for new Android projects written in Java?

Absolutely not. If you want a better Java on Android, pick Kotlin, which is supported by Google at least.

I have no experience with android projects. I guess it's useful with every Java as it cuts down a lot of the boilerplate.