# Garajdaş: model-specific community without the forum sprawl

> A Reddit-like community platform where every vehicle make and model has its own club, holding ICE and EV under one roof; web and mobile run in parallel.

- What it does today: A community platform where every car make and model has its own club; identity, content, notifications and moderation all run on a single-schema API, with the web and mobile clients sharing that one schema. Anyone looking for a community specific to their car's model can join today.
- Form: Web app, Mobile app
- Maturity: Beta
- State: In development
- Focus: Community & platform
- Started: 2026-07-02
- Technologies: Laravel, PHP, PostgreSQL, Next.js, React, Tailwind CSS, Expo, React Native, TypeScript
- Tags: #community, #mobile, #web
- Website: https://garajdas.com
- Source: https://www.muhammetsafak.com.tr/en/labs/garajdas/
- Language: en-US
- Author: Muhammet Şafak

---
The question a vehicle owner asks most often: "Does this model year have a
known issue?" Today the answer is scattered across Facebook groups, forums and
WhatsApp threads — none of them organised per model, none searchable, none
permanent. Garajdaş is an attempt to gather that in one place: every make and
model gets its own **club**, users subscribe to the clubs they care about, and
the feed follows from there.

## A club per make and model

The taxonomy decision is the product: ICE (internal combustion) and EV are not separate worlds, and
neither are four wheels and two. One roof, one club model. The name carries the
same stance — "garage" plus the Turkish kinship suffix; inside the product it
is an actual relationship type, not decoration.

The architecture stayed plain: a single API (Laravel 13) owns the schema, with
two clients on top — web in Next.js 16, mobile in Expo/React Native. The design
system lives in one file and is synchronised by hand across both platforms;
there is no token build step in the polyrepo, so when a token changes, both
sides change in the same commit.

## The MVP phases are closed

The MVP phases closed in order: local infrastructure and API skeleton, identity
and club taxonomy, the content and interaction surface, the Expo mobile client,
the Next.js web client, a hardening round, and notifications. 97 tests on the
API; lint, build and a live smoke run on web; lint, tsc and a bundle export on
mobile. Club and post pages are indexable without login — searchable
community content is the whole reason the product exists.

## One threshold left: launch

Nothing known is missing on the code side; what is left needs accounts and
credentials (Google OAuth verification, push notification keys) plus the store
process. The next threshold is launch.