When grouping records, another column is added to the UI. In tables with a lot of fields, this takes up valuable horizontal real estate. It would also be nice to have the option to collapse each group.
I don’t want to say you should blatantly rip off a competitor, but I really like how Airtable handles this. Borrowing some of this UI would greatly improve the experience when grouping records.
Thanks for sharing this great idea, @shawn! I’ll communicate it to the team. 
Hey @shawn, I’m back with some updates on your feedback. We plan to implement all the features you mentioned. Here are the links to track the progress:
Hopefully this feature will be implemented soon 
Not sure why there wasn’t such a feature already, since it’s such a crucial QOL feature when groups are used.
And conditional rollups/lookups too, which are even more important, imo — I’m rebuilding the database from Airtable, but even after Airtable import feature, it’s such a massive PITA, because the Airtable one used conditionals quite a lot.
For example, lookup the “Price” in “Invoices”, but filter only ones with “Unpaid” (or “Paid”) status in “Status”. I’ve created so many fields to create workarounds and, not gonna lie, I got pissed off so much while doing this.
Honestly speaking, I thought transition from Airtable to Baserow would be so much easier. I understand that Airtable is a super-duper-massive company, but lack of some features is mind-boggling. There are “Automations” and “Applications Builder”, and even an AI “companion” while core functionality (Databases) need lots of UX tweaks (I listed only two, but I have more issues that I will give feedback on later). I might be wrong, but I don’t think Baserow has such a massive team with different dev groups that are focused on multiple things, hence why I don’t understand lack of UX in quite many areas.
P.S: Not trying to offend Baserow team, I’m not saying Baserow is a bad product, I do think it’s pretty nice and good, but I thought the number 1 alternative to Airtable would be very toe-to-toe with it, but that’s not the case. I’m half glad that I offered Baserow as an alternative to my client, half upset and think that I should’ve kept using Airtable instead.
Hey @Georgy, thanks for the detailed feedback!
We’re actively working on improving many UI/UX aspects of the core database and addressing smaller issues as quickly as we can.
For example, collapsing rows in a group by is currently planned for Q2:
Conditional filters for the Lookup field are also on our roadmap: