Hi. Looks interesting. Iâm not sure if itâs related to this improvement, but it would be nice if it was possible to group Rules in some way. Now we face a problem when navigation through the created rules is not very convenient because of their number.
I decided to write about it because the layouts look as if it is possible to add folders somewhere.
I like it, it helps keep context by having the database components (data, fields etc.) visible in the sidebar.
I know the focus is on using this as a Space Setup screen but I think View could be generally useful as a focused Subspace because it filters down the sidebar.
Love it. I still think there is a need for a âFilter/Searchâ in sidebar to âonly showâ Folder > Subitems that match the keyword placed in Filter/Search.
I think the breakdown here is intuitive and logical, in theory this should be easier to understand (other than the fact itâs using the same sidebar in two different ways and could be slightly confusing initially).
I personally donât have any problems with the existing location of these items, so I wouldnât say it solves a current pain point.
Side note (as perhaps this isnât a large feature to add):
What I am waiting for is the ability to use URL parameters (or even better, a unique link) to pre-fill hidden fields in forms as this unlocks a load of use cases for feedback gathering, surveys, customer interactions and various other triggers etc.
@mdubakov This is a great idea and really simplifies the usage of Fibery. The separation between âhow one uses Fiberyâ and the configuration/setup of space is cool and helps declutter the interface. BR, Oliver
The fields canât be hidden though as far as Iâm aware?
For example, I have a meeting record and I want to gather feedback on that meeting with a link via email using a form. I could have a field on the form with related_id that is auto populated based on the url parameter etc. The problem is that this is visible to the user and they can change it.
This looks great!! Makes setting up a lot clearer, makes data, fields, rules, buttons, access templates, and views on the same âimportance levelâ. Which is great as it really encourages users who set up to use all the powerful features Fibery has to offer.
Some thoughts:
Databases look like spaces, confused me a bit at first look. Maybe including the Spaces as the top level, in the sidebar can be clearer? But this might just be a thing of getting used to. This way you can also show all the different spaces, and the ability to change and edit their fields (across spaces) faster. As well drag around the databases across spaces.
I really like the current 50 entity limit, and the inability to choose different columns and sort. it really shows that this view isnât about viewing data, but for creating structure. Wondering why change that? I think that if change, indeed making it all reset per session would be better.
Are the views the thing that is shown in the main user folder? Folders are in the view section as well? Maybe calling that, âSidebar Viewsâ or âSidebarâ could make that clearer. Maybe having 2 folders: Backend and Frontend. Frontend is the sidebar view.
Overall looks like a great development to Workspace setup!!
I like this a lot. It seems much more intuitive. The video didnât mention if reordering rules and buttons would be possible. Thatâs a pain point right now. If you have a lot of automation rules and buttons for a single database, you canât sort them into an intuitive order. So I end up having to read the entire list to find which one Iâm looking for.
Bonus points if you added the ability to reorder buttons and it reflected the new order on the entity context menu.
Looks like a great step forward to me! Love that youâre considering using the sidebar more for space/database management.
Some questions and thoughts:
Youâve said yes this will allow rule reordering now, which is great, but will this also unlock the ability to duplicate rules?
I would also think this is a great opportunity to rename âShareâ to something more relevant like âAccessâ or âCollaboratorsâ or something. When I see Share, I think of sharing a link on social media or slack, when in reality thatâs the place that space-level user permissions are created and managed. âAccess Templatesâ (aka Permissions) are essentially the same concept just at the database-level, right? I always get those 2 areas confusedâŚdoesnât help that the role names awkwardly half match between them either.
In my mind, users get âAccessâ to spaces and databases allow for more granular âPermissionsâ to be set.
I would recommend renaming âIntegrateâ to âIntegrationsâ and putting it at the top under âShareâ (or if you take my suggestion in point #2, âAccessâ ). Seems weird that itâs at the bottom under the âadd databaseâ button.
Also agree with @RonMakesSystems that from a UX perspective, databases in the sidebar start to look a lot like spaces now and users could maybe be get a little disoriented as to what theyâre looking at. My suggestion is just to add a âDatabasesâ label (in your mockup, between âShareâ and âCategoryâ) similar to how you have a âSpacesâ label in the âmainâ sidebar.
I LOVE this approach, absolute home run for me. I have always felt a little bit of friction at the number of clicks it can take to access a specific automation rule for editing, and the navigation always felt a little disjointed. This approach unifies all space setup into one clean interface, and it makes me quite happy
My only question at this point is, under this new UI, you can now configure Views in two separate places. Would this approach replace the ability to edit / create a View on the âfrontendâ? Or would you simply be able to edit / add in two separate interfaces?
See Airtable Apps for a reference that does this. 3 completely different interfaces for 1. Data back end. 2. App setup 3. Final app front end. Very interesting way this is done, and I think Fibery can do it better.
A big advantage of this is that the set can be more complicated and intricate without being in the way or too cluttered in the front end. One example: Creating a âhiddenâ smart folder. there the folder itself isnt shown and just entities are there. Setting it up in frontend is tricky because it will be hidden. But in the back end it can be shown and one of the config can be âDonât show in folderâ.