Try the experimental mobile footer navigation!

AI-generated summary

awesomerobot announced an experimental “Mobile footer navigation” feature for Discourse, designed to improve thumb reachability by placing a persistent navigation bar at the bottom of mobile screens. Available via /admin/upcoming-changes, the footer provides shortcuts to site sections (Topics, Chat, AI, Admin), a global menu, and content creation tools. It supports extensibility via APIs and includes secondary rows for sub-navigation like topic views.

Key features include contextual hiding of the footer when the keyboard is open or when scrolling down (with return on scroll up), and state preservation when switching between sections. Developers can integrate their own sections using MobileTabBarViews and helper methods like routeWithin and findRoute.

Feedback from users such as putty, darkpixlz, and NateDhaliwal highlighted both interest and concerns. Darkpixlz suggested dynamic scrolling behaviors and profile placement similar to Instagram, while NateDhaliwal reported bugs such as obscured topic titles, draft access issues, and awkward timeline placement. Ethsim2 expressed preference for keeping back navigation in the top-left corner for consistency with other apps.

Awesomerobot addressed these points, explaining that the footer aims to flatten navigation structures for increasingly complex Discourse sites, reducing steps needed to switch between diverse content types. While acknowledging that a fixed profile icon isn’t feasible due to varying site features, they confirmed that section visibility is conditional on enabled plugins (e.g., Chat or AI). In response to clutter concerns raised by Andrew_Bond, awesomerobot stated that future updates will include admin settings to customize which sections appear in the footer. Additionally, updates were made to fix composer visibility and improve scroll behavior to maximize reading space, responding to feedback from sniper756 and others about screen real estate.

We’re introducing an experimental mobile navigation layout that puts the main areas of your community within easier reach of your thumbs. This is behind an experimental upcoming change called “Mobile footer navigation.” Admins with a recently updated Discourse site can enable it from /admin/upcoming-changes.

Instead of opening the menu from the header, you’ll find a navigation bar at the bottom of the screen, with shortcuts to site sections, a global menu button, and a button for creating new content.

If you’d like to try it out here on Meta, join the design experiments group! This will be broadened to all Meta users if it goes well.

What does it change?

The new footer brings together:

  • Site sections: Switch between Topics, Chat, AI conversations, Admin and more! Other sections can be added via the API, and we’ll likely add support for more of our own plugins if this experiment progresses.
  • Menu: Open the site’s global hamburger menu… this is no longer contextual and will be persistent no matter where you are.
  • Create: Start a topic, personal message, chat, or AI conversation, according to your permissions and enabled features. Drafts are available here too.
  • Subnavs: On topic lists, views such as Latest, New, Unread, and Top appear in a secondary row above the main navigation.

The secondary row slides away as you scroll down and returns when you scroll up. The footer also hides while your keyboard is open for composing or chatting.

Switching between sections remembers where you left off. For example, you can move from a topic to Chat and then return to that topic. Tapping the active nav item again takes you back toward its start: from a topic to the topic list, from a chat channel to the channel list, etc.

When there are more than four navigation tabs, the first three stay visible and the remaining sections appear in an ellipsis button menu.

Anonymous visitors to public sites can use the footer too, with the login button available.

Navigation for larger screens remains unchanged, but we’re interested in exploring a consistent way to switch contexts there too.

For plugin and theme developers

This is an experimental change, so keep in mind these methods may change, but if you’d like to experiment with it the footer builds on the existing sidebar panel API. A panel opts in by returning a mobileTab object from its mobileTab getter.

Add a section tab

Use api.addSidebarPanel() to register a panel, or add a mobileTab getter to an existing panel:

import { routeWithin } from "discourse/lib/mobile-tab-bar";
import { withPluginApi } from "discourse/lib/plugin-api";
import { i18n } from "discourse-i18n";

export default {
  name: "example-mobile-navigation",

  initialize(container) {
    const router = container.lookup("service:router");

    withPluginApi((api) => {
      api.addSidebarPanel(
        (BaseCustomSidebarPanel) =>
          class extends BaseCustomSidebarPanel {
            key = "example";
            switchButtonIcon = "compass";

            get switchButtonLabel() {
              return i18n("example.navigation.title");
            }

            get switchButtonDefaultUrl() {
              return "/example";
            }

            get mobileTab() {
              return {
                label: this.switchButtonLabel,
                icon: this.switchButtonIcon,
                url: "/example",
                ownsRoute: (routeInfo) =>
                  routeWithin(routeInfo, "example"),
                isNestedRoute: (routeInfo) =>
                  routeWithin(routeInfo, "example.item"),
                createActions: [
                  {
                    label: i18n("example.navigation.new_item"),
                    icon: "plus",
                    action: () =>
                      router.transitionTo("example.new"),
                  },
                ],
              };
            }
          }
      );
    });
  },
};

The mobileTab object supports these properties:

Property Purpose
label Translated text displayed on the tab.
icon Icon displayed on the tab.
url The section’s starting URL, used before a previous location has been remembered.
primary Optional. Places the tab after Topics and ahead of other tabs.
badgeComponent Optional. Component rendered over the icon for unread indicators or counts.
ownsRoute(routeInfo) Identifies routes belonging to the section and determines when its tab is active.
isNestedRoute(routeInfo) Identifies detail pages where tapping the active tab or using the header’s back button should return to the section’s list.
showsTitleInHeader(routeInfo) Controls whether a nested page uses the title-style header beside the back button. Defaults to true.
createActions Optional array of { label, icon, action } objects contributed to the global Create button.

Topics appear first, followed by primary navigation tabs, other tabs, and admin.

Match routes and nested pages

Two helpers are available from discourse/lib/mobile-tab-bar:

  • routeWithin(routeInfo, ...names) matches a named route and its descendants.
  • findRoute(routeInfo, name) finds a named route in the current route’s ancestry, allowing access to its model through .attributes.

Other sections are checked before Topics when determining route ownership. This lets an extension claim a topic that represents content in its own section, as AI conversations do.

If no section claims a route, no section tab is highlighted, and the previously remembered section locations are retained.

Add secondary navigation

Use MobileTabBarViews to render a section’s views or controls in the row above the footer:

import Component from "@glimmer/component";
import { service } from "@ember/service";
import MobileTabBarViews from "discourse/components/mobile-tab-bar/views";
import ExampleNavigation from "./example-navigation";

export default class ExamplePage extends Component {
  @service mobileTabBar;

  <template>
    {{#if this.mobileTabBar.enabled}}
      <MobileTabBarViews>
        <ExampleNavigation />
      </MobileTabBarViews>
    {{else}}
      <ExampleNavigation />
    {{/if}}
  </template>
}

MobileTabBarViews renders its block into the footer’s secondary row. It renders nothing while the footer is hidden or disabled, so keep your usual navigation as the fallback.

The footer’s Menu button always opens the forum menu. Each section should provide its own navigation on its pages or through this secondary row.

Add creation actions and badges

Creation actions from all participating tabs are collected into the global Create button, with the current section’s actions first. Drafts are appended when available. If there is only one action, the button runs it directly… otherwise, it opens a menu.

For unread indicators, supply a badgeComponent that renders its own state and renders nothing when there is nothing to show.

:rocket: Let us know what you think!

Please let us know how the new navigation feels, especially when moving between topics, Chat, and other sections. If you encounter a layout or navigation issue, please let us know which device/browser combo you’re using!

15 likes

Looks great! I can see this being very helpful for those with larger devices :+1:

Is it safe to assume that if someone doesn’t have chat or AI agents enabled, those buttons don’t show up?

1 like

Yep! It might be useful to have a setting to exclude some sections even when enabled, but starting simple for now.

1 like

This is cool! I like it more than I expected to. My only thoughts is that it’s static and doesn’t move at all…

Wouldn’t it make a little bit of sense to respond to scrolls and lower it like this?

Would it also not make sense to have your profile down there like how Instagram works?

4 likes

Maybe! Instagram has it easy because they have a fixed number of options for everyone, in the case of Discourse we’re definitely going to be adding more features that could make sense in a footer bar, so a “…” button with a drawer to more sections may be necessary (and would always be the rightmost icon).

So the last item in the bar might not always be consistent, and ideally your notifications/user menu would always be in the same place. For now the header makes that easy.

1 like

Understood and 100% agreed—it would annoy me if the profile icon was darting around from site-to-site based on if I had admin or some features enabled. If this is ever customizable I think it would be great if that was a user option and admins only set default because that seems like one of those things that admins have no right controlling for every user when it is something so personal. Besides that nice work :slight_smile:

1 like

an option for backward navigation on the DiscourseHub app would be less annoying, rather than this being replaced from bottom left to top left corner :thinking:

any of meta’s button on the top left consumes too much width on an iPhone, with the search icon staying there and a language drop-down

1 like

Maybe! but also, I consider this special navigation bar only for DiscourseHub a mask for some design inconsistency on our part. The back button on the top left is fairly common amongst other apps… and bringing it to our mobile web experience means that we don’t need a separate way to handle it for Hub.

I think you mean bringing top left back button to apps other than DiscourseHub, if you want my short answer, please don’t​:thinking:

On my Safari PWA there’s a back button on the bottom left (and a forward button), and the top left (logo) goes to the homepage. It would be confusing, at least for a time, if the back button was relocated.

The other thing is that, the top row changes layout when i have scrolled through posts, i’m missing that on Meta on the DiscourseHub, though the PWA still has this character.

Overall, it’s a relief the impact of these changes is confined to the Hub, i can live with that​:slightly_smiling_face:

2 likes

Would that lead to this component being discontinued and merged into the core after the stable release?

3 likes

That’s not an official component so it would be up to the author to decide whether to continue supporting it if we go forward with our own version, we don’t have control over it.

1 like

A minor bug: If we entered a new topic, scroll to the bottom, and click the middle button of the nav bar to return to the topic list, the topic list would sometimes be kept at the bottom, maybe to the top will be better.

Also, add some Liquid Glass effects when dragging the menu buttons from one to another, or add some animations may be better?

1 like

I think this is part of the change, but is probably unintended. All on mobile :

You can’t see the topic title, category or tags, nor edit them.


Also, the footer nav blocks draft access.

Going to the pencil icon > My Drafts > Edit draft doesn’t open the draft still. The only solution is to reload.


I also feel the topic timeline is oddly placed. It’s not center, but not flushed right either. Could it be flushed right?


I’d also like to know the design rationale and reason for this change. Also, @awesomerobot is it possible for this to be a user preference?

1 like

The biggest issue this is trying to solve is that we’re adding more “sections” or types of content and navigation to Discourse (ai conversations, docs, boards, blog, etc) but have no unifying structure. It can take twice the number of steps and some guessing to get to the right nav right now.

A couple examples:

Getting from a topic to site settings and back again

Currently:

  1. open the ☰ menu
  2. click admin
  3. open the ☰ menu again[1]
  4. click site settings
  5. open the ☰ menu
  6. click “back to forum” to get back to the topic

With the footer nav:

  1. click admin in the footer
  2. click site settings
  3. click topics in the footer to get back to the topic

Getting back to an existing AI conversation from a chat channel

  1. Click back (because there’s no ☰ menu in Chat)
  2. Open the ☰ menu
  3. Click AI bot
  4. Open the ☰ menu[2] to find your previous conversations

With the footer nav:

  1. Click AI bot in the footer
  2. Scroll to find your previous conversation and click it

The footer provides a base to flatten the navigation structure on mobile, and make these paths predictable. Right now there’s a lot of nesting and it’s not very linear, and you have to know that the ☰ menu changes contextually.


  1. you have to know if just changed to the admin menu, which is not at all obvious ↩︎

  2. you have to know if just changed to the AI conversation history menu, which is not at all obvious ↩︎

1 like

Sorry, I’d like to share my personal perspective. Smartphone screens are already small. Thinking from a reader’s standpoint, enabling this feature would take up precious screen space and hinder reading. I suggest we not prioritize ease of operation alone; we should ensure it makes reading easier while remaining simple to use. Most forum users are readers, not writers.

2 likes

But mobile apps like Xiaohongshu (rednote), Douyin (TikTok), and X all follow this design pattern. Although I rarely post, I still frequently switch between the tabs at the bottom.

2 likes

Is it possible to reduce the footer options? For instance on the desktop site I am happy for my users to have ask ai. On the mobile version though too many options make it look cluttered.

1 like

I’ve made a few minor updates in this change

the biggest problem being collapsed the composer… it’s reachable now

No need to apologize, not everyone will agree on everything and that’s ok. I did consider this and now I’m trying out hiding the navigation on scroll down in topics to improve the reading space available.

was this after resizing the page in the browser to be more narrow? I did see an issue there and added a fix (and also tried to gain a little more space)

yes this was a clash with the DiscoTOC theme component, should be improved now…

yes, before this change is finalized I want to include settings so admins can control what appears in it

2 likes