May 15, 2025 / The smallest release of all time

Maybe the smallest release of all time with just few improvements and bug fixes. We did release one quite important thing silently, but will not tell you what it is this week. Anyway, you can silently discover it and try it :face_with_peeking_eye:.

:butterfly: Improvements

  • Permissions: access templates explanation now features your, not sample, Databases whenever possible.
  • Integrations: mapping source columns to Fibery fields has been simplified, paving the way for upcoming improvements in import.
  • HubSpot sync: Add support for Task due date in Hubspot integration
  • Billing: Now you can pay for Fibery via Apple Pay

:shrimp: Fixed Bugs

  • Table View: Wrong value for number in table on quick values editing
  • Fields: Fields used in formula can not be re-arranged in quick add pop-up
  • Permissions: DB-level Creator can’t create fields for enums
8 Likes

OMG it is Fibery AI. Trying now :fire::shushing_face:

2 Likes

Oh, no silence then… Ask it “what you can do?” first to see what, well, it can do.

4 Likes

It looks beautiful! :heart_eyes:
Tried the web search too — very exciting progress.

I’m guessing this was a soft release to avoid being overwhelmed with feedback… if so, apologies in advance :sweat_smile:

My top feature requests:

  • Chat history
  • Entity creation from responses

Chat history is “bigly” important for reflection on both human and artificial level. Being able to start a new chat and reference the previous is vital. These could potentially be combined — if chat history is saved as an entity, it could then be duplicated to a document. Ideally, chats should be stored in a “Private” database or under a “Personal” Space (e.g., Fibery AI).

  • Referencing documents, views, and databases

This would be incredibly useful for analysis and for helping the AI stay on track during planning or exploration.

Looking forward to seeing the product morph and grow! Thank you guys.

EDIT:

Looks like you already mentioned chat history and entity creation here!

2 Likes

We did not want to announce it without chat history, entity creation and some polishing. So all this should be available soon in the real release.

3 Likes

BTW, if you really want to feel what it can do, try complex questions around relational data.

2 Likes

Don’t threaten me with a good time :joy:

I’ve been trying for two weeks now to get Fibery AI to produce decent progress summaries. Time to give it another go.

2 Likes

Well, I don’t want to seem ungrateful, but still want to express the opinion that I would prefer to see more down-to-earth and practical updates rather than trendy AI stuff :melting_face:

3 Likes

We can’t resist exploring new ways of information extraction from the data you have. Try it for yourself on your data and share your feedback! But anyway we have 3 devs in this theme, majority of the team works on other things.

3 Likes

Sometime small is good! :slightly_smiling_face:

Thanks for the continuous development!

3 Likes

I LOVE FIBERY. That is all.

5 Likes

Agreed! I’m all for exploring new tech and seeing cool ways it could be integrated. I played with the chat bot a bit and it looks very impressive!

From a strategic perspective it is a bit weird though. From what recall your target group were builders, but now investing in AI workspace creation feels like stepping away from that… It allows people just vibe code a workspace without know what it’s doing or how it works.

Maybe if the new space creator guides the builder step by step as to what it is doing and why? This way it’s not just about automatically creating a space (which I think it will never get 100% right for complex and pespoke work flows), but it’s also learning how to build it yourself.

Just a thought! Keep going and exploring :))

I see this differently. AI-approach can potentially let more people be Builders. It would be great if just domain knowledge is enough to build a solution in Fibery. The dream is a user operates in “problems” space, and Fibery creates good enough solutions.

1 Like

Yeah, but our goal here is let builder iterate. Like I don’t need these fields, remove them, and this rules works not fully correctly, please consider this edge case as well, etc. From what we see on our early experiments, it is possible to have with current tech.

I see what you’re saying, and agree that it would allow more people to build workspaces, but I wouldn’t call their persona “builders”, at least not at the beginning.

People who are builders are different from people who will use AI to try and prompt a workspace into existence. Unless you also make a clear pathway making the user to a builder by explaining why things are built in certain ways, show where they could tweak, ask for permission to make changes at every step (like copilot). Like this is not just an AI workspace builder, it’s an AI workspace builder and educator. THIS will make more people builders.

Webflow I think does an amazing job at taking people who are not web developers and using the platform for the learn how to be web developers.

The whole fun of building (for builders) is thinking about solutions to the problem, iterating, and finally seeing it all work!

Someone shared a thing with me a few months ago that using formulas in Fibery just makes them feel stupid. They felt like a superstar developer in Coda when making formulas and in Fibery they need to ask the aĂ­ to do it for them. Using AI to build complex things for you is a workaround way to make complex things more simple.

I think most the people on this community fall under the builder persona, I think they make it clear the features they want, and I haven’t seen anyone ask for better AI creation… But I’m open to be wrong about it too! As ford said: if you asked the people what they want, they would say faster horses.

To be fair, most people using Fibery are not in this community :winking_face_with_tongue:

2 Likes

Hmm Ron, I feel like we learn a lot from each other in the Partner calls. This is because there is so much to learn, improve, and iterate on, even when the core of a system is configured. Frankly, I would like to do less! I frequently lament in the forums that some things take too much time/effort/friction in Fibery.
I’m happy to see the barriers lower in any and every place we can lower them. This means that “builders” such as ourselves can spend more time solving real problems and not (for example) manually copying and pasting formulas into near identical fields, just to manually reconfigure the same currency settings over and over and over :cough: :cough:

1 Like