Hi team, I'm wondering if we have documentation describing the strategy and the positioning of the AFS. I'm thinking of topics like: - Mission & vision statement - Intended use (and users) - Positioning of the AFS in relation to the Mendix platform & ecosystem - Is the AFS still intended to be a template/starter app that customers own and build upon themselves, or do we offer it more as managed software (including upgrades to already existing AFS implementations at customers) I think if we have clarity and a common understanding on the topics above, we can apply this context when thinking about ideas for improvements, feedback, user profiles etc. I think this could also help to provide clarity in both our internal discussions as well as manage expectations with customers when providing them with the AFS. Just to give one example; i think the current app model of the AFS is becoming pretty complex, which makes it hard for (junior) developers at customers to maintain and build upon. If the AFS is intended as template software, this can be improved. If we offer it as managed software, this might not be such a big concern.
You are absolutely right! We’ll be working on this when Berend returns from his PTO and share it on this space asap!