Otto on mobile and desktop

The mobile website adapts inbox, compose, calendar, tasks and assistant to a smaller screen. Homepage store badges indicate whether an iOS or Android listing is available; a “coming soon” badge is not a download link.

On supported browsers, use Add to Home Screen or Install app. A home-screen installation and a native store app have different permission settings. Sign into the same Otto account to access your data.

Permissions and navigation

Allow push separately on each device. Follow a notification to its linked item, and use Back/close to leave a panel. Check system notification and microphone permissions if a feature is unavailable.

Downloads and exports

On the website, downloads use your browser. In native apps, attachments and exports open the system save/share chooser; choose an available destination. Canceling leaves the file unsaved. These native controls require an updated app binary.

Connectivity

Do not assume full offline editing or background delivery. Provider operations and AI need a connection; wait for a confirmed result before treating a change as complete. See Undo Send for queued and failed delivery.

Purchases

Use the purchase or management flow shown on your platform. Native subscriptions may be managed in Apple or Google settings, while web purchases use the web billing provider. Use Restore purchases in Plan & usage for an existing store purchase, using the same store account that purchased it.