Miru Mobile App Preview: Track Time From Your Phone

The hours you forget to log are almost always the ones that happen away from your desk. A quick client call from the parking lot. A site visit that took three hours but got recorded as “misc” on Friday afternoon because you couldn’t remember the details.

We live this. Saeloun is a consulting company. The desktop and CLI cover 80% of our time tracking. The other 20% leaks because nobody is going to open a laptop on a train platform to log 45 minutes.

So we’re building a mobile app.

---

Why Expo

Our entire frontend team writes React and TypeScript. Expo lets us use the same language, same mental model, same component patterns. The mobile app shares types with the web app. The API contract is identical.

Expo 54 handles the platform-specific stuff — navigation, status bar, safe areas, gestures. We write the logic once. It compiles to real native code on iOS and Android. No WebView wrapper. The pragmatic choice.

---

What’s in v1

Four screens. That’s it.

Today view. Your entries for the current day, the project that’s eating the most hours, and a quick-add button. This is the screen you’ll use 90% of the time. Open the app, log what you just did, close the app. Five seconds.

Week view. Seven days laid out with per-day totals and entry counts. At a glance, you see the shape of your week. Which days are light. Which are overloaded. Where the gaps are. This is the screen you open on Friday to make sure nothing slipped through.

Activity feed. Recent entries across all sources — manual, CLI, MCP, automation. Source badges carry over from the web app.

Workspace switching. Multiple organizations? Switch between them from the More tab. Your entries, projects, and clients change with the workspace context.

What’s NOT in v1: invoicing. Invoicing is a desktop workflow — reviewing line items, adjusting amounts, clicking send. Cramming that onto a phone makes it worse. The mobile app is for capturing time, not running your business.

---

Offline Queue

Mobile means spotty connections. Subway. Airplane. Rural client site with one bar of signal.

v1 will queue time entries locally and sync when connectivity returns. Log 90 minutes on Acme while offline. The entry sits in a local queue. Phone reconnects, it pushes to the API. No data loss. No duplicate entries.

We’re not pretending this is simple to get right. Conflict resolution and retry logic need to be solid before we ship. That’s why it’s beta first.

---

Timeline

Beta for iOS and Android in Q2 2026. TestFlight and Google Play internal testing. Existing Miru users first. Want early access? Email us or open an issue on GitHub.

General availability depends on how beta goes. We’d rather ship late and solid than early and broken. The web app and CLI aren’t going anywhere. The mobile app is additive — it catches the hours that currently fall through the cracks.

No release date we’d regret promising. Just a mobile app that does the one thing mobile should do: capture work from wherever you are, as fast as possible.