Repository navigation
feat(mobileapp): pay/request trigger, recipient search, note input, and visibility selector - #1103
Merged
ONEONUORA merged 1 commit intoSep 28, 2026
Conversation
…e input, and visibility selector Closes Fracverse#886, Fracverse#887, Fracverse#888, Fracverse#889 - Fracverse#886: Design 'Pay / Request' trigger button on home balance card to launch transfer flow - Fracverse#887: Update transfer flow to dynamically search recipients by Zaps ID - Fracverse#888: Implement Note / Description input field with 100 character limit in transfer flow - Fracverse#889: Implement Payment Visibility Selector with icons updating summary and confirmation cards
|
@GF-Hunter Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
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.
Closes #886
Closes #887
Closes #888
Closes #889
Summary
This PR addresses four assigned frontend issues enhancing the social transfer flow across the mobile app:
1. Design 'Pay / Request' trigger button (#886)
mobileapp/app/(personal)/home.tsx.TouchableOpacitywith primary background color (COLORS.primary), accessibility role, and clear labeling.router.push("/transfer")).2. Update transfer flow to search recipients (#887)
mobileapp/app/transfer.tsx./api/users/search) dynamically as the user types with debouncing.3. Implement Note / Description input field in Transfer flow (#888)
mobileapp/app/transfer.tsxasking what the payment is for with placeholder"What is this for? (e.g. Lunch 🍕)".maxLength={100}.4. Implement Payment Visibility Selector (#889)
PUBLIC,FRIENDS, andPRIVATEbefore sending.Testing & Quality
TransferConfirmationCardvisibility rendering