Track final stages of MVP development and release readiness

[pedrazamiguez]

Problem / Motivation

As SplitTrip enters the final stages of its MVP development, several critical blocks of work (bugfixes, nice-to-haves, settlements, missing features, monetization, publishing) are currently unstructured. Without a consolidated roadmap and checkpoint tracker, the team risks scope creep, broken user loops, and out-of-order development.

Proposed Solution

Establish a master tracking issue (this checkpoint issue) listing all planned epics and sub-issues. Progress will be tracked incrementally across 6 core phases:

1. Phase 1: Core Flow Rescue (Settlement & Teardown Stabilization)
2. Phase 2: Navigation Cleanup & Status Hub (3-tab bottom nav & "My Status" screen)
3. Phase 3: Expenses Analytics & Filtering (Categories summary & search filters)
4. Phase 4: Settings Clean-up & Completion (Removal of redundant items, implementing missing items)
5. Phase 5: Feature Gating & Remote Config Parameterization (Subscription tier & remote limits)
6. Phase 6: Release Polish & Productionization (UI audit, Proguard, Play Store config)

Detailed implementation plans and individual PRs will be created for each sub-issue.

Acceptance Criteria

• Epics and sub-issues are formalized on GitHub.
• Progress checklist in this issue is updated as sub-issues are resolved.
• Phase gates are respected (Phase N must be complete before closing Phase N+1 sub-issues).
• All existing and new tests pass on the CI pipeline.
• make check passes with 0 failures on all merged PRs.
• No new detekt findings introduced.

Out of Scope

• Implementing code changes directly under this issue.
• Auto-creating all sub-issues on GitHub simultaneously.

Related Issues / PRs

• Relates to Introduce "My Status" & Standalone Settlement Resolution Hub on Balances Screen #1354 (My Status screen)
• Relates to Implement Excel Import/Export for groups and expenses #1207 (Excel import/export)
• Relates to Support actual payment amount confirmation and rate-shift tracking for foreign scheduled expenses #1400 (Foreign scheduled expenses)
• Refers to settlement-acknowledgment-and-consensus.md

[pedrazamiguez]

SplitTrip MVP Release Roadmap & Checkpoint (Finalized)

This document outlines the final stages of the SplitTrip MVP development. It incorporates your feedback, cleans up redundant settings list entries, and establishes a highly granular breakdown of sub-issues.

---

🗺️ Recommended Implementation Order

graph TD
    P1[Phase 1: Settlement & Group Exit Stabilization] --> P2[Phase 2: Navigation Cleanup & Status Hub]
    P2 --> P3[Phase 3: Expenses Analytics & Filters]
    P3 --> P4[Phase 4: Settings Clean-up & Completion]
    P4 --> P5[Phase 5: Feature Gating & Remote Config Parameterization]
    P5 --> P6[Phase 6: Release Polish & Productionization]

Loading

🔴 Phase 1: Core Flow Rescue (Block 4)

• Focus: Fixing group settlement calculations, exit flow, and group deletion/archiving.
• Rationale: A trip-expense app is non-functional if users are blocked when attempting to settle debts or leave groups. These flows must be stable first.

🟡 Phase 2: Navigation Cleanup & Status Hub (Block 5 - Status/Logger)

• Focus: Decommissioning the Activity Logger and establishing a 3-tab layout. Building the "My Status" screen.
• Rationale: We simplify the navigation bar and provide a dedicated personal overview screen for virtual pocket, cash in hand, and active settlements.

🟢 Phase 3: Expenses Analytics & Filters (Block 5 - Categories/Filters)

• Focus: Expense categorization summaries on the Balances screen and advanced list search & filters.
• Rationale: We enrich the balances tab with visual spending category breakdowns and introduce robust list search and multi-select filtering for expenses.

🔵 Phase 4: Settings Clean-up & Completion (Block 3)

• Focus: Consolidating redundant items (since Email linking is already handled in Account Status), cleaning up dead developer utilities, and building the remaining settings screens/intents.
• Rationale: Ensure settings are fully functional without redundant items or dead-end placeholders.

🟣 Phase 5: Feature Gating & Remote Config Parameterization (Block 2 & Block 5 - Monetization)

• Focus: Transitioning to a premium subscription tier model with feature gating and Remote Config controls.
• Rationale: Rather than AdMob (which conflicts with offline use), we review and expand the FeatureGateService to support free vs. premium tiers (AI receipt scans, group limits), parameterized via Firebase Remote Config. Complete Excel Import/Export.

🟤 Phase 6: Release Polish & Productionization (Block 1 & Block 7)

• Focus: UI/UX visual audit, Proguard configurations, and Google Play console setup.
• Rationale: Readying the application for public distribution.

---

📂 Epic & Detailed Issue Breakdown

Epic 1: Group Settlement & Teardown Flow Stabilization (Block 4)

• Issue 1.1 (bug): Refactor LeaveGroupUseCase to implement the "True Offline" write protocol #1405 Refactor LeaveGroupUseCase to implement the "True Offline" write protocol. Generate local UUIDs and write to Room first, then delete related Firestore subcollections (memberships, subunit assignments) before deleting parent group structures to avoid listener crashes.
• Issue 1.2 (bug): Refactor ArchiveGroupUseCase (End Trip) to implement the "True Offline" write protocol #1406 Refactor ArchiveGroupUseCase (End Trip) to use the "True Offline" write protocol, writing updates to Room first, then syncing, and gating explicitly on resolved settlements.
• Issue 1.3 (bug): Fix and stabilize the offline-first Settlement Consensus state machine (ConfirmSettlementUseCase / DisputeSettlementUseCase) #1407 Fix and stabilize the offline-first Settlement Consensus state machine (ConfirmSettlementUseCase / DisputeSettlementUseCase). Resolve counterparty identity checks (debtor/creditor) and handle DISPUTED transitions correctly in Room and Firestore.
• Issue 1.4 (feature/ui): Redesign the "Leave Group" wizard to display net positions, list pending settlements, and block exit until resolved #1408 Redesign the "Leave Group" UI Wizard to clearly display the user's net positions, list pending settlements, and block exit until they are resolved.
• Issue 1.5 (feature/ui): Redesign the "End Trip" / Archive UI flow as a guided consensus wizard for group creators #1409 Redesign the "End Trip" / Archive UI flow to guide the group creator on requesting consensus for all remaining unresolved group settlements before archiving.

Epic 2: Bottom Navigation Redesign & "My Status" Hub (Block 5 - Status/Logger)

• Issue 2.1 (config): Remove the :features:activity-logging stub module and establish clean 3-tab layout #1423 Remove the :features:activity-logging module, cleanup dependencies in :app configuration (FeatureModuleAggregations.kt and Koin registrations), and establish a clean 3-tab layout (Groups, Expenses, Balances).
• Issue 2.2 (feature): Implement "My Status" screen routing and wire Balances top-bar action #1429 Implement the "My Status" screen routing. Wire the top-bar main action button (TablerIcons.Outline.ChartArcs) in Balances tab to navigate to the new "My Status" screen.
• Issue 2.3 (feature): Build "My Status" Personal Position Card component #1430 Build "My Status" Personal Position Card to display the logged-in member's virtual pocket balance, physical cash in hand, and net position.
• Issue 2.4 (feature): Build "My Status" Settlement Consensus list #1431 Build "My Status" Settlement Consensus list, listing active suggested, payer-confirmed, or disputed settlements involving the current user, and providing action buttons (Confirm/Dispute).
• Issue 2.5 (feature): Write unit tests for the "My Status" ViewModel and UI Mapper following MVI triad guidelines #1432 Write unit tests for the "My Status" ViewModel and UI Mapper following the MVI triad guidelines.

Epic 3: Expenses Analytics & Filters (Block 5 - Categories/Filters)

• Issue 3.1 (feature): Build a Category Spending Summary section inside the Balances screen. Render localized visual breakdowns (donut chart/bar graph) for spending categories (accommodation, food, transport, etc.) within the active group.
• Issue 3.2 (feature): Implement a search bar on the Expenses List screen to filter expenses dynamically by title or notes.
• Issue 3.3 (feature): Implement category multi-select chip filters on the Expenses List screen.
• Issue 3.4 (feature): Implement member/payer filters on the Expenses List screen to filter by who paid or who is involved in the split.
• Issue 3.5 (feature): Implement date range filters on the Expenses List screen to filter by creation date.

Epic 4: Settings Clean-up & Completion (Block 3)

• Issue 4.1 (cleanup): Clean up redundant settings options. Remove settings_account_email_title (Email) from the parent settings screen list, as email linking and provider management are already fully implemented inside the Account Status screen (AccountStatusFeature).
• Issue 4.2 (cleanup): Remove the three dead-end developer placeholders: settings_developer_layout_title (Layout), settings_developer_widgets_title (Widgets), and settings_developer_assets_title (Assets) from the settings list. Keep Developer Services (Routes.SETTINGS_DEVELOPER_SERVICES) for OCR/AI debug testing.
• Issue 4.3 (feature): Implement the Subscriptions Management screen (Routes.SETTINGS_SUBSCRIPTIONS) to show available plan options, current user tier status (Free vs Premium), and a simulated purchase flow.
• Issue 4.4 (feature): Implement the Account Security screen (Routes.SETTINGS_SECURITY) to handle password reset requests, biometric lock options, or direct credential updates.
• Issue 4.5 (enhancement): Wire Support Option email intents. Implement click handlers for settings_support_feature_title (Suggest a feature) and settings_support_support_title (Contact support). Extend SupportEmailProvider with buildFeatureSuggestionEmail() and buildContactSupportEmail() to launch pre-filled email client intents.
• Issue 4.6 (feature): Implement the Developer Info screen (Routes.SETTINGS_DEVELOPER_INFO) to display credits, license lists, and app copyrights.

Epic 5: Feature Gating & Remote Config Parameterization (Block 2 & Block 5 - Monetization)

• Issue 5.1 (feature): Extend the User models. Add a tier field (enum: FREE, PREMIUM) to the User domain model, Room UserEntity, and Firestore UserDocument to sync subscriptions offline.
• Issue 5.2 (feature): Update FeatureGateServiceImpl to check user tier instead of simple anonymous checks. Gated limits should check database values and remote config thresholds.
• Issue 5.3 (feature): Parameterize limits via Remote Config. Expose variables like max_groups_count_free, max_groups_count_premium, and ai_receipt_monthly_limit_free in AppConfigRepository.
• Issue 5.4 (feature): Implement a feature gating bypass flag (subscription_gating_enabled) in Remote Config to globally enable/disable limits for promotions or outages.
• Issue 5.5 (feature): Finalize Excel Import/Export integration (Issue Implement Excel Import/Export for groups and expenses #1207) including validation banners, file shares, and background offline sync.

Epic 6: Release Polish & Productionization (Block 1 & Block 7)

• Issue 6.1 (enhancement): Perform a comprehensive UI/UX review of all screens to ensure compliance with the "Horizon Narrative" design system (gradients, micro-animations, glassmorphism).
• Issue 6.2 (config): Configure Proguard / R8 rules for release. Test compilation to ensure Kotlin serialization and Firebase/Room structures are not stripped, and check file size limits.
• Issue 6.3 (config): Setup production configurations, Google Play Console signing keys, and manual/CI publishing pipelines.