Antares asks you to think differently about the UI layer of an application in a few key ways:

1. The UI has a store - its own database, effectively.
2. The UI synchronously obtains data only from its own store. It can ask for data asynchronously via a subscription, or an Epic, and handle the fulfillment of either, but as for the data displayed in the UI, it comes only from the store.
3. The UI can always be built after the core data logic; no part of the app requires the UI to ensure that the correct data flows are in place. The UI depends on the rest of your app, not the other way around.