How edabarutcu/themeapp works
Project type and purpose
• This is an iOS application (“ThemeApp”) written in Swift, structured using VIPER (View-Interactor-Presenter-Entity-Router) per module.
• Its purpose is to let users browse, purchase, and apply themes (with widget support), plus user profile and authentication features.
File structure
• Top-level entries:
• ThemeApp-.xcodeproj / .xcworkspace – Xcode project & workspace files.
• Podfile – CocoaPods dependencies, including Firebase (GoogleService-Info.plist) and possibly other SDKs.
• Common/ – Shared code (authentication helpers, UI components, models, utilities).
• Modules/ – Feature modules, each following VIPER: Market, Profile, Purchased, ThemeDetail, WidgetManager.
• Resources/ – Localizable strings for en & tr.
• VIPER pattern:
• Each module has Contracts, Interactor, Presenter, Router, View (and supporting UI artifacts like ThemeCard, MenuRow).
• Common is a “shared library” layer providing UI building blocks and cross-cutting concerns (localization, auth).
Detail without over-splitting
– Capture every VIPER component per feature, but group them logically.
– Do not omit the Common layer – it underpins all modules.
– Highlight external dependencies (Firebase, Apple Sign-In, WidgetKit) to show integration points.