Architecture / 4+1 / View 04

/ARCHITECTURE /DEVELOPMENT VIEW

The Development View describes how the Intaliq code is organized: components, packages, layers and their dependencies. The SE365 high-fidelity prototype was designed in Figma, built with JavaScript, HTML and CSS using Vite, backed by Supabase, versioned on GitHub and deployed on Vercel. That stack is the starting point for this architecture.

Stakeholders: Programmers, Managers Concern: Software Management
COMPONENT_DIAGRAM.UML
Component Diagram
FIG 1.0 Intaliq components: the mobile UI shell, the feature modules (Sessions, Activities, Goals, Partners, AI Chatbox), the Supabase client, and the external AI, push-notification and email services they depend on.

Layers & Modules

L1 Presentation

Screens and shared components for Home, Activities, Sessions, Goals and More, including the bottom navigation bar, forms, and confirmation and error messages shown next to the related field (UI-3, UI-4, UI-8). Arabic and English are switched from Settings (UI-1).

screens navigation
L2 Application

Use-case logic: booking a session, admitting members, setting goals, sending partner requests, publishing announcements and querying the AI chatbox. It validates input, enforces the flow and calls infrastructure.

booking sessions
L3 Domain

Entities and rules from the SRS data dictionary — User, Coach, Session, Goal, Activity and Partner — with constraints such as capacity greater than 1, beginner/intermediate/advanced intensity, and locations inside Saudi Arabia.

entities rules
L4 Infrastructure

Supabase client for authentication and PostgreSQL access, the offline queue that stores unsent actions and syncs them when the connection returns (CI-4, CI-5), and adapters for the AI, push-notification and email services.

supabase-client sync-queue