# Proposal: UI Hints in USD

**URL:** <https://forum.aousd.org/t/proposal-ui-hints-in-usd/2485>\
**Category:** USD\
**Created:** [May 30, 2025, 9:15pm UTC](https://forum.aousd.org/t/proposal-ui-hints-in-usd/2485 "2025-05-30T21:15:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![allisonb](https://avatars.discourse-cdn.com/v4/letter/a/71e660/32.png) [@allisonb](https://forum.aousd.org/u/allisonb)\
**Post date:** [May 30, 2025, 9:15pm UTC](https://forum.aousd.org/t/proposal-ui-hints-in-usd/2485/1 "2025-05-30T21:15:50Z")

</div>

Hi all,

I’ve just posted a PR proposal for expanding presentation metadata (aka UI hints) support in USD. Things like specifying a particular widget type for use when displaying an attribute, min/max values that numeric fields can enforce, and expressions defining dynamic hiddenness for attributes and display groups.

PR [here](https://github.com/PixarAnimationStudios/OpenUSD-proposals/pull/85)  
Rendered view [here](https://github.com/agb63/OpenUSD-proposals/blob/c64264479d0133f1c803d0050c5c4ce0e45c7e94/proposals/ui-hints/README.md)

Feedback welcome in this thread, or on the PR directly.

Thanks!  
Allison

---

<div class="post-metadata">

**Author:** ![allisonb](https://avatars.discourse-cdn.com/v4/letter/a/71e660/32.png) [@allisonb](https://forum.aousd.org/u/allisonb)\
**Post date:** [July 22, 2025, 6:48pm UTC](https://forum.aousd.org/t/proposal-ui-hints-in-usd/2485/2 "2025-07-22T18:48:50Z")

</div>

I just updated the proposal with our latest thinking, for anyone who’s following along:

```auto
* Removed reference to the locked hint, which will be addressed separately
* Added more detail to the limits discussion section
* Added arraySizeConstraint discussion section
* Noted deferral of widgetType and widgetOptions implementation

```

The big takeaway is the deferral on implementing `widgetType` and `widgetOptions`, for now. Some concerns have been raised in particular about them being open-ended and what that means for DCC vendors. We want to return to these fields in the future and make sure they’re fully baked, but in the meantime we don’t want to hold up implementation of the other fields.

The `arraySizeConstraint` core field, newly added to the proposal, will replace the array-related widget options that had been described in the proposal.

The updated rendered view is [here](https://github.com/agb63/OpenUSD-proposals/blob/f8cd7e40837b81953be812c14ac3bd65179e8f0b/proposals/ui-hints/README.md).