How xbmc/official-kodi-remote-ios works
Project Type and Purpose
• This is a native iOS client (“Official-Kodi-Remote-iOS”) built in Objective-C/Xcode.
• Its purpose is to let an iOS device browse and control one or more remote Kodi (XBMC) media-center instances via JSON-RPC over TCP/IP.
• It’s a single, monolithic mobile app (no custom backend), organized using the MVC pattern, with a network layer, a presentation layer (ViewControllers/XIBs), and third-party libraries for UI and caching.
Top-Level Structure
• Xcode Project (Kodi Remote.xcodeproj)
• App code in “XBMC Remote/…”:
• ViewControllers & UI resources (XIBs, storyboards)
• AppDelegate, navigation controllers
• Custom Views & Cells (e.g. PosterCell, BroadcastProgressView)
• Categories and Utilities (NSString+MD5, UIImage+Resize)
• Network module (RemoteController, DSJSONRPC, tcpJSONRPC, low-level headers in Network/)
• Data module (GlobalData, NowPlaying)
• Third-party subfolders:
• SDWebImage (image caching/download)
• SVPullToRefresh (pull-to-refresh)
• ECSlidingViewController, BDKCollectionIndexView, OBShapedButton, OBSlider, JBKenBurnsView
• Demiurgic-JSON-RPC (RPC messaging)
• Settings.bundle (in-app preferences)
• fastlane and .github/workflows/ci.yml (CI/CD pipelines for TestFlight/AppStore)
Key Architectural Patterns
• MVC (Model: GlobalData/JSONRPC-parsed objects; View: XIBs/Views; Controller: ViewControllers, RemoteController)
• Delegate/callbacks for JSON-RPC responses
• Layered separation:
• Presentation (ViewControllers → UIKit)
• Business/networking (RemoteController + JSONRPC layers)
• Data/Cache (GlobalData, SDImageCache, NSUserDefaults)
• External integration: communicates over TCP sockets (json over TCP) to Kodi’s JSON-RPC API