Hi Tap‑Payments / Card‑Flutter team,
I’d like to request a feature enhancement: the ability to auto‑focus the first input field (card number) in the TapCardViewWidget when it’s displayed, and open the keyboard automatically.
Use case / motivation:
Improves UX: user can start typing card details immediately without needing to tap the form field.
Reduces friction, especially on mobile devices.
Proposal:
Add a bool autofocus parameter to TapCardViewWidget (default: false). So keyboard basically open so user not impose efforts to click on widget.
Optionally, allow passing a FocusNode (e.g., cardNumberFocusNode) so consumers can control focus programmatically.
Hi Tap‑Payments / Card‑Flutter team,
I’d like to request a feature enhancement: the ability to auto‑focus the first input field (card number) in the TapCardViewWidget when it’s displayed, and open the keyboard automatically.
Use case / motivation:
Improves UX: user can start typing card details immediately without needing to tap the form field.
Reduces friction, especially on mobile devices.
Proposal:
Add a bool autofocus parameter to TapCardViewWidget (default: false). So keyboard basically open so user not impose efforts to click on widget.
Optionally, allow passing a FocusNode (e.g., cardNumberFocusNode) so consumers can control focus programmatically.