b2c-android-explain-flow

To trace an Android flow from UI to API, provide a keyword to scan code references across Screen, ViewModel, UseCase, and Repository components. This generates a coherent end-to-end flow description mapping UI interactions to API calls for debugging or onboarding.

Mapping a keyword like login through Android MVVM layers involves scanning component references from Screen to ViewModel to UseCase to Repository. This documents the full orchestration path, clarifying how UI actions trigger API calls across the app's architecture.

Yes, you can trace purchases, favorites, and reviews flows in a B2C Android app by providing the relevant keyword. The analysis scans UI interactions and UseCase orchestration to assemble a clear description of how these specific user actions reach the API.

No dependencies or specific components are required to run this flow trace. It operates by scanning existing code references and related PRD or documentation within your Android project to assemble the end-to-end flow mapping.

To start analyzing a Screen to ViewModel to API flow, simply provide a keyword related to the feature. The analysis scans code references across components and related PRDs to document the complete data flow from UI interaction to API execution.

The primary limitation is that tracing code references across Android app components requires scanning existing code and related PRDs. If the codebase lacks clear MVVM separation across Screen, ViewModel, UseCase, and Repository, the assembled flow description may be incomplete or fragmented.