This issue is rather vague. I appreciate it, and I'll make a note where we list competing systems, but...
Airtable has over $10.6 million in funding to produce this system.
Essentially this issue is a "make a system as user friendly as Airtable" rather than a specific feature, and we couldn't do it without at least a six-figure investment specifically in that.
I also think that as we have templates for the different views, allowing these to be selected on the frontend (grid view, tabular, etc) would be a nice touch if no default is selected as an override to providing all 4 view options to members.
Mythus suggested something similar re finding records (I linked the issue).
To be clear the only reason this issue was closed is that it just wasn't something clear enough to manage. I am keeping Mythus's issue open as it's pretty specific, and if implemented could be done for all content types.
It is very unlikely this feature would make v11 as we have so many basic UX things to do (e.g. auto-fixing photo orientation as recently discussed, or the major theme upgrading): tackling UX for people with huge amounts of content is much more minority use case. That doesn't mean I don't want it to happen, e.g. in the future or if someone can contribute the code.
Airtable has over $10.6 million in funding to produce this system.
Essentially this issue is a "make a system as user friendly as Airtable" rather than a specific feature, and we couldn't do it without at least a six-figure investment specifically in that.
(Click to enlarge)
Mythus suggested something similar re finding records (I linked the issue).
To be clear the only reason this issue was closed is that it just wasn't something clear enough to manage. I am keeping Mythus's issue open as it's pretty specific, and if implemented could be done for all content types.
It is very unlikely this feature would make v11 as we have so many basic UX things to do (e.g. auto-fixing photo orientation as recently discussed, or the major theme upgrading): tackling UX for people with huge amounts of content is much more minority use case. That doesn't mean I don't want it to happen, e.g. in the future or if someone can contribute the code.