Tecnoblog's Experience With Discourse Comments

[Thiago_Mobilon]

That’s strange… are you logged in? Also, did you try swiping sideways to see if the horizontal scroll bar appears?

If so, I wonder if it’s something that only happens with admin accounts.

[pmusaraj (Penar Musaraj)]

I am not logged in, I did try swiping left-right.

It’s possibly something that happens with admins. I see no repro with a regular user in a Chrome mobile emulator window.

Actually: I can repro as admin on our own blog.

[pmusaraj (Penar Musaraj)]

The horizontal scrollbar issue should be fixed once this lands: UX: Ensure hidden upload field does not break layout by pmusaraj · Pull Request #39619 · discourse/discourse · GitHub

[Thiago_Mobilon]

Nice, thank you! @pmusaraj

[Thiago_Mobilon]

@Thiago_Mobilon

The current flow is a bit of a conversion killer: User clicks login → New tab opens → Login happens → User is left on the community homepage. Back on the blog post, the iframe still looks logged out until the user manually refreshes the whole page. It’s a confusing loop that makes people give up and leave before commenting.

Just a quick heads-up: while this flow has been fixed for Google One Tap, it’s still behaving this way when using the native Discourse login.

[Falco]

We are working on making that flow better

https://github.com/discourse/discourse/pull/39756

It’s a complex change, but we are hopeful we can get a better UX.

[Thiago_Mobilon]

I found another UI bug:

When I click to edit my post, a blank space appears at the bottom of the iframe with no content. The ‘standard’ form remains open, but my comment isn’t inside it for editing. Also, the element showing the thread’s post count shifts to the left.

[Falco]

Sound similar to a bug on the AI Bot composer right @keegan ?

[keegan (Keegan George)]

@Thiago_Mobilon

When I click to edit my post, a blank space appears at the bottom of the iframe with no content. The ‘standard’ form remains open, but my comment isn’t inside it for editing. Also, the element showing the thread’s post count shifts to the left.

This should be now resolved with:

https://github.com/discourse/discourse/commit/c26bd748ccd71a1635909c3694540525281403af

[Thiago_Mobilon]

@Falco

FEATURE: Route full app embed pageviews into a dedicated `page_view_embed` counter by xfalcox · Pull Request #39535 · discourse/discourse · GitHub

I was just looking over the stats and I’m wondering if everything is working as expected. I’m seeing fewer than 400 daily pageviews under ‘Embedded Views.’

For context, the entire Community used to get about 8k pageviews a day before we switched to the full app embed—and that number has jumped more than 5x since we went live.

Shouldn’t that difference be reflected in the ‘Embedded Views’ section?

[Falco]

@Thiago_Mobilon

5. Login Friction

The current flow is a bit of a conversion killer: User clicks login → New tab opens → Login happens → User is left on the community homepage. Back on the blog post, the iframe still looks logged out until the user manually refreshes the whole page. It’s a confusing loop that makes people give up and leave before commenting.

Since we activated the new embed, our daily registrations have more than doubled, which is great. However, our engagement metrics haven’t moved at all. In fact, our DAU/MAU dropped – we have more logged-in users, but they aren’t interacting. Metrics like “Daily Engaged Users,” “New Contributors,” and “Postings” haven’t seen any increase.

This proves that people want to join the conversation, but they’re getting lost in the login loop and abandoning the post before they can actually comment.

This is now fixed, please update to get the new login flow.

https://github.com/discourse/discourse/pull/39756

[Thiago_Mobilon]

I think the new nested replies feature might not be compatible with Embed Mode.

I enabled nested replies on a topic to test it out, and instead of loading the comments section, the iframe ended up loading the post inside the post.