bytelyst/learning_ai_notes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
main
learning_ai_notes/docs/roadmaps/11_MOBILE_REUSE_ALIGNMENT_ROADMAP.md
saravanakumardb1 4667f85e20 docs(cleanup): move historical roadmaps to docs/archive/ and update AGENTS.md 
Sprint B — closes audit item B7 (doc consolidation).

- docs/AGENT_TASK_ROADMAP.md, docs/ARCHITECTURE_REVIEW_AND_REUSE_ROADMAP.md,
  docs/GAP_ANALYSIS.md were each self-marked as historical snapshots
  but kept polluting the top of docs/. Moved them under docs/archive/
  in the previous commit; this commit:
  - Adds docs/archive/README.md explaining what's archived vs active
  - Repoints cross-doc links in docs/IMPLEMENTATION_TRACKER.md,
    docs/WEB_AI_FAST_ROADMAP.md, and docs/roadmaps/*.md to the new
    archive paths
  - Fixes relative links inside the archived files themselves so
    historical readers can still navigate back to active docs
- AGENTS.md §1.1 refreshed: reflects the May 22 re-verified state
  (382/96/97 tests), links the two new runbooks, and points readers
  away from docs/archive/ as a work source.
2026-05-22 23:23:50 -07:00

3.8 KiB
Raw Permalink Blame History

Mobile Reuse Alignment Roadmap

Historical reuse roadmap. This draft is superseded by ../PRODUCTION_READINESS_HANDOFF_ROADMAP.md for active production-readiness execution. Current mobile SDK/sync/platform decisions are tracked there in P2 and P7.

Status: Draft Parent: docs/archive/ARCHITECTURE_REVIEW_AND_REUSE_ROADMAP.md Scope: mobile/

Goal

Make the React Native / Expo MVP follow the ByteLyst reuse-first path more strictly by removing temporary local wrapper code and relying on shared clients and shared platform capabilities wherever available.

Baseline Already Confirmed

  • mobile follows the intended Expo / React Native MVP path
  • mobile/package.json already consumes multiple shared @bytelyst/* packages
  • @bytelyst/offline-queue is already part of the current mobile direction

Phase M0 — Identity and Config Alignment

  • Align mobile config with shared/product.json
  • Remove hardcoded raw identity values where a canonical source can be used
  • Standardize auth storage prefix with web/backend
  • Standardize platform/product base URL strategy

Phase M1 — Shared Client and SDK Alignment

  • Keep @bytelyst/auth-client as auth foundation
  • Keep @bytelyst/api-client as product-backend client foundation
  • Keep @bytelyst/platform-client as platform-service client foundation
  • Keep @bytelyst/offline-queue as queue foundation
  • Evaluate actual runtime adoption path for @bytelyst/react-native-platform-sdk

Dependency Notes

  • Complete M0 before broad auth/storage cleanup
  • Complete M2 before declaring mobile reuse alignment healthy
  • Use backend contract decisions to drive M3 data-shape cleanup
  • Coordinate telemetry/diagnostics/blob/extraction choices with the platform/shared-services roadmap

Phase M2 — Remove Placeholder Local Wrappers

Checkpoint:

  • Placeholder wrapper cleanup completed in 86e2da8
  • Delete or replace mobile/src/lib/platform.ts
  • Delete or replace mobile/src/lib/telemetry.ts
  • Audit other local helper files for no-op or placeholder behavior
  • Keep only thin product-specific composition helpers that add real value

Phase M3 — Replace Fallback Runtime Paths

Checkpoint:

  • Mobile backend-backed runtime alignment completed in 8580ad3

  • Replace fallback notes as the primary runtime path

  • Replace inline workspace returns with real API calls

  • Persist note edits to the backend

  • Align mobile note detail with real backend fields

  • Ensure approval/activity flows use real backend-backed data where intended

Phase M4 — Shared Platform Completion

  • Wire real telemetry through shared client/runtime path
  • Wire diagnostics if supported on the selected RN path
  • Keep blob/extraction/feature flag integrations on shared-platform rails
  • Avoid creating product-local substitutes for shared platform capabilities

Phase M5 — Verification

  • Add tests for auth/bootstrap behavior
  • Add tests for API wrapper behavior
  • Add tests for store behavior under real backend contracts
  • Add smoke tests for note list/detail/edit flows

High-Collision Areas

  • mobile/src/api/config.ts
  • mobile/src/api/auth.ts
  • mobile/src/api/client.ts
  • mobile/src/api/notes.ts
  • mobile/src/api/workspaces.ts
  • mobile/src/lib/platform.ts
  • mobile/src/lib/telemetry.ts
  • mobile stores that assume local-only persistence

Done When

  • mobile relies primarily on shared clients and shared platform capabilities
  • no fake wrapper files remain
  • no inline workspace or long-term fallback note runtime remains
  • notes-specific mobile UX remains local and intentional