🧐 Ask Community: How would you extend Fibery's UI or build on top of Fibery if you had an easy way to do it?

[Finanzamt_Muellheim]

I can also use it for Inventory Management. Fibery handels big Databases really great with a lot of items, relations and fields, but having a more intuitive “App-Feeling” to walk trough the storage and update inventorys would be aswesome. I think there are many workflows that could use a more “app” feeling.

[Eva_Folch]

I’ve been experimenting with the new Page Agent and I’m genuinely excited about what it can already do — I built a test page connected to a database of portfolio files (audio and video), and it automatically created a clean player with download buttons. Really impressive for an early prototype.

That said, I have a few questions and feature requests:

Public sharing for pages— Is there a plan to allow UI pages to be shared publicly, without requiring a Fibery login? This would be a game-changer for portfolio and client-facing use cases.

Forms and booking — I’d love to be able to build more polished questionnaires and a proper booking page. The current form options feel limited for client-facing workflows.

Document generation — It would be incredibly useful to generate documents from stored data (proposals, contracts, invoices, etc.) and be able to review and edit them before sending. Even a basic template-based export would go a long way.

Flexible entity layouts — This is probably my biggest pain point. Not being able to reorder fields or place them side by side in entity views makes it hard to create clean, readable layouts. For example, I’d love to display Price, VAT, Total, and Currency all on one line rather than in a long vertical list. More control over field arrangement and grouping in entity views would make a huge difference to day-to-day usability.

This is all very promissing! Thank you!

[timothy]

This! We’re thinking about how we could use the page agent and especially the app agent for these types of things — it would revolutionize our ability to work with clients and save a lot of the ingest and export problems that eat such a chunk of our time:

Public sharing for pages— Is there a plan to allow UI pages to be shared publicly, without requiring a Fibery login? This would be a game-changer for portfolio and client-facing use cases.

Forms and booking — I’d love to be able to build more polished questionnaires and a proper booking page. The current form options feel limited for client-facing workflows.

Document generation — It would be incredibly useful to generate documents from stored data (proposals, contracts, invoices, etc.) and be able to review and edit them before sending. Even a basic template-based export would go a long way.

Flexible entity layouts — This is probably my biggest pain point. Not being able to reorder fields or place them side by side in entity views makes it hard to create clean, readable layouts. For example, I’d love to display Price, VAT, Total, and Currency all on one line rather than in a long vertical list. More control over field arrangement and grouping in entity views would make a huge difference to day-to-day usability.

[bear]

I will write a longer reply here later but I want to say already that I am very happy with these features - I was hoping that you guys would do something like this for years!

I would make front-ends for non tech-savvy folks or for very specific use cases, so people do not get overwhelmed and can send/get just the information that is important in an intuitive and pleasant way.

More will follow and I will share some of my own examples!

[Gerardo_Ducos]

That’s a great question.

Coming from Coda and new to Fibery (I’ve been playing with Fibery for just a week!), one thing that I found really insteresting in Coda and that I couldn’t yet find (if it exists in Fibery), is the possibility to add ‘buttons’ to Documents.

For example, ‘Add Entity’ to a defined db, or ‘Modify entity’ (in coda these are ‘add rows’ and ‘modify row’), or simply run a script or a formula when the button is clicked (so the possible actions would be endless).

This feature greatly enhances the users’ experience and can make Fibery feel/act like an app.

One upvote for flexibly layouts. At the moment, everything is forced into a long list. If we could get 3 or 4 columns with the possibility of having the fields names visible, invisible or show something else, the visible layout for an entity could look more like a form which will also improve the users’ experience. An example from coda:

[Eva_Folch]

@Gerardo_Ducos

One upvote for flexibly layouts. At the moment, everything is forced into a long list. If we could get 3 or 4 columns with the possibility of having the fields names visible, invisible or show something else, the visible layout for an entity could look more like a form which will also improve the users’ experience. An example from coda:

Totally agree! I would love to be able to have more flexibility on the entities’ columns. Then you can have, for example, the Subtotal, currency, VAT, total in one line. and it’s much cleaner!

About the button, you can! You will see them if you right click on the entity when you create one on the DB. You can also show it on the entity. But buttons like in a dashboard outside the entity do not exist. I come from Coda as well, and I would not go back to it! There are some things that I miss, but others I did not have before, that I find just amazing, like creating a PDF from HTML, and the new AI Page Creator! Hoping that it keeps being developed!
AH; and costumer service is amazing!!! And the speed on which it’s getting better and better every week!

[Gerardo_Ducos]

Thanks Eva for the button tip!

[Will]

Also from Coda and missing some things… but enjoying what I seeing so far… talk to me more about the PDF from HTML!?

[Chr1sG]

@Lee_Denny

Id build myself a copy of sunsama to help with planning my time

Had a quick go at making a ‘sunsama-lite’ custom app.
It displays my Google Calendar events, and allows me to plan Fibery Tasks into the next free slot

[TBSFelicia]

Great timing on this question — we’ve been building custom UI pages in Fibery since they released and they’re already very helpful but we’ve been hitting some gaps.

Here’s what we’d build if we had the ability.

A support inbox app

This is our most pressing need. Our support team works in Fibery for everything else, but the current views are too complex for inbox triage — too many fields, too many relations, too much visible at once. What we want is a focused surface: one ticket at a time, inline reply, status update, and escalation as a single action. The data model is already there. What’s missing is a purpose-built skin that hides everything irrelevant to the person handling tickets.

The escalation path matters a lot here. When a support staffer needs to send something to the dev or product queue, that should be a single button that pre-populates a new entity with the context from the original thread. Right now that handoff is manual and lossy.

For this to actually work as an email interface, we’d need a few things that aren’t currently possible in UI pages:

• Rich text input — at minimum bold, italic, bullet lists, and links. Support responses need to look like real emails, not plain text. We’ve built a basic toolbar in the page ui before, but a native component would be ideal.

• Image and file upload — customers send screenshots, support needs to be able to attach files to replies and store them in context with the ticket. Right now there’s no path to do this from a custom page without making the user open the Fibery entity directly.

• Rendered rich text output — the reply composer needs to look like a real email composition surface, not a raw textarea.

A QA run tracker

We currently run structured test plans in documents — manually checking off pass/fail/flagged per item, then filing bug reports separately. A proper app would let us open a test plan, check off results inline, and have failures auto-create bug report entities with pre-filled fields (environment, severity, linked feature). The backend is already in Fibery. The missing piece is the test-execution UI that talks to it.

This is actually a good example of where the “order-of-magnitude less code” argument lands for us. The QA tracker isn’t a complex app — it’s mostly Fibery data with a thin, focused UI layer. That’s exactly the case where building inside Fibery beats building something standalone.

The permissions point in your post also resonates practically. In the triage dashboard, we have role-based “advanced mode” access gated by hardcoded Fibery user IDs. It works, but it’s brittle. If Apps inherited Fibery’s actual permission model, that whole mechanism could go away.

Most of what we want to build follows the same shape: Fibery already holds the right data, in the right structure, with the right relations — but the default views expose too much of it to the wrong people, or don’t have the input components needed for real workflows. An Apps layer that lets you build opinionated, role-specific surfaces on top of an existing workspace — without replicating the data model elsewhere — is exactly the right abstraction for this.

One question: are Apps intended to be schema-aware at build time (field picker, live enum values), or is the current thinking more API-based where the builder constructs queries manually?

[bear]

I would come back to this thread. Going to read through it all as I find it very interesting, but I already have 2 requests:

1. Option to interact with Files. For example, I could add a geopackage (a type of sqlite) and use that for data on the app. Or other data formats not supported by Fibery I could use. For example, then I can use 3d objects and visualize them.

2. I would want to make public facing pages. Now if I make a page with an Embed public I see this:
   

   

3. Backend code, and the option to put API keys in that code - as a way for these keys to be hidden from people seeing the embedded view.

I imagine there to be security risks that need to be addressed first for all of these questions.

That is all for now. As I said I will read the rest now and reply again soon.

[bear]

I agree with everything you say! And great that you want to make maps! I will share some examples of custom maps soon perhaps that is interesting, and I’d love to see what you make!

[Sergey_Truhtanov]

@TBSFelicia

One question: are Apps intended to be schema-aware at build time (field picker, live enum values), or is the current thinking more API-based where the builder constructs queries manually?

Builder will write code, that will fetch live enum-values, relations, etc. when you open the App or exact select control for Enum in this App.

That means new values should immediately appear in the App.

On the other hand we expect Builder to be aware of certain parts of the schema on Build time. And queries to concrete Databases will be hardcoded in code generated by Builder. Similarly with Database Fields.

So if you delete Database, your App will just break.

We see this as a custom UI, that works with the certain part of your Fibery workspace Schema, and relies on it.

[mdubakov]

Poor’s man Slack can be created in Fibery Apps it seems with few prompts, but as usual, devil is in the details, like good notifications, mentions support, etc. But I hope eventually we can get there

[nathan_jay]

I’m a bit late to the party and all of what I would do has already been mentioned by others in different guises e.g.:

• Custom reports - more like a Board-level paper which needs commentary mixed with Graphs and single metrics. Although if there were some minor improvements to exisiting Dashboards and widgets then it would go a long way towards solving this without a react app
• Custom entity views. These can better display a single entity and it’s related dbs e.g. 360 customer view.
• Forms and task apps
  • Internal data input (especially pre-filled data and conditional logic, field validation on input)
  • Internal Task specific (document generation, proposals, invoices, send SMS to customer). These also need to integrate with 3rd party to be useful so need to send Webhook/HTTP AND then use the response data.
  • External forms like lead submission or customer onboarding. Auth is critical. Reopen existing partial submissions. This is live use case I’m grappling with now.

@tstirm

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?

Yes this. I’m happy to use our existing internal workflows (outside Fibery) and have invested in prompts/agents/workflow

It hope it moves more towards “let me do it outside Fibery (using my own tools/flow) and then deploy it to Fibery” Simple things maybe can be done all in Fibery because it’s very fast to get up and running. But complex, critical, integrating with 3rd parties, I still want to experiment safely and branch/version and export it out to use my own tools which I’m comfortable using.

If I can build outside Fibery and deploy to hosted Fibery. The existing MCP is now very powerful to support this. A pure chat interface doesn’t cut it. You need to chat AND be able to make code level edits. This is exactly like Codex, Conductor or Claude Code Desktop (which they totally ripped off Conductor).

A Fibery CLI may help. I’m seeing many more example of this with other products. Its not that CLI is necessarily good for humans but its a good tool for Agents to use in a dev loop.

@AdVhPkgKad

since Threads are stuck in Experimental Lab purgatory

this is a good call, it needs to be deployed properly. It’s a fantastic feature I prefer it to the standard Comments.

[mdubakov]

Apps are there and they enable many requested use cases above, check them out

June 25, 2026 / Custom Apps, AI credits & extra usage, Better performance for large tables, Set static default values for basic fields, Automations history

Yesterday we had a very long degraded performance incident for integrations, reports and automations. We still didn’t identify the root cause (and even AI feels helpless here). The incident has nothing to do with today’s release, but if things will go south again, blame the heatwave and MongoDB. Custom Apps (experimental) Fibery now lets you build your own Apps — custom, client-side UI that runs on top of your workspace data. Now any user can build custom solutions tailored for speci…

[mdubakov]

@here Please share some examples of the Apps you created via custom Apps!

Custom Apps (new)

You can enable them in Settings → Experimental Lab

[Michael_Ichter]

We created a meeting planner app. It’s a calendar where people can propose dates and times. There are buttons that people can press to show if a proposal works for them, and a way to delete proposals, and a way to confirm/choose a proposal (which then converts the proposal to a meeting).

Confirming a chosen proposal also gives the option to delete all existing proposals (for that department, other departments’ proposals persist). And you can see that a proposal shows how many people have noted the proposal as working for them (and clicking “Works” will undo).

This took about 450 credits to make using Sonnet. Probably would have been less if I had gotten a clearer or more thought out plan in the first place instead of having to iterate several times. I think I had 4 or 5 follow-up suggestions for the AI. Credit usage was generally 70-140 per prompt.

[Eren_Turgut]

My first test was a “Contract Browser” for our legal team, for a quick & easy way to find and download existing contracts:

• Filter options are dynamic, i.e. if I select a contract category for example, I only see contract parties which have contracts in that category.
• And the list below shows matching contracts “live”, no apply button needed and it works extremely smoothly.
• Fields are read-only, except for Files where I can add (incl. drag-and-drop), rename and delete files.

Created a separate APP CONFIG space with “App config data” database, where in a rich text of an entity I can define

• group (Contract Parties, Status & dates) & subgroup headers (Notice)
• how many columns each has
• which fields exactly to show, with options to:
  • hide field name (-> Contract Parties hidden as = group header → looks nicer)
  • define location, for example effective date and end date look nicer next to each other, so I defined “End date” row = 2, which otherwise per default would show next to Status.
• => definable per contract category.

Limitations:

• Can’t show file thumbnail as with Fibery-native gallery view
• Couldn’t make a download file button work. Clicking on preview image opens file in new tab which triggers download if not a PDF, so functionally it’s all good. But having a download icon to trigger “save as” function or automatic download without new tab was not possible. Download all files button was also not possible. Both buttons did nothing on click.

Near-zero impact limitations.

It took like 8k credits to build, but probably around half was trying to make the limitations work. I started with Opus 4.8 and since there is no option to switch, it made it very inefficient… Having to use Opus to ask for mini changes multiple times is likely unnecessarily expensive, so this will not be a problem in the near-future.