AmirSAmirhossein Shakernezhad
Back to the work

EjaRent

An online rental platform for Qom.

eja.rent is a Persian-first rental marketplace focused on Qom, with map-based discovery, rental listings and tools for owners to publish and manage their listings. It was a genuinely shared build: Behnam owned the backend, I owned everything the user sees, and a hand-authored OpenAPI contract was the seam between us. An API change and the web change that depends on it land together.

Role
Web app — interface & interaction design, frontend engineering, API integration
Collaboration
Built with Behnam, who designed and built the backend API
Year
2026
Status
Details coming
Disciplines
Web platforms · Software · 3D · Product presentation
Stack
Next.jsReact 19TypeScriptCSS ModulesOpenAPILeafletNestJSFastifyDrizzlePostgreSQL / PostGISRTL / Persian UI

Inside the rental marketplace

Who built what

Web application
Amirhossein — Next.js, interface, maps, flows
API & data
Behnam — NestJS, PostgreSQL / PostGIS
The seam
A hand-authored OpenAPI 3.1 contract; typed client generated from it

Finding a place in Qom

The homepage starts with a practical question: where do you want to rent, and what fits your budget? Persian search controls, neighbourhoods and listing cards lead into map-based discovery and individual property pages.

The interface keeps the rental search and the owner's publishing workflow in the same visual system. The captures here use the application's built-in development inventory; the listing page explicitly identifies the sample when its backend is unavailable.

What I built

  1. 1Map search

    Viewport-driven pins with a switch to server clustering when results truncate, single-cluster deep links, and a tile-provider fallback chain.

  2. 2Listings

    Query-param search with cursor pagination, neighbourhood slugs from the API, and money handled as rial strings parsed with BigInt — never floats.

  3. 3Owner tools

    A listing wizard with dynamic per-property-type fields from the taxonomy API and a three-step presigned media upload; an owner dashboard to publish, pause, mark rented, edit and delete.

  4. 4Accounts & admin

    OTP sign-in, a tabbed account area (profile, sessions, saved searches) and a role-gated admin panel — on one shared, themed shell.

  5. 5Persian-first

    Designed RTL from the start, with a unified token system across every surface, security headers and honest empty, error and 404 states.