# Ability to add developer comments in components in UX

**URL:** https://community.glideapps.com/t/ability-to-add-developer-comments-in-components-in-ux/26007
**Category:** Feature Requests
**Created:** [April 25, 2021, 9:45am UTC](https://community.glideapps.com/t/ability-to-add-developer-comments-in-components-in-ux/26007 "2021-04-25T09:45:21Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Mark\_Turrell](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark_turrell/32/26605_2.png) [@Mark\_Turrell](https://community.glideapps.com/u/Mark_Turrell)
#### Post date: [April 25, 2021, 9:45am UTC](https://community.glideapps.com/t/ability-to-add-developer-comments-in-components-in-ux/26007/1 "2021-04-25T09:45:21Z")

</div>

![Screenshot 2021-04-25 at 11.42.12](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/4/8/48e9699a3344e9dd6dc3b20278f4013e0ce2f921.png)

It gets really heard in complex apps to remember how everything fits together. For instance, I have found that the Delete Row action is quite slow (5 - 10 seconds) which means that I cannot assume that the row is actually deleted. This means I need an error trap somewhere to handle phantom rows.

OK, I get that… but I have been working on the app for 5 weeks, and it has lots and lots of pieces. And a few others have worked on the app.

It would be very useful to have a space for a comment in the UX designer for components - as warnings, let another person know where the component or data is used, etc.

---

<div class="post-metadata">

### Author: ![dregar](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dregar/32/20035_2.png) [@dregar](https://community.glideapps.com/u/dregar)
#### Post date: [September 30, 2021, 1:14am UTC](https://community.glideapps.com/t/ability-to-add-developer-comments-in-components-in-ux/26007/2 "2021-09-30T01:14:05Z")

</div>

Totally agree with this feature request. Coming as a traditional software developer, I find myself making so many “workarounds” in Glide. Without comments, pretty sure I will forget why I implemented things the way I did.