# DEFERRED.md — Final disposition (Chapter 24)

## Real-time Chat (WebSockets)
Status: ARCHIVED
Decision: WebSocket architecture exceeds PocketBoard 2.0 scope.
          Polling via Chapter 19’s MessagesContext is sufficient for
          community notice board latency requirements.
          Candidate for a future edition of the series.

## Map/Location Browsing
Status: DEFERRED — Version 3.0
Condition: If user research shows location is a top-requested feature.
           Requires expo-location, a maps provider (Google/Mapbox), and
           significant data model changes.

## Social Login (OAuth)
Status: DEFERRED — Version 2.1
Condition: If registration drop-off rate exceeds 40% (per Chapter 2 spec).
           Implement Google Sign-In first; add Apple Sign-In (required by
           App Store Guidelines if Google is present on iOS).

## Offline-First Sync
Status: ARCHIVED
Decision: Conflict resolution complexity is not justified for a community
          notice board. Basic React Query caching provides acceptable
          offline experience for read operations.

## Account Deletion
Status: PARTIAL — implemented via support process (Chapter 24)
Remaining: Automated in-app deletion flow. Required by Google Play policy
           for apps that collect personal data and allow account creation.
           Deferred to Version 2.1. Add dedicated /account/delete endpoint
           to backend and in-app confirmation flow.

## Refresh Tokens
Status: DEFERRED — Version 2.1
Condition: If user research identifies session expiry as significant pain.
           Re-login after 24h is current behaviour. Monitor session length
           data via PostHog before investing.

## Push Notification Inbox
Status: DEFERRED — Version 2.1
Notes: Straightforward extension of Chapter 19. Low effort, clear value.
       Next natural addition after the 2.0 launch stabilises.

## User Reviews/Ratings
Status: DEFERRED — Version 3.0
Condition: When PocketBoard has sufficient transaction volume to make
           fake review detection meaningful.

## Video Listings
Status: ARCHIVED
Decision: Transcoding pipeline cost and complexity is not justified.
          Curated photo upload (Chapter 8) meets current user needs.

## Data Safety Form Updates
Status: COMPLETE (updated throughout Parts III–VI)

## MessagesContext Split
Status: COMPLETE (Chapter 19)

## Performance.md Re-test
Status: IN PROGRESS — run Chapter 17 load tests against 2.0 backend
        after deployment.
