Web, mobile and desktop apps

Access the same instance from a browser, an installed web app or the desktop app. Choose the installation steps for your device, then check connectivity, updates and notification permissions for that platform.

Work in a browser or on a small screen

Open your instance address and sign in to that instance. On a narrow viewport, reveal the sidebar to choose a project, then open an issue from its list or board. Read details in the responsive panel, change the intended field or add a comment, and wait for the save result before closing it. Close the detail panel to return to the list; its mobile presentation differs from a wide desktop layout.

Open Numo through its floating button or contextual issue action. Check the issue context in the composer. Close one panel before navigating when another overlays the content you need. Use explicit buttons and menus instead of assuming hover actions or desktop shortcuts are available on touch devices.

Keyboard and connectivity

Keyboard users can focus controls and use the command palette for navigation and common actions. A visible send button remains an alternative to keyboard submission. Follow the shortcut shown by the app for your platform.

The installed web app and browser require network access for project data and writes. The service worker handles push and does not implement an offline data cache. After a connection failure, inspect whether the change persisted before repeating it. Installing the PWA does not create a separate account or bypass instance permissions.

On a narrow screen, issue details occupy a responsive panel. Use the close button to return to the project; Numo remains reachable through its floating button.

Install the web app on a phone or tablet

Open the intended minddy instance in Safari on iPhone or iPad, or Chrome or a compatible Android browser. If a link opened inside another app, open it in the full browser first. Self-hosted users install their own server address.

On iOS, open Share, choose Add to Home Screen, keep Open as Web App enabled and tap Add. Depending on Safari layout, open More before Share; if the action is missing, inspect Edit Actions.

On Android, use an offered installation prompt or the browser menu's Install app or Add to Home screen, then confirm Install. Labels vary by browser. Open the new icon and sign in with the account belonging to that instance. This is a browser-installed PWA; there is no minddy native app in the iOS App Store or Google Play.

Updates, offline access and push

Installation does not create an offline project copy. minddy's service worker handles push only and does not cache application requests. Use a network connection and reload to obtain current web content. Notifications additionally require browser support, permission and configured server push; on iOS the installed app is required when prompted. If an installation option is unavailable, use the supported full browser and check whether the instance is already installed.

The public guide illustrates the three Safari steps and keeping Open as Web App enabled. These are instructional illustrations rendered by minddy, not screenshots of a completed iOS installation.

Install and manage the desktop app

Use the public download page. Choose Apple silicon or Intel on macOS; install through Microsoft Store on Windows; choose an AppImage or signed deb/rpm matching x64 or ARM64 on Linux. Follow the platform guide and verification instructions for the package. Windows does not provide an exe installer.

At the server picker, choose minddy Cloud, a self-hosted server origin or the available local runtime. Check the destination before signing in: accounts belong to their instance. OAuth uses the system browser and returns to desktop.

Tabs, closing and updates

Use the desktop tab controls and command palette to move between work. Follow the displayed platform shortcuts; macOS uses Command where Windows/Linux commonly use Control. Closing the window hides it and keeps the app running. Use Quit to end the application; macOS offers Cmd+Q. Background notification behavior depends on the package and platform capabilities.

macOS and portable AppImage builds offer updates in the app. Windows updates through Microsoft Store. For deb/rpm, install the next verified package. In the desktop app, Account settings → Preferences → Desktop app shows the connected server, the preview channel when available and the app version, with an update check where the package supports it. On the web, the same card links to the download page. Check the displayed desktop version after updating and confirm that the intended instance still opens.

Recover a stopped window

If a desktop window crashes, a local recovery page offers Reload window. Use it to reopen the last screen on the currently selected server. Unsaved changes may be lost. The app waits for your action instead of repeatedly reloading the failing page. If the recovery page also fails, the native message asks you to quit and reopen minddy. These native recovery controls currently use English labels.

If a page is still loading after 30 seconds, or a window remains unresponsive for five seconds after the desktop app detects it, a native dialog offers Wait and Recover window. Wait is the default and leaves your work and the current request in place. The dialog closes if loading finishes or the window responds again. Recovering may lose unsaved changes: choose Recover window to open the local recovery page, then Reload window to return to the last screen.

The optional saved query cache holds up to 2 MiB of query data. If the full cache is too large, minddy keeps complete query results that can be saved, favoring current views and tabs in the tab bar when needed. If that selection still exceeds the limit, the previous local snapshot is removed. Data omitted from the saved cache stays in memory for the session and is fetched again when needed after a restart. Separately saved drafts are unaffected. This cache is not a backup of your work.

To reduce memory use during long sessions, inactive PR details, commit diffs and page bodies are released after one minute and reloaded when needed. Active queries are retained. Tab labels keep only lightweight PR information, so keeping a tab open does not retain its patches.

Recovery page in the macOS development app with an isolated profile and demonstration server. The native shell uses English labels in every language.

Enable notifications on a device

Open notifications in account settings on the device you want to register. Enable notifications and accept the browser or OS permission request. A denied permission must be changed in browser or system settings; repeatedly switching the minddy control cannot override it. On iOS, install and open the web app first when the interface requires it.

Check that the device appears in the list and use its test control. Inspect the last-delivery information. You can disable or remove individual registrations without deleting the account. The categories in Account settings → Notifications control which events notify you; the in-app Inbox remains available when push is unavailable.

This browser blocks notifications. Restore site permission before trying to register this device.

Platform conditions

Web push requires a supported browser and configured instance push service. Native banners and background delivery differ. Signed packaged macOS supports APNs; packaged Windows needs its optional WNS helper for background transport. Linux uses the packaged app's background session rather than APNs or WNS.

If the selected server has no APNs or WNS configuration, the desktop app uses local native banners while it is running or hidden. This fallback does not deliver notifications after you quit the app.

Check OS notification permission, browser installation state and the displayed “not configured” or “unsupported” explanation. A successful test does not guarantee delivery while offline or under every OS background restriction. Keep the application or its configured background service available as required by the platform.

The account has an active registered browser device. The list shows its registration and last-send dates. Browser permission and operating-system settings still determine whether a banner appears.