Platform Differences
The app provides a consistent core workflow across platforms, but some capabilities vary due to OS permission and API constraints. iOS differs the most from desktop: there is no equivalent to Windows/macOS-style continuous background clipboard monitoring; more work happens in the foreground, via Share Sheet, and via Shortcuts.
Capability overview
| Capability | Windows | macOS | Android | iOS |
|---|---|---|---|---|
| Clip history capture | Supported | Supported | Supported | Supported (visibility often depends on foreground use and trigger path) |
| Nearby Sync | Supported | Supported | Supported | Supported |
| Cloud Sync | Supported | Supported | Supported | Supported |
| System-level paste shortcut chain | Supported | Conditional | Conditional | Constrained (not the same programmable global hotkey model as desktop) |
| Background clipboard monitoring | Supported | Conditional | Conditional | Constrained (no continuous OS-level background listener; relies on foreground / Share / Shortcuts, etc.) |
Conditional: available with extra permissions, OS constraints, or setup. Constrained: the OS policy prevents a desktop-equivalent implementation; use alternative paths to reach the same goals.
Platform-specific guidance
- Best support for deep system integration and hotkey-heavy workflows.
- Recommended baseline: clip history + Nearby Sync + Win+V replacement workflow.
Distribution channels: store vs. direct-download
Beyond OS-level capability differences, on the same platform Octoclip can also ship through two installation channels:
- Store build — installed from an app store (Google Play, App Store, Microsoft Store, etc.), updated through the store, and tied to your store account.
- Direct-download build — installed from octoclip.app and updated in-app.
The two builds share the same core functionality — sync logic, clip history, Quick Input, aliases, favorites, and storage all behave identically. Differences only come from app-store policy.
App stores tightly restrict certain permissions and capabilities (for example: reading SMS, screen capture, system-level accessibility, unsigned plugins). To keep the store build publishable, we remove those restricted capabilities from the store build. The direct-download build isn't bound by store policy and can keep them.
Current status per platform
| Platform | Store build | Direct-download build | Differences today |
|---|---|---|---|
| Android | Google Play | APK (octoclip.app) | Yes — see below |
| iOS / iPadOS | App Store | — | Store build only |
| macOS | App Store | Direct download (planned) | Planned |
| Windows | Microsoft Store | — (planned) | Store build only |
| Linux | — | — | Planned |
Android: current differences
| Clip source / capability | Direct-download (APK) | Store (Google Play) |
|---|---|---|
| Clipboard source (system copy) | ✓ | ✓ |
| Notification source | ✓ | ✓ |
| Cross-device sync, clip history, Quick Input, aliases, favorites | ✓ | ✓ |
| Background persistence & accessibility service | ✓ | ✓ |
| SMS source (capture incoming SMS as clips) | ✓ | — |
| Screenshot source (extract content from screenshots) | ✓ | — |
Google Play tightly restricts READ_SMS-class SMS permissions and MediaProjection screen-capture usage. A clipboard utility cannot pass review with these as declared use cases. To keep the store build shippable, we disable both sources in the store build.
How to tell which build is installed
Open the app and go to Settings → About. The build channel is labeled as "Store build" or "Direct-download build", along with the installation source.
Switching between builds
Check Settings → About to see which build you currently have.
Local clip history and local settings do not migrate automatically. Enable Cloud Sync first to avoid losing data.
Uninstall the current build, then install from the target channel (app store or octoclip.app).
Which one should I pick?
- Automatic updates and store-account management
- Sufficient for most users
- Easy to reinstall on new devices via your store account
Troubleshooting order
Most cross-platform issues are permission-related.
Check OS version, vendor policy, and network restrictions.On iOS, also confirm foreground / Share / Shortcuts paths before assuming a defect.
Review shortcut mapping, sync scope, and background policy.
Related docs
Windows-specific capabilities and setup paths.
Background paths and OEM variance.
Permissions and desktop-class behavior.
Foreground, Share, and OS limits.
Tune parameters based on platform behavior.