How nexters/tidify-ios works
Project type and purpose
• tidify-iOS is a mobile client application for the Tidify bookmark service, built with Clean Architecture (Presentation, Domain, Data, Core), ReactorKit, Coordinators, RxSwift/RxCocoa, RxMoya for networking, and Tuist for modular project generation.
File structure
• Top-level modules under “Tidify/Targets”:
– Tidify (UIApplication target + Share Extension)
– TidifyCore (utilities, DI container, extension, storage)
– TidifyData (network layer, DTO→Domain mapping, repositories)
– TidifyDomain (entities, repository interfaces, use cases)
– TidifyPresentation (UI: Coordinators, ViewControllers, ViewModels)
• Plugins: Tuist plugin to scaffold new modules or targets (“tidify-my-cli”)
• Config files: xcconfig per build configuration; Tuist Project.swift and Dependencies.swift
• Resources: Assets.xcassets, storyboards, Lottie, share extension storyboard
README for additional insights
• Architecture: Clean + ReactorKit + Coordinator
• Networking: Moya + RxMoya
• Reactive programming: RxSwift/RxCocoa
• UI Layout: SnapKit + Then
• Tuist modularization
Main components & their relationships
a. Presentation Layer
– Coordinators orchestrate flows (MainCoordinator → TabBar, Onboarding, SignIn, Home, Folder, Search, BookmarkCreation, Setting, ShareExtension)
– ViewControllers + ViewModels use RxSwift to handle UI events and bind to Domain use cases
b. Domain Layer
– Entities: Bookmark, Folder, UserToken, Onboarding
– Repository Interfaces (BookmarkRepository, FolderRepository, etc.)
– Use Cases implement business rules (FetchFolderUseCase, CreateBookmarkUseCase, SearchUseCase, etc.)
c. Data Layer
– NetworkProvider (Moya + plugins, HTTPMethod, error handling)
– Endpoints (BookmarkEndpoint, FolderEndpoint, UserEndpoint)
– DTOs & mappers map APIResponse → Domain Entities
– Default repositories implement Domain interfaces, call NetworkProvider or local storage
d. Core Layer
– DIContainer wires Presentation→Domain→Data dependencies
– AppProperties, UserDefaultsStorage, KeyChain for local persistence
– Extensions & helpers
e. External Services
– RESTful API server (Bookmark/Folder/User endpoints)
– OAuth providers (Google, Apple, Kakao)
Architectural patterns & design principles
• Clean Architecture layered separation
• Dependency Inversion: Domain defines interfaces; Data implements
• Single Responsibility: Each Coordinator, ViewModel, UseCase, Repository class has one concern
• Reactive Streams: RxSwift flows from View → ViewModel → UseCase → Repository → Network → back
• Modularization via Tuist: each layer is a separate framework target