This is a modernization of the clojure-android project.

• Run native Clojure on Android
• Develop over nREPL
• Build for F-Droid or Google Play
• Write UIs in a declarative DSL with reactive cells
• Use device sensors as reactive cells
• Use intent callbacks without wanting to smash your device with a hammer
• Fast startup - release builds launch in under 2 seconds on a five year old midrange phone

Google plans to prevent most Android users from installing apps unless the developer registers with Google, giving Google the power to ban developers and apps it doesn't like. See https://keepandroidopen.org/ for what you can do about it.

Clone the sample app and follow the build instructions in its README. It's a template repository and CC0 license, so you are encouraged to use it as a starting point for your own apps.

This is not very mature at this point. A lot of the code was written by a robot; it's plausible, but not necessarily correct, and it works on my machine (tm).

I've used this to build Ceilingbounce, a datalogging app for flashlight reviewers. It's hand written so I've had some opportunity to get a feel for pain points and fix them.

Please try this for your hobby project. Your investors would like me to say please don't bet your company on it.

See the docs repo for mostly machine-generated documentation.

They make the use of a dynamic classloader optional. If you follow the pattern of subclassing ClojureActivity, you don't really have to write any Java.

The source code of the sample app is designed to serve as part of the documentation. It's also helpful to use neko.doc/describe from the REPL.

It requires Kotlin-specific features that aren't straightforward to call via Java interop.

Yes. Your phone is probably a lot faster now. Apps compiled with the current toolchain also launch much faster on the same hardware.

Release builds launch in under 2 seconds on anything remotely modern.

I share your concerns, but I also know that it's perilous to ignore major technological shifts. I wanted to see what LLM coding tools can do, and this seemed like a good project for it since there was an existing implementation to work from and a well-defined success condition.

I wouldn't have done this if I had to do it all by hand, and neither did anybody else in the nine years clojure-android has been unusable.

Now I get to hand-code Clojure for my phone with all the joy inherent in that experience. You can too if you like.

I like hand-coding in nice environments, and I'm not convinced human developers are as obsolete as the AI maximalists would like the world to believe. See the link about plausible code above.

I also think this is a good environment for LLM tools for two reasons. One is that they can use the Clojure REPL via MCP or command-line tools. LLMs make a lot of mistakes, so they're faster and more accurate given a tight feedback loop. The other is that a language which enables more succinct code uses fewer tokens. That makes it cheaper, but more importantly, LLMs consistently produce more correct results when the context is smaller.