How WeActually Build This
It started with one developer and state-of-the-art AI. Six months in, the foundation is built — and the team is just getting started. Here are the real numbers, real tools, and real methodology behind Tawaasal.
The Numbers
Real metrics from our git repositories. No vanity numbers — every stat is pulled directly from our codebase.
700,000+
Lines of Code
2,200+
Git Commits
120+
Feature Specs
9,300+
Tracked Tasks
38
Django Apps
25
Mobile Features
550+
i18n Files
6
Months Active
Spec-Driven Development
Every feature starts as a specification, not a Jira ticket. We built a custom framework called SpecKit that enforces a rigorous pipeline from idea to production code.
Specify
Natural language feature description becomes a structured spec.md with user stories, acceptance criteria, and scope boundaries.
Plan
Technical architecture, data models, API contracts, and file structure — all documented before a single line of code is written.
Tasks
Dependency-ordered task breakdown with parallel markers, validation checkpoints, and phase gates. Every task has file-level traceability.
Implement
AI executes tasks sequentially, loading context per-task from the constitution and pattern references. Micro-reviews after each task.
Review
Constitution-aware code review with severity levels (BLOCKER/ERROR/WARNING/INFO), spec traceability, and automated fix suggestions.
We have written 120+ feature specifications across the project, generating over 9,300 tracked tasks with an 80% completion rate.
github/spec-kitThe Constitution
A 2,202-line living document of 27 engineering principles that every line of code must comply with. From UUIDv7 primary keys to tenant isolation, i18n parity to accessibility standards — the constitution is the single source of truth.
27 principles covering code quality, security, permissions, i18n, accessibility, performance, and design consistency.
The Tools We Use
Building a production app with AI requires more than one tool. Each serves a different purpose in the development workflow.
The Full Stack
Three platforms, one codebase philosophy — always on the latest stable releases. Every layer follows the same constitution and spec-driven process.
Backend
LatestPython, Django, DRF — 38 apps, 1,037 files, 239K lines. Multi-tenant via django-tenants with PostgreSQL. UUIDv7 primary keys, centralized permissions, audit logging.
Frontend
LatestReact, TypeScript, Vite — 965 files, 276K lines. Tailwind CSS, Framer Motion, Zustand state, react-i18next with 11-language support and full RTL layout.
Shared i18n
555 files555 translation files across 11 languages. Every user-facing string goes through the shared i18n pipeline — backend, frontend, and mobile all consume the same source of truth.
Chapter One
Six months from first commit to a full-stack production platform with 700K+ lines of code. This is the foundation — what comes next is bigger.
November 2025
Project kickoff. Backend foundation, multi-tenant architecture, user management, and the first Django apps. SpecKit workflow established.
December 2025
Core features: homework, grading, attendance, calendar, messaging, permissions system, and subscription management. 20+ specs completed.
January 2026
Advanced features: safeguarding, communication templates, data import/export, rich text editor, student lifecycle management.
February 2026
Flutter mobile app: student, guardian, teacher, and staff experiences. Offline sync, theme system, and cross-platform parity.
March 2026
Marketing website, CMS, public pages, and this very page you're reading. UI design revolution across web and mobile.
April 2026
Production hardening: GitOps continuous delivery, full metrics-and-logs observability, automated database backups, and a shared caching layer. Plus privacy and compliance — DSAR data-rights workflows and an operational notifications system.
May 2026
Going global: the app expanded to 11 languages with a one-tap, tenant-aware switcher and a redesigned per-school Languages admin, every language context-reviewed. A unified brand pack landed across web and mobile, alongside a business voicemail line.
What's Next
Growing the team, onboarding pilot schools, and building the features that turn a platform into a product. The architecture is ready — now it scales.
Want to See It in Action?
Six months of engineering by one developer with AI. Imagine what a growing team will do. Try the demo and see what's already possible.