How team-ampersand/dotori-ios works
High-Level Architecture Components
a. Presentation Layer (Features)
• MainTab Feature
• Home Feature
• Auth Features (Signin/Signup)
• Music Feature
• Notice Feature
• Massage Feature
• SelfStudy Feature
• Profile Features
b. Domain Layer
• Auth Domain
• Music Domain
• Notice Domain
• Massage Domain
• SelfStudy Domain
• User Domain
• Violation Domain
• Base Domain
c. Core Layer
• Database
• JwtStore
• KeyValueStore
• Networking
• Timer
d. Shared Infrastructure
• CombineUtility
• ConcurrencyUtil
• DateUtility
• UIKitUtil
• DesignSystem
Component Relationships
a. Data Flow
• User interactions → Feature Modules
• Feature Modules → Domain Layer (Use Cases)
• Domain Layer → Core Layer (Repositories)
• Core Layer → External Services (API, Database)
b. Dependencies
• How Features depend on Domain modules
• Domain modules' usage of Core components
• Demonstrate shared utility usage across layers
Specific Architectural Patterns
Following patterns:
a. Clean Architecture
• Clear separation between UI, Domain, and Data layers
• Dependency rule (inner layers don't know about outer layers)
b. MVVM + Coordinator
• Store (ViewModel) pattern usage
• Moordinator implementation for navigation
Technical Elements
Specific technical components:
a. Framework Integration
• Combine integration points
• Swift Concurrency usage
• Demonstrate Swinject DI container setup
b. Infrastructure
• Tuist build system integration
• Github Actions CI/CD flow
Additional Details
• Third-party dependencies
• Resource management (Localization, Assets)
• Testing architecture
• Share Extension integration
Testing strategy integration
Remember to maintain a balance between detail and clarity, focusing on the architectural decisions that make this project unique, such as the feature-based modularity and the use of custom frameworks like Store and Moordinator.