Skip to main content
Socializioz uses a dedicated mobile application shell rather than simply shrinking the desktop sidebar. Core workflows stay available through five persistent tabs, while detail pages open within the mobile navigation stack.

​
Bottom navigation

The current mobile tab bar contains five destinations in this order: The shell keeps tab roots mounted so switching between the main tabs can preserve in-progress tab state instead of recreating every tab from scratch. The tab bar collapses while the on-screen keyboard is open. Chat also sends an explicit input-focus signal so the navigation does not briefly steal space during keyboard transitions on mobile browsers.

​
Header and detail navigation

The mobile header can include:
  • A back control on detail routes.
  • A route or workspace-view title when the current page needs one.
  • The notification bell for signed-in users.
  • The mobile menu.
On supported touch layouts, a swipe from the left edge can trigger back navigation on eligible detail screens. Android/WebView builds also use the mobile navigation-stack handling for the system back action.

​
Mobile menu

Open the menu from the header for account, workspace, billing, and secondary tools. The current menu includes access to:
  • Profile.
  • Active workspace settings.
  • Current plan and Billing.
  • Campaigns.
  • Connections.
  • Settings.
  • Analytics.
  • Comments.
  • Language switching.
  • Help & Support.
  • Documentation.
  • Log out and other account controls exposed by the current settings flow.
The exact arrangement can change as the mobile shell evolves, so use the labels shown in the current app rather than relying on an old 2×2-menu screenshot.

​
New-user activation

New users who are required to complete Activation Journey V2 are routed through the real Getting started journey before normal app access. The five-step journey establishes discovery context, workspace, preferred work surfaces, brand context, and the first verified Agent handoff. MobileWorkspaceGate remains as a fallback for grandfathered or edge-case accounts that do not require the activation journey but still have no active workspace. It can let those users select an existing workspace or create one. This means the fallback workspace gate should not be documented as the normal onboarding experience for every new mobile user.

​
Mobile Composer

The mobile Composer uses the same underlying post/workspace state as desktop while adapting the controls to the smaller viewport. You can still work with:
  • Destination selection.
  • Caption/content editing.
  • Media attachment.
  • Destination-specific platform settings.
  • Validation.
  • Drafting, approvals, scheduling, and publishing where the selected destination and plan allow them.
Because the desktop Composer design is actively evolving, the mobile docs focus on behavior rather than promising a specific side-by-side or toggle layout that can change between responsive revisions.

​
Mobile schedule

Schedule remains one of the five primary mobile tabs. The mobile view is optimized for touch and smaller screens while using the same underlying scheduled-post state as the rest of Socializioz. Use the Scheduling and calendar guide for lifecycle and rescheduling behavior.

​
Chat and keyboard behavior

The mobile Agent is built from the same ChatExperience used by the wider product. The mobile shell is keyboard-aware:
  • The bottom navigation hides while the keyboard is open.
  • The chat composer can explicitly signal focus so layout changes happen without waiting for the browser viewport calculation.
  • Chat and other mobile surfaces own their scroll behavior rather than forcing one global page scroller.
Slash commands, @ context tagging, attachments, and other current Chat controls are documented in Keyboard shortcuts and quick reference.

​
Notifications on mobile

The mobile header uses the same Socializioz notification center as desktop. Current public notification behavior is primarily in-app plus supported email delivery. Browser/OS push is not currently exposed as a complete user-facing notification channel in Notification Settings. See Notifications for the current controls rather than relying on older push-notification instructions.

​
Haptic feedback

The mobile shell can request light haptic feedback for selected navigation interactions where the runtime/device supports it. Haptics are enhancement only. A workflow must remain understandable and usable when the device, browser, or WebView does not provide vibration feedback.

​
Safe areas

The mobile shell accounts for device safe-area insets around the header and bottom navigation so controls do not intentionally sit underneath notches, rounded corners, or home indicators.

​
Connectivity

Socializioz is an online application. Core workspace actions require network access to authenticated backend and provider services. The product includes an offline notice when connectivity is lost, but this should not be treated as an offline publishing or offline-sync mode. Do not assume a draft, upload, schedule change, or Agent request completed until the server result confirms it.

​
Install options

Depending on platform and current distribution, users can open Socializioz through the supported web, PWA, or app-store experience. See Download and install for current installation links and guidance.

​
Troubleshooting

Last modified on August 16, 2026