Fixes Issue #67 feat: Add Jetpack Navigation to Sample App - #75
Open
tokelo-12 wants to merge 1 commit into
Open
Fixes Issue #67 feat: Add Jetpack Navigation to Sample App #75tokelo-12 wants to merge 1 commit into
tokelo-12 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe the changes proposed
Summary of Changes
This pull request introduces the Jetpack Navigation Component to the sample app, transforming it from a single-screen demonstration into a multi-screen, state-driven workflow that better reflects a real-world Android application architecture.
1. Added Navigation Structure
Introduced the Jetpack Navigation dependencies (
androidx.navigation:navigation-compose).Implemented a central NavHost to manage app routing and screen transitions.
2. Screen Modularization
Split the existing monolithic UI into distinct, single-responsibility composable screens:
ProductScreen: Displays product details, pricing, and the Google Pay trigger button.
PaymentsSuccessScreen: Displays a success confirmation view along with dynamic user data (e.g., payer name) passed via navigation arguments.
3. State-Driven Navigation Flow
Configured the app to automatically navigate from the ProductScreen to the PaymentSuccessScreen upon successful completion of the Google Pay transaction state (PaymentUiState.PaymentCompleted).