# Garajdaş

> Garajdaş is a community platform where every car make-and-model has its own club, keeping internal-combustion and electric vehicles under one roof. A single API schema is shared by the web (Next.js) and mobile (Expo/React Native) clients, the design system is defined in one file and synced by hand. The MVP phases are closed, the API has 97 tests; the platform is live.

- Role: Founder & Developer
- Class: Side Publications
- Status: Ongoing
- Started: 2026-09-23
- Technologies: Laravel, PHP, PostgreSQL, Next.js, React, Tailwind CSS, Expo, React Native, TypeScript
- Skills: API Design, Product Taxonomy, Cross-Platform Architecture, Mobile Development, Design Systems, Community Platform Design
- Website: https://garajdas.com
- Source: https://muhammetsafak.com/portfolio/garajdas/
- Language: en-US
- Author: Muhammet Şafak

---
Garajdaş is a community platform where every car make-and-model has its own club, keeping internal-combustion and electric vehicles under one roof. Making the club unit make-and-model rather than just make is a deliberate call: a single club at the make level would shorten the list and make moderation easier, but since almost every question about a car is specific to its model and year, the make level isn't the resolution the question is actually asked at. Users subscribe to the clubs they care about, and that's where the feed comes from.

I kept the architecture plain: a single API (Laravel 13) is the sole owner of the schema, with a Next.js 16 web client and an Expo/React Native mobile client on top of it. The design system is defined in a single file and synced by hand across the two platforms — I didn't set up a token build tool in a polyrepo; a third build step and release line wasn't worth paying for two clients, so the rule got written into the contract instead. The MVP phases — infrastructure, identity and club taxonomy, the content/interaction surface, mobile and web clients, hardening and notifications — are closed; the API side has 97 tests, and lint/build/live smoke on web and lint/tsc/bundle export on mobile have been verified. There's no known gap on the code side; what's left is account/credentials (Google OAuth, push notifications) and the mobile store process; the platform itself is live.