Building an offline-first EMR prototype forces clarity. You can’t hide behind databases, authentication, or infrastructure. You either have a coherent workflow—or you don’t.
Local-first is also a philosophy: design the clinical interface around speed, cognition, and reliability first. Then decide what deserves to be networked.
When you eventually move to a server-backed system, your architecture is cleaner because you earned it through constraint.