Loop Habit Tracker is a mature, open-source Android application for building and maintaining habits through daily check-ins, scoring, streaks, and detailed statistics. The system is architected as a Kotlin Multiplatform project with a shared core module (`uhabits-core`) containing all business logic, models, commands, and platform abstractions, and an Android-specific module (`uhabits-android`) providing the UI, widgets, notifications, and platform implementations. The core uses an MVP-like pattern with presenters, immutable state, and a command pattern for all habit mutations (create, edit, delete, archive, toggle checkmarks). Data is persisted locally in SQLite with a custom migration system supporting 25+ schema versions. The app features extensive home screen widgets (checkmark, score, streak, frequency, history, target), reminders with snooze, Tasker/Locale automation, CSV export, and import from other habit trackers (HabitBull, Rewire, Tickmate). External dependencies include AndroidX, Material Components, Ktor (for sync), AppIntro, and OpenCSV. The codebase demonstrates strong engineering practices: dependency injection via kotlin-inject, platform-agnostic canvas drawing for custom charts, a robust caching layer for list performance, and comprehensive test coverage including unit tests, instrumented UI tests, and snapshot-based rendering tests.
This is a full-featured task, project, and habit management plugin for the SiYuan note-taking application. It implements the 'Bulletproof Note Method' philosophy, integrating tasks, reminders, projects (with kanban and Eisenhower matrix views), habits with check-ins and streaks, a pomodoro timer with detailed statistics, and calendar views (day, week, month, agenda). The plugin goes beyond basic task management with support for natural language date parsing (including lunar calendar), recurring tasks with complex patterns (daily, weekly, monthly, yearly, Ebbinghaus), ICS export/import and CalDAV subscription synchronization, WebDAV/S3 cloud backup, and MCP (Model Context Protocol) integration for AI-assisted task creation. It is monetized via a VIP subscription model with elliptic-curve signed licenses. Architecturally, it is a SiYuan plugin (extends the base Plugin class) with a mix of Svelte components (settings panels) and imperative DOM-based dialogs and panels. The codebase is organized into data managers (singletons for projects, habits, categories, pomodoro records, etc.), utility functions, and UI components (dialogs, panels, renderers). The main entry point is `src/index.ts`, which registers all dock panels, tabs, menus, and event listeners. There is a separate kernel entry `src/kernel.ts` for MCP tool registration, allowing the plugin to be controlled via AI or external scripts. Notable integrations include: ICS subscription (auto-sync external calendars), CalDAV bi-directional sync with allowed providers, Webhook notifications, and S3/WebDAV cloud upload of exported ICS files. The plugin handles mobile notifications, multiple backends (desktop, mobile, browser), and includes data migration helpers for upgrades across its long development history.
This repository is the public-facing support and distribution hub for LifeUp, a closed-source gamified to-do list and habit-tracking Android app. The repository itself contains no application source code whatsoever—only a feature-rich README, promotional screenshots, issue templates (English and Chinese bug/feature reports), a funding placeholder file, and a GitHub Actions workflow that auto-translates non-English issues. The actual LifeUp application is closed source, and the README explicitly states this is intentional, directing users to separate repositories for the SDK, desktop client, wiki, and translations. This repo serves as the official issue tracker, trial-version release channel, and community coordination point. From a code reuse perspective, there is nothing here: no libraries, services, algorithms, or buildable software. Its main value is organizational—describing the app's features, collecting user feedback, and maintaining community resources. The single workflow file merely invokes a third-party translation action and is not a meaningful engineering asset. It is not a data research repository, and there are no data pipelines or notebooks.