Is anyone else experiencing problems with AI Component rendering? I thought it was just the builder, but checking the web app through a browser it rendered fine… until it didn’t. Through the mobile app it’s unusable… sometimes. Perfect… sometimes.
Refreshing the page, or changing screens on the app, will often re-render and make it usable, but even then sometimes the cards, in this example, will often times have 10-50 pixels or more cut off the bottom cutting buttons in half or disappearing information.
Sometimes.
Other times it’s fine. Consistent.
On the web/browser side I have noticed that it’s usually when one card of three in a row contains a bit more data - elongating the card in comparison to the other two. It cuts off at the same height. Instead of making the other two cards slightly taller to match, or simply displaying the longer card, it preferences chopping off part of the longer card. Sometimes.
While scrolling the AI collection it will randomly re-render and chop off buttons at the bottom of the card, or leave card sized gaps between cards.
Anyone else experiencing this? I can’t put that in production. I’m using the AI Custom component, and don’t know if this is a widespread bug or my lack of skills.
How exactly are you using the custom AI component? What is the “AI collection” you mention?
Situations where using the custom AI component feels safe enough
Creating a simple component because that component doesn’t exist at all as a native component or because you need to slightly enhance an existing component. Think “simple static components”.
Situations where using the custom AI component might be looking for trouble
Using the custom AI component inside a custom collection or using it in tandem with a code column to create a collection. It might work, it might not, I have no clue. I wouldn’t attempt it, first because I don’t have the know-how, but second and more importantly because I wouldn’t trust the custom AI component to behave reliably in those setups.
It’s fun and satisfying to push the limits of the platform to do things that its product people and developers hadn’t thought of. But my general rule of thumb is that the more you move away from the core functionality of the tool – what it was designed to do – the more chances you are taking that things will break on the long run or will not work as expected.
For reliable results and a robust build, I personally try to keep things as simple as possible. As soon as the build starts getting too creative (technically), I know I’ve gone astray and the build won’t be durable.
