How tfourj/nickel works
Project type and purpose
• Type: Native iOS application (built with SwiftUI) plus a Share Extension.
• Purpose: Acts as a third-party client for self-hosted Cobalt API servers to download media from social platforms. It does not connect directly to social platforms—it forwards requests to a user-provided Cobalt API instance.
File structure
• Top level
• Nickel/… – main iOS app source code and assets
• Nickel Share Extension/… – share extension that invokes the same backend API
• Nickel.xcodeproj, build scripts, CI workflows, tests, license, README
• Within Nickel/
• SwiftUI views (ContentView, ConsoleView, DebugView, LandingPageView, MainTabView, SettingsView)
• Models and managers (DownloadManager, FileDownloader, NotificationManager, SettingsModel, AppAttest)
• Info.plist and entitlements
• Tests folder
• Patterns
• UI (SwiftUI)
• Business logic and state (SettingsModel, NotificationManager)
• Networking layer (DownloadManager, FileDownloader using URLSession)
• Persistence (FileManager storage for downloads)
• Security (AppAttest integration)
Extra insights from README
• Relies on external Cobalt API server; optionally integrates with Nickel-Auth for authentication.
• Targets iOS 17+ and uses Xcode 15.3+.
• Feature set: download media, auto-save, notifications.