arquitecto-offline

To prevent direct API calls from UI components, route all data mutations through domain logic and state stores like Zustand. This enforces strict separation of concerns across presentation, domain logic, and data actions while keeping UI code free of server interactions.

Implement offline-first state management with Zustand by making local state the source of truth. Prioritize local persistence and optimistic UI updates, then handle second-phase synchronization to ensure remote and offline scenarios stay aligned without direct server requests from components.

Structure new modules following clean architecture rules by separating domain logic, data actions, and presentation layers. Ensure UI code in directories like src/components, src/hooks, and src/actions adheres strictly to this separation, routing mutations through stores rather than APIs.

Yes, the offline-first clean architecture approach is compatible with Tailwind CSS v4 and PostgreSQL. It guides structuring logic components and state synchronization while maintaining strict separation of concerns across the data and presentation layers in these environments.

Use Zustand as the source of truth to enforce offline-first workflows and separation of concerns. This prevents UI components from making direct server requests, prioritizes local persistence with optimistic updates, and manages second-phase synchronization for reliable state management.

Avoid offline-first architecture when your application requires immediate server-side validation or real-time data accuracy without optimistic updates. This approach prioritizes local persistence and second-phase synchronization, which may conflict with strict immediate consistency requirements.