Working with Appfarm AI, I keep running into a recurring issue: it sometimes inserts components with property configurations that aren’t supported in Appfarm Create (at least not in a way a human developer can reproduce or maintain).
Example: I asked it to add an Icon to indicate whether an item is locked or available, along with a context dump on what data resources to use and which logical rules to apply. Appfarm AI implemented this by assigning a function to evaluate which icon to show (i.e., dynamic icon selection via code).
From a code-first perspective, this is a sound approach - but in Appfarm Create, I can’t replicate that setup through the UI, and I also can’t meaningfully tweak it afterwards because the configuration path it chose isn’t something I can manage manually.
I then tried to push the AI toward an “Appfarm-allowed” approach, e.g. using conditional properties, but even with explicit instructions, it refused and responded with:
The Icon component only supports
conditionalStylesfor dynamic changes, and that’s limited to visual style properties (likecolor), not the icon itself.
The existing approach usingfunctionValueoniconValueis actually the correct and only supported way to dynamically change which icon is displayed. The component is still in its original working state since both failed operations did not apply.
This creates a gap where the AI can generate solutions that “work”, but that developers can’t reproduce, audit, or maintain within Create.
My assumption is that the component definition used by Appfarm AI isn’t defined correctly?