# PocketBoard — Deferred Features

This document records features that were considered for the initial
version of PocketBoard and deliberately deferred. Each entry includes
the reason for deferral and the conditions under which the feature
should be reconsidered.

---

## Real-Time Chat (WebSockets)

**Why deferred:** Requires WebSocket lifecycle management, reconnection
logic, message queuing during disconnection, and race condition handling
between HTTP and WebSocket delivery. This is a non-trivial distributed
systems problem that deserves dedicated treatment.

**Current approach:** HTTP polling at five-second intervals in active
conversations. Acceptable latency for the asynchronous messaging use case.

**Reconsider when:** Daily active message volume exceeds 10,000 messages
or user feedback identifies polling latency as a pain point.

---

## Map and Location Browsing

**Why deferred:** Requires a native maps SDK that exits the Expo managed
workflow boundary, plus geocoding API integration and location permission
handling. Adds native configuration complexity without addressing the
core use case.

**Reconsider when:** Geographic concentration of listings in specific
neighbourhoods makes spatial browsing valuable.

---

## Social Login (Sign in with Apple / Google)

**Why deferred:** OAuth flows on mobile require specific native
implementation. Apple requires Sign in with Apple whenever any social
login is offered. Account linking (same email, different provider) adds
complexity. Email/password with a strong UX is sufficient for launch.

**Reconsider when:** Registration drop-off rate exceeds 40%.

---

## Offline-First Sync

**Why deferred:** Requires a local database, a conflict resolution
protocol, a mutation queue, and background sync. Substantial additional
complexity. Graceful error handling when offline is sufficient for launch.

**Reconsider when:** Significant usage in low-connectivity environments
is identified in analytics.

---

## Admin Moderation Dashboard

**Why deferred:** A web concern, not a mobile concern. Manual moderation
via direct database access is sufficient for a controlled community launch.

**Reconsider when:** Community size exceeds the capacity for manual review.

---

## Video Listings

**Why deferred:** Transcoding, storage costs, streaming vs download
decisions, and native video player dependencies. Photo listings are
sufficient for the core use case.

**Reconsider when:** Listing categories emerge where video is clearly
superior (e.g. vehicle walkarounds, furniture condition reviews).

---

## User Reviews and Ratings

**Why deferred:** Data model changes, review submission flow, duplicate
prevention, fake review detection, and trust score calculation.

**Reconsider when:** Community size makes reputation establishment through
messaging history insufficient for trust.

---
