How planetable/planet works
Project’s Core Purpose and Type
• Planet is a native macOS application built with SwiftUI.
• Its main objective is to allow users to publish blogs and follow web content in a decentralized manner using both IPFS (for peer-to-peer content distribution) and Ethereum Name Service (ENS) for content addressing.
• It works as a full-featured app with a built-in local IPFS node, content pinning, RSS reading, and various integrations (wallet, analytics, file handling).
Relationships & Data Flow
• How the UI components interact with the underlying business logic (e.g., views sending events to corresponding view models in “Views” and “Writer”).
• Use of the API layer (found under “Planet/API”) that includes services for authentication, logging, and control of the app’s web views.
• Integration with IPFS – for example, how the “IPFS” module handles starting/monitoring the local node and how content gets pinned and updated to IPNS.
Architectural Patterns & Design Principles
• Separation of concerns – clearly delineate between presentation (UI/SwiftUI views), business logic (entities, models, services), and integration layers (IPFS, ENS, Wallets).
• Dependency Injection & Communication – indicate probable use of view models and helpers that serve as intermediaries between UI and data sources.
• Peer-to-peer & decentralized architecture – mark the IPFS node and ENS interfaces as critical service blocks.
Final Assembly
• Notes for components such as “Key Manager”, “TemplateBrowser”, and “Labs” which provide extended functionalities (payments, wallet integration, dApps).
• Finally, be sure to capture the many supporting modules (e.g., Downloads, Quick Share, and various Views) by grouping them into common functional clusters.