Steph Johnson
@bkstephj1.bsky.social
CEO at Multiplayer.app, full stack session recordings to seamlessly capture and resolve issues or develop new features - without breaking your flow.
I wish I could laugh, but it’s an uncomfortable truth most executives overlook.
We obsess over churn rates and retention metrics, yet rarely measure how much inefficient debugging and support workflows cost the company (and who they actually serve).
We obsess over churn rates and retention metrics, yet rarely measure how much inefficient debugging and support workflows cost the company (and who they actually serve).
November 28, 2025 at 12:58 PM
I wish I could laugh, but it’s an uncomfortable truth most executives overlook.
We obsess over churn rates and retention metrics, yet rarely measure how much inefficient debugging and support workflows cost the company (and who they actually serve).
We obsess over churn rates and retention metrics, yet rarely measure how much inefficient debugging and support workflows cost the company (and who they actually serve).
Fullstory is fantastic for understanding user behavior. But debugging technical issues? That usually needs more than a replay of the UI.
For engineering teams that need deeper visibility there's Multiplayer.
dev.to/rohan_rajpal...
For engineering teams that need deeper visibility there's Multiplayer.
dev.to/rohan_rajpal...
Multiplayer vs Fullstory
Session replay tools have become a key component of testing and debugging workflows in recent years....
dev.to
November 25, 2025 at 2:31 PM
Fullstory is fantastic for understanding user behavior. But debugging technical issues? That usually needs more than a replay of the UI.
For engineering teams that need deeper visibility there's Multiplayer.
dev.to/rohan_rajpal...
For engineering teams that need deeper visibility there's Multiplayer.
dev.to/rohan_rajpal...
Raise your hand if this describes your technical support 👇
👀 If this feels familiar, I’d love to hear what’s working (or not) in your support flow. Ping me in the comments or DMs.
My take: the real problem isn’t the bug. It’s the missing context.
👀 If this feels familiar, I’d love to hear what’s working (or not) in your support flow. Ping me in the comments or DMs.
My take: the real problem isn’t the bug. It’s the missing context.
November 19, 2025 at 3:08 PM
Raise your hand if this describes your technical support 👇
👀 If this feels familiar, I’d love to hear what’s working (or not) in your support flow. Ping me in the comments or DMs.
My take: the real problem isn’t the bug. It’s the missing context.
👀 If this feels familiar, I’d love to hear what’s working (or not) in your support flow. Ping me in the comments or DMs.
My take: the real problem isn’t the bug. It’s the missing context.
November 11, 2025 at 10:51 AM
We tend to talk about innovation as if it comes from sudden sparks of genius: one person, one idea, one breakthrough. But most progress doesn’t look like that.
It’s rarely a lightbulb moment. It’s actually more like a relay race. 🧵
It’s rarely a lightbulb moment. It’s actually more like a relay race. 🧵
November 6, 2025 at 4:17 PM
We tend to talk about innovation as if it comes from sudden sparks of genius: one person, one idea, one breakthrough. But most progress doesn’t look like that.
It’s rarely a lightbulb moment. It’s actually more like a relay race. 🧵
It’s rarely a lightbulb moment. It’s actually more like a relay race. 🧵
End-user support is supposed to be simple: a user reports a problem, the team fixes it, everyone moves on. In reality, it’s usually a marathon of manual steps, tool-switching, and endless back-and-forth.
What’s tricky is that this marathon often ends with a (deceptively) positive outcome: 🧵👇
What’s tricky is that this marathon often ends with a (deceptively) positive outcome: 🧵👇
November 3, 2025 at 3:24 PM
End-user support is supposed to be simple: a user reports a problem, the team fixes it, everyone moves on. In reality, it’s usually a marathon of manual steps, tool-switching, and endless back-and-forth.
What’s tricky is that this marathon often ends with a (deceptively) positive outcome: 🧵👇
What’s tricky is that this marathon often ends with a (deceptively) positive outcome: 🧵👇
Looking for AI-related ice breakers for tomorrow’s MCP demo night in NY. Would this do? 😉
October 21, 2025 at 2:35 PM
Looking for AI-related ice breakers for tomorrow’s MCP demo night in NY. Would this do? 😉
Guess the team at Anthropic could’ve used a Multiplayer session replay for that one 👀
Claude Code error or human error?
From the latest Anthropic blog post: variable names don’t match (red)…misspelling of urgent (blue) … unnecessary second check (second yellow line)
From the latest Anthropic blog post: variable names don’t match (red)…misspelling of urgent (blue) … unnecessary second check (second yellow line)
October 16, 2025 at 5:38 PM
Guess the team at Anthropic could’ve used a Multiplayer session replay for that one 👀
Capture a full stack session recording once, use it for debugging, testing, support, feature development, and AI prompts.
Here's everything you can do in Multiplayer 👀 👇
Here's everything you can do in Multiplayer 👀 👇
October 8, 2025 at 3:52 PM
Capture a full stack session recording once, use it for debugging, testing, support, feature development, and AI prompts.
Here's everything you can do in Multiplayer 👀 👇
Here's everything you can do in Multiplayer 👀 👇
The best way to ‘win’ at Product Hunt is… not to chase upvotes? 🤔
Even though we weren’t gunning for the top, we ended up #8. Above Lovable. Above OpenAI. 😅
I’m not about to start believing PH is worth sinking weeks of effort into.
But I am grateful for everyone who left a comment, shared a thought, or yes, upvoted anyway.
I’m not about to start believing PH is worth sinking weeks of effort into.
But I am grateful for everyone who left a comment, shared a thought, or yes, upvoted anyway.
October 1, 2025 at 11:25 AM
The best way to ‘win’ at Product Hunt is… not to chase upvotes? 🤔
Product hunt is dead. Here’s what happened as soon as we launched Multiplayer 👇.
But here’s also why we did it anyway 🧵
But here’s also why we did it anyway 🧵
September 30, 2025 at 1:09 PM
Product hunt is dead. Here’s what happened as soon as we launched Multiplayer 👇.
But here’s also why we did it anyway 🧵
But here’s also why we did it anyway 🧵
We didn't launch on one of the biggest Product Hunt launch days of the last few weeks to “win”.
We launched to share why full stack session recordings matter.
We launched to share why full stack session recordings matter.
Multiplayer is live on Product Hunt 🚀 Here’s how you can support us:
1️⃣ DON’T UPVOTE (yes, you’ve read it right)
2️⃣ COMMENT with your feedback
Upvotes? Nah. Feedback? Yes.
1️⃣ DON’T UPVOTE (yes, you’ve read it right)
2️⃣ COMMENT with your feedback
Upvotes? Nah. Feedback? Yes.
September 30, 2025 at 12:52 PM
We didn't launch on one of the biggest Product Hunt launch days of the last few weeks to “win”.
We launched to share why full stack session recordings matter.
We launched to share why full stack session recordings matter.
Our first post on Hacker News 🤩
This feels like a rite of passage.
news.ycombinator.com/item?id=4537...
This feels like a rite of passage.
news.ycombinator.com/item?id=4537...
September 25, 2025 at 1:42 PM
Our first post on Hacker News 🤩
This feels like a rite of passage.
news.ycombinator.com/item?id=4537...
This feels like a rite of passage.
news.ycombinator.com/item?id=4537...
Debug faster, validate fixes, and even feed the whole story into your AI IDE.
Multiplayer’s full stack session recordings allow you to seamlessly capture and resolve issues or new develop features - without breaking your flow.
Multiplayer’s full stack session recordings allow you to seamlessly capture and resolve issues or new develop features - without breaking your flow.
September 25, 2025 at 12:37 PM
Debug faster, validate fixes, and even feed the whole story into your AI IDE.
Multiplayer’s full stack session recordings allow you to seamlessly capture and resolve issues or new develop features - without breaking your flow.
Multiplayer’s full stack session recordings allow you to seamlessly capture and resolve issues or new develop features - without breaking your flow.
We need to stop treating documentation as a static pile of text.
The future is documentation as an experience: dynamic, contextual, and part of the workflow.
Otherwise, the vicious cycle of outdated docs will never end.
The future is documentation as an experience: dynamic, contextual, and part of the workflow.
Otherwise, the vicious cycle of outdated docs will never end.
September 11, 2025 at 4:09 PM
We need to stop treating documentation as a static pile of text.
The future is documentation as an experience: dynamic, contextual, and part of the workflow.
Otherwise, the vicious cycle of outdated docs will never end.
The future is documentation as an experience: dynamic, contextual, and part of the workflow.
Otherwise, the vicious cycle of outdated docs will never end.
Reposted by Steph Johnson
I had the chance to speak at API World 2025 last week on a topic I’ve seen frustrate teams for years: API documentation.
Because let’s face it: most developers don’t want to read static docs. Outdated Postman collections and PDF references slow everyone down.
Because let’s face it: most developers don’t want to read static docs. Outdated Postman collections and PDF references slow everyone down.
September 11, 2025 at 3:59 PM
I had the chance to speak at API World 2025 last week on a topic I’ve seen frustrate teams for years: API documentation.
Because let’s face it: most developers don’t want to read static docs. Outdated Postman collections and PDF references slow everyone down.
Because let’s face it: most developers don’t want to read static docs. Outdated Postman collections and PDF references slow everyone down.
When we build something at @multiplayer.app, we aim for insanely great quality.
For example: we’ve been building a sandbox so you can test Multiplayer without signing up for a free trial. Seems straightforward, right?
But in practice, there’s a lot to think through 👇
For example: we’ve been building a sandbox so you can test Multiplayer without signing up for a free trial. Seems straightforward, right?
But in practice, there’s a lot to think through 👇
August 28, 2025 at 5:58 PM
When we build something at @multiplayer.app, we aim for insanely great quality.
For example: we’ve been building a sandbox so you can test Multiplayer without signing up for a free trial. Seems straightforward, right?
But in practice, there’s a lot to think through 👇
For example: we’ve been building a sandbox so you can test Multiplayer without signing up for a free trial. Seems straightforward, right?
But in practice, there’s a lot to think through 👇
A GTM tip for anyone building for developers:
If every feedback call is positive, it means you are only talking to fans and you are not learning enough.
Growth comes from talking to people who are struggling with some aspect of your product because its likely they are not the only ones.
If every feedback call is positive, it means you are only talking to fans and you are not learning enough.
Growth comes from talking to people who are struggling with some aspect of your product because its likely they are not the only ones.
August 19, 2025 at 3:32 PM
A GTM tip for anyone building for developers:
If every feedback call is positive, it means you are only talking to fans and you are not learning enough.
Growth comes from talking to people who are struggling with some aspect of your product because its likely they are not the only ones.
If every feedback call is positive, it means you are only talking to fans and you are not learning enough.
Growth comes from talking to people who are struggling with some aspect of your product because its likely they are not the only ones.
There’s a difference between searching the entire game to review a play and seeing it from the player’s helmet cam.
---
That’s the difference between observability tools and Multiplayer.
---
That’s the difference between observability tools and Multiplayer.
August 15, 2025 at 3:22 PM
There’s a difference between searching the entire game to review a play and seeing it from the player’s helmet cam.
---
That’s the difference between observability tools and Multiplayer.
---
That’s the difference between observability tools and Multiplayer.
Multiplayer doesn’t try to show you everything.
It shows everything that matters for a single bug, test run, or user session.
It’s not about coverage; it’s about clarity.
It shows everything that matters for a single bug, test run, or user session.
It’s not about coverage; it’s about clarity.
August 13, 2025 at 7:47 PM
Multiplayer doesn’t try to show you everything.
It shows everything that matters for a single bug, test run, or user session.
It’s not about coverage; it’s about clarity.
It shows everything that matters for a single bug, test run, or user session.
It’s not about coverage; it’s about clarity.
If your AI can write code but can’t help fix bugs, you’re only solving half the problem.
August 8, 2025 at 1:16 PM
If your AI can write code but can’t help fix bugs, you’re only solving half the problem.
“Works on my machine” isn’t just a joke.
It’s a symptom of broken workflows.
It’s a symptom of broken workflows.
August 1, 2025 at 11:56 AM
“Works on my machine” isn’t just a joke.
It’s a symptom of broken workflows.
It’s a symptom of broken workflows.
❝An information retrieval system will tend not to be used whenever it is more painful and troublesome for a customer to have information than for him not to have it.❞
👇 That’s why we focused on getting devs *all* the data for a bug, in a single timeline.
👇 That’s why we focused on getting devs *all* the data for a bug, in a single timeline.
July 29, 2025 at 12:59 PM
❝An information retrieval system will tend not to be used whenever it is more painful and troublesome for a customer to have information than for him not to have it.❞
👇 That’s why we focused on getting devs *all* the data for a bug, in a single timeline.
👇 That’s why we focused on getting devs *all* the data for a bug, in a single timeline.
If every outage still ends with 'can someone repro this?', you don’t have a reliable test case (👀👇).
You have a one-off incident waiting to happen again.
You have a one-off incident waiting to happen again.
July 22, 2025 at 1:59 PM
If every outage still ends with 'can someone repro this?', you don’t have a reliable test case (👀👇).
You have a one-off incident waiting to happen again.
You have a one-off incident waiting to happen again.
Every minute your engineers spend reconstructing context is a minute they’re not solving problems.
July 18, 2025 at 12:33 PM
Every minute your engineers spend reconstructing context is a minute they’re not solving problems.