How nbcamp-ch4-team3/kickboardapp works
Project Type and Purpose
• KickboardApp is an iOS mobile application written in Swift.
• It follows a Clean-Architecture / MVVM pattern, structured into layers: Application, Common, DataLayer, DomainLayer, PresentationLayer, and Resources.
• Purpose: let users register kickboards, view available models on a map, track ride history, manage user account (log in, sign up, my page), and handle location services.
File Structure Analysis
• Top-level “KickboardApp” directory houses all source code.
• Application: AppDelegate, SceneDelegate, DIContainer, LogInManager – the composition root and bootstrap of the app.
• Common: shared extensions and utilities (e.g., DateUtility, UI extensions).
• DataLayer:
• CoreData (local persistence)
• Network (NetworkService + DTOs)
• Mapper (transform DTO ↔ Domain models)
• Repository (concrete implementations of DomainLayer protocols)
• DomainLayer:
• Model (plain Swift structs for User, Kickboard, History, ErrorType, etc.)
• RepositoryProtocol (abstractions for Brand, Kickboard, User, RideHistory, LocationManager)
• UseCase (business logic operations: HomeUseCase, RegisterUseCase, LoginValidateUseCase, etc.)
• PresentationLayer: subdivided by feature (Onboarding, Home, MyPage, Register). Each feature has ViewControllers, Views, and ViewModels.
• Resources: asset catalogs, storyboards, fonts, Info.plist.
README Insights
• The README only contains the project title; no additional architectural guidance is provided.
Detailed Capture of Essential Elements
• Feature’s ViewController, ViewModel, UseCase, and RepositoryProtocol.
• Mappers between Network DTOs / CoreData entities and Domain Models.
• Shared utilities (DateUtility, Extensions) as a side component.
• Don’t overcomplicate—represent each folder/module as one component with sublabels listing its classes.