How danilkinkin/buckwheat works
Project type and purpose
• This is a single-module Android mobile application (“Buckwheat”) for tracking and budgeting personal or travel spending.
• It’s built with Kotlin, Jetpack Compose (UI packages like home, history, analytics, etc.), Room for persistence, and a simple DI setup (packages under di).
File structure
• Top-level: Gradle/Kotlin DSL build files, Fastlane for CI/CD, Crowdin config for localization, screenshots, policy/license.
• app/: the only Android module, with:
• src/main/java/com/danilkinkin/buckwheat/... — all code subdivided by feature (UI, analytics, editor, history, wallet, settings, widget, util, effects, etc.)
• src/main/res/ — layouts, drawables, themes, multilingual resources.
• src/androidTest/ — end-to-end tests with fake DI components.
• schemas/ — JSON schemas for the DI DatabaseModule (Room).
• Key architectural clues:
• MVVM pattern (ViewModels in data, editor, recalcBudget, etc.)
• Clean separation: UI packages → ViewModel → Repository/UseCases (di + data/dao + data/entities) → Room Database
• External flows: Crash reporting (CatchAndSendCrashReport), Analytics (analytics package), App Widgets (widget packages)
Extract architecture cues from README
• No server-side component—fully on-device.
• Localization via Crowdin.
• Distribution via Google Play, F-Droid, IzzyOnDroid (handled in Fastlane metadata).
Diagramming recommendations
– Group related components in containers (e.g., “app/src/main/java/com/danilkinkin/buckwheat” as one module)