Skip to content

Conversation

@samholmes
Copy link
Contributor

@samholmes samholmes commented Aug 13, 2025

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

  • Tested on iOS device
  • Tested on Android device
  • Tested on small-screen device (iPod Touch)
  • Tested on large-screen device (tablet)
Simulator Screenshot - iPhone 15 Pro - 2025-08-13 at 12 37 57 Simulator Screenshot - iPhone 15 Pro - 2025-08-13 at 12 37 40 Simulator Screenshot - iPhone 15 Pro - 2025-08-13 at 12 28 37 Simulator Screenshot - iPhone 15 Pro - 2025-08-13 at 12 28 43 Simulator Screenshot - iPhone 15 Pro - 2025-08-13 at 12 28 46 Simulator Screenshot - iPhone 15 Pro - 2025-08-13 at 12 28 51

cursor[bot]

This comment was marked as outdated.

cursor[bot]

This comment was marked as outdated.

@Jon-edge
Copy link
Collaborator

Jon-edge commented Aug 15, 2025

image

I think there are better ways to start this flow. The UI/UX should always to the best of our ability make it obvious what to do without reading instructions on how to use the app.

There's only one thing to do in this part of the flow: to select the region. This entire flow can actually be gated by region selection. This is one aspect of our legacy flow that I liked.

If the country selection modal is dismissed, THEN we can expose a brief message on the scene:

"Select your region for personalized ways to buy crypto:" (personalized "options" sounds vague)
[Select your region]

The rest of the scenes similarly should make it obvious what to do for that particular step.

@Jon-edge
Copy link
Collaborator

Jon-edge commented Aug 15, 2025

image

The "Next" button is a moving tap target.

Anchor it to the bottom of the scene/top of the keyboard with KavButton.tsx. The initial implementation called for a full width button for KavButton, though I disagree with that design. This is a good opportunity to keep our UI unified and update it to typical button dimensions we use in the rest of our app.

@Jon-edge
Copy link
Collaborator

Jon-edge commented Aug 15, 2025

image

Is this always the exact rate? If it's a variable rate scenario, we should be sure to represent that with a "≈" sign

@Jon-edge
Copy link
Collaborator

Like we discussed, use KavButton and gate the LogBox suppression under an env.json var.

@samholmes
Copy link
Contributor Author

image The "Next" button is a moving tap target.

Anchor it to the bottom of the scene/top of the keyboard with KavButton.tsx. The initial implementation called for a full width button for KavButton, though I disagree with that design. This is a good opportunity to keep our UI unified and update it to typical button dimensions we use in the rest of our app.

We need to use KavButton to keep the button stable on the TradeCreateScene.tsx

@samholmes samholmes force-pushed the sam/ramp-plugins branch 2 times, most recently from bb609ef to c213502 Compare September 8, 2025 21:50
@samholmes samholmes mentioned this pull request Sep 8, 2025
6 tasks
This is an attempt to get the agent to automatically document lessons
learned to the docs/ directory. This way conventions are maintained and
over time as the agent is course corrected.
- Create docs/localization-guidelines.md with mandatory UI string localization rules
- Create docs/component-styling-guidelines.md with styled HOC usage patterns
- Update AGENTS.md with Documentation section indexing all docs/ files
- Add rule requiring all docs/ markdown files to be indexed in AGENTS.md
- Add localized strings for TradeRegionSelectScene to en_US.ts
This file contains run configuration such as RN_SIMULATOR and RN_PORT
to be used by a rn-ios script. This is for development purposes
This is a consistent card design for the new fiat buy UI.
- Implement TradeCreateScene and TradeOptionSelectScene for buy/sell flow
- Add Paybis as first ramp plugin with full API integration
- Create reusable hooks for ramp plugin management (useRampPlugins, useRampQuotes)
- Add payment type icon system with comprehensive mappings
- Implement quote fetching and comparison across multiple providers
- Add best rate badge component for quote comparison
- Create ramp plugin type definitions and store utilities
- Add comprehensive documentation for migration and architecture
- Include unit tests for payment types and store IDs
- Update navigation and deeplink handlers for ramp flows

BREAKING CHANGE: Replaces legacy FiatPluginUi with new ramp plugin system
@samholmes
Copy link
Contributor Author

Replaced by #5740

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants