Weâre working on the next iteration of something what we call Fibery Apps. We do have some ideas what Apps could do, but weâre blind to majority of use cases in domains we donât understand well.
Weâd like to learn your needs and desires. What are you going to build if you have a possibility? Here are some examples we tried internally for inspiration
First, I would build internal dashboards â much like views, but with more carefully controlled environment. The number one complaint I get from my handful of colleagues is distraction â they donât know what to click / where to click, especially in entity view. So I would build very carefully curated dashboards (responsive to the user) â like your bottom examples.
I would also build intake forms for clients â intake forms that allow them to initiate certain actions, with Javascript to make more automation happen that we canât currently do in forms.
I donât have time to play with it as much as I want, but this is so exciting, and really throws Fibery into an irreplaceable category. I recently did an analysis that Fibery was able to perform ~6 tools work for us, so itâs at the breakeven point. We were exploring have to learn Vercel etc. â and we were carefully avoiding it as just another ecosystem to learn, manage, etc. This would solve that. With N8N and ChatGPT MCPâd to Fibery and N8N (I wish Microsoft Copilot was easier to connect MCP tools to because Copilot is great at working natively in all of our documents, meetings, emails, etc.) to help shorten the curve of linking it all together, this is making Fibery transformative.
A big use case for me is being able to create forms that pull from multiple databases and can filter from options you previously select in the form, because fibery forms currently donât have these capabilities.
A quick example would be adding a new project. You want to add your project, but you might need to add a new client and client contacts too. While you can do this, with the little form popups, itâs not as easy as having it all on one integrated form.
A little app it helped me create was for submitting timesheet entries, because I needed to select the project and then the task, and this is not possible with native forms.
Of course itâs useful for many other things, but thatâs the one I can see most people needing/wanting, rather than things that are more vague or specific use cases.
Quite frankly this seems like it might be a solution to a lot of things, not all necessarily obvious or intuitive. You say Fibery is for geeks and you donât apologize for that? What if you didnât have to because a Fibery admin could just build bespoke UIs that display exactly and only what their users need for their workflows, that work in the ways most intuitive to that particular user group, and which has functions up to and including things Fibery does not include or support natively (e.g. no more clunky workarounds for work time tracking, timer is built-in to your custom coded in-Fibery solution).
Clearly some of this is what you guys are thinking as well, given some of the examples. I just wanted to point out that itâs not just about âCreate some interface or dashboard or analysis that Fibery doesnât haveâ, it could also about e.g. âTake an existing Fibery view like Table and make it work and look exactly the way you wantâ. It could be a sort of solution to Natively integrated custom CSS (and editor) for Fibery workspaces for at least some use cases.
As for me, I was just recently starting to contemplate building a map view, search, and filter system outside Fibery but based on Fibery data, since Fiberyâs built-in maps are limited. With Fibery Apps I may not have to! So itâs amazing to see this, and Iâm looking forward to seeing how it develops!
A few use cases that immediately come to mind from our side:
Heavy conditional forms
For example: creation, adaptation, localization, and other workflows where one form needs to create/update data across several related databases depending on user choices.
Node-based workflow views
Views with node-like behavior for complex workflows. I canât share all details due to internal rules, but this is very relevant for processes where tasks are created through branching logic and connected steps. [Yes, I know this basically sounds like we want to build a supercharged Whiteboard ]
Matrix dashboards tied to time periods
Finally, it could become possible to build beautiful matrix-style dashboards where rows/columns are linked to people, teams, dates, statuses, or time periods â something that is hard to express with standard views.
Department performance maps
Interactive âmini mapsâ of departments/teams, where you can expand areas like a mind map and see live performance metrics for each team or sub-team.
Like this: âA quick example would be adding a new project. You want to add your project, but you might need to add a new client and client contacts too. While you can do this, with the little form popups, itâs not as easy as having it all on one integrated form.â
Leveraging Fibery for remote work chats/discussions around work items- I have been hoping forever that you guys would expand on the ability of comments and your threads feature to be able to have some kind of chat functionality in Fibery - if this could expand Threads and then get more sophisticated with a Slack âmirrorâ functionality it would be great to be able to go back and forth so you keep Fibery contextâŚso I could use a message in Fibery like âhey user x can you do this taskâ and #tag the task, then keep the context in Slack by having that message move to Slack. The 2 parts of how this would be aided by Fibery Apps -1) a better UI than your current Threads set up, and 2) since you mention here:
leverage that for the Slack mirror part of this
I am in the website business and would love to be able to show a âlive mapâ of my website roadmap with its components and work items, all things Iâd track in Fibery with its excellent structures
A bonafide âCalendar of company historyâ in a rich visual based on all the dates that exist in Fibery, or possibly extracted from the Activity log which we have as a way to see what happened on a daily basis while we wait on Dates as first class citizens - maybe with some admin controls for privacy - but the ability to see what items in Fibery are trending, etc. One thing that would help the search results I think are showing tags like âpopularâ etc around items that are being frequently accessed. The concept of a good âsystem of recordâ is huge right now for the proliferation of AI and I feel like if Fibery plays its cards right it could get a good niche position in the market to serve the various AIsâ needs to assimilate chat extracts in a way that AI can in turn read that and manage around the memory limitations all of the major tools suffer from. So setting up all the great db structures and relations in Fibery, then tracking their history since Fibery can serve here as a place where all an orgâs activity is recorded, feels like a very cool asset a team could cultivate moving along its AI transformation path
The roadmap is actually another idea I hadnât thought of at first. We work with long-timeline legal cases (mostly patents) â and weâve been looking for how to show to clients where they are in the overall timeline relative.
Also, thereâs a plan we use visually similar to a 1-page business canvas. This would enable us to populate that visually with Fibery data.
Reskinning for technically challenged users and reducing the clutter would be the main reasons Iâd consider writing a custom UI.
Creating entities via API calls after putting a validation layer over a custom form, and integrating proper communication (since Threads are stuck in Experimental Lab purgatory and users are complaining about the notifications inbox being too much information) would also be beneficial.
This is a great point. I really think Threads is a brilliant innovation that no other tool has - a way to just âchatâ in Fibery and tag away key items and have all that context viewable on the items as updates, all barely moving the keyboard due to the #mentioning creating references on all entities that are involved - talk about low friction! With some attention I feel like Threads could become a backbone feature of Fibery to give it a lot more widespread appeal to teams with big sets of non architect types.
And glad you brought up the notification situation. I in fact canât even use them anymore due to the reality that many entities have long history and the way they are set up with all updates showing as soon as a new one hits, I can get almost the entire inbox taken over by one update if things like references hit or other non-comment updates. In fact I have to use the Slack integration to actually manage the mentions because over there at least you only see in one message one update from Fibery, unlike the Fibery inboxâŚ
And speaking of both the inbox and under promoted features - really like the âwatchlistâ (kind of a primitive solution to the âtrendingâ items I spoke of in my first post here) and feel like that has huge potential too - but practically never have seen any mention of it - I donât even know when it came out, just noticed it a while ago and liked it!
I disagree, but only because it doesnât get used properly by our team, and that you canât put a priority on certain fields changing â example scenario: user wants to know when a task is closed out, but doesnât want to be notified when any other field changes on that entity. I know this can be handled with a custom trigger, but thatâs akin to using a sledgehammer to punch in a nail.
I think the biggest letdown for our team with the base app is that comments arenât treated as first-class citizens. Weâd love to have a default feed of comments across workspaces or databases the user is âsubscribedâ to, completely searchable, filterable, and ordered by most recent. This is where I think Threads is a great idea in concept, if not execution.
An extension on this would be to let the AI agent give a summary of important changes, maybe at set intervals of daily/weekly. Just food for thought.
yes I am pretty desperate to see comments get some improvements as they seem to have been unaddressed for a while - things like indexing them in search results (rare in most other apps so another huge win for Fibery on this one) and the threaded responses are now pretty old features Iâd sayâŚwould also love to see a chronological feed of comments and references as a way to track an entityâs activity and if itâs âtrendingâ - not sure the AI app builder could help with that, but seems to me like a good way to see a roundup of activity on an entity - and what that activity was by virtue of the references being visible - all in one place at a glance.
I can share that I had a client who worked in Fibery but then connected their data to lovable apps for:
Prettier and more custom reports
Some custom data input
I would love to see AI views integrated into the system as Entity Views + Relation Views. But this might be just because Iâm stuck in an old way of thinking. New model may be a more clear âArchitect Backend + AI App Front Endâ
Not sureâŚ
I really like having it all in one place, and dislike Airtableâs implimentation of it of Interfaces. I think itâs a similar idea.
I am wondering if in some future the react app could have custom npm packages installed as well⌠Then this would open doors to replacing n8n as well in some way? But it may get complex to have automation rules of a database in different places⌠Iâm not sure, but AI work flows/automations would be nice to have in Fibery.
I have a ton of charts, reports, maps and views that I have created weekly and monthly. I tried to place them in a dashboard, but somehow I need more place, so I went to a whiteboardâŚbut unfortunately is not responsive, becomes slow, the charts are zoomed very weird, it is laggy.
I can imagine creating a dashboard app for all my reports, incluiding my texts, charts and pictures.
Instead of jumping between databases, change tabs inside an app and have an overview of my charts with date and entity filters.
My use case is probably pretty different from your typical target audience.
I started in Notion, but their pseudo-databases didnât give me the relational capability I needed. Fibery hit that sweet spot.
I use Fibery to track my competitive training(sports) â goals, drills, sessions, shows/events, results, etc. Iâm also planning to use it as a content store for lessons Iâll eventually port to a hosting platform where clients can subscribe or pay for content.
Several of my clients would love to leverage what Iâve built for tracking their own training, but Fiberyâs learning curve is a real barrier. Being able to abstract away the databases and present a simpler frontend â one that isnât tightly coupled to the underlying schema (completely understandable why itâs designed that way) â would be a game changer.
The two areas this would unlock:
A more streamlined, user-friendly frontend for tracking training (sessions, goals, drills, exercises, shows/events, results)
A way to manage and deliver content for clients to subscribe to or purchase
Honestly, my use case is close to the point where Iâd just build my own standalone app â but thatâs a significant lift even with tools like Claude Code accelerating it. Fibery Apps could be the thing that makes that unnecessary.
Questions Iâm not seeing raised yet:
Developer workflow â If Iâm building and versioning this code in Git, how does that integrate with Fibery? What does the development loop look like: edit â test â deploy?
AI tooling integration â How would this work with Claude Design and Claude Code? Claude Design is purpose-built for creating polished prototypes and UI assets, and it has a direct handoff to Claude Code for implementation. That design-to-code pipeline on top of Fibery data could dramatically lower the bar for someone like me to build a polished client-facing app without a full dev team.
Pricing â If clients are accessing a custom frontend that abstracts away most of Fiberyâs native UI, should they need a full Fibery seat? A lighter viewer/frontend-only tier would make this genuinely viable for client-facing use cases.
Hey! Impatiently waiting for your next iteration for Fibery Apps!
My uses-cases are quite blunt and a bit messy:
Iâd develop more of HRM features: 360-feedback and web/radar diagram, Competency Model/Matrix, Scorecards, Assessment Center and LMS (ie onboarding course) on your screenshot is a part of what I need! greedy one right?
Surveys with all that bells and whistles like sliders, star rating, conditional logic, branching, adaptive filters, etc. As a part of it - voting similar to doodle.com
Live coding tool for tech.interview
Slack/chat-mode
Glossary/Ontology graph and tooltips for each term found in text
Gamification app - different ladders and employee recognition perks based on data.
New widgets for homepage in accordance to items above.
Landing page (corporate site) replacing Wordpress with Fibery!
Maybe the app-helper/auto-wiki describing Workspace Architecture, so imagine my the only Fibery Architect is hit by bus or no so dramatic - new Fibery Architect joins the team and my workspace has dozens of spaces and hundreds of views+dbs full of relations, lookups, formulas and automationsâŚso I want minimise onboarding and learning curve. Also such app could be a good adviser in change management, extending and refactoring the Architecture of Workspace.
]
greedy one right?