# Frontend is essential! **URL:** \ **Category:** Ideas & Features\ **Created:** [June 15, 2025, 12:31pm UTC](https://community.fibery.io/t/frontend-is-essential/8991 "2025-06-15T12:31:56Z")\ **Posts on this page:** 5\ **Page:** 3
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [May 12, 2026, 12:22pm UTC](https://community.fibery.io/t/frontend-is-essential/8991/41 "2026-05-12T12:22:29Z")
Yes, I do use them a lot. But it’s not enough ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [May 12, 2026, 1:04pm UTC](https://community.fibery.io/t/frontend-is-essential/8991/42 "2026-05-12T13:04:07Z")
> [@myg\_ge](#): > > But it’s not enough What’s missing? ---
**Author:** ![Eren\_Turgut](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eren_turgut/32/4425_2.png) [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)\ **Post date:** [May 12, 2026, 2:26pm UTC](https://community.fibery.io/t/frontend-is-essential/8991/43 "2026-05-12T14:26:15Z")
What’s missing is a nice UI contributing to a positive UX I already described here in-depth: > [@Eren\_Turgut](#): > > Lack of “visual distinction” of information pieces belonging together → I call it visual clarity: > > - Lack of control over semantic grouping of fields (e.g. Address, Personal data etc. fields..) > - Lack of (control over) distinction between expected input fields and informational fields (could be view-dependent) > - Poor “label-to-content” contrast > - Tabs of Entity views > - Tabs of pinned Relation Views > - Field names: > - To-many Relation view can show lots of information, especially with multiple views within, but it takes too much conscious effort to scan and understand where to click. Relation name and views within are too blended background. > - Using to-many relation field with views within is a necessary work-around for many workflows, which I might want to describe in form of a title, but I can only use relation name. > - Rich text field headers are barely visible, this becomes especially obvious between two RT fields. > > - inefficient use of space overall > - incl. extensive padding > - worsened by the problems above > > - Visual clarity in sidebar Full rant: > [@Frontend is essential!](https://community.fibery.io/t/frontend-is-essential/8991/35): > > Rant on: I agree it’s hard to pinpoint exactly what the “wish” is here, but the underlying “pain point” is the UI. I believe the argument, and maybe I’m conflating with my own arguments here as well, is that Fibery is extremely powerful in its capabilities and a heaven for nerds like me/us who deeply enjoy using those capabilities to ease our and other’s lives. But as much as we control what happens in the back-end, especially with scripting and API, and we lack on the front-end, which is the … Multiple Entity views are great, but they don’t solve the problem of providing the necessary information to a user in a well-digestible format. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [May 12, 2026, 4:32pm UTC](https://community.fibery.io/t/frontend-is-essential/8991/44 "2026-05-12T16:32:27Z")
If you think that topic covers the need, then I will merge this topic into that. @myg_ge do you consider your need covered by the discussion in that topic? ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [May 12, 2026, 5:08pm UTC](https://community.fibery.io/t/frontend-is-essential/8991/45 "2026-05-12T17:08:58Z")
100% agree [Previous page](https://community.fibery.io/t/frontend-is-essential/8991.md?page=2)