Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blog: How we built mobile replay #9376

Merged
merged 23 commits into from
Oct 17, 2024
Merged

Blog: How we built mobile replay #9376

merged 23 commits into from
Oct 17, 2024

Conversation

ivanagas
Copy link
Contributor

@ivanagas ivanagas commented Sep 18, 2024

Changes

How we built mobile replay

Checklist

  • Words are spelled using American English
  • Titles are in sentence case
  • Feature names are in sentence case too
  • Use relative URLs for internal links

Article checklist

  • I've added (at least) 3-5 internal links to this new article
  • I've added keywords for this page to the rank tracker in Ahrefs
  • I've checked the preview build of the article
  • The date on the article is today's date

Useful resources

@ivanagas ivanagas self-assigned this Sep 18, 2024
Copy link

vercel bot commented Sep 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Oct 17, 2024 0:15am

Copy link
Contributor

@Lior539 Lior539 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
@andyvan-ph andyvan-ph self-requested a review October 8, 2024 08:24
Copy link
Contributor

@andyvan-ph andyvan-ph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few bits I think we should tighten up, but this is looking good.

Also, does the headline make sense? I think "why it took so long" is a pretty minor part of the story and the real answer is "because we only started last year"! If that's part of the story, we should make it clearer when we actually started work on it.

contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
Comment on lines 35 to 39
Phones are much less powerful than desktops. Because of this, we need to be much more sensitive about performance.

If you've ever tried to record your phone screen, you would know its impact on performance. Apps take longer to load, animations become choppy, reactivity degrades, and your phone heats up.

Anything that degrades your user experience is not an option for many developers.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could do with a bit more caveating and context. Something about how the vast majority of phones aren't top-of-the-range iPhones. Your app needs to work just as well on $150 Android phone as a $1,500 iPhone 16 etc. That screen recording example is not universally true, so probably not a great example.

contents/blog/mobile-session-replay.md Show resolved Hide resolved

Not slowing down people's apps was core to our mission with session replay.

To do this, we decided to focus on capturing wireframes instead of screenshots. Although we built both in the end, wireframe mode is much less performance-intensive, meaning it is the mode users prefer.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we quantify this? how big is the difference?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

contents/blog/mobile-session-replay.md Show resolved Hide resolved
Co-authored-by: Andy Vandervell <[email protected]>
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
contents/blog/mobile-session-replay.md Outdated Show resolved Hide resolved
Co-authored-by: Andy Vandervell <[email protected]>
@ivanagas
Copy link
Contributor Author

Going to wait for Manoel's benchmarks then I'll merge this

@ivanagas ivanagas enabled auto-merge (squash) October 16, 2024 23:59
@ivanagas ivanagas merged commit 43d9ee1 into master Oct 17, 2024
3 checks passed
@ivanagas ivanagas deleted the built-mobile-replay branch October 17, 2024 00:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants