Your question is Offline-First Mobile Architecture. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
How would you design a mobile app architecture to support offline-first functionality?
Explain how the client stores data locally, serves core features without connectivity, synchronizes changes when the network returns, and resolves conflicting edits. Address security, schema migration, retry behavior, observability, and how any on-device ML or personalized ranking would operate offline. Discuss tradeoffs between consistency, freshness, battery usage, storage, and implementation complexity.