Platform, Limits & Notifications

Language, theme and text size, push notifications, the two screens that can stop the app outright, and the limits you can actually hit — the platform-level behaviour underneath whatever you are doing in chat.

Language, theme and text size

Seven languages — English, Arabic, Azerbaijani, French, Italian, Portuguese and Turkish — offered under their own names. On first launch the app takes the device’s language if it is one of the seven and falls back to English otherwise; after that your choice wins. Arabic renders the whole app right to left: rows, sheets, alerts, chat bubbles and rendered documents all mirror, and directional icons flip.

Changing language can require a one-time automatic restart to flip the layout direction — on iOS only when crossing into or out of Arabic, on Android for any language change. Theme is light, dark or system, applied immediately. Font size scales every piece of text in the app, from small to extra large.

Push notifications

Push tells you when a long answer has finished while you were away from the app. The permission prompt is asked once, and only after you have reached the chat surface with a complete profile — never on the login or onboarding screens. What triggers a push today is a completed AI response; there are no reminders, marketing or activity notifications.

Tapping a notification opens the chat it refers to, whether the app was backgrounded or fully closed. One that arrives while you are already looking at that exact chat is suppressed, because the answer has already streamed into view. The switch in settings is a soft opt-out: it leaves the OS permission alone and simply stops the device receiving. If the OS has blocked notifications outright, the switch sends you to the system settings instead of re-prompting.

Two screens that can stop the app

• Update required. A build below the minimum supported version for its platform is replaced by a full-screen, non-dismissible notice showing the installed and required versions, with a button to the store listing. It is evaluated before sign-in too, so an outdated build is blocked at the login screen.
• Secure device required. A rooted or jailbroken device is blocked outright, on the grounds that the modification weakens the protections around conversations, documents and account data. The check runs at launch and again every time the app returns to the foreground.

No offline mode

HAQQ mobile needs a connection. There is no offline cache and no offline banner: without connectivity, requests fail and surface as errors where they are. What the app does well is fail legibly — it tells you it cannot reach the service rather than spinning. The one thing that keeps working offline is the follow-up suggestion chips, which are computed on the device.

Two things the app does not have

There is no biometric unlock. No Face ID, no fingerprint, on either platform. The app restores your saved session at launch and goes straight into chat; the only unlock protecting it is the device’s own.

There is no separate mobile storage quota. The per-file size limit and the number of files a single data room may hold both come from your workspace’s plan, and where the plan sets no size limit uploads are not capped. A file over the size limit is skipped and the rest of the batch still uploads. When a data room is full the picker is not opened at all — the app says the room already holds the maximum its plan allows.

The limits you can actually hit on a phone