# 🐢 Fibery Product Report: April 2025 **URL:** \ **Category:** News & Announcements\ **Created:** [May 15, 2025, 12:35pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794 "2025-05-15T12:35:37Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [May 15, 2025, 1:23pm UTC](https://community.fibery.io/t/fibery-product-report-april-2025/8794/3 "2025-05-15T13:23:28Z")
Although April was “slow,” personally, I’m happy with the quality of the updates that were made. I’m partial to developers and good process so I’m biased here. But I don’t mind slowness when the features are thorough and effective. However, I’ve been watching the roadmap and I’m noticing that improving entity layouts hasn’t made it to the list of priorities for the year. I know Fibery is younger and smaller than a lot of tools in the space, but I find that the older my Fibery workspace gets, the more I’m in need of solutions grouping fields visually (workflow management) and archiving, but not deleting databases that have become out-of-service. The discussions may not have a lot of steam but I know these features will make a big difference for heavy users. > [@Declutter the entity display by grouping fields in collapsible field groups](https://community.fibery.io/t/declutter-the-entity-display-by-grouping-fields-in-collapsible-field-groups/4603): > > Declutter the entity display by grouping fields in collapsible field groups. Currently the fields, especially many to many relation fields which cannot be hidden, are taking up a lot of space and is a big UX tension. In general, I see that users (including myself) work mostly with title and richt text content of entities. Although Fibery apears more structure oriented, day to day work with Fibery requires a lot of clicks and the fields are a big distraction. Drupal solved this also with the f… > [@Archive Databases/Spaces without Deletion](https://community.fibery.io/t/archive-databases-spaces-without-deletion/8208): > > As companies grow and evolve some databases should become read-only and/or removed from day to day operations. How are people handling this right now? I often avoid creating databases in Fibery for small projects or project specific data because there is no way to “Archive” a database or space. Examples: When building a custom workspace for a client (in Notion or Fibery) I often map out fields and their functions. When working in Fibery I do this off platform, but I would have just created a… --- _[View the full topic](https://community.fibery.io/t/fibery-product-report-april-2025/8794)._