System Requirements Document (SRD)

Project Name: stone-chat

1. Introduction

Welcome to the System Requirements Document (SRD) for stone-chat, a cutting-edge chat application designed to provide seamless communication experiences for users in India and beyond. This document outlines the functional and non-functional requirements, technical specifications, and design concepts for the project.

The goal of stone-chat is to deliver a robust, user-friendly platform for one-on-one and group chats, voice/video calls, status updates, and customizable themes, while ensuring privacy and offline functionality.

This SRD has been tailored to meet the needs of Zeeshan Ahmed and incorporates locale-specific considerations such as timezone (IST), cultural preferences, and user expectations.

2. System Overview

stone-chat is a web and mobile application designed for communication and social interaction. The system will include:

• Core Features: Chat (personal and group), voice/video calls, status updates, and user profile management.
• Customization: Theme and UI personalization, including light/dark mode and color schemes.
• Privacy Controls: Public/private profile toggles and secure account settings.
• Offline Functionality: Cached chats and drafts accessible without internet.
• Admin Panel: A simple yet powerful dashboard for user and analytics management.

The application will support Android devices via a native APK and web deployment through cPanel hosting.

3. Functional Requirements

As User:

• I should be able to register and log in to the application.
• I should be able to chat one-on-one and in groups.
• I should be able to make voice and video calls.
• I should be able to upload statuses from my gallery or share them directly from other applications.
• I should be able to view and interact with statuses uploaded by my friends.
• I should be able to customize the application theme and toggle between light and dark modes.
• I should be able to set my profile as public or private.
• I should be able to edit my profile details, including my username (with a 5-day lock).
• I should be able to access chats offline and resume typing drafts without internet.

As Admin:

• I should be able to log in to the admin panel using a fixed email and password.
• I should be able to view analytics such as total users, active users, and message volume.
• I should be able to manage users (search, edit, delete, ban/unban).
• I should be able to toggle user status (active/suspended).

4. User Personas

1. Regular User

• Description: Individuals using the app for personal communication.
• Needs: Seamless chat, calls, status updates, and customization options.
• Behavior: Active on chats, uploads statuses, and engages with friends.

2. Admin

• Description: The sole administrator managing the platform.
• Needs: Access to analytics, user management, and system control.
• Behavior: Monitors user activity and ensures smooth operation of the platform.

5. Visuals Colors and Theme

Unique Color Palette for stone-chat:

• Background: #F3F8FF (Soft Sky Blue)
• Surface: #FFFFFF (Pure White)
• Text: #2E3A59 (Deep Navy Blue)
• Accent: #FF6F61 (Vibrant Coral)
• Muted Tones: #A6B1C0 (Calm Gray-Blue)

This palette reflects a modern, clean aesthetic while maintaining a friendly and approachable vibe.

6. Signature Design Concept

Interactive Floating Chat Islands

The homepage of stone-chat will feature a bold and unforgettable design:

• Visual Concept: A 3D floating island interface where each island represents a feature (Chats, Groups, Calls, Status). Users can "fly" between islands by swiping or clicking.
• Animations: Smooth transitions as islands rotate and zoom into focus. Hover effects will reveal additional details about each feature.
• Color Shifts: Islands subtly change colors based on the time of day (morning = soft blue, evening = coral tones).
• Micro-Interactions: Chat bubbles float around the "Chats" island, and clicking them opens previews of recent conversations.

This design will create an immersive and playful experience, making the app instantly memorable.

7. Non-Functional Requirements

• Performance: The app must load within 2 seconds on both web and mobile platforms.
• Scalability: Support up to 1 million users concurrently.
• Security: Implement robust authentication and encryption for user data.
• Reliability: Ensure 99.9% uptime for the application.
• Accessibility: Adhere to WCAG 2.1 standards for accessibility.

8. Tech Stack

Frontend:

• React for Web
• React Native for Mobile

Backend:

• Python
• FastAPI

Database:

• MySQL (preferred) or MariaDB for relational data
• MongoDB for NoSQL requirements
• WeaviateDB for vector-based queries

AI Models:

• GPT 5.4 for user-friendly responses
• Claude 4.6 Opas for academic or coding work
• Gemini 3.1 Pro for conversational AI
• Google Nano Banana for image generation

AI Tools:

• Litellm for LLM routing
• Langchain

Orchestration:

• Docker and docker-compose for local development
• Kubernetes for server-side orchestration

9. Assumptions and Constraints

Assumptions:

• Users will primarily access the app via Android devices and web browsers.
• Internet connectivity will be intermittent for some users, necessitating offline functionality.
• Status uploads will include images and videos from both gallery and external apps.

Constraints:

• Admin panel design will remain basic to prioritize functionality over aesthetics.
• Deployment will be limited to cPanel hosting and Android APK distribution.

10. Glossary

• APK: Android Package Kit, used for distributing and installing apps on Android devices.
• Capacitor: A cross-platform app runtime for building native mobile apps.
• Supabase: An open-source backend-as-a-service platform.
• WCAG: Web Content Accessibility Guidelines, standards for accessible web design.
• LLM: Large Language Model, used for AI-driven responses.

End of Document