Bansify Computer is a Kotlin Android application that presents a desktop-style environment with an app grid, taskbar, floating built-in windows, file manager, browser and web-app shortcuts. It runs on Android devices (including devices without a touchscreen); it is not a Windows emulator and does not run Windows executables.
Current state: The manifest registers a Home candidate; the user must choose it in Android settings. Initial recovery support is not yet verified on real TVs or tablets: keep another launcher installed and do not rely on this as your only Home. Some settings and legacy TV-related configuration are incomplete. See the analysis and Phase 1 / Phase 2 test protocols.
- Desktop grid, start menu, taskbar, app search, notifications and settings.
- Launch installed Android apps; hide, pin and arrange desktop entries.
- In-app floating windows for File Manager, Web Browser and Bansify Store.
- Browser-based shortcuts (
pwa://entries), not separately installed Android packages. - Optional launcher-level app/device locks, overlay taskbar, custom wallpaper and display settings. These are not substitutes for Android system security.
- Limited, opt-in per-device shortcuts for Start, Search and Quick Settings under System settings. They work only on the Home desktop; Android may reserve or withhold keys.
Private browsing, browser uploads/file drops and website camera/microphone/location are currently unavailable. Normal browser sessions share WebView data; some websites may not work. File moves across filesystems are unavailable to avoid unsafe copy/delete. See release blockers and limitations.
The UI uses Android Views, XML, ViewBinding, Fragments and RecyclerView. Do not add Compose: see AGENTS.md.
| Item | Current configuration |
|---|---|
| App ID / namespace | com.gothwad.computer |
| Minimum / target / compile SDK | 21 / 34 / 34 |
| Java / Kotlin | JDK 17 / Kotlin 2.0.20 |
| Android Gradle Plugin / wrapper | 8.5.2 / Gradle 8.7 |
| Default version | 1.0.6 (code 7); overridable via Gradle properties |
| Persistence | Preferences DataStore, JSON files, SharedPreferences and internal files |
The Gradle/AGP pair above is what is checked in, not a compatibility guarantee; see build limitations.
Prerequisites: JDK 17, Android SDK Platform 34 and matching SDK Build Tools, plus network access to the Gradle distribution and the Google/Maven/plugin repositories. Open the project in a compatible Android Studio or configure ANDROID_HOME / local.properties yourself.
# Build the debug APK
./gradlew assembleDebugDebug output: app/build/outputs/apk/debug/. Build release artifacts with:
sh ./gradlew assembleRelease bundleReleaseSigning-key change: the owner reports that v1.0.20 used an incorrect signing key. New releases use the corrected key and may not upgrade over v1.0.20 in place. Uninstalling can erase local app data: back up first, test migration, and keep an alternate Home installed.
Release builds are unsigned by default. For local testing only, -PlocalSign uses a debug signing key; do not distribute that as a production release. app/build.gradle.kts also supports CI signing with KEYSTORE_FILE, KEYSTORE_PASSWORD, KEY_ALIAS and KEY_PASSWORD. The GitHub workflows instead build and sign in a separate step using repository secrets; see the CI section.
- Full project analysis and developer guide: architecture, flows, storage, permissions, security findings, build/CI and test plan.
- Developer rules: native-Views-only architecture.
- Five-phase Home launcher master plan: consolidated roadmap, acceptance gates and release-readiness criteria.
- GitHub automation: dependency updates, AI review, scanning, CI and owner setup.
- Release blockers and limitations: unfinished gates and deliberately disabled unsafe features.
- Historical lock design notes: superseded by the master plan; do not use as an implementation specification.
The old README stated Apache 2.0, but this checkout has no LICENSE file. Confirm the intended license with the project owner before redistribution or adding a license file.