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).
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.
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? 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).
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.
It’s an idea we have considered (vote on it here 
) 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).
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.
