# sharnjeet21/atomic_tasker architecture

> Architecture diagram of the GitHub repository sharnjeet21/atomic_tasker, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-08). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/sharnjeet21/atomic_tasker
- Repository: https://github.com/sharnjeet21/atomic_tasker

## Overview

##### Main Components
- UI/Presentation Layer (React Native Components) – Examine the “code/MyComp” directory which contains almost all UI components (e.g., Home.jsx, Header.js, Details.js, AddTask.js, etc.). This layer handles the user interface, navigation (AppNavigator.jsx), and interaction events.
- Business Logic – The “code/brain” directory holds components such as QuickTasker.js, UtilityFuncs.js, logic.js, modal.js, and testing.js. These provide the core functionality and processing of task scheduling logic.
- Assets and Styling – Note the “code/Assets” and “code/Style” directories. Assets include images and themes (custom-theme.json) that define the visual appearance.
- Configuration & Development Tools – Files like package.json, tsconfig.json, .eslintrc.js, .prettierrc.js, and others provide setup and linting rules, build configuration, and code styling—all of which are crucial for development.
- Native Platform Integration – The “code/android” and “code/ios” directories contain the platform-specific code/configurations (Gradle files for Android, Xcode project and Podfile for iOS) required to bundle and run the React Native app on those platforms.

##### Relationships and Interactions
- The UI components interact with the business logic layer to perform operations (e.g., adding a task, marking a task completed) using functions from the “brain” directory.
- Both the UI and logic layers rely on the styles and assets defined in “Style” and “Assets” directories respectively.
- The native layer (Android and iOS code) acts as the bridge to the mobile hardware and platform-specific services (notifications, alarms, etc.) and interacts with the React Native runtime.

##### Architectural Patterns / Design Principles
- Component-Based Architecture – The project is split into smaller, reusable components each handling a single UI function (e.g., Header, Menu, QuickTasker).
- Separation of Concerns – UI components are separated from business logic; app-specific functions are handled within the “brain” directory.
- Cross-Platform Abstraction – By using React Native, the app abstracts much of the platform differences, while still including platform-specific code/configurations for Android and iOS builds.
- Navigation and State Management – While not explicitly detailed, the presence of components like AppContainer and AppNavigator implies that navigation and possibly state management are key factors.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% External Dependencies
    Ext["External Dependencies (Git,Node,NPM)"]:::external

    %% Configuration & Development Tools
    subgraph "Configuration & Development Tools"
        PKG["package.json"]:::config
        TS["tsconfig.json"]:::config
        ESL[".eslintrc.js"]:::config
        PPT[".prettierrc.js"]:::config
    end

    %% React Native Core
    subgraph "React Native Core"
        UI["UI/Presentation Layer"]:::ui
        BL["Business Logic"]:::logic
        subgraph "Assets & Styling"
            AS["Assets"]:::assets
            ST["Styling"]:::assets
        end
    end

    %% Native Platform Integration
    subgraph "Native Platform Integration"
        ANDR["Native Android"]:::native
        IOS["Native iOS"]:::native
    end

    %% Connections from External Dependencies
    Ext -->|"provides_setup"| PKG
    Ext --> TS
    Ext --> ESL
    Ext --> PPT
    Ext -->|"supports"| UI
    Ext -->|"supports"| BL
    Ext -->|"provides_assets"| AS
    Ext -->|"provides_styling"| ST

    %% Interactions within React Native Core
    UI -->|"calls_functions"| BL
    BL -->|"updates_state"| UI
    UI -->|"uses_assets"| AS
    UI -->|"uses_styling"| ST

    %% Interactions with Native Platforms
    BL -->|"calls_nativeAPI"| ANDR
    BL -->|"calls_nativeAPI"| IOS
    UI -->|"triggers_platformEvents"| ANDR
    UI -->|"triggers_platformEvents"| IOS

    %% Styles
    classDef external fill:#F5A623,stroke:#333,stroke-width:2px;
    classDef config fill:#967ADC,stroke:#333,stroke-width:2px;
    classDef ui fill:#A0D468,stroke:#333,stroke-width:2px;
    classDef logic fill:#4A89DC,stroke:#333,stroke-width:2px;
    classDef assets fill:#FFCE54,stroke:#333,stroke-width:2px;
    classDef native fill:#ED5565,stroke:#333,stroke-width:2px;

    %% Click Events
    click UI "https://github.com/sharnjeet21/atomic_tasker/tree/main/code/MyComp"
    click BL "https://github.com/sharnjeet21/atomic_tasker/tree/main/code/brain"
    click AS "https://github.com/sharnjeet21/atomic_tasker/tree/main/code/Assets"
    click ST "https://github.com/sharnjeet21/atomic_tasker/tree/main/code/Style"
    click ANDR "https://github.com/sharnjeet21/atomic_tasker/tree/main/code/android"
    click IOS "https://github.com/sharnjeet21/atomic_tasker/tree/main/code/ios"
    click PKG "https://github.com/sharnjeet21/atomic_tasker/blob/main/code/package.json"
    click TS "https://github.com/sharnjeet21/atomic_tasker/blob/main/code/tsconfig.json"
    click ESL "https://github.com/sharnjeet21/atomic_tasker/blob/main/code/.eslintrc.js"
    click PPT "https://github.com/sharnjeet21/atomic_tasker/blob/main/code/.prettierrc.js"
```
