Drive UI/UX from a model
A key principle of AAC is that the code should be model-centric and drive the UI/UX from a model. The majority of all apps benefit from a persistent model. Models are the components that are responsible for handling the data/content that supports the Business Use Cases for any typical app. The model(s) are independent from the View/Widget objects and app components in your app, so they can be unaffected by the app's lifecycle and the resulting concerns.
Persistence is important for the following disruptive reasons:
Users won't lose data if the Android OS destroys the app to free up resources. The app continues to work in cases when a network connection is unstable or unreachable. By basing the app on model classes, with well-defined boundaries of responsibility for managing the data, the app is more consistent and verifiable.
No comments:
Post a Comment