Native Data Access Patterns

Core Principles

Use native data access ONLY for observables from the iOS/Android container. For server data, use GraphQL or REST patterns. Native repositories provide a bridge between native modules and React Query, with event-driven updates and fallback handling.

Why: Native data access is specialized for container-provided observables (auth, config, plan). Using it for server data would bypass proper API patterns and lose features like request cancellation, retry logic, and error handling.

When to Use This Skill

Use these patterns when:

• Accessing data from native iOS/Android container modules
• Working with observables provided by the container app
• Need event-driven updates from native layer
• Requires fallback to initial state when native doesn't respond
• Working with auth tokens, app config, or plan data
• Need consistent query keys for native repositories
• Building data access objects for RepositoryLoader