Frequently asked questions¶

Does an ApkPy APK contain Python?¶

No. ApkPy generates Java, XML, resources and a Gradle project. The APK runs as a native Android application without embedding a Python interpreter.

Can I open the result in Android Studio?¶

Yes. apkpy build creates a normal Android project that can be inspected and compiled in Android Studio.

Does every Python library work on Android?¶

No. ApkPy translates its documented declarative API and supported Python patterns. An arbitrary desktop Python package does not automatically become Java.

Is the Hot Previewer an Android emulator?¶

No. It is a fast desktop renderer for layout and callbacks. Android permissions, services, codecs, FCM, GPS and OEM behavior require an emulator or device.

It can generate much of the native client. Accounts, moderation, payments, recommendations, dispatch and canonical server data remain application infrastructure. See Can ApkPy build this?.

Is local data encrypted?¶

ApkPy provides encrypted local values and password hashing, but security still depends on correct key handling, server authorization and threat modeling.

Is the generated project conditional?¶

Yes. Feature helpers and dependencies are emitted only when the source uses the matching capability.

What happens to work when the app is closed?¶

Work declared with background_job() is handed to WorkManager, which stores the queue in its own database. It survives backgrounding, process death and a reboot, and runs when the declared constraints allow it. See Background jobs.

Is ApkPy open source?¶

Not currently. ApkPy is actively developed as proprietary software. The maintainer may choose to open-source the core later and commits to doing so if the project is permanently abandoned, allowing others to continue it. A pause or slower release cadence does not change the present licence; an open-source transition requires an explicit announcement, published source and a named new licence. See Project continuity.