You're designing an iOS file and folder list feature with search and pull-to-refresh. To keep it maintainable independent of the UI framework, what module boundaries would you draw between the list, search, and refresh state and the data access?
A FileListFeature module that knows neither UIKit nor SwiftUI holds a reducer with the list, the query, and the loading phase as one state value, and remote list and local cache access hide behind a FileRepository protocol so the Feature never sees URLSession or SwiftData directly.
ArchitectureShort answerAdvanced
This is a whiteboard design. You're building a stripped-down Outlook app with only a…
#repository
ArchitectureShort answerAdvanced
In an existing UIKit shopping app, the UIViewController handles the API calls, the cache…
#repository
ConcurrencyShort answerBasics
Calling the API on every keystroke in a search field floods it with requests. Can you…
#search
ConcurrencyShort answerBasics
When the search query changes, the previous search's network, decoding, and image work…
#search