You're explaining a card freeze feature for a banking app in a one-hour system design session. What interfaces would you use to separate the screen, the domain use case, the API, and analytics?
Cut it into four protocols: use case, Repository, ViewModel, and Analytics. The use case calls the API through a CardRepository protocol and returns a domain value, and the ViewModel knows only the use case and builds screen state. Analytics events go through an analytics protocol fed by the use case's result, so the screen knows neither the API nor the analytics SDK.
ArchitectureShort answerExpert
When you apply Clean Architecture on iOS, can you walk me through the layers and the…
#use-case
ArchitectureShort answerAdvanced
Your tech lead says "the Clean Architecture circles (the concentric diagram) don't seem…
#use-case
Build and distributionShort answerAdvanced
The App Store has no rollback. What would you build into the release process to limit the…
#rollback
SecurityShort answerAdvanced
You're designing the transfer feature of an iOS banking app. Which layers of defense…
#banking