BrightDigit was created with the idea that great apps are made by thinking ahead. Founded in 2012 by Leo Dion, a software developer with over 20 years’ experience, BrightDigit has focused on building high-quality apps for Apple devices. We specialize in building apps using Swift and exploring all the new opportunities in the growing Apple software market.
Automate Xcode setup with Tuist Swift manifests—generate projects you don’t commit or edit. Configure targets/deploymentTargets, add AppIcon and a privacy manifest, set signing team and Info.plist overrides, use an xcconfig for MARKETING_VERSION/CURRENT_PROJECT_VERSION.
Guide to adopting Mise to manage Swift tooling for iOS projects and CI. Define tools in .mise.toml (enable experimental SPM), choose spm/aqua/core backends, pin versions, and use jdx/mise-action@v4. Includes Makefile/CLI examples plus fixes for PATH and SPM build failures.
MistKit’s type-safe CloudKit REST client proved in production with CLI updaters for Celestra and Bushel. Covers query filters, batch modifyRecords, protocol-based mapping and references. Lessons: 200 ops/request so chunk, booleans as INT64, server-to-server auth OK. AI excels at test gen; humans guide architecture.
Rebuild of MistKit using Claude Code + swift-openapi-generator: turn CloudKit docs into an OpenAPI spec to generate a type-safe client. Handle polymorphic fields via typeOverrides/CustomFieldValue, auth with ClientMiddleware (API/WebAuth/Server-to-Server), structured error mapping, and a clean Swift wrapper API.
SwiftSyntax makes macro code generation verbose. The author builds SyntaxKit, a Swift package/DSL with result builders to generate Swift via SwiftSyntax, using Cursor and Claude. Covers workflow tips, unit tests, CI with GitHub Actions. Takeaway: readable, type-safe codegen.
swift-build is a composite GitHub Action that removes Swift CI/CD boilerplate. It runs SPM or xcodebuild across Ubuntu and Apple platforms with matrix testing (Swift/Xcode/devices) and intelligent caching (irgaly/xcode-cache, actions/cache), optional simulator downloads.
Decision guide for local persistence: SwiftData vs Core Data/SQLite. Explains Apple API pros/cons, docs gaps, and abstraction friction. Recommends SwiftData for greenfield SwiftUI (iOS 17+), but warns about @Query/macro and Swift 6 issues; use ModelActor or GRDB when needed.
watchOS Simulator lacks Sign in with Apple. Implement a debug‑only file‑based login: server writes a token into the watch app’s tmp container via SimulatorServices/simctl; the app polls with Combine (Timer.publish + async filter) in a SimulatorLoginButton, validates, then persists. Clean up temp files.
How to add Sign in with Apple end‑to‑end: set up the capability, verify Apple JWTs on the server using JWTKit (Apple JWKS) with Vapor/Hummingbird/OpenAPI, and wire SignInWithAppleButton in SwiftUI to send credentials. Includes audience/issuer checks, Keychain storage, and error handling.
Case study: evolving a heart‑rate streaming prototype into gBeat, a full‑stack fitness platform built with Server‑Side Swift (Vapor). Covers SPM code sharing, HealthKit input, WebSockets, push notifications, and an architecture with server auth/streaming and client sync.
Apple dev year-in-review: hiring was tough; Vision Pro and Apple Intelligence underwhelmed; SwiftUI interest surged; Swift 6 emphasized thread safety. New OSS: DataThespian (SwiftData + actors), RadiantKit, BushelKit, PackageDSL. 2025: smaller apps, Bushel, WWDC-timed content.
Type‑safe CRUD for SwiftData ModelActor via a Queryable protocol and Selector enums. Implements insert/fetch/delete/save with withModelContext and convenience/throwing updates. Caveat: new models get temporary IDs—save, then query again by a unique field.