How r0rt1z2/grindrplus works
Project Type & Purpose
• This is an Android application that serves two roles:
1. A “Manager” app (built in Jetpack Compose/Kotlin) which downloads, patches, signs, and installs a modified version of the official Grindr APK using either LSPosed or LSPatch.
2. An Xposed-style module that hooks into the running Grindr process at runtime to modify behavior and unlock features (via individual Hook classes, a Command system, a BridgeService, and persistent storage).
• Purpose: Provide an installer/manager GUI for end users and inject mod features into the target Grindr app process.
File Structure Analysis
• Top level:
• .github & CI workflows (build APK, fetch version)
• Scripts: fetch_version.py
• Gradle (build scripts, libs.versions.toml)
• crowdsourcing config: crowdin.yml
• app/ module (the only code module):
• build.gradle.kts, proguard rules, third-party JARs and lspatch binary assets
• src/main/AndroidManifest.xml
• AIDL definitions (IBridgeService) under aidl/com/grindrplus/bridge
• assets/lspatch (native .so files per ABI)
• assets/translations (i18n JSON files)
• Java/Kotlin code organized into packages:
– com.grindrplus.manager (UI screens, ViewModels, installation flow steps)
– com.grindrplus.bridge (BridgeService + client for IPC using AIDL)
– com.grindrplus.commands (command DSL + handlers for in-app console)
– com.grindrplus.core (shared utilities: config, HTTP client, database helper, scheduler)
– com.grindrplus.hooks (≈30 individual hook classes implementing features)
– com.grindrplus.persistence (Room database: entities, DAOs, converters, mappers)
– com.grindrplus.ui/components & theme (Jetpack Compose widgets)
– com.grindrplus.utils & tasks (feature manager, hook manager, task scheduler)
Key README Insights
• Architecture isn’t explicitly drawn but describes two distinct modes (LSPosed vs LSPatch), an installation pipeline (download → patch → sign → install), runtime hook injection, and a built-in command console.
• Dependencies: Room, Retrofit, Xposed APIs, AIDL-based IPC.
a. Main Components
1. Android Device (host environment)
2. Manager App UI (Jetpack Compose screens + ViewModels)
3. Installation Pipeline
– Downloader (HTTP client)
– LSPatch native binaries (assets)
– Apk Cloner/Patcher (ManifestPatcher, Signer)
– SessionInstaller (file operations, zip extraction)
4. Original Grindr APK (external input)
5. Modified Grindr APK (output of pipeline)
6. Xposed Runtime (LSPosed or LSPatch host)
7. Grindr Process (modified)
8. BridgeService (AIDL service inside Grindr process)
9. Hook Modules (classes under hooks/)
10. Command Console (in-app command interpreter hooking UI)
11. Persistence Layer (Room DB)
12. External Services
• Google Maps API
• Google Login (GMS)
b. Relationships & Interactions
• On launch of modified Grindr, Xposed runtime loads Hook Modules into Grindr process
• Hook Modules intercept target methods, call into Core utilities or CommandHandler
• BridgeClient (in Manager) binds to BridgeService (in Grindr) via AIDL; bi-directional calls to enable toggle of features at runtime
• HookModules read/write Settings and persistent data via GPDatabase (Room)
• Some hooks (e.g., maps) make HTTP calls via Retrofit (Core/http/Client) to external APIs
c. Architectural Patterns & Principles
• Modular Hook classes: Single-responsibility per feature
• Command pattern for in-app console commands
• MVVM (Manager UI: ViewModels + Compose)
• Repository/DAO pattern (Room database)
• Service-based IPC (AIDL BridgeService)
• Task scheduling via CoroutineHelper + TaskScheduler
d. Key Technologies & Frameworks
• Kotlin + Jetpack Compose
• Android Architecture Components (ViewModel, Room, LiveData)
• AIDL (inter-process service)
• Retrofit + OkHttp (Core/http)
• Xposed APIs (for method hooking)
• Gradle Kotlin DSL for build
• GitHub Actions for CI (build_apk.yml)
Essential Details to Capture
• Distinct separation of concerns: UI vs installer vs runtime hooks
• Assets (lspatch .so files) feeding into the Apk Patcher
• Call out Database schema (GPDatabase + DAOs) as the single source of persistent state
• Xposed runtime as the loader/environment that wires hooks into target app