To clarify my statement: the idea of lean Clojure for making Clojure viable for Android development basically works. More static compilation of vars dramatically reduced startup times; I think further "lean Clojure" changes like dependency shaking would bring equally dramatic improvements. I'm handwaving a bit here at the challenges involved in making further changes, but the direction seems quite promising, at least for reducing startup times.
General performance is more difficult to speak for. If it is within a factor of two of Java that seems pretty similar to Clojure vs Java on the desktop and is a tradeoff many are willing to make. It's also true that Clojure relies heavily on Java libraries and Android app performance is highly dependent on underlying library and native performance. So basically for run time performance I don't think the performance of Clojure itself is the most significant factor.
General performance is more difficult to speak for. If it is within a factor of two of Java that seems pretty similar to Clojure vs Java on the desktop and is a tradeoff many are willing to make. It's also true that Clojure relies heavily on Java libraries and Android app performance is highly dependent on underlying library and native performance. So basically for run time performance I don't think the performance of Clojure itself is the most significant factor.