Yeah agreed, none of my users have been able to figure this out.

Hello,

https://take.ms/m7ihL Can you provide a specific page or full page screenshot on it? From your screenshot we hard to find out which page or which section on it, thanks.

What I’m saying and what I think Greg is getting at is that the icon doesn’t really effectively communicate the options are available through it.

For example in the events/groups/pages etc listings you would have to hit that button to create a new event/group/page and that isn’t very clear from the icon. So I’m constantly being asked by users how to create things on the site because they’re primarily mobile users and the icon isn’t very intuitive.

It looks like it’s a filter or settings button rather than a button for actions such as creation.

A different icon or a separate action icon alongside the current one would be ideal.

This is obviously also a problem in the current version, but I just wanted to put my voice behind this post.

Yeah Dom has it right, that icon is the mobile action icon on most pages, I've attached screenshots from the marketplace, groups, pages, event and user listing

I see, I will log this and discuss with my teammate to see how we can improve it, thanks for heads up.

Thanks Chang! Appreciate that!

You are most welcome Dom. By the way, the new beta 3 should already have these changes in place.

Oh fantastic! You guys work quick!

Thank you

Good catch.

Why not a button with text "New" that you can translate.

Why not a button with text "New" that you can translate.

Why spend more time into translations when everybody (I guess so...) understand the icon ??
... and it is already implemented ssnobben

1. The + symbol is generic and it everyone understands it.

2. It is only 1 character.

3. The word "New" is short in English. If you deal with customers with different translations, you will end up with some translations that uses 5 - 10 characters just for the word "New" which causes more issues.

Mark agree on that.

Aye I’m happy with a +

Thanks, since this is already implemented in beta 3, I am going to mark this thread as resolved and close this ticket