Typical mobile contexts: feedback forms, message composers, notes, support request descriptions.

• Boolean property uses Yes/No. isFilled=yes/no cannot map to Swift Bool or Kotlin Boolean without a translation layer. Input Field already fixed this — Text Area should follow. C2 · Variant & Property Naming
• Desktop resize-handle glyph baked into a mobile component. The text-area icon (12×12px, bottom-right) mirrors the browser-only resize: both affordance. Native TextField(axis: .vertical) / OutlinedTextField(maxLines = n) auto-grow without a user-facing handle — the glyph has no native equivalent and should not ship in mobile variants. C4 · Native Mappability
• Resize handle is a raster PNG, once per state. Four separate PNG assets are referenced for the same 12×12px glyph. Even if the handle survives, it should be a single vector instance tinted by main/text-area/color/{state}/icon-resizer. C6 · Asset & Icon Quality
• No label or helperText slot. Labels and validation messages are handled by the consumer, so every screen re-implements the anatomy. Native multi-line text fields expose both as first-class parameters. C5 · Interaction State Coverage
• No characterCount / limit affordance. Multi-line entry is the canonical use case for character limits (comments, reviews, message composers). There is no count slot and no maxLength hook — the DS cannot represent limit state today. C5 · Interaction State Coverage
• Tokens duplicated under main/text-area/*. Every value in main/text-area/color/* mirrors main/input-field/color/* exactly. If Text Area folds into Input Field, this namespace collapses; if it stays, the two token sets should alias a shared main/field/* collection to prevent drift. C1 · Layer Structure & Naming
• Code Connect mappings not registered. Blocked by property naming and the multi-line-vs-Input Field decision. Cannot register until the family shape is finalized. C7 · Code Connect Linkability

• Fold Text Area into Input Field as a multiline / lineLimit prop. SwiftUI models this as TextField(text:, axis: .vertical).lineLimit(3...6); Compose models it as OutlinedTextField(singleLine = false, maxLines = 6). Both are the same primitive with a single flag. Mirroring that in Figma collapses 8 variants into 0 net new variants on Input Field (add a multiline boolean to the existing 8-variant matrix) and removes the duplicated token namespace. Family
• Rename isFilled to use true/false. Same fix Input Field already shipped in 1.1.0. Required for Swift Bool / Kotlin Boolean mapping. Rename
• Rename state=active to state=focused. Matches SwiftUI @FocusState and Compose FocusRequester vocabulary. Apply to Input Field and the whole Form Elements family at once so the rename lands once. Rename
• Drop the desktop resize handle on mobile variants. If Text Area survives as a sibling, remove the expand-icon frame — it has no native equivalent on iOS/Android. Keep it only if a web/desktop DS variant is in scope, gated behind a platform axis. Asset
• Add a helperText slot and a characterCount slot beneath the field. Multi-line is the canonical character-count surface. Expose a supporting-text row that can host either error copy, hint copy, or a count — matching Material 3's supportingText / counter pattern. If Text Area folds into Input Field, this slot lives on Input Field and serves both single- and multi-line. Slot
• Alias main/text-area/* to a shared main/field/* collection. If the family stays split for any reason, the two token sets must reference a single source so border/bg/placeholder/disabled colors never drift. Preferable outcome: delete main/text-area/* outright after consolidation. Token