QPython: the newcomers' branch is this repository, and the newest binary is from the other one
QPython is an Android Python engine primarily designed for Python and AI learners. It offers a range of impressive features to enhance Python programming experience.
At a glance
- What is it?
- An Android Python engine built around SL4A so scripts can drive the device itself, with an editor, runtime and plugin manager. It is described as free and open source, there is no LICENSE file at the root, and the newest tagged release is from February 2023 while commits continue.
- Who is it for?
- QPython fits an Android user who wants to script the device itself rather than just run Python on it, and who can tolerate an alpha-grade tool with a wiki instead of setup documentation. It does not fit anyone who needs a current tagged build or clear licensing.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Activity is slowing. The repository last received commits 7 months ago.
- What is it written in?
- Mainly Java, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- qpython-android/qpython1,228 ★ · +14
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| qpython-android/qpython | 1.2k | 1.2k |
14 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
This repository is the beginners' branch, not the newest build
QPython ships as two branches and the distinction decides which repository you want. Ox is aimed at programming learners and provides friendlier features for beginners. 3x is aimed at experienced Python users and provides advanced technical features.
The repository you are reading is the Ox project repository. The Quick start section says so explicitly. So the tree you are about to clone is the beginners' line.
The newest build, meanwhile, is advertised on the other line. The related links point at QPython 3.2.5, hosted as a file on Google Drive, which belongs to the 3x branch rather than to Ox. So a newcomer who clones this repository and a user who installs the advertised binary are running different code.
The release history makes the gap concrete. There are three tags: an Ox beta from 2020-02-08, version 3.0.1 from 2021-12-17, and v3.2.3 from 2023-02-08. The newest tag is therefore more than three years older than the last commit, which is dated 2026-04-14. Work has continued on the default branch without a new tag, and the current binaries travel through a Drive link rather than a release page.
For a project whose users install an APK, that distinction between what is built and what is tagged is the difference between a version you can name and one you cannot.
Free and open source, with no license file at the root
The project describes itself in two ways that a reader will want reconciled. It says it is free, and it says it is also an open source project, and it adds that it has millions of users worldwide.
The repository root does not support the second claim in the way a reader would expect. There is no LICENSE file in the tree listing, and the repository's license metadata carries no recognised identifier. Nothing in the file states what may be done with the code.
That is a real gap for an Android engine whose components are spread across several repositories. The related links point to separate repositories for the documentation site, the SL4A bindings, the package index and this engine, and each of those would need its own answer.
Two other files in the root are the ones an Android project normally keeps out of version control. A debug.keystore file is committed, which is the shared debug signing key every Android sample project ships with. A local.properties file is committed too, which is where the local SDK path lives. Both are harmless in the sense that the debug key is public by design, and both are the kind of artefact that indicates the ignore rules were written before the build was wired up.
Clone over SSH, then the build step is two words
The entire setup procedure fits in six lines, and one of them is a placeholder.
git clone [email protected]:qpython-android/qpython.git
git submodule init
git submodule sync
git submodule updateThree things are worth noticing. The clone URL is the SSH form, so a contributor without a key configured has to rewrite it before the first command runs, and the README offers no HTTPS alternative. The submodule sequence is spelled out in full rather than collapsed into a single recursive clone, which means the project expects people to know why submodules matter here. And after those commands the list says build it, with a link to the wiki for anything further.
So the setup path is: an operating system pair named first, macOS with Android Studio and a note that Ubuntu may work too, then the clone, then the submodules, then the wiki. There is no Gradle invocation in the file even though the repository ships a Gradle wrapper, a settings file and a project properties file, which is a strange omission for a Java project whose build system is that visible.
The practical consequence is that this repository is not self-explanatory to build. A newcomer who cannot get to the wiki has no path.
Three repositories, three issue trackers
Bug reports are split across three repositories, and the split is by object rather than by severity.
An app problem goes to the issues of this repository. Anything that is not about the app goes to the documentation site repository. A request to support a particular package goes to the package index repository. That last split is the useful one: asking for a package to be made available is not a bug in the engine and is not a bug in the documentation, so it has its own queue.
The same division runs through the related links. Feature documentation for both branches lives in the documentation repository as two source files, one for the 3x features and one for the Ox features. The SL4A API reference lives in the SL4A repository, and the test scripts for those bindings are linked as an entry in that repository's issue tracker rather than as a directory, which suggests the tests are discussed in a thread rather than published as a suite.
So the project is one engine, one documentation site, one package index and one bindings library, with a triage rule that sends each kind of question to the right one of the four. That is more thought than most projects of this size put into issue routing, and it is documented in a handful of links.
The engine is the secondary part, SL4A is the point
What the project says it contains is a Python interpreter, a runtime environment, an editor, something called QPYI, and integrated SL4A.
The differentiation sentence follows immediately, and it is not about the interpreter. Compared with other Python apps, the claim is that QPython solves how to use Python to drive the Android device, and that good SL4A support is the main goal, naming the camera, sensor, and SMS media APIs among the targets.
That reframing explains the repository layout better than the feature list does. Two directories in the tree are named for terminal work, one for the emulator and one for command execution, and the component directories follow the platform rather than the language: a base library, an FTP library, a plugin manager, an SDK directory, the SL4A directory, and the Python directory itself.
So the product is a Python runtime plus a bridge to device capabilities, plus the pieces needed to make it usable on a phone: an editor, a terminal, and a plugin manager. Someone choosing between Android Python apps is being asked to compare two different things, whether they realise it or not.
What the project does not offer in the README is any statement about which Android versions it supports, or which Python version it embeds, which is the first thing a person would look for.
The component layout is a dozen directories
The tree is a Gradle multi-module project with a directory per subsystem rather than a single app module.
Alongside the usual Android project files, build.gradle at the root, settings.gradle, gradle.properties, a gradle directory and the Gradle wrapper scripts for both platforms, there are eleven component directories: qbaselib, qftplib, a plugin manager directory, an SDK directory, the SL4A directory, the Python directory, the two terminal directories, and a utilities directory. There is also a docs directory at the root and a .gitmodules file, which is the file that makes the three submodule commands in the quick start necessary.
Two of the names are opaque until you read them. qbaselib is the base library the rest builds on, and qftplib is an FTP library, which suggests file transfer to and from a device is a shipped feature rather than something users implement themselves.
The plugin manager is worth noting on its own. A Python engine on Android that also has a plugin system and an SDK directory is built to be extended, which is consistent with the project positioning itself for learners who will keep building after the first script.
Nothing in the README maps these directories to features. That mapping lives in the wiki, which is the same place the build instructions live, and it means the repository and its documentation are effectively one artefact split across a code host and a wiki.
Support is split by audience, and bug reports ask for a lot
The project routes people to four different communities depending on who they are. General users are pointed at a Facebook group. Contributors are pointed at a Slack workspace. Everyone has a Discord server. And Chinese speakers are given a WeChat group that requires scanning a code in the README and sending a friend request with a specific comment.
That is an unusual amount of channel management for a project of this size, and it suggests the user base is large and split across regions rather than concentrated in one place.
The bug report request is unusually specific as well. It asks for the phone's information, the Android OS information, which QPython branch was used, the code, where the app was installed, and a description of the situation encountered. Five pieces of context before anyone will look at a report.
Some of that makes sense for a device-specific runtime, where the same Python code behaves differently across models and Android versions. Some of it is a documentation gap showing through: the README states no Android version range and no embedded Python version, which are exactly two of the five things a reporter is asked to supply.
The file also carries typos in that paragraph, in the words for information and situation, which is a small signal that the surrounding documentation is maintained by people whose time goes into support rather than into editing.
Editorial conclusion
QPython fits an Android user who wants to script the device itself rather than just run Python on it, and who can tolerate an alpha-grade tool with a wiki instead of setup documentation. It does not fit anyone who needs a current tagged build or clear licensing. Verify four things before you depend on it. Establish the licensing terms yourself, because the README calls the project free and an open source project while the repository root has no LICENSE file and the license metadata carries no recognised identifier. Check which branch you are actually installing, since this repository is the Ox branch aimed at learners while the newest advertised build is version 3.2.5 from the 3x line. Plan around the release gap: the newest tag is v3.2.3 from 2023-02-08, the binaries are linked from a Google Drive file, and the last commit is dated 2026-04-14. And read the submodule sequence before cloning, because the quick start clones over SSH and needs three submodule commands before the build, whose instructions are one word long. Support is community-run across Facebook, Slack, Discord and WeChat, and bug reports are asked to include the phone model, the Android version, the branch and the code.
Frequently asked questions
what is qpython
QPython is a Python engine for Android, containing a Python interpreter, a runtime environment, an editor, QPYI and integrated SL4A, and it is free. Its stated focus is not competing on the interpreter but on driving the Android device from Python through SL4A, naming the camera, sensor and SMS media APIs among its targets. It ships in two branches, Ox for learners and 3x for experienced users.
how to install qpython
This repository does not describe installing an app. It describes building one: clone the repository over SSH with git clone [email protected]:qpython-android/qpython.git, then run git submodule init, git submodule sync and git submodule update, with macOS plus Android Studio named as the environment and the wiki holding the remaining detail. To get a released build instead, the newest version is linked as a file on Google Drive.
qpython alternative
The repository does not name any alternative, so this article will not either. What it does state is its own position: QPython is built around SL4A support so scripts can use device capabilities such as the camera, sensors and SMS media APIs, and it splits into an Ox branch for programming learners and a 3x branch for experienced users carrying the advanced technical features.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/qpython-android-qpython)Star history chart for your README
[](https://hysenlabs.com/projects/qpython-android-qpython)Was this useful?