How vodgroup/voiceoverdesigner works
Project type and purpose
• This is a multi-platform, Swift-based design tool suite:
• “VoiceOver Designer” – a macOS desktop app for laying out accessibility (VoiceOver) mockups.
• “VoiceOver Preview” – an iOS companion app to preview those mockups on a device.
• “Shared” – a cross-platform Swift package containing core models, presenters, document logic, drawing/Canvas abstractions, accessibility utilities, persistence, sample loaders, and text-recognition services.
• Several helper/extras: a CLI “FolderSnapshot” utility, a macOS QuickLook/Thumbnail extension (“MacOSPreview”), unit-test and UI-test suites.
File structure
• Top-level modules:
• FolderSnapshot (Swift CLI)
• MacOSPreview (Thumbnail & QuickLook extensions)
• Shared (root of business logic & models, delivered as a Swift package)
• VoiceOver Designer (macOS app workspace)
• VoiceOver Preview (iOS app + related targets)
• Inside “Shared”: clear separation by feature area (Artboard, Canvas, Document, Accessibility, ElementSettings, Presentation, Purchases, Samples, TextRecognition, Tests).
• VoiceOver Designer & VoiceOver Preview each import “Shared” via SwiftPM and add platform‐specific UI, App lifecycle (AppDelegate/SceneDelegate), window management, and feature modules (CanvasAppKit, CommonUIAppKit, Navigator, Recent, Settings, etc.).
• Configuration/deployment files: Xcode projects/workspaces, Info.plist, entitlements, Package.swift in every package/workspace.
README for additional insights
• Model Layer (Artboard, Element, Container, Frame)
• Data Layer (NS/UIDocument persistence)
• Logic Layer (DocumentPresenter, UndoManager, ArtboardPublisher, CanvasPresenter, selectedPublisher)
• UI Layer (Navigator, Canvas, ElementSettings)
Elements
• Clear labels for each module/component.
• From UI components → Presenters → Model → Persistence.
• From Shared Core → macOS App / iOS App / CLI / Extensions.
• Green for macOS UI modules.
• Orange for iOS UI modules.
• Gray for CLI/tools.
Final advice
• Things by layer and by package boundary.
• Every critical flow: user action → UI → presenter → model → persistence → back to UI.