DailyCoding.dev VS Measure.sh

Measure.sh's answer:

Porsche, Astro, Hoichoi

DailyCoding.dev's answer

I do Advent of Code every December and try to keep the habit going on LeetCode every January. It never lasted more than a week, too many problems, no reason to do this one today. So I built what I actually wanted: one challenge, the same for everybody, all year round. Seven months of evenings and about 470 commits later, it runs in 11 languages.

Measure.sh's answer:

Measure grew out of a problem its founders kept running into. Between them they had led mobile engineering at companies including Gojek, Rapido and Groww, including the years when Gojek's app scaled from around 10,000 to 35 million daily active users. At each company they ended up building similar internal tooling to answer the same question: why is the app slow, frozen or broken for a real user in production when crash reporting shows nothing wrong? After rebuilding versions of the same tool more than once, they decided to apply the DRY principle to the problem itself and turn it into a product instead of another internal project. Measure was released publicly in September 2024 and is developed in the open under the Apache 2.0 license, with the roadmap and issues visible on GitHub.

DailyCoding.dev's answer

Developers who want a small daily habit rather than interview grinding: people who enjoy Advent of Code and miss it in January, students and apprentices practising algorithms, and experienced developers warming up in a language they are currently learning.

Measure.sh's answer:

Mobile engineering teams running consumer apps in production, especially at high growth companies where app quality has a direct effect on revenue and retention. Typical users are Android and iOS engineers, mobile platform and foundation teams, mobile leads and engineering managers who are accountable for crash free rates, ANRs, startup time and release health, along with the CTOs and VPs of Engineering who own those outcomes. Because Measure is open source and can be self hosted, it also fits teams with strict data residency or privacy requirements, and smaller teams looking for an open alternative to Firebase Crashlytics.

DailyCoding.dev's answer

One challenge per day, and it is the same challenge for everyone. There is no catalogue to browse and nothing to pick, that decision is exactly what makes most people quit after a week. Once you submit, every other solution to the same challenge becomes readable, across all 11 languages.

Measure.sh's answer:

Measure.sh is an open source observability platform built specifically for mobile apps, rather than a mobile SDK attached to a backend monitoring product. Its defining capability is the session timeline, which reconstructs a complete user session including interactions, navigations, network calls, logs, lifecycle events and CPU and memory signals. This allows teams to diagnose problems that never produce a crash, such as ANRs, UI freezes, slow API chains and edge case state bugs. Measure also provides Adaptive Capture, which lets teams change what data is collected remotely without shipping an app update, and an MCP server that exposes crashes, traces and sessions to coding agents. It is available as a managed cloud service or fully self hosted, and is licensed under Apache 2.0.

DailyCoding.dev's answer

Because it takes choice away instead of adding more. LeetCode and Codewars offer thousands of problems; Daily Coding offers the one that is live today. It is free with no paid tier, today's challenge works without an account, and the whole thing is open source under MIT, including the sandbox that runs the code.

Measure.sh's answer:

• Mobile first by design. Measure is built by mobile engineers for mobile teams, not adapted from a web or backend APM tool.
• Full session context. Session replays and timelines show the user actions, navigations, network calls and logs that led to an issue, not just a stack trace.
• Coverage beyond crashes. Crashes, ANRs, performance traces, network performance, bug reports, user journeys and app health metrics live in a single dashboard.
• Open source and self hostable. Apache 2.0 licensed, so teams can keep all app and user data inside their own infrastructure.
• Cost control. Per GB pricing combined with Adaptive Capture, which lets teams increase data collection during a risky release and reduce it afterwards without shipping an app update.
• Broad platform support. Android, iOS, Flutter, React Native and Kotlin Multiplatform.
• Agent ready. An MCP server exposes errors, traces and session data to coding agents and Slack for natural language debugging.

DailyCoding.dev's answer

Next.js 16 and TypeScript with the Monaco editor, deployed on Vercel. Submissions are executed on a self-hosted Piston instance on a Hetzner server, with typed test harnesses generated per language. Prisma for data access, Postgres DB

Measure.sh's answer:

• Backend services: Go
• Dashboard: TypeScript, React and Next.js
• Data stores: ClickHouse for events, sessions and traces, PostgreSQL for application data
• Streaming and caching: Apache Iggy and Valkey
• Object storage: S3 compatible storage, with MinIO used in self hosted deployments
• Symbolication: Symbolicator for native and mobile stack traces
• SDKs: Kotlin for Android, Swift for iOS, Dart for Flutter, and TypeScript for React Native, plus Kotlin Multiplatform support
• Deployment: Docker and Docker Compose for self hosting
• License: Apache 2.0, with the full source available on GitHub at github.com/measure-sh/measure