# fouadraheb/watusi-for-whatsapp architecture

> Architecture diagram of the GitHub repository fouadraheb/watusi-for-whatsapp, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-31). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/fouadraheb/watusi-for-whatsapp
- Repository: https://github.com/fouadraheb/watusi-for-whatsapp

## Overview

##### Main Components
- Project Repository: Represented by the project’s Git repository containing configuration files (e.g., .gitignore), the README (which doubles as installation and usage documentation), and folders like “altstore” (with source.json and the “watusi” binary or metadata) plus the “images” folder used for branding.
- IPA Artifacts: These are the compiled binaries (IPA files) for various variants (e.g., original vs. duplicate, with/without plugins). They are referenced via various hosted links.
- Distribution Channels: Several external platforms are used for distribution:
- AltStore – where the “altstore” folder and its JSON play a role in facilitating sideloading.
- TrollStore – used for users on specific iOS versions.
- Build server links (e.g., builds.io, flekstore) and CDN hosting for the IPA downloads.
- Installation Modes on User Devices:
- Jailbroken Installation: Via adding the repo to Cydia/Zebra/Sileo.
- Sideloading via AltStore: Using the IPA files and using Apple’s signing process.
- Linked Device Installation: Where the modified (duplicated) app syncs with the original WhatsApp.
- User’s Device Environment: The actual iOS device that ultimately runs WhatsApp with Watusi functions and integrates with iCloud and push notification mechanisms.

##### Relationships and Interactions
- The repository (with its altstore folder) produces the IPA and accompanying metadata.
- The installation guides (detailed in the README) form the “workflow” elements showing how a user picks the desired installation method and then signs/installs the IPA onto their device.
- The modified WhatsApp executes on the iOS device and may interact with external services (Apple’s push notification system, iCloud, etc.) or with the original WhatsApp (in the linked device scenario).

##### Architectural Patterns/Design Principles
- Separation of Concerns: Although not a typical “server–client” architecture, note the clear separation between distribution (production of IPA files and provision of metadata/assets) and installation (the actual process on user devices).
- Multi-Channel Distribution: The system leverages multiple distribution and installation pipelines (jailbreak repo vs. sideloading vs. TrollStore) to accommodate different user environments.
- Modularity: The project breaks out different IPA variations (standard, duplicate, with/without plugins) to address various use cases.

##### Relevant Technologies and Frameworks
- iOS Platform: The entire system is built around modifying an iOS app (WhatsApp).
- AltStore Integration: Use of the altstore folder (with source.json) indicates a configuration point for AltStore.
- Jailbreaking Tools: References to Cydia/Zebra/Sileo indicate traditional jailbreak repository distribution mechanisms.
- TrollStore: A specialized installation for certain iOS versions.
- Digital Signing: Apple ID authentication and signing processes (re-signing via AltStore) are key to the sideloading process.

##### Detail
- Every component from source to installation is present.
- Provide annotations on any external interactions, like Apple’s signing mechanisms and push notification service.

## Diagram (Mermaid)

```mermaid
graph TD
    subgraph "Repository and Artifacts"
        PR["Project Repository"]:::repo
        BA["Branding Assets"]:::asset
        IPA["IPA Artifacts"]:::artifact
    end

    subgraph "Distribution Channels"
        AS["AltStore"]:::external
        BS["Build Server (builds.io)"]:::external
        FS["Flekstore"]:::external
        CDN["CDN Host"]:::external
        TS["TrollStore"]:::external
        JB["Jailbreak Repo"]:::external
    end

    subgraph "Installation Modes"
        SI["Sideloading (AltStore)"]:::install
        JI["Jailbroken Installation"]:::install
        LDI["Linked Device Installation"]:::install
    end

    UD["User Device: WhatsApp with Watusi"]:::user

    PR -->|"produces"| IPA
    PR -->|"contains"| BA
    IPA -->|"distributed_via"| AS
    IPA -->|"distributed_via"| BS
    IPA -->|"distributed_via"| FS
    IPA -->|"distributed_via"| CDN
    IPA -->|"distributed_via"| TS
    IPA -->|"distributed_via"| JB

    AS -->|"enables"| SI
    TS -->|"alternative"| SI
    JB -->|"enables"| JI
    BS -->|"triggers"| LDI
    FS -->|"triggers"| LDI
    CDN -->|"triggers"| LDI

    SI -->|"installs_on"| UD
    JI -->|"installs_on"| UD
    LDI -->|"installs_on"| UD

    classDef repo fill:#fce,stroke:#333,stroke-width:2px;
    classDef asset fill:#fcf,stroke:#333,stroke-width:2px;
    classDef artifact fill:#cde,stroke:#333,stroke-width:2px;
    classDef external fill:#efe,stroke:#333,stroke-width:2px;
    classDef install fill:#def,stroke:#333,stroke-width:2px;
    classDef user fill:#ffd,stroke:#333,stroke-width:2px;

    click PR "https://github.com/fouadraheb/watusi-for-whatsapp/tree/master/Root directory"
    click AS "https://github.com/fouadraheb/watusi-for-whatsapp/tree/master/altstore folder"
    click BA "https://github.com/fouadraheb/watusi-for-whatsapp/tree/master/images folder"
```
