Back to work

In development

Projecty

A bilingual workspace for software-project onboarding, documentation and delivery governance.

Projecty requirements list with version history
Projecty requirements list on a phone (light theme)
Status
In development
Contribution
Product design and Full Stack development.

A bilingual workspace for software-project onboarding, documentation and delivery governance.

Objective

Freelancers, studios and small teams keep retyping the same client and project facts into proposals, questionnaires, contracts and handover documents. Projecty keeps one governed Project record that feeds every document, so what was agreed stays traceable.

Engineering approach

Next.js App Router on Supabase Postgres, built phase by phase through 14 migrations: workspaces and roles, row-level security, an immutable audit log, private files, and a review flow where proposed changes to project data are accepted, corrected or rejected before they become the record. A document engine with themes renders Arabic, English and bilingual documents. The interface is bilingual with light and dark themes, covered by unit, database, security and Playwright accessibility tests.

Responsibilities

  • Product design and the bilingual interface (Arabic and English, light and dark themes).
  • Data model, 14 migrations, row-level security and the audit log.
  • The document engine and the review flow for proposed changes.
  • Unit, database, security and Playwright accessibility tests.

Engineering decisions

  1. A modular monolith, not servicesOne deployable application with strongly separated modules and one transactional database, with no microservices, queues or caches until a measured need appears.
  2. Authorization in two layersSupabase row-level security protects the database, and server-side application checks carry the richer business permissions.
  3. One governed Project recordClient answers never silently become agreed requirements: proposed changes are accepted, corrected or rejected before they become the record.
  4. Documents as structured dataDocuments are rendered by one themed engine in Arabic, English and bilingual form, instead of being stored as free-form HTML.

Technical challenges

  1. History that can be trustedAn immutable audit log and private files, so what was agreed stays traceable.
  2. Arabic as a first-class languageRight-to-left layouts and bilingual documents are part of the design from the start, not added later.

Trade-offs

  1. Simplicity over distributionA single deployable unit simplifies authorization, migrations and local development, at the cost of scaling modules independently.
  2. A review step before data changesReviewing every proposed change is slower than direct editing, but nothing becomes the agreed record without a decision.

Technologies

  • Next.js
  • React
  • TypeScript
  • Supabase
  • PostgreSQL
  • Tailwind CSS
  • shadcn/ui
  • Zod
  • React Hook Form
  • Vitest
  • Playwright
Skip screens

Visual evidence

Visual evidence

Projecty sign-in screen
Sign in
Projecty workspace home
Workspace home
Projecty project phases view with a checklist per phase
Phases
Projecty decisions and open-questions log
Decisions and questions
Projecty requirements list with version history
Requirements
Projecty review of a proposed change: current approved value next to the proposed value
Change review
Projecty kickoff meeting records
Kickoff records

Next project

Filmmaker & Creative Director Portfolio