Awesome! Ping us on discord (link in README) if you face any challenge setting it up.

Hey @tijs.org, iOS support just dropped on @measure.sh 🚀 Would love for you to give it a spin and share your thoughts!
github.com/measure-sh/m...

#iOSDev #swiftlang

Great to see this! Open source for a reason 🙌🏽

The script in @measure.sh repo- github.com/measure-sh/m...

Do you think that when the same big tech hire outside Indonesia, they tend to pay a comfortable salary?

@measure.sh empowers mobile teams to debug faster and more effectively with features like:
• Session Timelines
• Proactive Debugging
• Full control with self-hosting

Think of it as your team’s own internal tool, built for everyone. Get started on GitHub- github.com/measure-sh/m...

Building a tool like Healthline takes massive investment, which isn’t feasible for most teams.

That’s why we built @measure.sh —an open-source tool to help mobile developers debug production apps easily, without the overhead of building or maintaining it themselves.

MTTD ranging from days to months is something I’ve often heard from #AndroidDev and #iOSDev teams.

Uber’s tool, Healthline, tackles this with data like:
• Analytics
• Error Logs
• Time Spans
• Experiment Logs
• Backtraces

What’s your biggest MTTD challenge?

So now we’re building @measure.sh. It correlates user actions, app lifecycle events, device performance, network calls, and custom logs into one step-by-step view—helping devs spot patterns, find root causes, and resolve issues faster without juggling multiple tools.

To make matters worse, mobile apps lack continuous deployment. Updates go through App Store/Play Store reviews, phased rollouts, and user downloads—making it hard to quickly add logs or fix issues when something breaks in production.

Some tools used by mobile devs are owned by PMs (product analytics for user actions), marketing (session recording—rarely useful), customer support (user-reported issues), or backend teams (API monitoring). Debugging ends up as broken as the org design itself.

Been talking to mobile devs about monitoring (observability’s too mouthful for me to speak with stuttering 😅). One common theme: they juggle tools to piece together user actions, app state, logs, device state, API responses, and issues—to find patterns and pinpoint the root cause.

Also depends on what did they hire first for- web or mobile. First hire mobile- Flutter
First hire web- RN

I have been talking to mobile devs as well. Newer apps built in LATAM are being built in RN, newer apps built in India/ SEA are are being built in Flutter. That's true for agencies building for US biz as well.

Seems like it about access to talent with specific framework.

Inspired from Trainline and Tumblr, we had started doing it at Gojek. Now even Tumblr stopped. Gojek still seems to continue.