Overview
Machi iOS is not a Web wrapper. It has local persistence, drafts, Keychain-protected credentials and recovery-oriented sync.
Loading content
Machi / iOS
Machi iOS Native City-Life Client
An offline-first iOS client built with SwiftUI and SwiftData, covering home, discovery, publishing, notifications, messages, profile and settings.
App in preparationiOS architecture, SwiftUI screens, local data layer, sync service, auth and product features
Tech Stack
SwiftUISwiftDataKeychainURLSessionMVVMRepositoryOffline-first
My Role
iOS architecture, SwiftUI screens, local data layer, sync service, auth and product features
Problem
Keeping offline browsing, drafts, sync recovery and the shared backend cleanly separated.
Solution
I split local persistence, repositories, services and Keychain-backed auth into clear boundaries.
Result
Built a native iOS foundation that can share accounts, posts, messages, notifications and membership with Machi Web.
My Role
- SwiftUI 页面与导航
- SwiftData Schema 与迁移
- Repository / Service 分层
- Keychain 登录状态
- 远端同步与错误恢复
Problem
- 离线草稿
- 同步冲突
- 多 Tab 状态
- 凭据安全
Solution
- 本地优先读写
- 网络恢复后同步
- Keychain 保存 Token
- 服务层拆分认证、媒体、地区和通知偏好
Architecture
SwiftUI 负责界面和 NavigationStack；SwiftData 负责本地持久化；Repository 管理本地实体；Service 管理认证、网络、同步和偏好。
- SwiftUI
- SwiftData
Background
Machi iOS is the native iOS client for Machi. It is a real product client with publishing, interactions, messages, notifications, city channels and membership state.
Stack
- SwiftUI for UI, NavigationStack and tabs
- SwiftData for local persistence and schema migration
- Repository layer for local reads and writes
- Service layer for auth, networking, sync, media and region data
- Keychain for credentials
Takeaway
Offline-first is not just caching. It means designing data, sync, failure recovery and user experience together.
