Native Performanceでできること
Native App Footprint
Uses macOS frameworks directly instead of bundling a second browser engine.
Signed Mac Download
Ships as one notarized macOS disk image for Apple Silicon and Intel Macs.
Cache-First Launch
Restores local app and license state before background network refreshes.
Native macOS Integration
Uses SwiftUI, AppKit where needed, WebKit, and system media commands on macOS.
仕組み
Swift and SwiftUI
Native Swift code owns application state, windows, settings, licensing, and lifecycle.
Live WebKit
Supported services remain interactive inside a live WKWebView; the app never substitutes a screenshot or page-JavaScript picture-in-picture.
System Integration
macOS APIs provide window behavior and media-command integration without global keyboard monitoring.
ポイント
Native Frameworks
Uses the frameworks already provided by macOS.
One Mac App
A single direct download supports Apple Silicon and Intel.
Local State First
Launch does not wait on a licensing network request.
macOS Lifecycle
Foreground and background behavior follows native app lifecycle events.
技術的な話
- featureContent.nativePerformance.technicalDetails.detail1
- featureContent.nativePerformance.technicalDetails.detail2
- featureContent.nativePerformance.technicalDetails.detail3
- featureContent.nativePerformance.technicalDetails.detail4
- featureContent.nativePerformance.technicalDetails.detail5
- featureContent.nativePerformance.technicalDetails.detail6
- featureContent.nativePerformance.technicalDetails.detail7