# 🔮 Fibery roadmap for July-Dec 2023 + previous roadmap reflection **URL:** \ **Category:** News & Announcements\ **Created:** [June 29, 2023, 7:19am UTC](https://community.fibery.io/t/fibery-roadmap-for-july-dec-2023-previous-roadmap-reflection/4690 "2023-06-29T07:19:04Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [June 29, 2023, 7:19am UTC](https://community.fibery.io/t/fibery-roadmap-for-july-dec-2023-previous-roadmap-reflection/4690/1 "2023-06-29T07:19:04Z")
We’ve nailed what we are going to focus on till the end of the year. [I shared our roadmap till May previously](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940) and we implemented [many of the listed things](https://community.fibery.io/c/news-announcements/changelog/17). First, let me reflect on our progress. # Feb-May roadmap reflections 🤔 Overall we are pretty happy with the progress. We kept the focus in most areas. Unfortunately, we have nothing to show for permissions and tables yet. ## 🐢 Permissions (some progress) We’ve finalized all technical details and started real implementation of entity-level permissions. It was slower than we expected, but we made progress. ## 🍋 Tables improvements (some progress) We’ve spent 2 months on AG Grid prototype and decided to go for it. We have nothing major to show, since we need to catch up with existing tables first and only then we will release something and iterate. ![Screenshot 2023-06-29 at 10.21.33 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/ec27b96270539cccf541d294bab45107c003903d.jpeg) ## 🐸 Filters improvements (done) Just some quality of life things many people need: - Group filters with nested logical operators (or/and) - Filter and sort in relations selector ## 🧠 Documents improvements (almost done) Knowledge management in Fibery is not great, many people are struggling to setup Wiki, so we will focus on many improvements in this area: - Nested documents (done) - Files block (done) - iFrame block (not done, but still in scope) - Callout block (done) - Custom emojis (in progress) ## 🚦 Getting started improvements Progress was not that great overall. - Better import from Notion, Confluence (we’ve made some progress here, now you can import markdown files. But overall we got distracted by ClickUp import) - Invite users via a link (done) ## 🐣 GPT-3 - AI assistance in Documents and Rich Text fields (done) - Invoke AI actions in automations (done) ## 🎬 Whiteboard View We evaluated [https://www.tldraw.com/](https://www.tldraw.com/) as a new technology for our Whiteboard and really liked it. However, we decided to not re-write Whiteboard so far. However, if it will be needed for some use cases, we will go for it. ![Screenshot 2023-06-29 at 10.20.42 AM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f0c28f5f201726ffa8f6f4f3c27ad760aa8af25b.jpeg) ## 🫣 Communication in Fibery research We did a lot of research and discussions in this area, but implemented nothing. # July-Dec 2023 roadmap 🍿 We’ve made the following major decisions: - We’ll put serious effort into Fibery simplification, polishing and emotional part. - We’ll focus on 2-3 vertical use cases for product teams: collect feedback, work with insights, prioritize work based on feedback - We’ll continue and finalize entity-level permissions and new table view - We’ll significantly improve comments and notifications Here are more detailed set of features in these areas ## 🐢 Permissions We’ve started implementation and want to have the first working prototype in 4-6 weeks. We have to check scalability, this is the only remaining issue with the technical solution. If it will be fine, then we’ll move forward and finally release something here. ## 🍋 New Table View We’ll spend around 3 months improving tables in Fibery and solve ALL major problems and missing things you reported. We expect to have the first release in 3-5 weeks here. ## 💬 Comments and notifications Comments in Fibery are awful. We explored novel ways to collaborate, but decided to not go for it. So now we’ll spend 2-3 months to solve major problems. You can expect features like: - Full-text search in Comments - Make comment section easily accessible from entity view - Reply in comments / threads - Emoji reactions on comments - Read/Unread comments - Comment resolutions - Comments as first-class citizens (create Views with Comments) - Fine-tune / configure notifications better - Filter notifications by notification type - Follow/Watch Entity and get notifications ![Screenshot 2023-06-16 at 3.30.19 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/148fc6717cf70b7d5183bb0313894e1fe1e9e22b.png) ## 😛 Simplification, polishing, emotions Scope here is less clear, but we are forming a team of 4 developers that will spend the next 6 months together solving a lot of problems. Some features are: - hints, simple way to create view, cleaner left menu, simpler entity view, … - more customization, colors, emojis, …. - fix many annoying little bugs ## 🍿 Vertical use cases for product teams: collect feedback, work with insights, prioritize work based on feedback Scope is not super clear here as well (we will have it in a month), but in terms of problems that we will solve here are they: - improve References in text. It will be possible to add fields to references to set weight, priority, etc - it will be possible to create views with References, move them from entity to entity faster, link reference to many entities - we’ll experiment with automatic insights extraction from feedback using AI models - we add more feedback collection sources (maybe feedback portal) Overall, we will catchup with Dovetail, Cycle and ProductBoard here. Our goal is to help product teams extract knowledge from raw data and make better decisions. As always, your feedback is really appreciated! --- _[View the full topic](https://community.fibery.io/t/fibery-roadmap-for-july-dec-2023-previous-roadmap-reflection/4690)._