Contexts are illustrative. Final screens will reference actual GCash patterns (Send Money, Cash-In, Top-up).

• None yet — initial assessment.

• Peso Sign glyph is a raster image. The ₱ mark renders via an <img> reference (imgShapeFull) rather than an instance of the Peso Sign - Proxima vector icon. Raster assets can't be recolored with tokens, scale poorly on high-DPI screens, and block Code Connect asset mapping. C6 · Asset & Icon Quality
• Missing Active (focused) state. The component exposes only Default / Filled / Error. Native keyboards surface a caret on focus, but the DS has no defined focused-border or amount color — devs have to invent one per flow. C5 · Interaction State Coverage
• Missing Disabled state. Amount confirmations, locked top-up amounts, and review screens use an inert version of this field. Without a state=Disabled variant there's no single source of truth for its appearance. C5 · Interaction State Coverage
• label property uses yes/no instead of true/false. Boolean naming. label=Yes doesn't map cleanly to Swift Bool / Kotlin Boolean, and it diverges from sibling fields that were already migrated to true/false (Input Field's isFilled). Should also be renamed to hasLabel or showLabel. C2 · Variant & Property Naming
• Large variant drops the peso glyph. When size=Large the ₱ is removed entirely — the amount is just 500.00. If this is intentional it's under-documented; if not, it's an inconsistency that users and devs will stumble on. No property controls it, so it can't be opted into. C2 · Variant & Property Naming
• Code Connect mappings not registered. Blocked by the structural issues above — register after peso glyph is vectorized, states are added, and label is migrated to Boolean. C7 · Code Connect Linkability

• Replace the raster peso with a vector instance of Peso Sign - Proxima. That library component already exists and is sized per font tier — swap the current <img> for an instance-swap slot so color can bind to main/amount-text-field/{state}/icon-currency and scale at any DPR. Asset
• Add state=Active and state=Disabled variants. Extends the enum to the same 4-state model used by Input Field (Default / Active / Error / Disabled) plus a Filled display-only state, or collapse Filled into a derived-from-content view. Either way, lock the state axis to match siblings. State
• Migrate label=yes/no to a Boolean showLabel=true/false. Matches the canonical naming used by Input Field's isFilled and unlocks direct Code Connect mapping to Swift Bool / Kotlin Boolean. Consider splitting subtext out as its own Boolean so error-copy and helper-copy can be toggled independently of label. Rename
• Expose leading and trailing slots for the currency mark and unit suffix. Hard-coding the peso glyph ties the component to PHP. A leadingCurrency slot (₱, $, €) and an optional trailingUnit slot ("PHP") future-proofs the component for multi-currency flows without a per-country fork. Slot
• Family decision — fold into Input Field as type: .currency, or keep as EBAmountTextField sibling. Option A: Keep separate — Amount Text Field stays a display-style sibling of Input Field with its own underline anatomy; share tokens via a common text-field token tier. Option B (recommended): Fold into Input Field as EBInputField(type: .currency, …), using SwiftUI's TextField(value:format:.currency(code:)) + .keyboardType(.decimalPad) and Compose's OutlinedTextField(keyboardOptions = KeyboardOptions(keyboardType = KeyboardType.Decimal), leadingIcon = { Text("₱") }). Option B eliminates the duplicate peso glyph instance inside Dropdown's "Amount" variant and the Recipient Field's currency-prefix case. Family
• Document locale and keyboard behavior in the component. Decimal separator, thousands separator, minimum/maximum, and zero-padding rules are product concerns today. Adding a short Docs note in Figma (or in this assessment's Code tab) gives implementers a single source of truth. Docs