Skip to main content
Back to selected projects

First Filter Automotive Platform

A catalogue and operations platform connecting automotive filters, vehicles, manufacturers, categories, media, administration, and web/mobile clients.

Backend
Python, Django, Django REST Framework
Data
PostgreSQL and MySQL relational models
Clients
React, Next.js, and React Native

My contribution

I designed Django/DRF models and APIs for the automotive catalogue and implemented permissions, image-upload flows, administrative workflows, and client integration.

I also supported deployment and production debugging while connecting the backend to web and mobile product surfaces.

Technical scope

  • Automotive filters, vehicles, manufacturers, categories, and related catalogue data
  • REST APIs, relational data modelling, permissions, validation, and image uploads
  • Administrative workflows and integration with React, Next.js, and React Native clients
  • Deployment support and production debugging across the product stack

Engineering evidence

This map focuses on verified technical scope and the engineering concerns behind it. It does not claim unverified catalogue size, users, performance, or business results.

01

Relational automotive catalogue

Django models and DRF APIs represent filters, vehicles, manufacturers, categories, and their relationships instead of flattening the catalogue into disconnected records.

Concern addressed: Keeping catalogue relationships understandable and maintainable

02

Permission-aware operations

API and administrative workflows apply permissions around catalogue and operational changes, with validation kept on the backend for web and mobile clients.

Concern addressed: Preventing unauthorized changes through different clients

03

Media and administration workflows

Image uploads and administrative operations are part of the product workflow rather than separate manual steps outside the platform.

Concern addressed: Keeping product data and media management in one controlled flow

04

Shared API boundary

The Django/DRF backend supports React, Next.js, and React Native clients through shared resource and validation contracts.

Concern addressed: Consistent behavior across web and mobile surfaces

Evidence boundary

The available evidence confirms technical scope and delivery responsibilities. No verified user, revenue, catalogue-size, or performance outcome is presented here.

Discuss the implementation

I can explain the data model, permissions, API contracts, media workflows, and the integration boundary between Django and the web/mobile clients.

Email Ahmed