Acode: an Android code editor built on Cordova, Ace and a plugin API

What Acode solves, and who is actually editing code on a phone

Acode is a code editor for Android. The README frames the audience directly: people working on HTML, CSS and JavaScript who want to code on the go, plus anyone modifying source files for Python, Java and other languages from a phone or tablet. The differentiator is the file system workspace. A browser-based editor on Android is limited to what the browser sandbox exposes; Acode ships as a Cordova application, so it can reach device storage through plugins such as cordova-plugin-file and cordova-plugin-sdcard. That is the whole point of the project. If your workflow is "open a real directory, edit files in place, preview the result," the mobile browser tab is the wrong shape for the job. Acode is also not a general-purpose text editor with syntax colours bolted on. The README lists a built-in JavaScript console, multi-language editing with management tools, and a collection of community plugins. The plugin API is documented separately at docs.acode.app and in the acode-plugin repository, which tells you the maintainers expect third parties to extend the editor rather than fork it.

Cordova shell, Ace core, and a plugin layer that carries the platform features

The architecture is visible in package.json. The package name is com.foxdebug.acode and the keywords array contains a single entry: ecosystem:cordova. The cordova.plugins block lists the native capabilities the editor depends on. cordova-plugin-file and cordova-plugin-sdcard handle storage, cordova-plugin-server and cordova-plugin-websocket handle local serving and live connections, cordova-plugin-ftp and cordova-plugin-sftp cover remote transfer, and a set of com.foxdebug.acode.rk.* plugins (terminal execution, plugin context, auth, proot execution) carry the more privileged operations. That list is the real feature matrix. Anything not backed by a Cordova plugin cannot work on the device.

The repository layout separates concerns cleanly. src/ holds core code and language files, www/ holds public documents, compiled files and HTML templates, and utils/ holds CLI tools for building and string manipulation. The editor itself is Ace-based: package.json includes an updateAce script, so the Ace editor is vendored and refreshed rather than pulled as a normal dependency. The README's language instructions confirm the pattern. To add a language you create a file named with the language code, such as en-us, in src/lang/ and register it in src/lib/lang.js. There is no runtime language download. Localisation is a build-time concern.

Installing Acode on Android and opening a first project

The README gives two distribution channels and no source install steps for end users. You get Acode from Google Play under the application id com.foxdebug.acodefree, or from F-Droid under the package com.foxdebug.acode. If you want the APK directly, the README does not link one; it points at those two stores. Once installed, the first useful action is opening a folder rather than a single file, because the workspace is what distinguishes Acode from a viewer. The README describes the workflow as editing and creating websites and previewing them in a browser, so the shortest path to a real result is an HTML file with a linked stylesheet and script.

For anyone building the application itself, the README defers to CONTRIBUTING.md for detailed instructions. The scripts in package.json show the intended entry points:

pnpm run setup
pnpm run dev:android

The setup script is node ./utils/setup.js and the Android dev script is node utils/scripts/dev.js android. A full build goes through utils/scripts/build.sh. Note that the README's own language-management examples use pnpm:

pnpm run lang add
pnpm run lang remove
pnpm run lang search
pnpm run lang update

Those four commands drive node ./utils/lang.js. The repository also carries package-lock.json and bun.lock alongside each other, and the admob build script uses npm ci --prefix src/plugins/admob. The lockfile situation is not explained anywhere in the README, so pick one package manager and stay with it.

Where Acode is the wrong tool

The release history is the first constraint. The recent releases listed for this repository are all nightlies: 1.13.1-nightly.5612038, 1.13.1-nightly.8d7148a and 1.13.1-nightly.3387ceb, dated 2026-08-26 and 2026-08-27. Meanwhile package.json declares version 1.13.5. The nightly version string and the package version do not line up, and nothing in the README explains the relationship between them. If you need a predictable release channel with a changelog you can diff, this is a poor fit. The CHANGELOG.md file exists at the top level, but the README does not describe a release cadence.

Second, the build path assumes Cordova and Android tooling knowledge. The README says only "See CONTRIBUTING.md for detailed instructions." It does not document prerequisites, JDK versions, SDK levels or what the gradle and fastlane directories expect. Several scripts shell out to .sh files, so the build is oriented toward a Unix-like host.

Third, the plugin dependency list is a liability as much as a feature. Every native capability routes through a Cordova plugin, including third-party ones and a set of com.foxdebug.acode.rk.* plugins that appear to be maintained alongside the app. A plugin that stops tracking a new Android API level takes the corresponding feature with it. The README does not state a minimum supported Android version, which is the single fact most likely to rule Acode out for a fleet of older devices.

Acode against Termux and against desktop editors

The honest comparison is not Acode versus VS Code, even though that is what people search for. It is Acode versus running a terminal on the same phone. Termux gives you a real shell, a real package manager and real language runtimes; Acode gives you a graphical editor with a file tree, syntax highlighting and a JavaScript console. They solve different halves of the problem. Acode's advantage is that editing is the primary interaction and the file system is exposed through a UI; Termux's advantage is that nothing is mediated by a Cordova plugin, so the toolchain is whatever you install.

The second comparison is Acode versus a desktop editor reached over SSH or a sync service. That setup wins on CPU, screen size and extension ecosystem, and loses on latency and offline use. Acode's own plugin story is the closest thing it has to an extension ecosystem, and the README points plugin authors at the acode-plugin repository and docs.acode.app rather than describing the API inline. So the decision is less about features and more about where the files live. If the code is already on the device and you want to edit it there, Acode is aimed at you. If the code lives on a server, an SSH client plus a terminal editor is a shorter path.

Licence, maintenance signals and what an upgrade costs

Acode is MIT-licensed. The repository carries license.txt and package.json declares "license": "MIT". For most users that is the end of the story: MIT permits commercial and private use, modification and redistribution, provided the copyright notice and permission notice are preserved. If you fork Acode and ship it, keep license.txt intact. If you bundle the Cordova plugins listed in package.json, check each one separately, because the MIT licence on the application does not automatically cover every dependency. That is a factual boundary, not legal advice; a lawyer should review anything you ship commercially.

The last push to the default branch was on 2026-08-27, and the repository is not archived. That is recent enough that calling the project maintained is fair, but the evidence for it is commit activity and nightly builds, not a tagged release. The upgrade cost is concentrated in two places. First, the Ace editor is vendored, so a version bump means running the updateAce script and re-testing the editor surface. Second, the Cordova plugin set is the compatibility surface with Android, and each plugin upgrade is a separate decision. Neither cost is documented in the README. CONTRIBUTING.md is where you would look, and the README explicitly sends you there.

Editorial conclusion

Adopt Acode if you edit files on an Android device and want a real file system workspace, a JavaScript console and a plugin API rather than a web-only editor. Do not adopt it if you need a desktop IDE, a stable tagged release, or a documented build path that does not assume you already know Cordova. Before committing, open CONTRIBUTING.md and confirm the build script works on your machine, check whether the nightly version in package.json matches the release you intend to ship, and read the plugin documentation at docs.acode.app to see whether the API covers the hooks you need.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes