# Multi modules Architecture
AppKickstarter has a multi-module Gradle structure, embracing Clean Architecture and Separation of Concerns. This structure is aimed at enhancing maintainability and promoting a robust development framework. The codebase is divided into distinct modules, each serving a specific function, adhering to SOLID principles, and ensuring a clear separation of concerns:
AppKickstarter modules architecture
* **Umbrella Shared Module:** Acts as the central entry point for the app.
* **Shared Module:** Provides common utilities and foundational components.
* **Domain Module:** Contains the business logic and use cases, crucial to the Clean Architecture model.
* **ComposeUI Module:** Focuses on UI development with Compose UI, housing all UI components.
* **Firebase Module:** Centralizes Firebase services, managing database operations and more.
* **Auth Module:** Oversees user authentication, ensuring secure access control.
* **Settings Module:** Offers a comprehensive interface for settings and preferences management.
* **Resources Module:** Stores all app resources, ensuring centralized management of strings, themes, and fonts.
* **Onboarding Module:** Aids new users in familiarizing themselves with the app's functionalities.
* **Maps Module:** Manages all map-related features, including permissions and location services.
* **Monetization Module:** Integrates Revenue Cat for subscriptions and in-app purchases, along with pre-built paywalls.
* **Dates Module:** Specializes in date and time operations, promoting consistency in managing temporal data.
* **WhatsNew Module:** Handles the presentation and management of updates and new features.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.appkickstarter.com/tech-things/multi-modules-architecture.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.