Creating/Editing a post on mobile: let's discuss the 2026 Discourse experience

Discourse is supposed to be mobile-first (though the experience has told me otherwise multiple times): it’s written here and here.

But Discourse has also brought more and more features (often useful!) over the years.

It’s a bit hard to find a screenshot of what the mobile composer looked like 10 years ago, but there is one here provided by @codinghorror on an iPhone 5:

How it looks like today (I purposely added content in the text area, because adding content also adds new icons/features on the screen… :sparkles:)

It feels overwhelming. There’s the top left icon which changes if I’m creating, editing, or doing something else.
There’s a icon whose purpose is not clear to me, as I have never tried tapping it (does it trigger a function, or show a tooltip?).
There’s the icon, which I don’t know what it does either. I know the two other icons on the same row, and I use them from time to time :slight_smile:

Anyway, the very first row of what we see on the topic creation contains text and 5 different icons, some of them being a bit cryptic until we try them (I suppose).


Then, there are the fields :sheaf_of_rice::sheaf_of_rice::sheaf_of_rice:.

The narrow category selector can barely contain a short, parent category name. Children category will be almost always truncated or simply out of sight.
Both inputs are even more crushing the content because they contain :

  • the categories icon or bullet,
  • a or icon
  • and a icon.

Then, the composer which forcefully displays the toolbar.

I don’t think we can toggle it? Anyway, a toolbar is useful for sure. We can scroll horizontally to reveal more formatting option, and I think you’ll miss this feature if you don’t already know it (the gradient hint is too subtle).

Having the rich/markdown toggle as the very first (and the widest, and the only colored one) icon from the toolbar seems a weird choice. I’m more likely to use bold or italic than going forth and back between the two editors.

Finally, on the last line, we have option that make sense.

But, again, there’s text and 5 more icons, but I think I don’t have much against them… Except, perhaps, the Gif option. Many smartphone keyboards have a Gif search. It could be removed, or put in the toolbar.

I know nothing about design, so I won’t try suggesting more, just mostly sharing my experience, what I see when I create a topic, and what above all, what and how much information my brain has to process. And, I must say, there is a little too much to see and process.

I wish the layout was cleaner, less icon and feature-bloated, focused on the task we ask for: write content, post content, be happy.


edit: small additional thought. Back in the days of older forum software, they would provide many features of questionable interest and tons of useless information. They would add all of those to show to their users and visitors, “look at all we can do!”

They did things because they could, not because they wanted to or needed to.

Seeing the profusion of icons and features added to Discourse over time (most are optional, but still… Just look back at the screenshot :smile:), I sometimes feel Discourse is slowly drifting toward the same old, and undesirable “show-off” path.

4 Likes

the experience is horrible on iphone and ipad. i don’t even know where to begin. can’t even upload a picture half the time, dropdown fills don’t fill or are out of screen view, or the composer locks up. i use mobile for only reading and basic posting because anything more is a headache.

3 Likes

It’s difficult to approach because most of these features were added out of some necessity or request… but it’s useful to step back and look at what they’ve added up to.

There are certainly ways we can look at simplifying and don’t disagree with any feedback here, but also Meta is a bit of a worst-case scenario where we test all the things… the default is at least a little calmer. AI, translations, and GIFs are all disabled.

To keep this on the path of being actionable, what should we remove from this default experience?

Some things that I see as possibilities:

  • The hamburger icon to show/hide the toolbar… should we always show the toolbar if your device is above a certain size so we can remove the toggle? (we have to make it toggleable on very small devices, because sometimes the composer is constrained to a single line of text otherwise)

  • I know that x is close and :wastebasket: is delete… but they certainly feel like they’re in the same realm of functionality. We used to have one and would ask about saving a draft with a modal… was that trade-off worth having fewer buttons here?

  • Can we collapse the tag input to a smaller button and only expand it on tap and when tags are present?

Does this start pushing things in the right direction? is there more worth hacking off?

2 Likes

tagging - tapping in some random place to close a menu seems not intuitive.

1 Like

I find the visual UX itself to be fine - i care less about the UX than i do about actual functionality. if i click the reply button, i don’t expect the composer to be locked up and not repsonsive. if i want to use a dropdown to fill with users or groups, or if want to upload a file, or if i select text to quote, i expect to be able to do so, without having to do some screen rotation or switch to my desktop. and it’s weird, because occasionally these things work on mobile, and sometimes they do not. i don’t know about android, but iOS just seems difficult to work with.

1 Like

I agree, the mobile UX is really not great. We have a lot going on…

I know that @chapoi had some ideas she shared with me last year on ways to make this mobile experience a lot cleaner.


In regard to feedback, I have something I’d like to share, but you can take it or leave it.

“The experience is horrible” coming form someone who is an avid user of Discourse feels a little unhelpful. I don’t want to be the word police here but offer some tips on giving feedback.

I think canapin’s post is a good example of how to give product feedback without the use of overly descriptive & emotional words.

What about it specifically is “horrible” for you?

I gave a presentation about discussing design that I like to come back to every now and again. (No credit to me, it’s just a presentation with info sourced from a book :smiley:)

I wonder if it would be helpful to read through? Wdyt?

Discussing-Design-Printable.pdf (7.6 MB)

2 Likes

sorry the strong words if they hurt. but the experience is poor and often frustrating, so the sentiment stands. i don’t even think it’s really a discourse thing, it’s a lot of iOS. if you think of it as a slight against you or discourse, it isn’t. i know from building components and customizing myself how difficult it is to accommodate mobile in general these days.

3 Likes

That reminds me of this bug report

2 Likes

That’s a good point! It’s the primary showcase of the software.

As a newly registered user (say hello to @Canapin2), here’s what it looks like on mobile:

It’s better of course, but could be even better. Still a bit intimidating. As a new user, I think I’d be very puzzled by the first row of icons, I’d understand only the ×.

Can’t answer all the open questions from your post, but I like your screenshot very much, especially the small tag part.

Overall, I like the elegance and how the composer finally breathes. I’m just judging how it looks, not really thinking about lost features. My first impression is “it’s the maximum apparent complexity the composer should display”.

3 Likes

Two things that I find difficult is fairly often buttons stop working (closing and re-opening the hub app fixes that) and sometimes clicking on a text area makes it disappear from the screen (abandoning the idea and sitting down at the desktop is the answer to that one). iPhone 11.

1 Like

Might be worth mentioning I never used the app, so my Discourse mobile experience is solely from a smartphone’s browser.

2 Likes

It’s a while ago so I can’t be certain, but I think I moved to the app because it was better.

OK i was pretty critical so i also want to “boost” (figuratively lol) the design/development improvement on mobile that i don’t think gets enough praise or attention the deprecation of /mobile and /desktop folder paths for the views.

at first i was skeptical and even a bit annoyed, but it did not take me long to like it better. this was a great and much needed change IMO. i think i recall Moin scolding me for not liking it at first lol. but, yea, thank you for that because i love that i can target all viewport sizes in one code file, including tablet size specifically. :clap: