Companion mobile app

A mobile app that complements the desktop Tree experience with quick status checks, notifications, and lightweight interactions. Ships post-v1.

The companion mobile app is a planned mobile application for iOS and Android that complements the desktop Tree experience. It does not ship at v1. This entry describes what the mobile app will be when it ships.

What the mobile app will do

The mobile app is scoped to the things mobile is genuinely good for:

  • Quick status checks: see what's available, what's in-progress, what's coming up
  • Notifications: receive in-app, push, and other reminder notifications on the go
  • Marking nodes complete: close out a task you finished offline or on the move
  • Capturing quick thoughts: add a node or comment when an idea strikes, expand on it later from desktop
  • Reviewing recent activity: catch up on what changed in a project (see Activity feed)

The mobile app is not the place to plan, restructure, or design complex graphs. The graph view requires screen real estate that phones don't have, and trying to make graph editing work on mobile would compromise the desktop experience.

What the mobile app won't do

The companion app deliberately won't:

  • Replace the desktop experience. Project planning is a desktop activity, and the mobile app is a satellite to that, not a substitute.
  • Try to render the full graph view at scale. Phones can show a few nodes at a time, but the structural argument Tree makes works best on a larger canvas.
  • Support every desktop feature. Bulk operations, advanced filtering, custom themes, and similar power-user features will remain desktop-only.

The mobile app is a complement, not a port.

Why it ships post-v1

Tree's v1 ships without a mobile app because:

  • The desktop experience has to be right first. The graph model, the UX patterns, the data structure: all of these need to be solid before they get adapted to a smaller form factor.
  • Mobile development doubles platform surface area. Adding mobile at v1 would slow the desktop product without serving the audience that's actually waiting for Tree.
  • The audience uses Tree mostly on desktop. Technical teams, developers, and PMs spend their planning time on laptops. Mobile is for the edges of the workflow, not the center.

Once the desktop product is stable and the audience is asking for specific mobile use cases, we'll build the companion app with that signal.

Tier availability

When the companion mobile app ships, it will be available on Free, Paid, and Team. There is no separate mobile-only tier.

LAST UPDATED · 2026-05-12