Mobile browser responsive navigation experience

Overview

Users accessing Simpplr from a mobile browser now get a navigation experience that is optimized for smaller screens while staying aligned with your existing navigation setup. This update improves discoverability, touch usability, and consistency by automatically organizing navigation into primary and secondary patterns for mobile browsing.

Before you begin

Administrators continue to manage navigation through existing desktop configuration. End users automatically receive the mobile-optimized browser experience with no additional setup required.

What is new

Mobile browser navigation now uses a mobile-first layout that respects existing navigation configuration, including ordering, grouping, and visibility settings, so users get a clearer and more usable experience on smaller screens.

What changed

Simpplr now delivers an improved navigation experience for people using the platform in a mobile browser. Instead of presenting navigation in a way that feels like a compressed desktop experience, the system adapts it into patterns that work better on phones and other small screens.

• Navigation items are presented in a more touch-friendly structure, with key destinations surfaced in primary navigation and additional destinations available through secondary navigation and the More experience.

• Primary navigation is easier to reach and use on smaller screens.

• Secondary navigation is organized to support discovery without overcrowding the interface.

• Ordering, grouping, and visibility remain aligned with configured navigation settings.

• The mobile browser experience is designed to feel more like a native mobile navigation model.

Why this matters

Navigation that works well on desktop does not always translate cleanly to a mobile browser. Smaller screens need clearer hierarchy, larger touch targets, and simpler access to common destinations.

This improvement helps by:

• Making important destinations easier to find quickly

• Reducing clutter on smaller screens

• Improving tap accuracy and general usability

• Providing a more consistent experience between configured navigation and what users see on mobile browsers

What users can expect on mobile browsers

When users open Simpplr in a mobile browser, they will see a navigation experience designed around smaller screens and touch interaction.

What is included in this update

The following behaviors are part of this release:

• Primary and secondary navigation mapping for mobile browser layouts

• Mobile-first navigation patterns to avoid a desktop-like experience on small screens

• A More view to support overflow items and additional actions

• Header behavior for search and notifications in mobile browser use

• Loading states so navigation does not briefly show stale or incomplete items

• Improved active state handling for landing pages, nested pages, and back navigation behavior

• Adjusted create actions and dashboard controls so they do not interfere with bottom navigation

• Refined search, notification, nested navigation, and More interactions to avoid overlapping UI states

Troubleshooting

Navigation items are not appearing in the expected order on a mobile browser.

• What happened: The mobile browser navigation uses existing navigation configuration as its source, including ordering, grouping, and visibility settings. If items appear out of order, the configuration may not be set up as intended, or the mobile layout may be organizing items into primary, secondary, and More patterns differently than expected.

• What to do: Review the navigation configuration in the desktop admin settings and confirm that the ordering and grouping are set correctly. The mobile browser layout respects these settings and organizes items accordingly. If the configuration looks correct, try refreshing the mobile browser and check again.

Some navigation items are not visible on the mobile browser.

• What happened: The mobile browser layout organizes navigation into primary, secondary, and a More view to avoid overcrowding smaller screens. Items that are not in the primary navigation may have been moved into the secondary navigation or the More view based on the configured setup.

• What to do: Check the More view in the mobile browser navigation for additional items. If specific items should appear in primary navigation, review the navigation configuration in the desktop admin settings and adjust the ordering or grouping as needed.

Search or notifications are not appearing in the mobile browser header.

• What happened: Search and notifications are part of the mobile browser header experience included in this update. If they are not visible, there may be a loading or display issue with the mobile browser session.

• What to do: Refresh the mobile browser and sign back in if needed. If search or notifications are still not appearing in the header, try clearing the browser cache and reloading Simpplr. If the issue persists, raise a support request.

Navigation briefly shows incomplete or stale items when the page loads on mobile.

• What happened: Loading states were introduced as part of this update to prevent navigation from briefly showing stale or incomplete items. If this is still occurring, the browser may be loading a cached version of the previous navigation experience.

• What to do: Clear the mobile browser cache and reload Simpplr. If the issue continues after clearing the cache, try accessing Simpplr from a different mobile browser to confirm whether the behavior is browser-specific.

Tapping a navigation item on mobile is opening the wrong destination or not responding.

• What happened: Active state handling for landing pages, nested pages, and back navigation was improved as part of this update. If a tap is opening an unexpected destination, there may be a conflict with a previous browser session or a cached navigation state.

• What to do: Refresh the mobile browser and try tapping the navigation item again. If the issue persists, clear the browser cache and reload Simpplr. If a specific navigation item is consistently routing to the wrong destination, raise a support request with details about the item and the destination it is opening.

Create actions or dashboard controls are overlapping the bottom navigation on mobile.

• What happened: Create actions and dashboard controls were adjusted as part of this update to avoid interfering with bottom navigation. If overlap is still occurring, the browser may be displaying a cached version of the previous layout.

• What to do: Clear the mobile browser cache and reload Simpplr. If the overlap continues, try accessing Simpplr from a different mobile browser to confirm whether the behavior is browser-specific. If the issue is consistent, raise a support request with a screenshot showing the overlap.

Frequently asked questions

Q: Do administrators need to reconfigure navigation for mobile browsers?

Ans: No. The mobile browser experience uses existing navigation configuration as its source and optimizes the presentation for smaller screens. No additional configuration is required.

Q: Will the navigation look exactly the same as on desktop?

Ans: It stays aligned with configured ordering, grouping, and visibility, but the presentation is adapted for mobile. Users may see items organized into primary, secondary, and More patterns rather than a desktop-style layout.

Q: Who benefits from this improvement?

Ans: End users who access Simpplr through a mobile browser and need a navigation experience that is easier to use on smaller screens.

Q: Does this improve touch usability?

Ans: Yes. The updated experience is designed to improve discoverability and touch usability by using mobile-friendly navigation patterns.