CoolMallKotlin, also called 青商城, is an open-source Android e-commerce application written entirely in Kotlin on top of Jetpack Compose, intended for Android developers who want a working reference for a modern, modular app architecture and a complete shopping flow.

What it is

CoolMallKotlin is an e-commerce application for Android built with Kotlin and Jetpack Compose and released under the MIT licence. It follows the architecture Google recommends, combining MVVM with Clean Architecture inside a modular project layout whose structure is modelled on Now in Android. The core commerce flow is described as essentially complete: user authentication, product display, shopping cart and order payment are all implemented, and the interface follows Material Design 3 with light and dark themes plus Chinese and English localisation. The project is the work of a single independent developer across more than half a year of spare time, and the README states plainly that progress is slower than a full-time team's and that some features remain unpolished.

The concrete problem it solves is the gap between Android architecture samples and a real commercial application. Most reference projects stop at one screen backed by a fake repository, so anyone starting a shopping app still has to assemble navigation, dependency injection, networking, local storage, image loading, permissions and session state by hand. CoolMallKotlin ships those pieces already wired together, so a developer can read how a feature module is separated from the data layer, how Hilt supplies dependencies, and how cart and order screens share state. API documentation is published alongside the code, and a companion scaffold exists for teams who want the same stack without the mall domain.

Key capabilities

• Customer-facing commerce flow covering user authentication, product display, shopping cart and order payment, each handled as its own feature module.
• Modular architecture with Clean Architecture layering and MVVM presentation, keeping feature modules decoupled from shared data and domain code.
• Navigation built on Navigation3 1.0.1 with Lifecycle ViewModel Navigation3 2.10.0, and dependency injection through Hilt 2.59.2.
• Networking through Retrofit 3.0.0 and OkHttp 5.3.2 with Kotlinx Serialization 1.10.0 for JSON, and Coil Compose 2.7.0 for image loading and caching.
• Local persistence using Room 2.8.4 for SQLite data and MMKV 2.4.0 for high-performance key-value storage.
• Asynchronous work through Kotlin Coroutines and Flow 1.9.0, with Timber 5.0.1 for logging and XXPermissions 28.0 for runtime permission requests.
• Debug builds bundle LeakCanary 2.14 and Chucker 4.3.1; a long press on the launcher icon opens Leaks and Open Chucker directly, while JUnit 4.13.2 covers unit and UI tests.

Who uses it and how

• Android developers studying a full Kotlin and Compose stack end to end, using the repository as a reading reference for module boundaries and Clean Architecture layering.
• Teams seeding a new product on the same stack, starting from the AndroidProject-Compose single-module scaffold, which keeps basic capabilities and example routes and runs immediately after cloning.
• Evaluators who want to try the app before compiling it, using the prebuilt APKs on Pgyer: the Release build at 3.6 MB, the Debug build at 19 MB, both supporting Android 6.0 and above.
• Testers running both builds side by side, since the Debug package carries a .debug suffix and installs alongside the Release version on one device.
• Client integrators reading the Apifox documentation at coolmall.apifox.cn, which lists request parameters and response examples and is updated as development proceeds.

Getting started

The README points to cloning the repository from GitHub or Gitee and opening it in Android Studio, with prebuilt Release and Debug APKs also available from the Pgyer download links.

How it compares

No list of paid commercial products is given as something this replaces, so the closest named reference point is Now in Android: CoolMallKotlin adopts that sample's architecture and modular conventions but applies them to a shopping domain rather than a news feed, which makes it a domain-specific reference instead of a general-purpose sample. It therefore sits beside generic Compose scaffolds and samples rather than competing with a hosted commerce platform, being a client application distributed under MIT.

When to use it — and when not to

Choose it when the goal is to learn or bootstrap a modular Kotlin and Compose Android client and the mall domain is useful; expect to supply the backend yourself, because the README documents only an API interface and describes no server component. Avoid it where a commercially supported platform is required: maintenance comes from one developer working in spare time, complete test coverage and tablet and foldable large-screen adaptation are both listed as planned rather than finished, the README is written in Chinese, and bundled media assets are taken from the internet for learning and exchange only, so their reuse in a shipped product is not established.

├── app/                   # 应用入口模块
├── build-logic/          # 构建逻辑
├── core/                 # 核心模块
│   ├── common/           # 通用工具和扩展
│   ├── data/             # 数据层
│   ├── database/         # 数据库
│   ├── datastore/        # 数据存储
│   ├── designsystem/     # 设计系统
│   ├── model/            # 数据模型
│   ├── network/          # 网络层
│   ├── result/           # 结果处理
│   ├── ui/               # UI组件
│   └── util/             # 工具类
│   └── navigation/       # 导航
├── feature/              # 功能模块
│   ├── auth/             # 认证模块
│   ├── common/           # 公共模块
│   ├── cs/               # 客服模块
│   ├── feedback/         # 反馈模块
│   ├── goods/            # 商品模块
│   ├── launch/           # 启动模块
│   ├── main/             # 主模块
│   ├── market/           # 营销模块
│   ├── order/            # 订单模块
│   └── user/             # 用户模块