Minimum System Requirements & Compliance: Android Application

The Shustree mobile application is engineered for high-performance, low-level network routing. Unlike generic wrappers, the core architecture relies on our fully proprietary, custom-built TCP/UDP engine operating directly at the transport layer, while utilizing Jetpack Compose for a modern declarative user interface.

Core Software Specifications

Our build environment sets strict operational boundaries to guarantee the cryptographic integrity of our custom network tunnels and overall system stability:

• Minimum SDK Version: API Level 24 (Android 7.0 Nougat). The application cannot be installed or executed on legacy devices running API levels below this threshold.
• Target & Compile SDK: API Level 35 (Android 15 / Vanilla Ice Cream). This ensures full compatibility with modern Google runtime environments, advanced system-level background execution restrictions, and contemporary sandbox isolation models.

Proprietary L4 Architecture & Hardware Runtime

The Shustree Android client features an incredibly optimized, native-like runtime memory footprint. However, users should account for the robust multi-threaded processing required by our custom network stack:

Engine Specifics and Concurrency: Instead of relying on standard high-level libraries, Shustree deploys a completely in-house TCP/UDP machine implementing proprietary L4 protocols and custom end-to-end encryption mechanics. To maintain line-rate packet processing, state synchronization, and tunnel resilience, the core application runtime guarantees the execution of 5 dedicated system threads supplemented by approximately 5 active Kotlin coroutines. (Note: The Ktor framework is strictly isolated and utilized exclusively as a lightweight client for control-plane API calls).

On legacy or ultra-low-end SOCs (System-on-Chip), this concurrent execution model may induce minor CPU overhead due to continuous, low-level cryptographic operations performed by our proprietary transport engine.

Disclaimer regarding Customized OEM Roms

Users deploying Shustree on heavily customized Android distributions (including, but not limited to, aggressive proprietary ecosystems from various Chinese smartphone manufacturers like TECNO, POCO and some other brands) may encounter atypical operational failures.

Certain OEM software profiles implement non-standard background process managers that prematurely terminate network services, modify default VPNService prioritization rules, or restrict concurrent coroutine threads to enforce artificial power-saving metrics. If your secure tunnel unexpectedly drops, ensure that Shustree is explicitly excluded from your device's system-level battery optimization and process-killing protocols.

Google Play Developer Compliance & Integrity

The Shustree application fully conforms to the strict regulations established by the Google Play VPNService Policy. Under these legal guidelines, the deployment of the system-level VpnService API is strictly limited to applications acting as core communication gateways.

Shustree satisfies all operational and identity transparency mandates established by Google for security-critical service providers:

• Verified Organizational Status: In accordance with Play Console mandates for VPN service publishers, Shustree operates under a verified, formal Organization Account profile rather than an individual developer designation.
• D-U-N-S Registration: Our business structure and infrastructure legal identity are officially verified by Dun & Bradstreet under the global data universal numbering system with DUNS Number: 933899214.
• Data Protection Standards: We strictly adhere to the non-monetization clause of the VPN policy. Because our L4 protocols and encryption are completely proprietary, no traffic data can be inspected, intercepted, or harvested by third-party SDKs or intermediate nodes.