terrakok/kmp-awesome

1. This repository is a curated knowledge base, not an application or library codebase. Its “architecture” is mostly informational: one README-driven catalog plus a small image asset folder.

2. The primary subsystem is the README itself. It acts as the single source of truth for the project’s content, structure, and navigation. There are no source packages, build scripts, tests, or runtime components in the repo tree.

3. The content model is taxonomy-based. The README organizes the ecosystem into categories such as tooling, logging, networking, storage, device APIs, dependency injection, architecture, analytics, testing, crypto, file I/O, serialization, date-time, async, Compose UI, graphics, service SDKs, arithmetic, resources, and utilities.

4. Each catalog entry follows the same pattern: project name, external repository link, optional Maven Central badge, and a short description. That makes the README function like a structured index rather than prose documentation.

5. The main “data flow” is editorial: maintainers collect Kotlin Multiplatform libraries, verify they support Android and iOS first, confirm Maven Central publication, and then add them into the appropriate category. Consumers browse the list and click out to external library sites.

6. The repository depends heavily on external platforms for meaning and freshness. GitHub hosts the upstream projects, Maven Central provides artifact verification badges, and Awesome/PR badges communicate repository status and contribution openness.

7. The img/ directory is the only local asset boundary. It contains the repository icon and the banner illustration used in the README header, so the visual identity is embedded but kept separate from the curated text content.

8. Governance is explicit and important to the structure. The contribution guide defines acceptance criteria for new entries: real-world usage links, Android + iOS support, Maven Central publication, and a popularity threshold. This acts as the curation policy for the whole repo.

9. The repository’s audience is developers evaluating Kotlin Multiplatform options. Its output is not compiled software but a maintained reference list that helps teams choose libraries across architectural concerns like networking, state management, persistence, UI, and tooling.

10. For an architecture diagram, the correct shape is: maintainer/editors update README and assets → GitHub renders the catalog → readers navigate categories and external links → external library repos and Maven Central provide the referenced implementation and package metadata.