Understand appflowy-io/appflowy's source layout and find a starting point for your task using the saved repository evidence.
Detailed import-graph metrics were not captured for this report.
Files at 5cf3a365dec0 · descriptions are AI-written.
Suggested by the saved analysis. Some step paths were not captured or refer to generated or vendor files; only observed source files are linked.
Suggested by the saved analysis. Verify the proposed change against these source files.
Suggested by the saved analysis. Some step paths were not captured or refer to generated or vendor files; only observed source files are linked.
Use a nearby test as a pattern. Read the root manifest or contribution guide for the correct test command. These suggestions use file names, not verified execution paths.
Inspect the relevant configuration and the commands it runs before changing the workflow. These suggestions use file names, not verified execution paths.
File paths come from a snapshot of up to 500 captured paths; an omitted file may still exist.
Build orchestration for the Flutter frontend; defines compilation, testing, and deployment targets.
Android build configuration; specifies dependencies, SDK versions, and native compilation settings.
Dart/Flutter static analysis rules; enforces code quality and style consistency across the codebase.
Top-level Rust/Cargo build automation for the backend; orchestrates frontend and backend compilation.
CI/CD pipeline configuration; defines automated build, test, and release workflows across platforms.
Commit message linting rules; enforces conventional commit format for changelog and release automation.
Project overview and setup instructions; essential reference for understanding AppFlowy's purpose and contribution guidelines.
Flutter + Dart
Single codebase for iOS, Android, Windows, macOS, and Web; fast hot reload for iteration.
Rust Backend (inferred from Makefile.toml)
High-performance, memory-safe server for collaborative features and AI integration.
Android Gradle + CMake
Native Android build system with C/C++ support for platform-specific optimizations.
AGPL-3.0 Licensing
Ensures open-source transparency and community-driven development as Notion alternative.
Build-time
Runtime
Flutter for cross-platform UI instead of native per-platform
Faster time-to-market and consistent user experience across platforms.
Platform-specific features (e.g., native OS integration) require JNI bridging and platform channels.
Bundled AI prompts (built_in_prompts.json) instead of dynamic server fetching
Offline-first support and reduced latency for common use cases.
Prompt updates require app version upgrades rather than server-side changes.
Monorepo structure (frontend + backend in single repo)
Simplified dependency management and coordinated releases.
Larger clone size and potential build conflicts between subsystems.
This repo is in good health with CI, tests, and active maintenance.
How maintainable the code looks — from complexity, code issues, test presence, file size, and hotspot load. It grades the shape of the code, not defect risk, and doesn't replace review.
Provider: GitHub Actions
330 test files detected
Where: frontend/appflowy_flutter/test/bloc_test/board_test · frontend/appflowy_flutter/assets/test/images · frontend/appflowy_flutter/assets/test/workspaces
330 test files / 675 source files. This is a file-count ratio, not real line coverage — set up Codecov for authoritative numbers.
No Dependabot / Renovate / Snyk / Trivy / CodeQL config found. Enable Dependabot or Renovate.
Files edited often AND hard to reason about. Churn = recent commit frequency, Complexity = branches and nesting, Risk = both combined. These are the highest-leverage targets for refactoring or testing.
Files that change often and are complex tend to accumulate more bugs
Pattern-matches from the file structure and dependencies — useful as hypotheses, but not grounded in actual source. For real findings see Code Scanning above.
Embedding prompts as static JSON requires app updates to modify; inflexible for experimentation and A/B testing.
frontend/appflowy_flutter/assets/built_in_prompts.json
Lack of clear module separation increases coupling risk; frontend and backend changes can conflict during builds.
frontend/appflowy_flutter and (inferred) backend root
Direct JNI usage is error-prone and difficult to maintain; no abstraction layer for platform-specific logic.
frontend/appflowy_flutter/android/app/src/main/Classes/binding.h
Speculation from file structure, not profiling data. Validate against real metrics before acting on these.
Single CI/CD orchestration point; failure here blocks all platform releases (Android, iOS, Web).
codemagic.yaml (CI/CD pipeline)
All collaborative edits and AI requests funnel through backend; high contention point under load.
Rust Backend (inferred from Makefile.toml)
Prompts loaded at app startup; large prompt library could delay initial UI render.
built_in_prompts.json asset loading
Serialization/deserialization overhead on every backend request; potential latency bottleneck for real-time collaboration.
Flutter Frontend (platform channel communication)
Static analysis on sampled source files (up to 15 files).