# 🦭 Fibery Product Report: June 2025

**URL:** <https://community.fibery.io/t/fibery-product-report-june-2025/9145>\
**Category:** News & Announcements\
**Created:** [July 7, 2025, 12:41pm UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145 "2025-07-07T12:41:54Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [July 9, 2025, 10:33am UTC](https://community.fibery.io/t/fibery-product-report-june-2025/9145/11 "2025-07-09T10:33:57Z")

</div>

> [@mdubakov](#):
>
> Fully custom entity view layout is MUCH harder to implement. Maybe someday we will do it, but not in near future

From what you’ve shared in the past it was due to having tricky “Defaults” for an dashboard layout of an entity. Maybe there’s other reasons not shared. But having a dashboard layout (along with single and double columns) would be really amazing. It would start blank, and would just another entity view layout. No need for defaults.

I’m just worried you are making the same mistake you made with documents in the past. [Native documents vs. Documents database - #5 by mdubakov](https://community.fibery.io/t/native-documents-vs-documents-database/6323/5)

Personally I’d prefer taking the time to do it right, than rushing to do it in a way that will be harder to fix later.

---

_[View the full topic](https://community.fibery.io/t/fibery-product-report-june-2025/9145)._