# 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:** 1\ **Showing post:** 36
**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:** [January 9, 2026, 3:59pm UTC](https://community.fibery.io/t/frontend-is-essential/8991/36 "2026-01-09T15:59:44Z")
Thanks @Eren_Turgut. There’s a lot there, and it’s really good feedback 🙇 I can try and address some of these observations, and maybe place my responses in context of how we decide what to focus on (as evidenced by our strategy 2026 document). > [@Eren\_Turgut](#): > > Still, the UI feels a bit “clunky” > > … > > the UI still needs some urgent improvements. I feel like it should have been a significant part of the (recently released) strategy but it was barely mentioned. Yes. Fibery’s UI is not best-in-class, but we are trying to make continual improvements. Our strategy (as you have seen) is to focus on “_people who need power, embrace complexity, get abstractions and share our culture_”. Fibery is inherently complex. This makes it even more of a challenge to come up with a UI that works for everyone. But we won’t give up. > [@Eren\_Turgut](#): > > What if we could create “Dashboards” within Entity views, what if we could format field names, group fields together, have control over how compact they are etc. 💯 Something like this will almost certainly happen at some point. The only question is when - and this is decided by balancing it against the other opportunities we have to add value. For example, would our users (and potential users) appreciate this more (or less) than [validation rules](https://the.fibery.io/@public/Public_Roadmap/Roadmap_Item/Validation-rules-basic-use-cases-428)? At the moment, we think the latter will resonate with our target, so we’re working on that. But we do prioritise based on feedback, so the mere act of you mentioning the idea of dashboard as an entity view will serve to increase its score (and thus likelihood of being developed). > [@Eren\_Turgut](#): > > Add full table capabilities incl. in-cell formulas, pivoting, cell coloring > > … > > Most people are used to Spreadsheets, where you show a lot of information in such a nicely formatted way in a single window, due to grouping, highlighting, and overall formatting possibilities. Probably less likely. The behaviours of spreadsheets are fundamentally different to those of databases. Something like in-cell formulas would imply that each cell represents a unique calculation (record) and thus it would grow the data management complexity by an order of magnitude. Cell coloring? Maybe, since this could potentially be a front-end implementation. > [@Eren\_Turgut](#): > > Now here’s an idea: integrate the idea of Fiberflow (or Fiberflow itself) into Fibery. > > … > > where a CSS Script entity holds a piece of CSS customization code, which somehow can be “injected” to the users via automation > > … > This way, people could customize, present and share individual tweaks like many already existing in Fiberflow, or even entire Layouts, in the form of space templates. > > … > > I don’t know, I’m brainstorming. It’s an idea we have considered (vote on it [here](https://community.fibery.io/t/natively-integrated-custom-css-and-editor-for-fibery-workspaces/3921) 😉 ) but potentially this is an example of something we might not prioritise because it’s actually _too_ ‘nerdy’ for some people 🤷 As it happens, the Fiberflow extension (thanks @derbenoo ) was a great opportunity for people to experiment, and thus gave some insight into what people would value. But as far as I know, the extension did not achieve massive adoption, so this is perhaps a sign that it’s not something for us to replicate (yet). (or it could be a sign that people didn’t know about it, or chose not to use it because it only works at a per-user level rather than per-workspace). > [@Eren\_Turgut](#): > > Lack of “visual distinction” of information pieces belonging together → I call it visual clarity: > > - … > - … These are all valid opinions/suggestions, and you’re welcome to elaborate on them here in the community 🙏 (and/or ping us in intercom to tell us when they/others are complete PITA dealbreaker issues for you!) As I said in an earlier post, having a load of constructive criticism in a single generic topic like this is great for aggregation purposes, but is hard for us internally to process in prioritisation terms. Currently there are 8 votes for this topic. If it suddenly jumped to 25 votes, we would never know if those people were voting for CSS tweaks, cell coloring, header wrapping, etc. but we will of course log these requests. > [@Eren\_Turgut](#): > > That being said I love Fibery and have followed Fibery’s development for over 4 years now (dopamine hit each Thursday 😍), and I am confident you guys will continue to improve Fibery and I will continue to get that dopamine hit each Thursday (i.e. build on and use Fibery)😁 🫶 --- _[View the full topic](https://community.fibery.io/t/frontend-is-essential/8991)._