Website Portfolio Copy — Vertical Marketplace + Web/iOS/Android Delivery

Project positioning

Bazaar Bargh was a vertical marketplace created specifically for Iran’s electrical-goods market.

The client’s requirement was explicit: build a marketplace experience closely modeled on the interaction pattern of Divar, but specialized for electrical products, equipment, sellers, and buyers.

The project was delivered as a multi-channel product:

• a full web marketplace,
• an iOS client,
• an Android WebView client,
• and a custom visual identity based on a client-supplied hand-drawn logo concept.

The project was built on top of my reusable Laravel business/platform core rather than from a blank codebase. That core already contained a large set of configurable capabilities and optional modules that could be enabled, disabled, and adapted per client. Bazaar Bargh therefore demonstrates both platform reuse and domain-specific marketplace adaptation.

Classification

• Project Type: Vertical Classifieds / Marketplace Platform
• Period: 2019
• Public Evidence Dates: March–April 2019
• Domain: Electrical Goods / Electrical Market / Classifieds
• Business Model: Multi-seller marketplace / classified listing platform
• Delivery Channels: Web + iOS + Android
• Historical Backend: Laravel-based reusable platform/core
• Historical Mobile Delivery: Native iOS client + Android WebView client
• Logo Direction: Client-supplied hand-drawn concept, digitally implemented by me
• Status: Historical production / client project
• Portfolio Relevance: Strong Portfolio Evidence
• Suggested CV Relevance: Tier B, with Tier A support for product/platform discussions

Overview

Bazaar Bargh was designed as a specialized online marketplace for electrical goods.

The client’s reference model was Divar, one of Iran’s best-known classifieds platforms.

The requirement was not to create a generic store.

It was to take the familiar interaction pattern of a broad classifieds product and adapt it to one specific commercial domain:

electrical goods, electrical equipment, electrical-market sellers, and buyers.

The result was a vertical marketplace with:

• browsable product/listing categories,
• seller-oriented content,
• marketplace-style presentation,
• product discovery,
• mobile access,
• and a branded presence tailored to the electrical market.

Historical Evidence

The surviving public project evidence provides a clear timeline.

March 16, 2019

A public post shows the Bazaar Bargh website operating as an electrical-goods marketplace and describes the project as:

programming and designing a sales/classified-style website inspired by Divar.

The screenshot shows a dense marketplace grid containing electrical products and equipment across multiple categories.

April 10, 2019

A later public post shows the iOS project in Xcode.

Visible project artifacts include:

• AppDelegate.swift
• ViewController.swift
• Main.storyboard
• LaunchScreen.storyboard
• Assets.xcassets
• application icons prepared for multiple iOS sizes

The accompanying description identifies the work as an Apple/iOS implementation based on a WebView-style approach for the web application.

April 15, 2019

A later post shows the finalized Bazaar Bargh logo.

The logo itself originated from a client-supplied drawing / visual concept.

My role was to translate that concept into the finished digital asset.

Original Business Requirement

The client’s request can be summarized as:

“There is a site in Iran called Divar. I want essentially that marketplace model, but for the electrical market.”

This is important because the product requirement was based on a proven interaction model rather than on an abstract specification.

The engineering task was therefore:

Generic Classifieds Pattern
          ↓
Domain Adaptation
          ↓
Electrical-Goods Taxonomy
          ↓
Marketplace UI
          ↓
Web Platform
          ↓
iOS Client
          ↓
Android Client

Why This Was Not Just a Divar Copy

The client used Divar as the interaction reference.

The implementation problem was still domain-specific.

A vertical marketplace for electrical goods requires different concepts from a broad classifieds platform.

Examples include:

• electrical equipment categories,
• product specifications,
• brand/manufacturer relationships,
• industrial vs residential use,
• technical product naming,
• seller specialization,
• wholesale / retail context,
• new / used equipment,
• electrical-market vocabulary.

The interface model may be familiar, but the domain model must be adapted.

Reusable Laravel Core

This project was not developed from zero.

At the time, I already maintained a feature-rich reusable Laravel backend/core used across multiple client projects.

The platform contained more functionality than any single client normally required.

Modules and features could be enabled, disabled, or configured based on the project.

Conceptually:

Reusable Laravel Core
        ↓
Feature Modules
        ↓
Client Configuration
        ↓
Domain Customization
        ↓
Rapid Deployment
        ↓
Real User Feedback
        ↓
Iterative Refinement

This approach allowed client systems to become operational very quickly.

Instead of spending months building infrastructure before users could touch the software, a usable platform could be brought online in hours and then refined while real users worked with it.

Shared Platform vs Project-Specific Work

Shared Core

The underlying platform provided reusable capabilities such as:

• authentication,
• user management,
• configuration,
• content/product structures,
• administrative screens,
• common CRUD workflows,
• business modules,
• reusable UI patterns,
• reporting / operational primitives,
• and other configurable modules.

The exact historical module inventory belongs to the standalone reusable-platform project and should not be duplicated here.

Bazaar Bargh-Specific Layer

Bazaar Bargh required project-specific work around:

• marketplace information architecture,
• electrical-goods categorization,
• listing presentation,
• seller/buyer workflow,
• marketplace browsing,
• product cards,
• mobile delivery,
• domain-specific branding,
• and client-directed visual identity.

This is the layer that differentiates Bazaar Bargh from other client deployments of the same reusable core.

Marketplace Information Architecture

A simplified model:

Marketplace
   ↓
Category
   ↓
Subcategory
   ↓
Listing / Product
   ↓
Seller
   ↓
Contact / Transaction Intent

For electrical goods, categories can represent areas such as:

• cables,
• breakers,
• switches,
• distribution equipment,
• control equipment,
• industrial electrical components,
• tools,
• accessories,
• lighting,
• electrical infrastructure.

The historical screenshot confirms broad electrical-product coverage, though the exact category taxonomy should be reconstructed from source code or database backups if recovered.

Web Platform

The website was the primary marketplace experience.

It provided:

• marketplace browsing,
• product/listing presentation,
• category navigation,
• seller-facing content,
• a responsive presentation suitable for desktop and mobile use.

The visual density was intentionally closer to a classified marketplace than to a conventional single-store e-commerce site.

Listing Model

A listing-oriented marketplace typically needs to represent:

Listing
├── Title
├── Category
├── Images
├── Price
├── Description
├── Seller
├── Location / Market Context
└── Contact / Action

Bazaar Bargh adapted this model to electrical-market inventory.

Exact historical fields should be documented from recovered schema/source rather than inferred beyond available evidence.

Search and Browsing

The marketplace model requires discovery rather than only direct navigation.

Core discovery concepts included:

• category browsing,
• product/listing grids,
• visual scanning,
• seller/product discovery,
• and marketplace-oriented search behavior.

The modern V2 can strengthen this significantly with technical filtering and dedicated search infrastructure.

iOS Client

An iOS version was created in Xcode.

Historical evidence shows:

• Swift project files,
• storyboard-based project structure,
• dedicated app icons,
• mobile project packaging.

The iOS implementation connected the mobile application to the Bazaar Bargh web experience.

The public post from April 2019 explicitly documents this Apple client work.

Android Client

The Android delivery was intentionally pragmatic.

The client considered a WebView wrapper sufficient.

This was appropriate because the primary business logic and interaction already existed in the web platform.

Rather than duplicating the entire application stack natively, the Android app provided a packaged mobile entry point into the existing marketplace.

This was a deliberate cost/speed trade-off.

Mobile Delivery Strategy

The historical product therefore used different mobile delivery strategies by platform:

Core Web Platform
      ↓
 ┌────┴────┐
 ↓         ↓
iOS     Android
Client  WebView

This demonstrates an important product-engineering principle:

Not every platform requires the same implementation strategy.

The appropriate solution depends on:

• customer budget,
• expected usage,
• platform requirements,
• maintenance cost,
• and delivery speed.

Logo & Brand Implementation

The logo concept was provided by the client as a drawing / visual idea.

My responsibility was to convert that concept into a usable digital identity.

The resulting mark used a circular red visual language with the Persian Bazaar Bargh name.

Recommended public wording:

The client supplied the original hand-drawn logo concept; I translated it into the final digital logo and application assets.

This accurately distinguishes concept ownership from execution.

Application Icons

The iOS project included a complete set of application icons for different Apple icon sizes.

This extended the visual identity beyond the website into the installed mobile application.

The screenshot of Assets.xcassets provides historical evidence of this implementation.

My Role

My role covered the technical implementation and delivery of the system.

Responsibilities included:

• requirement interpretation,
• adapting the Divar-inspired marketplace model to the electrical-goods domain,
• Laravel backend/platform configuration,
• project-specific backend customization,
• marketplace website implementation,
• category/listing presentation,
• responsive delivery,
• iOS client implementation,
• iOS asset/icon preparation,
• Android WebView delivery,
• client-supplied logo concept digitization,
• brand integration,
• deployment-oriented work,
• and iterative client delivery.

Ownership Positioning

Recommended wording:

The client defined the high-level product concept: a Divar-like marketplace specialized for the electrical market, and supplied the original hand-drawn logo idea. I implemented the digital platform, adapted my reusable Laravel core to the marketplace domain, built the website and mobile clients, and converted the logo concept into production-ready digital assets.

Rapid Delivery Model

This project was part of a broader software-delivery approach I used at the time.

Instead of starting each client project from an empty repository, I maintained a large reusable Laravel platform with optional modules.

A new project could be brought online rapidly.

The workflow was effectively:

Deploy Core
   ↓
Enable Relevant Modules
   ↓
Apply Client Branding
   ↓
Start Real Usage
   ↓
Observe Actual Workflow
   ↓
Refine Requirements
   ↓
Customize Domain Logic

This allowed real requirements to emerge from actual use rather than relying entirely on speculative up-front analysis.

Why This Delivery Model Worked

Small businesses often cannot describe every requirement before seeing the software.

They know:

• what work they do,
• what frustrates them,
• what outcome they want.

They may not know:

• how to model the workflow,
• which screen should exist,
• how the data should relate,
• what should be automated.

A configurable working platform gives them something concrete to react to.

This turns requirements gathering into a collaborative, iterative process.

Outcome

Bazaar Bargh resulted in a real marketplace implementation with:

• a functional website,
• an iOS client,
• an Android client,
• client-specific branding,
• and a vertical-market adaptation of a proven classifieds interaction model.

The public posts from 2019 provide direct evidence of multiple stages of the project.

Evidence Available

Current evidence includes:

• marketplace website screenshot,
• public post dated March 16, 2019,
• Xcode/iOS project screenshot,
• public post dated April 10, 2019,
• app icon asset screenshot,
• logo evidence,
• public post dated April 15, 2019.

Potential additional evidence may exist in:

• Laravel source,
• database backups,
• web screenshots,
• Android package/project,
• iOS source,
• hosting backup,
• domain records,
• design files.

Evidence Status

Recommended label:

Strongly Partially Verified — Public screenshots verify the marketplace website, iOS project, app assets, and logo; complete backend/mobile source should be attached if recovered.

V2 — Modern Electrical Marketplace

The modern version should evolve beyond a generic classifieds model.

Recommended V2 title:

Bazaar Bargh — Electrical B2B/B2C Marketplace

The V2 should leverage the fact that electrical goods have structured technical characteristics.

That allows the platform to become more useful than a generic classifieds site.

V2 Product Vision

Electrical Marketplace
        +
Structured Technical Catalog
        +
Seller Listings
        +
Advanced Search
        +
B2B/B2C Discovery
        +
Messaging
        +
Notifications

V2 Core Domains

Users

• buyers,
• sellers,
• businesses,
• administrators,
• moderators.

Sellers

• company profile,
• contact information,
• verification state,
• service area,
• product categories,
• listing history.

Categories

A hierarchical electrical taxonomy.

Example:

Electrical
├── Cables
│   ├── Power Cable
│   ├── Control Cable
│   └── Data Cable
├── Protection
│   ├── MCB
│   ├── MCCB
│   ├── RCCB
│   └── Fuses
├── Industrial Control
├── Lighting
├── Switchgear
├── Transformers
└── Tools

Technical Attributes

A vertical marketplace becomes significantly stronger when product attributes are structured.

Possible attributes:

• manufacturer,
• model,
• voltage,
• current,
• power,
• frequency,
• phase,
• cable cross-section,
• conductor material,
• breaker rating,
• IP rating,
• dimensions,
• condition,
• warranty,
• new / used,
• wholesale / retail.

This makes filtering far more precise than a generic classifieds product.

V2 Listing Model

Listing
├── Seller
├── Category
├── Technical Attributes
├── Title
├── Description
├── Price
├── Quantity
├── Condition
├── Images
├── Location
├── Delivery Options
├── Published Status
└── Moderation State

V2 Search Architecture

Search should become a dedicated subsystem.

Recommended:

• PostgreSQL as system of record
• OpenSearch / Elasticsearch for discovery
• Redis for caching / queues

Indexed fields could include:

• title,
• category,
• manufacturer,
• model,
• specifications,
• location,
• seller,
• price,
• condition.

Faceted Search

Example filters:

• category,
• brand,
• voltage,
• amperage,
• price range,
• location,
• new / used,
• seller type,
• wholesale / retail,
• availability.

This gives the platform a clear vertical-market advantage.

Saved Searches

Users could save a search such as:

Siemens MCCB, 250–400A, Tehran

The platform could notify them when matching listings appear.

Favorites

Users can save:

• listings,
• sellers,
• searches.

Messaging

A built-in messaging system can support buyer/seller communication without immediately exposing direct contact details if the business model requires it.

Notifications

Possible notification channels:

• in-app,
• email,
• push,
• Telegram integration.

Events:

• new message,
• saved-search match,
• listing approved,
• listing expired,
• price changed.

Moderation

A classifieds platform requires moderation.

Potential workflows:

Draft
 ↓
Submitted
 ↓
Automated Checks
 ↓
Moderator Review
 ↓
Published

Moderation targets:

• duplicate listings,
• spam,
• prohibited content,
• misleading pricing,
• invalid categories,
• abusive content.

Fraud / Spam Controls

Possible controls:

• rate limiting,
• phone/email verification,
• listing frequency rules,
• duplicate-image detection,
• suspicious-content flags,
• seller reputation signals.

V2 Architecture

                 Web / PWA / Mobile
                         ↓
                      API
                         ↓
                Laravel Application
                         ↓
     ┌───────────────────┼───────────────────┐
     │                   │                   │
     ▼                   ▼                   ▼
 Listings            Sellers            Messaging
     │                   │                   │
     └───────────────────┼───────────────────┘
                         ↓
                    PostgreSQL
                         │
             ┌───────────┼───────────┐
             ▼           ▼           ▼
           Redis      OpenSearch    Queues

V2 Recommended Stack

Backend

• Laravel
• PHP 8.x
• REST / JSON API
• queues
• scheduler
• notifications

Database

• PostgreSQL

Search

• OpenSearch / Elasticsearch

Cache / Queue

• Redis

Frontend

Potential options:

• Laravel + Livewire
• or SPA/mobile clients if interaction needs justify it

Infrastructure

• Docker
• CI/CD
• object storage
• image processing
• backups
• structured logging
• health checks

Image Pipeline

Marketplace image handling is important.

A modern implementation should support:

• multiple images,
• resizing,
• thumbnail generation,
• compression,
• EXIF stripping,
• WebP/AVIF where appropriate,
• malware/file validation,
• object storage.

Mobile V2

The historical project used:

• iOS client,
• Android WebView.

A modern version has more options.

Possible strategy:

PWA-first

A responsive installable web application may cover most marketplace needs.

Native / Cross-Platform Client

If push notifications, deeper device integration, or app-store presence becomes important, a dedicated mobile client can be introduced.

The architecture should keep mobile clients API-driven rather than embedding business logic separately.

Seller Verification

V2 could introduce trust levels:

• unverified seller,
• phone verified,
• business verified,
• trusted seller.

Verification can improve marketplace credibility.

Analytics

Useful product analytics:

• searches,
• zero-result searches,
• listing views,
• contact conversions,
• saved searches,
• category demand,
• geographic demand,
• seller activity.

Zero-result search analysis can directly inform category/taxonomy improvements.

Audit Trail

Administrative actions should be auditable:

• listing approval,
• listing removal,
• seller suspension,
• category edits,
• role changes,
• moderation decisions.

Security

A modern marketplace should include:

• authentication,
• role-based authorization,
• server-side validation,
• rate limiting,
• CSRF protection,
• secure file uploads,
• abuse prevention,
• audit logging,
• secure secrets,
• encrypted transport.

Testing Strategy

Domain Tests

• listing state transitions,
• price validation,
• seller permissions,
• category rules,
• technical-attribute validation.

Feature Tests

• create listing,
• edit listing,
• search,
• filtering,
• moderation,
• favorites,
• messages.

Integration Tests

• search indexing,
• image processing,
• notifications,
• mobile API.

Engineering Highlights

• Adapted a proven general-classifieds interaction model to a specialized electrical-goods market.
• Delivered the product across web, iOS, and Android.
• Built the project on a reusable Laravel platform/core rather than duplicating infrastructure.
• Used modular configuration to accelerate client delivery.
• Converted a client-supplied hand-drawn logo concept into production-ready digital assets.
• Implemented an iOS client with dedicated Xcode project and application icons.
• Used a pragmatic Android WebView strategy where full native duplication was unnecessary.
• Created a clear modernization path toward a structured B2B/B2C electrical marketplace with technical attributes and advanced search.

Career Evidence

This project demonstrates:

• Product Engineering
• Marketplace Architecture
• Laravel Development
• Platform Reuse
• Rapid Application Delivery
• Mobile Engineering
• iOS Development
• Multi-Channel Delivery
• Client Requirements Translation
• Domain Modeling
• Search / Information Retrieval
• Legacy Modernization
• End-to-End Ownership

CV Relevance

Tier B — Strong Portfolio Evidence

This is stronger than a conventional small-business website because it combines:

• marketplace product design,
• domain adaptation,
• reusable backend architecture,
• web delivery,
• iOS delivery,
• Android delivery,
• and client-specific branding.

It can support Tier A interview stories around:

• reusable platforms,
• product-line thinking,
• rapid client delivery,
• marketplace architecture,
• and mobile/web trade-offs.

Interview Story

Situation

A client wanted a marketplace for Iran’s electrical-goods sector and explicitly requested an experience modeled on Divar.

Task

The solution needed to adapt the familiar classifieds interaction model to a specialized domain and be available across web, iOS, and Android.

Action

I adapted my reusable Laravel platform to the electrical marketplace domain, implemented the web marketplace, built the iOS client and application assets, delivered the Android client through a pragmatic WebView approach, and converted the client’s hand-drawn logo concept into production-ready digital branding.

Result

The client received a multi-channel vertical marketplace with a dedicated web presence, iOS application, Android access, and electrical-market-specific presentation.

Suggested Website Full Description

Overview

Bazaar Bargh was a vertical marketplace created for Iran’s electrical-goods sector in 2019.

The client wanted the interaction model of Divar, but focused specifically on electrical products and sellers.

I implemented the marketplace using my reusable Laravel business platform as the backend foundation and adapted it to the domain.

The project was delivered across:

• web,
• iOS,
• and Android.

The Challenge

The main challenge was not copying a user interface.

It was taking a successful general classifieds model and turning it into a specialized product for an electrical marketplace.

That required adapting:

• categories,
• listing structure,
• product presentation,
• branding,
• and mobile delivery.

Original Solution

The web platform provided the primary marketplace experience.

An iOS application was built in Xcode, including dedicated application assets.

The Android requirement was intentionally simpler and was delivered using a WebView wrapper around the web marketplace.

My Role

I was responsible for:

• domain adaptation,
• Laravel platform configuration,
• project-specific implementation,
• web marketplace delivery,
• iOS client,
• Android client,
• digital logo implementation,
• and overall technical delivery.

Version 2

The modern reconstruction would evolve Bazaar Bargh into a structured electrical B2B/B2C marketplace.

The V2 would add:

• technical product attributes,
• advanced search,
• seller verification,
• messaging,
• saved searches,
• notifications,
• moderation,
• analytics,
• and dedicated marketplace infrastructure.

Short Website Card Copy

Bazaar Bargh — Electrical Goods Marketplace Platform

A Divar-inspired electrical marketplace built on a reusable Laravel core and delivered across web, iOS, and Android.

Alternative One-Liners

Architecture-oriented

Adapted a reusable Laravel business platform into a vertical electrical-goods marketplace with web, iOS, and Android delivery.

Product-oriented

Converted a general classifieds interaction model into a specialized marketplace for Iran’s electrical market.

Mobile-oriented

Delivered a Laravel marketplace across web, a dedicated iOS client, and an Android WebView application.

Platform-oriented

Used a configurable reusable backend to launch a client-specific vertical marketplace rapidly, then adapted the workflow and domain model around real requirements.

Suggested Website Slug

/projects/bazaar-bargh-electrical-marketplace

Alternative:

/software/bazaar-bargh-marketplace

Visual Identity Collection Entry

This project can also appear in the separate Visual Identity & Brand Asset Engineering collection.

Recommended classification:

Client-Concept Logo Digitization

Description:

Converted the client’s hand-drawn Bazaar Bargh logo concept into the final digital identity and application assets.

This should link to the full marketplace project.

Cover Direction

Title

Bazaar Bargh

Subtitle

Electrical Goods Marketplace Platform

Supporting Line

Web · iOS · Android · Laravel Marketplace

Visual Direction

A premium square cover combining:

• electrical-market product imagery,
• cables,
• breakers,
• industrial electrical equipment,
• a marketplace listing interface,
• a smartphone/iOS client,
• a mobile Android/WebView cue,
• the historical red circular branding language,
• marketplace search/filter elements.

The cover should communicate:

Electrical Market
+
Marketplace
+
Web
+
Mobile
+
Search

Evidence Gallery Recommendation

Historical Evidence

• March 16, 2019 marketplace website screenshot,
• April 10, 2019 Xcode project screenshot,
• iOS asset catalog screenshot,
• April 15, 2019 logo post,
• client logo concept if available.

Code Evidence

If recovered:

• Laravel repository,
• database schema,
• iOS source,
• Android project/package,
• deployment files.

V2

• architecture diagram,
• OpenSearch index model,
• technical filters,
• seller dashboard,
• mobile API,
• automated test suite.

Reusable Platform Note

Bazaar Bargh should be understood as a client-specific product built on a reusable Laravel platform, not as a completely separate backend invented from scratch.

This distinction matters.

The reusable core reduced delivery time.

The project-specific value came from:

• domain modeling,
• marketplace adaptation,
• mobile delivery,
• branding,
• and client-specific workflows.

The standalone reusable-platform project will document the broader architecture separately.

Final Portfolio Statement

Bazaar Bargh demonstrates a recurring engineering pattern from my independent software work:

Build the reusable platform once; adapt the product to each client’s real domain.

For this client, that meant transforming a generic classifieds concept into:

Electrical Marketplace
+
Laravel Backend
+
Web Experience
+
iOS Client
+
Android Client
+
Client-Specific Brand

The modern V2 direction strengthens the same idea by adding structured electrical attributes, advanced search, seller trust, moderation, messaging, and marketplace analytics.