Hello @Alan_G , just following up on this topic, which is about adding support for App-data metafields for Customer Account Extensions. To help recap, I built this table:
I believe you submitted a request to the team and was wondering if there’s any updates on that.
Hey @flavio-b - thanks for following up on this, and thanks for putting that table together, super helpful.
I did check in on this there still aren’t any concrete updates on our end. Right now, the current supported metafield types for that surface are still limited to shop, customer, cart, order, company, and companyLocation.
I’ll follow up internally again to see if there’s been any recent discussion around this though, and I’ll loop back here if I hear anything new.
In the meantime the workaround with $app-prefixed metafields on the shop resource via useAppMetafields is still the best option for now.
Let me know if I can help out further!
Hey @flavio-b - just following up here after speaking with some folks internally. We still don’t have this on our roadmap, but I’ll pass along the table you shared for sure. Please let me know if I can pass along any other info, I can add it to our feature request log at the very least for you as well.
Just clarifying on my end, you’d mainly prefer to use app data metafields since app-owned metafields persist after app uninstallation, basically requiring more complex state management?
Hey @Alan_G, “you’d mainly prefer to use app data metafields since app-owned metafields persist after app uninstallation, basically requiring more complex state management” → That’s exactly it.
We have an app that provides both Theme Extensions and Customer Account Extensions. For Themes, we use an app-data Metafield to check whether the merchant has subscribed to the app or not. For Customer Accounts, we use an app-owned Metafield for the same purpose.
So, we need 2 Metafields for the same config data, but one of them needs complex state management and doesn’t cleanup automatically. If you look at any merchant store, you’ll likely find dozens of these app-owned Metafields that hold configuration state for apps that are no longer installed.
If it helps make a stronger case for it, I believe that a streamlined install and uninstall process was the main goal of the new theme architecture. App-data Metafields are already supported in Theme Extensions and align 100% with this goal.
I found quite a few posts of devs who are confused by the lack of app-data Metafields in Customer/Checkout Extensions.
Thanks @flavio-b - appreciate the breakdown there as always! I’ll share this with some folks on my end here, just to make sure we get it in front of the right people. Still can’t guarantee anything, but with specific like the above I can usually advocate much better.
Thanks again for flagging 
