How acristescu/onlinego works
Project type and purpose
• This is a client-only Android application (“OnlineGo”) that lets users play Go against other players on the Online-Go.com (OGS) service, or locally against a built-in AI (KataGo).
• It is not a server or full-stack web app, but it does interact with external services (OGS REST + WebSocket) and hosts a native AI engine via JNI.
File structure
• Top-level “app” module contains all Android code (Java/Kotlin, CMake, native libs).
• “schemas” folder shows Room database versions (16–19).
• src/main/java: organized by feature—ai, data (db, models, ogs, repositories), di, gamelogic, mvi, notifications, playstore, ui (composables + screens), usecases, utils.
• Native code in src/main/cpp with CMakeLists to build KataGo bindings.
• Build scripts: Gradle, proguard, gradle-wrapper.
• README confirms architectures used: MVP, MVI, Room, coroutines, RxJava2, Retrofit.
README for additional insights
• The app employs a mix of patterns: legacy MVP on some screens, modern MVI + Jetpack Compose on others.
• Data layer uses Room for local caching, Retrofit + Moshi for OGS REST, OkHttp WebSocket for real-time.
• Native AI engine (KataGo) bound by JNI to Kotlin via jnibindings.cpp.