The market research corpus lands — the broad pass, mapped
research/: long-term competitive-landscape research as a living body of work — the kanban market, the adjacent personal todo/task market, the file-based/local-first niche, and the AI-agent + task-management intersection, the two axes the bet actually lives on. The first pass (2026-08) is deliberately broad: a synthesis overview, the mainstream and native/indie/file-based segments, the todo-adjacent field, cross-cutting trends and success factors, the agents-and-tasks frontier, and a schema comparison against Signboard. The overview carries the narrow-pass agenda. Claude-Session: https://claude.ai/code/session_014PtZdPwqZuqEDLc6wZMtEy
This commit is contained in:
@@ -0,0 +1,58 @@
|
||||
# Market Overview — Synthesis of the Broad Pass
|
||||
|
||||
This is the synthesis of the 2026-08 broad pass over the kanban and adjacent todo/task-management markets, drawing on the four segment documents (02–05) and the agent-intersection deep slice (06). It maps the landscape, places Lanework in it, and distills what the evidence says about how apps in this space succeed and fail. Facts are cited loosely here; the segment docs carry the sources.
|
||||
|
||||
Researched: 2026-08-01
|
||||
|
||||
## The map: four rings around Lanework
|
||||
|
||||
The market divides cleanly into four rings, from farthest to closest to Lanework's position.
|
||||
|
||||
**Ring 1 — mainstream team SaaS (doc 02).** Trello, Asana, Monday, Jira, ClickUp, Notion, Linear, Airtable. Per-seat subscriptions, cloud-hosted, multi-billion-dollar revenues. Lanework does not compete here and shouldn't try; this ring matters as the source of the frustrations (bloat, seat-step billing, AI credit metering, cloud lock-in) that push users toward everything in the inner rings. Two structural facts stand out: kanban is usually a *view* over some other primitive (database, canvas, list), rarely the product itself; and offline/local-first is a near-universal gap treated as degraded fallback, never as architecture.
|
||||
|
||||
**Ring 2 — personal todo apps (doc 04).** Todoist, Things 3, TickTick, OmniFocus, plus the daily-planner wave (Sunsama, Akiflow, Motion). The durable businesses here are bootstrapped (Todoist, TickTick); the VC-funded ones keep pivoting out of the category (Motion to "AI Employees," Amie to meeting notes). Apple Reminders is the market's free ceiling — differentiation against it has to be structural, not featural. Kanban views exist (Todoist Boards, TickTick, Any.do, Lunatask) but always bolted onto a flat task list; nobody in this ring treats the board as the native data model.
|
||||
|
||||
**Ring 3 — native/indie/file-based tools (doc 03).** Lanework's actual neighborhood. The striking finding: at least six independent developers converged on "folder = column, file = card" within roughly 2024–2026 (Signboard, Tasks.md, Kanban MD, Kanbanero, banban, FileBoard). Tasks.md's 2.2k GitHub stars is the clearest demand signal for exactly this pattern. But every occupant is compromised for Lanework's purposes: Signboard is Electron; Tasks.md needs a self-hosted Docker container; Kanbanero is JSON with no card-body richness; FileBoard is brand-new and thin. The largest existing audience for markdown-backed kanban sits inside PKM tools (Obsidian's Kanban plugin, Logseq's plugin-only kanban) — real demand, always a secondary feature.
|
||||
|
||||
**Ring 4 — the agent intersection (doc 06).** The newest and fastest-moving ring. Markdown files are already the default substrate for feeding work to AI coding agents; Beads (~26k stars in months) proved pent-up demand for "an issue tracker an agent can drive"; OpenAI's Symphony turned a Linear board into a Codex control plane and reported a 500% increase in landed PRs — the strongest evidence anywhere that *a board with real states* unlocks agent throughput. Every mainstream tracker converged on hosted MCP + assignable agents within twelve months, so agent API access is now table stakes. A dense cluster of "kanban for agents" apps exists (Vibe Kanban, Conductor, Kanban Code), but all keep app-owned state.
|
||||
|
||||
## Where Lanework sits: the whitespace, precisely
|
||||
|
||||
The broad pass supports a precise statement of the gap: **nobody combines a genuinely good native human kanban UI with files-on-disk as the true source of truth, equally legible to any agent, script, or editor.**
|
||||
|
||||
Every agent-first tool has a weak or absent human GUI (Backlog.md, Beads, GNAP). Every polished GUI tool owns its state (Kanban Code's `~/.kanban-code/*.json`, Vibe Kanban's internal store, Kanbanero's JSON, Sprout's CoreData). Every mainstream tracker mediates agents through a server API. Lanework's "boards are folders and Markdown files; the app is the best human surface over that substrate" is validated from three independent directions — the file-over-app movement (Obsidian's scale, Steph Ango's essay), the convergent folder-as-board hobby projects, and the agent-tooling wave — yet unoccupied as a polished native product.
|
||||
|
||||
Two qualifications keep this honest. First, the window is narrowing: agent-friendliness went from novelty to expected-by-default in months, and an existing player (Signboard already ships an MCP server) could plausibly close the gap faster than Lanework builds breadth. Second, the demand signal for local-first is broad but not kanban-specific — the 9,300-post Reddit analysis found local-first demand at 7% of app wishes but no kanban-format requests within it; the kanban-specific demand evidence is developer-shaped (GitHub stars, HN threads), which says something about where early adopters will come from.
|
||||
|
||||
## What makes apps in this space succeed
|
||||
|
||||
Synthesized across all four rings, ordered by how consistently the evidence supports each.
|
||||
|
||||
1. **A sharp core promise kept undiluted beats feature breadth.** Things 3 thrives with no AI and no board view because the core promise (fast, beautiful, pay-once, reliable) never diluted; Linear won the Jira-refugee segment on focus and speed; every all-in-one player draws bloat complaints even while growing. Nobody has cracked simple-and-complete; picking a side and holding it is the proven pattern.
|
||||
2. **One-time or low-commitment pricing is a trust signal, not just a price point.** Subscription fatigue is measured and rising (active cancellation 31%→47%, 2024→2026). The $0–25 one-time range dominates native Mac kanban; users revolt not at price but at value-removal (Todoist's regional-pricing pull, Akiflow's billing surprises). Agenda's "pay once, keep what you unlocked" hybrid and Curio's MAS-subscription-or-perpetual-key dual track are the interesting patterns worth studying for Lanework's own model.
|
||||
3. **Bootstrapped survives; funded pivots or dies.** Every notable 2024–2026 failure (Height, Clockwise, Rise, Mayday) was VC-funded; the durable individual-focused businesses (Todoist, TickTick, Obsidian, TaskPaper's 15+ years) are all bootstrapped. Obsidian is the existence proof for the ceiling: ~$25M ARR, 18 people, zero VC, local-first — real money without the enterprise axis.
|
||||
4. **Native polish and speed are stated purchase reasons in the indie niche.** Repeated Electron-sluggishness complaints, repeated "feels like a real Mac app" praise; keyboard-first workflows lead the marketing of nearly every respected tool in ring 3. Lanework's native-Swift, keyboard-complete architecture is squarely what this buyer says they want.
|
||||
5. **AI that removes friction sticks; AI that replaces judgment doesn't (yet).** Natural-language capture demonstrably stuck (Todoist Ramble); summarization is used but not a switcher; full-delegation auto-scheduling is commercially fragile (Clockwise dead, Motion fleeing to B2B), and Height died five months after going all-in on autonomous PM. For Lanework the corollary is convenient: because the substrate is files, agents bring their own AI — Lanework never has to run, meter, or upsell compute, sidestepping the AI-credits resentment that plagues ring 1.
|
||||
6. **Abandonment is fatal in the indie niche; users tolerate minimalism but not staleness.** TidyCards (beloved, then stalled, then complained about) and Wunderlist (acquired, starved, killed) are the standing cautionary tales. Visible, steady development is part of the product.
|
||||
|
||||
## Threats and cautions
|
||||
|
||||
- **Obsidian Bases shipping a first-party kanban view** could commoditize markdown-board demand inside the largest existing file-based audience.
|
||||
- **Signboard** (Electron, same philosophy, MCP server, shipping since fall 2025) is the closest live competitor; "native, faster, more Mac-idiomatic" is the differentiation story against it and it must stay true.
|
||||
- **Pure-file storage has known scaling costs.** Taskwarrior's retreat from flat files to SQLite, Beads' entire thesis (markdown degrades under concurrent agent writers), and the Backlog.md thread's context-budget caveats all mark real technical territory Lanework must navigate — the write-provenance ledger and atomic-write architecture are already aimed at this, but multi-agent concurrent writes remain the hard open problem in the whole space.
|
||||
- **Category absorption from above:** Notion/Tana/Capacities absorbing tasks into cloud PKM graphs squeezes the casual end, and Apple Reminders squeezes the bottom. Both squeeze toward the same conclusion: Lanework's buyer is the person for whom file ownership and agent legibility are structural requirements, not nice-to-haves.
|
||||
|
||||
## The direct competitive set (for the narrow pass)
|
||||
|
||||
Ordered by how much attention each deserves in pass two: Signboard, Tasks.md, Kanban Code, Backlog.md, Beads, Kanbanero, Obsidian Kanban plugin (+ Bases trajectory), Vibe Kanban, FileBoard, Sprout, Conductor. Things 3 and Obsidian stay on the list not as competitors but as the business-model and community-playbook references respectively.
|
||||
|
||||
The Signboard deep dive is done: [07-schema-comparison-signboard.md](07-schema-comparison-signboard.md) compares the two on-disk formats and concludes the differentiation is durable and structural — Signboard's Obsidian-shaped format (mutable filenames as identity, prefix ordering, denormalized location keys) cannot adopt Lanework's posture (immutable UUIDs, rank ordering, versioned contract) without breaking every existing vault, and vice versa. It also sets the template for the remaining pass-two profiles.
|
||||
|
||||
## Open questions for the narrow pass
|
||||
|
||||
- Positioning and messaging study of the direct set above: exact feature matrices, pricing, and each one's actual traction beyond star counts.
|
||||
- Concrete launch case studies (HN/Product Hunt) for file-based task apps with real numbers — this pass found none; searching HN/PH directly rather than via aggregators is the fix.
|
||||
- Whether the agent-tooling audience (git/CLI discovery funnel) and the Mac-indie audience (MAS/Setapp/r/macapps funnel) overlap at all, since Lanework needs both and they may never see each other's channels.
|
||||
- Reddit/App Store review mining for kanban-specific (not PKM-general) local-first demand.
|
||||
- Pricing-model design: test the Agenda hybrid and Curio dual-track patterns against a straight Things-style one-time purchase for Lanework specifically.
|
||||
- Superlist's post-merger direction, as the one well-funded personal-task player still actively expanding.
|
||||
@@ -0,0 +1,146 @@
|
||||
# Mainstream / Team-Oriented Kanban and Project Boards
|
||||
|
||||
This document covers the mainstream, team-oriented kanban and project-board segment: cloud-hosted, account-based, multiplayer-first tools where the board lives on a vendor's server and is accessed through a web or desktop client.
|
||||
It is the segment Lanework is explicitly not competing head-on with (Lanework's boards are folders and Markdown files on disk, single-tenant, editor/git/agent-friendly), but understanding how this segment wins, monetizes, and where it frustrates users is the baseline for positioning everything else against.
|
||||
Researched: 2026-08-01
|
||||
|
||||
## Trello
|
||||
|
||||
- Positioning: the original consumer-friendly, card-based kanban tool; now Atlassian's low-friction on-ramp for individuals and small teams, sitting below Jira in Atlassian's portfolio.
|
||||
- Pricing: Free, Standard $5/user/mo, Premium $10/user/mo, Enterprise $17.50/user/mo (annual billing shaves ~17% off Standard/Premium); free tier now ships unlimited Power-Ups (up from a 1-Power-Up cap in earlier years).
|
||||
- Standout features / direction: 2025-2026 added Timeline, Dashboard, and Calendar views on Standard+; AI additions are incremental — AI quick-capture on Standard, AI content generation on Premium — described by reviewers as "help drafting, not project intelligence."
|
||||
- Signals: still huge — 50M+ global users, ~36,850 paying customers, subscriber base up ~25% YoY, and Trello is credited with contributing 700M+ of Atlassian's annual revenue. A 2025 UI redesign drew user backlash but doesn't appear to have dented growth.
|
||||
- Common complaints: to match what competitors ship natively (Gantt, time tracking, reporting) users stack 3-4 paid Power-Ups, which can add $20-40/user/mo on top of the subscription — at that point it's pricier than ClickUp or monday.com; no native task dependencies; permission/visibility gaps flagged by teams handling sensitive data; automation (Butler) run limits bite on the free plan.
|
||||
|
||||
## Asana
|
||||
|
||||
- Positioning: work-management platform for cross-functional teams that need process (goals, portfolios, workflows) more than a raw board; positioned above Trello, competing with monday.com and ClickUp.
|
||||
- Pricing: Free (Personal), Starter ~$10.99-13.49/user/mo, Advanced ~$24.99/user/mo (annual pricing varies by source/region); AI Studio ships with Starter+ and includes a monthly AI-credit allowance.
|
||||
- Standout features / direction: multiple views (kanban board, timeline, calendar, Gantt-style); Asana AI adds Smart Status (auto-analyzes project health) and Smart Summaries (AI recap of task/project activity).
|
||||
- Signals: large enterprise install base, steady public-company revenue growth; frequently named in "vs monday.com" comparison content, suggesting the two are each other's primary consideration set for buyers.
|
||||
- Common complaints: kanban board has no WIP limits, a real gap for teams trying to run disciplined flow; pricing escalates fast at scale; time tracking and other useful features are gated behind higher tiers; users want AI available below the Starter tier.
|
||||
|
||||
## Monday.com
|
||||
|
||||
- Positioning: "Work OS" — a highly visual, color-coded board-and-automation platform sold to ops-heavy teams (marketing, CRM, HR) as much as engineering; broad horizontal play.
|
||||
- Pricing: Basic $9/user/mo, Standard $12/user/mo, Pro $19/user/mo (annual), custom Enterprise; seats are sold in fixed blocks ("seat step"), not exact headcount.
|
||||
- Standout features / direction: repositioned in May 2026 as an "AI work platform with agents that actually do work"; AI is bundled into paid-plan seat pricing, but included credits cover only trial-level usage before teams must buy add-on credit packs.
|
||||
- Signals: public company (NASDAQ: MNDY); FY2025 revenue $1.232B (+27% YoY), Q1 2026 revenue $351.3M (+24% YoY), full-year 2026 guidance $1.466-1.474B; >$500K-ARR customer cohort grew 74% YoY; enterprise is now >42% of ARR; 250K+ customers, 2.5M+ paying users; GAAP-profitable with strong operating cash flow. This is the clearest financial-success story in the segment.
|
||||
- Common complaints: "seat step" billing forces paying for more seats than headcount; Reddit threads report serious customer-support frustration ("avoid this software at all costs" is a recurring sentiment); one analysis found tool-migration-away-from-monday.com activity up 23% YoY, suggesting churn pressure even as revenue grows — a "winning on financials, losing some goodwill" profile.
|
||||
|
||||
## Jira (incl. Jira's kanban story)
|
||||
|
||||
- Positioning: the engineering/agile default — kanban is a first-class board type alongside Scrum, but Jira's gravity is issue-tracking-for-developers rather than general-purpose kanban; kanban here means WIP-limited flow tightly coupled to sprints, backlogs, and dev tooling (branches, PRs, CI).
|
||||
- Pricing: Free (up to 10 users, unlimited projects/issues, Scrum+Kanban boards, but capped at 2GB storage, 100 automation runs/mo, 100 emails/day, community support only), Standard ~$6.52-7.91/user/mo, Premium ~$14.54/user/mo, custom Enterprise; Data Center (self-hosted) pricing rose ~15% in Feb 2026.
|
||||
- Standout features / direction: kanban vs. Scrum boards are differentiated primarily by sprint structure (Scrum = fixed iterations + ceremonies + roles; Kanban = continuous pull-based flow with WIP limits, no forced estimation) — this dual-mode flexibility inside one tool is Jira's core kanban pitch.
|
||||
- Signals: still the default for software teams; steady Atlassian-wide growth (see Trello section for shared Q3 FY2026 figures: revenue $1.787B, +32% YoY).
|
||||
- Common complaints: the real cost is the ecosystem, not the seat — no native time tracking or docs (needs Tempo/Confluence, both extra), Marketplace add-ons that can double per-user spend; steep learning curve alienates non-developer teams trying to use it as a general project board; regular price increases on both cloud and self-hosted tiers.
|
||||
|
||||
## ClickUp
|
||||
|
||||
- Positioning: "one app to replace them all" — maximalist all-in-one (docs, chat, whiteboards, goals, time tracking, kanban and 15+ other views) aimed at teams who want to consolidate tool sprawl.
|
||||
- Pricing: Free, then per-user paid tiers; pricing has been volatile enough that one Reddit user reported a bill jumping from $150 to nearly $1,200 overnight without warning.
|
||||
- Standout features / direction: ClickUp Brain (AI) expanded in 2026 with predictive timelines, smart task prioritization, and auto meeting notes; company reports 400% YoY AI sales growth and 800% YoY AI usage growth (Sept 2025).
|
||||
- Signals: $4B valuation (2021 raise), $537.5M total raised, ~$300M ARR (Sept 2025) with a public $1B ARR target for 2026 — but on May 21, 2026 the company laid off ~22% of its workforce (~290 of ~1,300 employees), explicitly framed as restructuring around AI, while simultaneously offering remaining staff up to $1M salaries. A genuinely mixed signal: strong top-line growth alongside a major structural reset.
|
||||
- Common complaints: "everything app" breeds feature bloat, confusing roles/permissions, and navigation/performance lag (status-update delays, calendar data loss) that persisted into 2026 per Trustpilot/Reddit reports; AI has gaps (no external file uploads, inconsistent task creation, no AI on custom dashboards); consistent theme across reviews: "great once configured, not plug-and-play."
|
||||
|
||||
## Notion (boards/databases)
|
||||
|
||||
- Positioning: flexible all-purpose workspace (docs + wiki + database) where kanban is one of several views on top of a database, not a dedicated product; wins teams that want one tool for notes and lightweight project tracking together.
|
||||
- Pricing: Free, Plus $10/user/mo, Business $20/user/mo, custom Enterprise; the standalone $10/mo AI add-on was eliminated in May 2025 — full AI (AI Agents, Ask Notion) now requires Business ($20/seat), which reviewers call "the floor for meaningful AI."
|
||||
- Standout features / direction: database "views" (table, kanban, list, calendar, gallery, timeline) over the same underlying records is the core mechanic; 2025 pushed autonomous multi-step AI agents and scheduled automations, aimed at moving upmarket.
|
||||
- Signals: $11B valuation (Jan 2026 employee tender), $600M ARR in 2025 (up from $300M in 2024), 100M+ users / 4M+ paying customers, headcount ~1,000 (up from 808 in 2024) — strong, sustained growth story with no new funding needed since 2021.
|
||||
- Common complaints: AI credit system has no rollover and burns fast (a simple daily-summary agent can eat ~3,000 credits/mo, ~$30); Business-tier billing practices draw complaints (guest-to-member auto-conversion charges, a Sept 2024 policy locking teams into unused seats until renewal); as a kanban tool specifically, it's "brilliant for docs, frustrating for automation" — the board is a view, not a purpose-built workflow engine, so things like WIP limits and swimlanes are weak or absent.
|
||||
|
||||
## Linear
|
||||
|
||||
- Positioning: opinionated, fast, keyboard-first issue tracker for software teams who find Jira too heavy; deliberately narrow scope rather than all-in-one.
|
||||
- Pricing: Free, Basic ~$10/user/mo (5 teams, unlimited issues, admin roles), Business ~$16/user/mo (unlimited teams, private teams, guests, Linear Insights, Zendesk/Intercom integration), custom Enterprise.
|
||||
- Standout features / direction: Cycles (lightweight sprint planning without ceremony), extremely fast native-feeling UI; 2025 added AI features — auto-categorization, sprint suggestions, AI-drafted release notes.
|
||||
- Signals: $52M raised, $400M+ valuation, 50+ employees (based on older figures likely understating current scale); reviewers consistently call it good value at its price points, and it has become the default "Jira alternative" recommendation for product-led dev teams.
|
||||
- Common complaints: per-seat pricing burdens fast-growing teams; enterprise-grade features locked behind the pricier tier; deliberately narrow scope means teams that need Jira/ClickUp-style breadth (arbitrary custom fields, non-eng workflows) outgrow it.
|
||||
|
||||
## Airtable (kanban view)
|
||||
|
||||
- Positioning: database-first, spreadsheet-flexible platform where kanban is one of 8+ views on a table of records; pitched at ops/marketing teams building custom internal tools as much as at project managers.
|
||||
- Pricing: Free, Team $20/user/mo, Business $45/user/mo, custom Enterprise Scale; a 40-seat Business deployment runs roughly $21,600/yr.
|
||||
- Standout features / direction: multiple views per table (kanban, grid, calendar, gallery, dashboard, form) with independent filters/sorts per view — powerful for teams where different roles need different lenses on the same underlying data.
|
||||
- Signals: mature, well-established in the ops/no-code space; frequently recommended as the go-to when kanban needs to be backed by relational data rather than freeform cards.
|
||||
- Common complaints: billing is asymmetric (mid-cycle seat additions charge immediately, removals don't refund the current invoice); performance degrades well below the platform's published record limits; steep learning curve ("incredibly powerful but will make you question your life choices"); uncontrolled Editor-seat sprawl is a real budget risk at scale.
|
||||
|
||||
## Height — DEFUNCT (signal worth flagging)
|
||||
|
||||
- Positioning (historical): venture-backed "autonomous project collaboration tool," an AI-native alternative to Linear/Jira aimed at product teams, founded 2018 by ex-Stripe engineer Michael Villar.
|
||||
- Funding: raised ~$18.3M total, including a $14M Series A (Redpoint Ventures, 2021).
|
||||
- Trajectory: launched "Height 2.0" in October 2024, marketed as the first fully autonomous PM tool with an embedded AI reasoning engine (auto bug triage, backlog pruning, self-updating specs) — then just five months later, on March 20, 2025, announced a full shutdown, going offline September 24, 2025.
|
||||
- Signal: the CEO gave no substantive public reason for the shutdown, and the timing (right after an ambitious, heavily-marketed AI pivot) strongly suggests the AI-autonomy bet didn't convert to sustainable revenue. This is the segment's clearest cautionary tale in 2024-2026: a well-funded, well-reviewed tool that bet everything on "AI does the project management for you" and folded anyway. Worth remembering when evaluating how much AI-agent framing to lead with versus treating it as one integration among several.
|
||||
|
||||
## GitHub Projects
|
||||
|
||||
- Positioning: free, built-in kanban/board layer over GitHub Issues and PRs, for teams whose work already lives in GitHub; not a standalone product.
|
||||
- Pricing: free with no meaningful limits for public repos; included with GitHub plans otherwise.
|
||||
- Standout features / direction: board view, roadmap view, and custom fields have matured well; genuinely good when a team's unit of work is already a GitHub issue.
|
||||
- Signals: default choice for open-source and GitHub-native dev teams; adoption is a function of GitHub's own dominance rather than independent PM-market share.
|
||||
- Common complaints: every card must be a GitHub issue — no concept of a freeform card, and creating items programmatically means going through GitHub's full auth model; large boards (50+ active cards) get slow and hard to scan; WIP-limit enforcement and cumulative-flow/cycle-time analytics vary by plan and are missing in several tiers; "too narrow for a general list" if work doesn't already live in GitHub.
|
||||
|
||||
## Basecamp (Card Table)
|
||||
|
||||
- Positioning: deliberately simple, bundled project-management-plus-communication suite from 37signals; Card Table is Basecamp's kanban-equivalent, one tool among Message Boards, Campfire chat, Check-ins, etc. Self-funded, no VC — a notably different company-structure signal than everything else in this list.
|
||||
- Pricing: Plus $15/user/mo (unlimited projects, guest invites, 500GB storage); Pro Unlimited $299-349/mo flat (no per-seat pricing at all) — the flat tier is the better deal for teams of ~20+.
|
||||
- Standout features / direction: Card Table defaults to columns like Triage / Figuring It Out / In Progress / Done, fully renamable/reorderable; cards carry title, assignee, due date, description, attachments, comments — intentionally shallow compared to competitors.
|
||||
- Signals: stable, profitable, long-lived (5+ years of reliability cited approvingly by users); no growth-at-all-costs narrative — 37signals is famously anti-VC and anti-feature-bloat by philosophy.
|
||||
- Common complaints: task management is "too simple" for complex workflows versus Asana/Jira; minor bugs (e.g., copied cards/to-dos retaining original creation dates); reviewers frame the value proposition bluntly: "worked in 2010, hard to justify in 2026 unless you specifically value simplicity over capability" — flat pricing is the main thing keeping it competitive.
|
||||
|
||||
## MeisterTask
|
||||
|
||||
- Positioning: design-forward kanban tool from the MindMeister family (mind-mapping heritage), aimed at small-to-mid teams who want an attractive, easy board plus light time tracking.
|
||||
- Pricing: Free (Basic), Pro ~€13.5/user/mo (~$4.99 annual), Business ~€24/user/mo (~$12.99 annual), custom Enterprise.
|
||||
- Standout features / direction: built-in time tracking and MindMeister mind-map integration are the differentiators; 2026 added "Meister AI" (note search + writing assistant) on tiered AI credits.
|
||||
- Signals: positioned as a budget-friendly, well-liked small-team tool; strong design/UX praise is the consistent throughline in reviews.
|
||||
- Common complaints: bugs and slow customer support recur in reviews; admin visibility and viewer-permission limitations; mobile app lags the web app; and — notably — pricing has crept up to Asana-territory levels "without offering anywhere near the tools or polish," per one reviewer, i.e. the segment's classic small-vendor risk of pricing outrunning perceived value.
|
||||
|
||||
## Kanbanize / Businessmap
|
||||
|
||||
- Positioning: enterprise-grade, analytics-heavy kanban for teams practicing formal Kanban method / Lean flow management, rebranded from Kanbanize to Businessmap to reflect a broader "align strategy to daily work" (OKRs, portfolio, whiteboards) pitch.
|
||||
- Pricing: from ~$149/yr for 15 users up to ~$10/user/mo tiers depending on plan; no free tier for individuals.
|
||||
- Standout features / direction: deep analytics module — cumulative flow, cycle time, task distribution, block-resolution time, created-vs-finished charts, task hierarchy — is the clear differentiator versus lighter kanban tools; strong automation and integration support.
|
||||
- Signals: well-regarded in Gartner Peer Insights for Kanban/PPM use cases specifically; positioned as the choice when a team is serious about flow metrics rather than just a visual board.
|
||||
- Common complaints: steep setup/learning curve given the feature depth; no free tier limits trial-ability for individuals; occasional friction in the advanced-analytics and card-management UI.
|
||||
|
||||
## Zenkit
|
||||
|
||||
- Positioning: flexible, view-agnostic work-management suite (part of a small European "Zenkit family" of apps including Zenkit To Do and Zenkit Hypernotes) aimed at small teams wanting Trello-like simplicity with more view options.
|
||||
- Pricing: Free (Personal), Plus ~$9/user/mo (~€8 annual, up to 10 users), Team ~€12/user/mo annual (unlimited users, advanced Gantt), Business ~$25/user/mo (~€21 annual, API/SCIM/SSO), custom Enterprise.
|
||||
- Standout features / direction: kanban, table, mind map, calendar, and list views over shared data; reporting flexibility (700+ report combinations cited); real-time collaboration.
|
||||
- Signals: smaller player, praised for a generous free tier and fair small-team pricing rather than for scale or growth headlines.
|
||||
- Common complaints: limited offline functionality (notable gap versus a filesystem-first tool); mobile app lacks features present on desktop/web; reminder system seen as weaker than dedicated task-reminder apps; support seen as improved but still occasionally slow.
|
||||
|
||||
## Miro (kanban)
|
||||
|
||||
- Positioning: infinite-canvas visual whiteboard where kanban is one structured layout among many (alongside diagrams, sticky-note brainstorms, retros); wins teams that want workshop/ideation and board tracking in the same tool.
|
||||
- Pricing: subscription tiers by feature/team size, monthly or annual; notably charges for every viewer, not just editors, which is a frequent point of user friction.
|
||||
- Standout features / direction: Miro AI can generate a kanban board directly from document notes or a prompt, and AI is being woven into Tables/Timelines as well — leaning into "AI drafts the board structure for you."
|
||||
- Signals: broad enterprise adoption as the default whiteboard tool, with kanban as a secondary but growing use case; strong G2/Gartner presence.
|
||||
- Common complaints: pricing is "pricey" and per-viewer billing is unpopular; free-tier board resolution/access is restricted; performance slows on large or complex boards; boards become hard to manage once they grow past initial planning-stage scope — i.e., Miro's kanban is good for lightweight/visual use but doesn't hold up as a long-running system of record for ongoing work.
|
||||
|
||||
## Wrike / Teamwork (brief)
|
||||
|
||||
- Wrike: positioning as a capable, "polarizing" enterprise work-management platform; pricing from $9.80/user/mo up to $25/user/mo (Business); Board/kanban view is intuitive early but cards get cramped once subtasks pile up; advanced reporting, budgeting, and key integrations are gated to Business+ — reviewers call it powerful but excessive for small teams with simple workflows.
|
||||
- Teamwork.com: pricing from $10/user/mo up to Grow at $24.99/user/mo; positioned similarly to Wrike for client-services/agency work; kanban is a core but not differentiating feature; both tools compete primarily on "can it also do budgeting/client-billing," not on kanban quality specifically.
|
||||
|
||||
## Notable newcomers, 2024-2026
|
||||
|
||||
- **Sprout** (sproutformac.com, Product Hunt Dec 2025) — a native macOS kanban board built by an independent developer (Elio Raineri), explicitly positioned against feature bloat: no accounts, no notifications, offline-first, $0.99/mo or $9.99/yr with a free tier. Storage is CoreData + iCloud sync, not plain files on disk, and boards export to JSON rather than living as an editable folder — so it validates the demand for "simple native Mac kanban" but does not occupy Lanework's filesystem-as-source-of-truth niche. Closest thing found in this pass to a direct stylistic precedent; worth a fuller look in the native/indie segment doc (03) rather than here.
|
||||
- **Kanban Kanban** (Product Hunt Nov 2025) — a novelty/recursive concept where every card opens into its own nested board ("Kanban within Kanbans"); still in validation phase, more a design experiment than a competitor.
|
||||
- Broader pattern: most genuinely new entrants in 2024-2026 are AI-agent-framed (per the market-trends search, "AI in Project Management" is projected to grow from $5.32B in 2025 to $14.14B by 2030 at ~22% CAGR) — but Height's collapse right after its own AI-autonomy relaunch is a strong counter-signal that "AI does your PM for you" alone isn't yet a durable product, even well-funded.
|
||||
|
||||
## Patterns across this segment
|
||||
|
||||
- **Monetization is almost universally per-seat SaaS**, usually 3-4 tiers (Free / Starter / Business / Enterprise) with the real feature ceiling (advanced automation, SSO, analytics, unlimited AI) reserved for the top two tiers; Basecamp's flat-fee Pro Unlimited tier is the one deliberate outlier, and reviewers consistently flag it as refreshing precisely because it's an outlier.
|
||||
- **AI is now default table stakes, but monetized separately from the base seat** — nearly every vendor above added AI credits, add-on tiers, or AI-gated top plans in 2025-2026, and nearly every vendor's user complaints include some version of "the credits run out fast" or "AI should be included, not upsold." This is a live, unresolved tension across the whole segment, not a solved problem — an opportunity for any tool that doesn't need to meter AI because it isn't running the AI's compute.
|
||||
- **Feature breadth is the main axis of both differentiation and complaint.** The all-in-one players (ClickUp, monday.com, Notion, Airtable) win deals by consolidating tool sprawl but consistently draw "bloat," "complexity," and "confusing pricing" complaints; the narrow players (Linear, Basecamp, GitHub Projects) draw praise for focus and speed but "outgrow it" complaints once teams need more. Nobody has cracked staying simple while also being complete.
|
||||
- **Kanban itself is rarely the product — it's a view.** Notion, Airtable, Miro, and Basecamp all treat the board as one lens over some other underlying primitive (a database, a canvas, a to-do list). Only Trello, Jira, and the dedicated Kanban-method vendors (Businessmap, Zenkit, MeisterTask) treat kanban as the primary mental model — this maps onto Lanework's own bet that a dedicated, opinionated kanban tool has room next to the generalists.
|
||||
- **Offline/local-first is a near-universal gap.** Every reviewed tool that mentions offline support treats it as a degraded fallback mode (cached view, sync-on-reconnect), never as the primary architecture; the one tool built local-first from day one (Sprout) is a solo-indie Mac app, not a team tool, and even it uses CoreData+iCloud rather than plain files. No mainstream team-kanban product treats "the board is just files you can point git or an editor at" as a feature — this remains open ground.
|
||||
- **Signals of health are decoupled from user sentiment.** monday.com and Notion are financially thriving (strong ARR growth, profitability, high valuations) while simultaneously generating real churn/complaint signal on Reddit (support quality, seat-step billing, AI credit exhaustion); ClickUp is growing ARR fast and cutting 22% of staff in the same year. Financial success in this segment does not require having resolved the UX/pricing complaints — there's a wide gap between "big and growing" and "loved," and that gap is where smaller, opinionated tools find room.
|
||||
- **AI-native repositioning is high-risk when it replaces rather than augments the core product.** Height's shutdown five months after going all-in on "autonomous PM" is the sharpest cautionary data point in this pass: a funded, well-reviewed tool bet the company on AI doing the PM work, and it didn't save them. The safer pattern among survivors (Notion, ClickUp, Trello, Linear) is AI as an added capability layered onto an already-working core product, not a replacement for it.
|
||||
- **Where the segment is heading:** continued AI-agent framing (autonomous status updates, auto-triage, AI-drafted boards) as the primary marketing surface for 2026; continued per-seat pricing with AI carved out as a separate metered layer; consolidation pressure (all-in-one suites absorbing point-solution features) balanced against a steady trickle of focused, fast, opinionated alternatives (Linear-style) winning specific technical audiences; and early, still-marginal interest in data sovereignty / local-first as a reaction to cloud-dependency fatigue, which is the crack in this segment's armor that a filesystem-native tool like Lanework can credibly target.
|
||||
@@ -0,0 +1,300 @@
|
||||
# Native macOS / Indie / Personal Kanban & Plain-Text-Adjacent Tools
|
||||
|
||||
Scope: this is Lanework's most direct competitive neighborhood — native or near-native macOS kanban apps built by indies, plus the wider ring of plain-text and markdown/file-based task tools (PKM apps with board views, open-source self-hosted kanban, CLI/plain-text ecosystems, and the newly-emerging category of AI-agent-native task trackers). For every app the key axis tracked is data model: does it own a proprietary database, or does it store state as files a human (or agent, or `git`) can read and edit directly. This is a broad first pass, not exhaustive — it's meant to map the neighborhood and surface patterns, not to be a definitive database.
|
||||
|
||||
Researched: 2026-08-01
|
||||
|
||||
## 1. Native macOS indie kanban apps (direct competitors)
|
||||
|
||||
### Kanbanier
|
||||
One-line: polished native Mac/iOS kanban board app, the closest thing to an "established" indie kanban incumbent on the Mac App Store.
|
||||
Platform: macOS + iOS, native (Swift/AppKit-family), historically on the Mac App Store.
|
||||
App Store: **apparently delisted** (checked 2026-08-01) — the widely-cited Mac (id1206854548) and iOS (id1206858343) listings both 404, and the iTunes Search API returns no hits for the app or its developer in either storefront, while kanbanier.com still markets it as live. A quiet delisting is a stronger decline signal than anything else in this entry.
|
||||
Data model: proprietary — boards live in the app's own storage, exported/synced via iCloud; no user-facing files.
|
||||
Pricing: one-time purchase, ~$15, with a free tier of limited functionality; in-app purchase unlocks swimlanes/sublanes.
|
||||
Standout features: swimlanes and hierarchical sub-lanes, tags/colors, iCloud sync, cross-device (iOS+Mac) support, no accounts/subscriptions.
|
||||
Sync: iCloud only.
|
||||
Signals: has been around for years (multiple SEO/download-mirror sites index it) and was the closest thing to an established indie incumbent — but the apparent App Store delisting (above) reclassifies it from "mature/low-growth" to likely abandoned or withdrawn; the incumbent slot on the MAS shelf may be effectively vacant.
|
||||
|
||||
### Kanbanero
|
||||
One-line: minimalist native Mac kanban board explicitly built around "boards are files" — the single closest analog to Lanework's own pitch in this whole survey.
|
||||
Platform: macOS only, native, universal binary, macOS 12+.
|
||||
App Store: [Mac](https://apps.apple.com/us/app/kanbanero/id1645553955?mt=12)
|
||||
Data model: **each board is a plain JSON file in a folder you pick** — explicitly pitched as diffable/git-friendly ("check them into your project repo, review changes in diffs, keep task state alongside your code").
|
||||
Pricing: one-time $8.99 on the Mac App Store, no subscriptions/accounts/IAP.
|
||||
Standout features: keyboard-driven (⌘N new task, ⌘L switch project), templates, themeable (fonts, accent colors, animated shader backgrounds), sync delegated to whatever the user already uses (iCloud Drive, Dropbox, Syncthing, git) rather than built-in.
|
||||
Sync: none built-in by design — user puts the folder wherever they already sync.
|
||||
Signals: small/new, marketed almost entirely on the "no accounts, no cloud, no tracking, your data is a file" pitch — i.e. explicitly courting the same buyer Lanework is courting, but with JSON rather than Markdown+folder-structure, and no first-class git/editor/agent story beyond "it's just a file."
|
||||
|
||||
### Sprout
|
||||
One-line: newer (Dec 2025 Product Hunt launch) "calm," minimalist native Mac kanban app pitched against feature bloat.
|
||||
Platform: macOS, native, Mac App Store.
|
||||
App Store: [Mac](https://apps.apple.com/us/app/sprout-kanban-board-tasks/id6752939873?mt=12)
|
||||
Data model: proprietary — Core Data, not user-facing files.
|
||||
Pricing: free with an optional Pro/lifetime upgrade.
|
||||
Standout features: zero onboarding, no accounts, offline-first, iCloud sync across devices, no notifications/ads.
|
||||
Sync: iCloud.
|
||||
Signals: fresh Product Hunt launch, positions directly against "everything apps" (implicitly Notion/ClickUp) — validates that "calm, native, boring-in-a-good-way kanban" is a currently-active niche indies are still entering.
|
||||
|
||||
### Kanba
|
||||
One-line: free-with-IAP simple kanban board on the Mac/iOS App Store.
|
||||
Platform: iOS-first; runs on Mac only via Apple Silicon's "iPad apps on Mac" compatibility (checked 2026-08-01), not a dedicated macOS binary — which explains the macOS 15+/Apple Silicon requirement.
|
||||
App Store: [Mac + iOS (universal listing)](https://apps.apple.com/us/app/kanba-kanban-project-board/id6499422529)
|
||||
Data model: proprietary, iCloud-synced.
|
||||
Pricing: free with in-app purchases (amounts not published on listing).
|
||||
Standout: clean layout, no sign-in, works offline, dark mode.
|
||||
Sync: iCloud.
|
||||
Signals: generic entrant, low differentiation; illustrates how crowded the "simple native kanban" MAS shelf is.
|
||||
|
||||
### Truly Simple Kanban
|
||||
One-line: minimalist single-board-free kanban targeted at makers/students.
|
||||
Platform: macOS + iPhone, native.
|
||||
App Store: [Mac + iOS (universal listing)](https://apps.apple.com/us/app/truly-simple-kanban/id6746863668)
|
||||
Data model: proprietary.
|
||||
Pricing: free for one board; $4.99 one-time lifetime IAP for unlimited boards.
|
||||
Standout: deliberately narrow scope, no subscriptions/hidden fees.
|
||||
Signals: another data point that $0–5 one-time is the going rate for "simple kanban" on MAS.
|
||||
|
||||
### TidyCards
|
||||
One-line: older, once-well-regarded native Mac kanban app now showing its age.
|
||||
Platform: macOS, native.
|
||||
App Store: [Mac](https://apps.apple.com/us/app/tidycards-awesome-kanban/id1285199566?mt=12)
|
||||
Data model: proprietary; supports drag-and-drop file/calendar/email attachments into cards.
|
||||
Pricing: paid app (legacy MAS pricing).
|
||||
Standout (historically): considered by some reviewers "the best Mac native, dedicated kanban app" for its native-feel simplicity.
|
||||
Complaints: reports of the app hanging/freezing after being open a while, requiring force-quit; no updates in ~2 years per App Store listing; developer only sporadically responsive.
|
||||
Signals: a cautionary tale — a well-loved native indie kanban app that stalled once the solo dev's attention moved on, and users noticed and complained loudly about staleness/bugs. Relevant to Lanework as evidence that in this niche, users will tolerate few features but not bugs/abandonment.
|
||||
|
||||
### WipQ – Kanban Projects
|
||||
One-line: kanban for solo professionals/small teams with an emphasis on WIP limits and full native macOS document model integration.
|
||||
Platform: macOS + iOS (macOS 11+/iOS 13+), native, uses Apple's document architecture (versioning, tabs, full screen, etc.).
|
||||
App Store: [Mac](https://apps.apple.com/us/app/wipq-kanban-projects/id1235518457?mt=12)
|
||||
Data model: proprietary, but **data stored locally on the Mac or in iCloud Drive**, explicitly "not a third party web service."
|
||||
Pricing: paid MAS app.
|
||||
Standout: customizable WIP limits, inter-card dependencies, card locking, favorites/priorities, file attachments, multiple card-display themes.
|
||||
Signals: one of the more feature-rich native entrants (closer to "real" kanban/WIP discipline than most indie boards), but data model is still app-owned files-in-iCloud-Drive rather than user-editable markdown.
|
||||
|
||||
### Propel
|
||||
One-line: open-source, zero-dependency native SwiftUI kanban app for personal task management, tuned for content-creator workflows (blog posts, talks, videos, podcasts).
|
||||
Platform: macOS 15+, native SwiftUI/Swift 6, no Xcode project (SPM only).
|
||||
Data model: **human-readable JSON** in `~/Library/Application Support/Propel/`, atomic writes with backup, 1s-debounced autosave — file-based but not markdown, and not a user-chosen folder (it's tucked in Application Support rather than a project folder).
|
||||
Pricing: free, MIT-licensed, open source.
|
||||
Standout: global hotkey capture, 3 boards with ⌘1/2/3 switching, weekly review summaries, auto-archive of week-old completed cards, menu bar stats.
|
||||
Signals: 11 GitHub stars/2 forks — small hobby project, but demonstrates the same instinct (native SwiftUI + plain files) an indie developer would reach for; useful as a build-pattern reference more than a market threat.
|
||||
|
||||
### FileBoard: Kanban for Files
|
||||
One-line: turns any real folder on disk into a kanban board where **columns are subfolders and cards are the actual files in them** — not markdown cards, but literally your files.
|
||||
Platform: macOS only, released Dec 2025 (very new, v1.1 as of late Dec 2025).
|
||||
App Store: [Mac](https://apps.apple.com/us/app/fileboard-kanban-for-files/id6745226062?mt=12)
|
||||
Data model: **the filesystem itself is the board** — no separate database, no card content of its own; dragging a card between columns physically moves the file between subfolders.
|
||||
Pricing: free to download, "FileBoard Lifetime" IAP at $0.99.
|
||||
Standout: real-time two-way sync with Finder (no duplication), file preview pane, folder tree browsing, keyboard-first navigation.
|
||||
Signals: brand new, not enough MAS reviews yet to gauge reception, but conceptually the single closest cousin to Lanework found in this research — same "folder structure IS the board" idea, just applied to arbitrary files/folders rather than a markdown-card-per-task model with frontmatter/metadata. Worth watching as it matures; currently much thinner (no card metadata, tags, dates, etc.) than what Lanework offers.
|
||||
|
||||
### Brisqi
|
||||
One-line: cross-platform "offline-first personal kanban" desktop+mobile app.
|
||||
Platform: Windows/macOS/Ubuntu desktop + mobile, appears Electron-based.
|
||||
Data model: local device storage, CSV export, no user-facing markdown/files during normal use.
|
||||
Pricing: one-time purchase (amount not listed on landing page), pitched explicitly against subscription fatigue.
|
||||
Standout: markdown-formatted card descriptions, monthly calendar view, "List Focus Mode," card linking, custom backgrounds, bulk paste-to-create.
|
||||
Sync: none — local only, manual backup.
|
||||
Signals: same buyer profile as Kanbanero/Sprout (privacy, offline, one-time price) but cross-platform Electron rather than native Mac.
|
||||
|
||||
## 2. Freeform / notebook apps with kanban as a feature
|
||||
|
||||
### Curio (Zengobi)
|
||||
One-line: the Mac's long-running "advanced notebook" app — freeform idea-space canvases that include Kanban "Stacks" as one of many card/board tools alongside mind maps, outlines, and tables.
|
||||
Platform: macOS, native, on the Mac App Store since long before most kanban-specific apps existed.
|
||||
App Store: [Mac](https://apps.apple.com/us/app/curio-notes-ideas-mind-map/id1475550603?mt=12)
|
||||
Data model: proprietary Curio project files stored locally on the Mac (offline-capable), not markdown.
|
||||
Pricing: dual model — Mac App Store subscription (Standard $4.99/mo or $49.99/yr; Professional $6.99/mo or $69.99/yr) **or** a one-time license key purchased directly from Zengobi (current version + 1 year of updates, then owned outright). This "subscribe via MAS or buy a perpetual key direct" dual-track pricing is a notable, still-rare pattern worth flagging.
|
||||
Standout: kanban is a minor feature inside a much larger freeform PKM/mind-mapping tool; not a kanban-first product.
|
||||
Signals: long-lived (Zengobi has sold Curio for close to two decades), loyal niche audience of "notebook" power users; not really competing for the "I just want a simple board" buyer.
|
||||
|
||||
### Walling
|
||||
One-line: card-based whiteboard/PKM app that combines a spatial "wall" view with a dedicated Kanban view over the same cards ("bricks").
|
||||
Platform: web app (cross-platform via browser), not native Mac.
|
||||
Data model: cloud/proprietary — data stored on Walling's servers, encrypted in transit and at rest; no local-file option.
|
||||
Pricing: free up to 100 bricks; Premium ~$5–8/month (or $59.99/yr annual); Team plans from $8/user/month.
|
||||
Standout: dual visual (freeform whiteboard) + kanban views of the same card set, OCR on images, templates.
|
||||
Signals: this is the opposite end of the spectrum from Lanework — cloud-hosted, subscription, no local-file story — useful mainly as a contrast case (what "modern whiteboard SaaS" pricing/positioning looks like).
|
||||
|
||||
### Craft
|
||||
One-line: polished all-in-one docs/notes app (Notion-adjacent) with a Kanban *view* over any Collection, not a dedicated kanban product.
|
||||
Platform: native-feeling apps on Mac/iOS/Windows/web, but backed by Craft's own cloud sync.
|
||||
App Store: [Mac + iOS (universal listing)](https://apps.apple.com/us/app/craft-notes-documents-ai/id1487937127)
|
||||
Data model: proprietary Craft documents/blocks; Kanban view auto-generates a Status field (To do/In progress/Done) grouping cards by a field value — not files on disk.
|
||||
Pricing: Free tier (1,500 blocks, 1GB storage, 15 AI credits/mo, 7-day history); Plus ~$8/mo (~$4.80/mo promo annual); Family $15/mo; Team $50/mo.
|
||||
Standout: kanban is one of several interchangeable views (table, board, gallery) over structured "Collections"; strong design polish.
|
||||
Signals: represents the "beautiful all-in-one workspace with a kanban view bolted on" category — direct evidence that kanban-as-a-feature inside a bigger subscription product is a well-trodden path Lanework is deliberately not taking.
|
||||
|
||||
## 3. File-based / markdown-native local kanban apps (closest philosophical peers)
|
||||
|
||||
This cluster is the most important for Lanework: every one of these stores board state as plain files on disk rather than in a database, which is Lanework's core bet.
|
||||
|
||||
### Signboard
|
||||
One-line: local-first desktop kanban app built explicitly on the "file over app" philosophy — **lists are folders, cards are Markdown files**, moving a card between lists literally moves the file between folders.
|
||||
Platform: macOS/Windows/Linux, **Electron** (not native) — Node.js/TypeScript codebase, universal binary on Mac.
|
||||
Data model: cards = individual Markdown files with frontmatter for metadata (dates, labels, links); lists = directories; boards can be nested directly inside an Obsidian vault (e.g. `Vault/Project/Signboard/<Board Name>/`).
|
||||
Pricing: MIT-licensed source; free for personal use, requested $49 one-time "sponsorship" for commercial/work use (honor system), optional tips.
|
||||
Standout features: multiple views (Kanban drag-and-drop, dense Table view, Planner with Calendar/Week/Day/Agenda), Smart Actions powered by *local* LLMs, an MCP server for AI-agent integration, a CLI for scripting/automation, checklists with progress counters, start/due dates with notifications, Obsidian vault interop.
|
||||
Sync: none built-in — relies on the folder being placed in iCloud Drive/Dropbox/Obsidian Sync/git, same as Lanework's approach.
|
||||
Traction: ~83 GitHub stars, 8 forks, actively developed (devlog, v1.6.0 recently shipped with performance work), built by Colin Devroe (a known indie/blogging-world figure), launched publicly in fall 2025.
|
||||
Deep-dive addendum (2026-08-01): launched Sept 16, 2025 deliberately unfinished ("very early and basic," no app icon) to invite community input; reached 1.6.0 by July 2026 — 1.4 added the Planner workspace (Calendar/This Week/Day/Agenda), 1.5 deepened Obsidian integration (properties, Bases generation, deep links, companion plugin), 1.6 added Smart Actions (local Ollama), start dates, and Table-view bulk actions. Stated principles: open source, performance, *clean markdown with minimal frontmatter*, no heavy frameworks (plain HTML/CSS/JS in Electron), minimal dependencies, zero web requests. Imports from Trello exports, Obsidian markdown boards, and Tasks.md workspaces — it is deliberately positioning as the consolidation point for the whole file-based-board niche. Multiple boards in tabs; labels with colors; card- and task-level due dates; Quick Add; archive/restore; notifications and a local calendar feed; MIT-licensed with honor-system $49 commercial payment plus tip jar. AI/MCP was not part of the original launch pitch (the Sept 2025 launch post doesn't mention agents at all) — it was added along the way, so its agent story is a bolt-on, not the founding thesis. Third-party coverage so far is thin (casual "looks interesting" blog mentions, no substantive reviews found), consistent with the ~83-star count: philosophy-aligned but small.
|
||||
Schema (from docs/using-signboard.md + MIT source, 2026-08-01): board = folder; list = subfolder with a numeric ordering prefix in the folder name (reorder renames directories); card = single `.md` file named `[order-prefix]-[title]-[random-id].md` (retitle/reorder renames the file); frontmatter is deliberately flat and Obsidian-property-friendly — `title`, `signboard_id`, `signboard_board`, `signboard_list`, `status`, `signboard_uri`, `related`, `linked_objects` — note `signboard_board`/`signboard_list` denormalize location into the file, duplicating what the path already says; checklist-item dates are inline body syntax `(start:|due:|scheduled: YYYY-MM-DD)`; `board-settings.md` at root; archive = `XXX-Archive` folder. No schema version key, no stated round-trip/preservation guarantees, no formal spec document — the format is defined by prose docs plus the MIT code. Key structural contrasts with Lanework: identity lives in mutable filenames (vs immutable UUID folder names), ordering lives in name prefixes causing rename cascades (vs gapped fractional ranks rewriting one file), location is duplicated into frontmatter where hand/agent moves can leave it stale (vs level-is-position with zero redundancy), and cards are single files with reference-style linked objects (vs folder-per-card with real `attachments/`). Full analysis: [07-schema-comparison-signboard.md](07-schema-comparison-signboard.md).
|
||||
**This is the single most directly comparable competitor found in this research.** Same file-over-app philosophy, same "folder=list, file=card" model, same explicit agent/MCP-friendliness pitch — but Electron rather than native macOS, and a paid-commercial-use/free-personal-use model rather than Lanework's presumed pricing. A native, faster, more Mac-idiomatic Lanework is a legitimate differentiation story against Signboard specifically.
|
||||
|
||||
### Tasks.md
|
||||
One-line: the most established member of this cluster — a **self-hosted web app** where lanes are directories and tasks are Markdown files, no database at all.
|
||||
Platform: self-hosted via single Docker image (Railway/Zeabur one-click deploys exist); frontend SolidJS, backend Koa/Node; accessed via browser, installable as a PWA.
|
||||
Data model: filesystem is the database — one directory per lane, one `.md` file per task; subdirectories can be opened as separate "projects."
|
||||
Pricing: free, MIT-licensed, open source.
|
||||
Standout: theme support (Adwaita/Nord/Catppuccin) that follows OS light/dark, reverse-proxy subpath support, deliberately narrow feature scope "for long-term sustainability" per the maintainer.
|
||||
Traction: **2.2k GitHub stars, 105 forks** — by far the most-starred file-based kanban tool found in this survey, suggesting real demand for exactly this "markdown files as kanban" model, just currently served by a self-hosted web tool rather than a native Mac app.
|
||||
Signals: proves the underlying idea (folder=column, file=card, no DB) has substantial developer-community appetite; a native Mac app doing the same thing with better UX is a clear opportunity, which is exactly Lanework's bet.
|
||||
|
||||
### Kanban MD (kanbanmd.lecaro.me)
|
||||
One-line: tiny desktop app that treats a handful of local text files as a kanban board — free, fast, offline, currently Linux-only.
|
||||
Data model: plain text files, no cloud.
|
||||
Signals: another indie solo-dev experiment validating the "text files as board" idea; Linux-only today means no direct macOS overlap yet, but shows the pattern recurring independently across multiple developers (Tasks.md, Signboard, Kanban MD, Kanbanero, banban, KanbanFiles, FileBoard all converged on similar ideas independently in roughly the same 2024-2026 window).
|
||||
|
||||
### KanbanFiles
|
||||
One-line: native Windows desktop app that turns folders and markdown files into a two-way-synced kanban board (cards = markdown files as columns' contents).
|
||||
Platform: Windows only (per search results) — not currently a Mac threat, but conceptually identical territory.
|
||||
|
||||
### kanban.md / Kanban Markdown (VS Code extensions)
|
||||
One-line: editor extensions ("VS Code meets Kanban") that render a markdown file's nested lists as a draggable board directly inside the code editor.
|
||||
Signals: shows the pattern extending into "kanban as an editor feature" rather than a standalone app — relevant to Lanework's "text editors are first-class users of a board" thesis, since these tools assume the *editor*, not a bespoke app, is where you'll often view the board.
|
||||
|
||||
### MarkdownTaskManager (ioniks)
|
||||
One-line: small open-source local-first Kanban task manager that turns markdown files into an interactive board, no database or server.
|
||||
Signals: yet another indie project independently reinventing the same "markdown files → kanban" pattern — further evidence of a real, recurring itch developers keep scratching for themselves.
|
||||
|
||||
### banban (two unrelated projects, same name)
|
||||
One-line: (1) HubertK05/banban — productivity app inspired by GitHub Projects' kanban; (2) m0g/banban — self-hosted kanban board tool. Both small open-source projects, not directly Mac-native, but both part of the same "roll your own lightweight kanban" wave.
|
||||
|
||||
### imdone
|
||||
One-line: the oldest/most mature entry in this space — turns `TODO`/`FIXME` code comments *and* markdown task files into a kanban board, tightly integrated with your editor and codebase.
|
||||
Platform: Imdone Desktop app, plus VS Code and Obsidian integrations; imdone-core is an open-source "text based kanban processor" npm package.
|
||||
Data model: **local-first**, markdown + code-comment-based; a CLI can pull Jira/GitHub issues into the repo as markdown files which then render as cards on the board.
|
||||
Pricing: Imdone Desktop, ~$14.99 (a 2020s TechRepublic piece flagged its price drop to this level).
|
||||
Standout: bridges the gap between "task tracker" and "code," making TODO comments in source files first-class kanban cards — a different but adjacent take on "the filesystem/repo is the board."
|
||||
Signals: imdone has existed since well before the current file-based-kanban wave (it's the "OG" of this niche) and is still maintained; worth understanding as the elder statesman of the category, more code-centric than Lanework's general-purpose board.
|
||||
|
||||
## 4. Open-source / self-hosted kanban (broader OSS category, mostly team/web-first)
|
||||
|
||||
### Kanri
|
||||
One-line: fully offline, cross-platform (Windows/macOS/Linux) Tauri+Nuxt kanban app, 100% free and open source.
|
||||
Data model: **entire board state in one local JSON file** — no server, no accounts.
|
||||
Pricing: free/OSS.
|
||||
Standout: unlimited boards/columns/cards, zero-latency offline, "if you want no one else looking at your data, this is the way" (paraphrased user sentiment).
|
||||
Complaints: no attachments, no card-to-card links (per a reviewer).
|
||||
Signals: HN launch thread existed (id 36745421) showing the "offline-first personal kanban" pitch resonates on HN, though direct thread content wasn't retrievable here; broadly the JSON-file/Tauri sibling of Kanbanero, but cross-platform and free rather than Mac-only and paid.
|
||||
|
||||
### Focalboard
|
||||
One-line: OSS Trello/Notion/Asana alternative from Mattermost, offered both as a team server and as a **standalone single-user "Personal Desktop" app** for Mac/Windows/Linux.
|
||||
Data model: own database (not markdown files) even in the personal desktop edition.
|
||||
Pricing: free/OSS; Mattermost Boards cloud/server editions exist for teams.
|
||||
Signals: mainly a team-collaboration/self-hosted-SaaS play; the personal desktop edition is a lesser-known side door that competes loosely with indie personal-kanban apps, but without the file-based data model. Its Mac App Store listing (id1556908618) appears delisted as of 2026-08-01 — Mattermost's docs still describe a MAS edition, but the listing 404s and store search doesn't surface it — so the desktop edition is effectively direct-download/build-only now.
|
||||
|
||||
### Planka
|
||||
One-line: OSS, Trello-look-alike self-hosted kanban (React/Node/Postgres), known for visual polish and snappy performance.
|
||||
Data model: own Postgres DB, not files.
|
||||
Licensing: **not** OSI-approved OSS — a custom "Fair Use License" that bars operating Planka as a hosted service for third parties and cross-company account sharing without a paid Pro tier.
|
||||
Signals: primarily a self-hosted team tool; Docker-deployed (8M+ pulls) — relevant as market-size evidence for "people want to self-host their own Trello," but not a personal-file-based competitor.
|
||||
|
||||
### Wekan
|
||||
One-line: long-running, MIT-licensed, Meteor/MongoDB OSS kanban, translated into ~50 languages, notable for a rules/automation engine.
|
||||
Data model: MongoDB, not files.
|
||||
Signals: mature (multi-year) OSS project, team/self-host oriented, not a Lanework analog but a market-size/longevity data point for "kanban that isn't Trello."
|
||||
|
||||
### Vikunja
|
||||
One-line: OSS (AGPLv3), self-hosted task manager (Go+Vue) offering lists, kanban boards, Gantt charts, and tables, with import from Todoist/Trello/MS To-Do.
|
||||
Data model: own DB; bootstrapped EU company also offers a hosted "Vikunja Cloud."
|
||||
Signals: broader task-manager-with-a-kanban-view rather than kanban-first; shows the self-hosted-SaaS-alternative segment is viable as an actual (bootstrapped, non-VC) business, which is encouraging context for indie/solo economics generally.
|
||||
|
||||
## 5. PKM / outliner apps with markdown + task/board features
|
||||
|
||||
### Obsidian Kanban plugin (mgmeyers, now community-maintained)
|
||||
One-line: the dominant way Obsidian users get kanban — markdown-backed drag-and-drop boards stored as a single markdown file per board, lists as headings, cards as list items.
|
||||
Data model: plain markdown, lives in the vault, fully git/editor-compatible.
|
||||
Pricing: free plugin; Obsidian itself is free for personal use ($50/yr commercial, $8-10/mo Sync/Publish add-ons).
|
||||
Notable forks/variants: **Plain Text Kanban** plugin renders nested markdown lists as a board while keeping the underlying file dead simple/readable in any editor (no special block syntax); **obsidian-mkanban** goes further, splitting each column/card into its own file in a folder structure — i.e. independently reinventing something close to Lanework's own model, inside Obsidian.
|
||||
Context: Obsidian shipped a native "Bases" feature (database-like views over notes) in 2025, and a first-party Kanban view for Bases is reportedly coming — which could commoditize the community plugin's core use case over time.
|
||||
Signals: this is arguably the largest existing user base of "markdown file-backed kanban" today (Obsidian has millions of users, Kanban is a top-tier community plugin), and it's the best evidence that a large audience already wants exactly Lanework's data model — Lanework's differentiation is being a dedicated, native, non-PKM app rather than a feature bolted onto a notes tool.
|
||||
|
||||
### Logseq
|
||||
One-line: open-source, local-first, block-based outliner/PKM (markdown or org-mode files) with kanban available only via community plugins/queries, not a first-class primitive.
|
||||
Data model: plain markdown/org files on disk, fully local-first, no proprietary format.
|
||||
Standout: a long-running (multi-year, 100+ reply) feature-request thread "Introduce Kanban boards as a new primitive" shows real, sustained user demand for native kanban that the core team hasn't prioritized — plugins (logseq-kanban-plugin, logseq-plugin-agenda's kanban view) fill the gap by treating parent blocks as columns and child blocks/queries as cards.
|
||||
Signals: another large local-first/markdown-native user base whose kanban needs are underserved by the core product — a potential adjacent-audience signal for Lanework (Logseq users who want real kanban and don't want to fight plugins for it).
|
||||
|
||||
### NotePlan
|
||||
One-line: markdown notes + calendar + tasks in one app, with each day as a markdown file; not kanban-first but heavily plain-text-native.
|
||||
Platform: macOS/iPad/iPhone, native-ish (details not fully confirmed), iCloud sync.
|
||||
App Store: [Mac + iOS (universal listing)](https://apps.apple.com/us/app/noteplan-to-do-list-notes/id1505432629)
|
||||
Data model: markdown notes/tasks, calendar-integrated, timeblocking.
|
||||
Pricing: subscription-based (via Setapp and direct), free trial.
|
||||
Signals: shows the "daily markdown note + tasks" niche is healthy and Mac-native-first; not a kanban competitor per se but a neighboring plain-text productivity app with a loyal following (MacStories/MacSparky coverage).
|
||||
|
||||
### Agenda
|
||||
One-line: date-focused notes app (notes meets calendar) for Mac/iPad/iPhone, not kanban but a well-known example of Mac-indie pricing innovation.
|
||||
App Store: [Mac](https://apps.apple.com/us/app/agenda-notes-meets-calendar/id1287445660?mt=12) / [iOS](https://apps.apple.com/us/app/agenda-notes-meets-calendar/id1370289240)
|
||||
Pricing model: notably generous — **free forever core app**, premium features unlocked via one-time-feeling IAP ($34.99/yr covers Mac+iOS, or $14.99/yr iOS-only) that stays unlocked permanently even if you stop paying (only *future* premium features added after your paid year require renewal). This "pay once, keep what you unlocked forever" hybrid is a well-regarded pricing pattern in the Mac indie world worth Lanework considering.
|
||||
Data model: proprietary, not markdown.
|
||||
|
||||
### TaskPaper
|
||||
One-line: the classic plain-text to-do list app for Mac — projects/tasks/notes/@tags encoded in a deliberately simple, human-readable plain-text syntax.
|
||||
Platform: macOS, native, Mac App Store, by Hog Bay Software (Jesse Grosjean).
|
||||
App Store: [Mac](https://apps.apple.com/us/app/taskpaper-plain-text-to-dos/id1090940630?mt=12)
|
||||
Data model: plain `.taskpaper` text files, explicitly designed to be "future proof," editable in any text editor, with a documented format other developers have built compatible tools around.
|
||||
Pricing: $24.99 one-time on the Mac App Store.
|
||||
Signals: TaskPaper is the longest-running proof that "plain text is the file format, and a dedicated Mac app is the good way to interact with it" is a viable, sustainable indie Mac business (TaskPaper 3 dates to 2016, format traces to 2006) — a strong precedent for Lanework's own bet, applied to task lists rather than boards.
|
||||
|
||||
### Zavala
|
||||
One-line: free, open-source, native outliner for Mac/iPad/iPhone.
|
||||
App Store: [Mac + iOS (universal listing)](https://apps.apple.com/us/app/zavala/id1546457750)
|
||||
Data model: proprietary outline format internally, but with OPML and Markdown *export*; iCloud sync/sharing.
|
||||
Pricing: completely free, no ads, no IAP — funded as a personal/open-source project by developer Maurice Parker.
|
||||
Signals: shows a native Mac indie tool can be given away entirely free and still be well-regarded (multiple positive reviews, MacPowerUsers community coverage) — an important pricing-strategy data point, though a very different economic model (not the developer's primary income) than what an indie kanban app like Lanework likely needs.
|
||||
|
||||
## 6. Plain-text / CLI task ecosystems
|
||||
|
||||
### todo.txt
|
||||
One-line: the original minimalist plain-text task format/standard (`(A) Buy milk +groceries @errands`), with a large multi-platform app ecosystem built around it.
|
||||
Data model: literally just a `.txt` file with a line-per-task convention; the "format" is the product, not any single app.
|
||||
Ecosystem: mobile apps (Android/iOS) syncing via Dropbox/Google Drive, desktop GUIs (e.g. Sleek), VS Code extensions for syntax highlighting, and a reference CLI with archiving/filtering.
|
||||
Signals: the longest-running proof that a dead-simple, fully open text convention can sustain a durable multi-app ecosystem for well over a decade — the strongest "format over app" precedent Lanework can point to, albeit for flat task lists rather than boards.
|
||||
|
||||
### Taskwarrior
|
||||
One-line: powerful CLI task manager for developers/power users, with urgency scoring, tags, filtering, and recurring tasks.
|
||||
Data model: **Taskwarrior 2.x stored plain `.data` files; Taskwarrior 3.x switched to a SQLite database** (`taskchampion.sqlite3`) — an instructive precedent of a plain-text-first tool *moving away* from plain text toward a database as it matured, presumably for performance/sync-conflict reasons. Worth noting as a counter-data-point: file-based purity can have real technical costs at scale that even beloved plain-text tools eventually pay down.
|
||||
Signals: still has an active, vocal power-user community (HN, multiple 2025-era how-to articles) valuing CLI speed, scriptability, and (formerly) plain text; a useful cautionary tale about the limits of pure flat-file storage as feature/dataset size grows.
|
||||
|
||||
## 7. AI-agent-native task/kanban trackers (fast-emerging 2025-2026 category)
|
||||
|
||||
This category didn't really exist before AI coding agents did, and it's now moving fast — directly validating Lanework's "AI agents are first-class users of a board" bet, though these tools are aimed at *coding-agent task queues* specifically rather than general personal/team kanban.
|
||||
|
||||
- **backlog.md** — MIT-licensed CLI+web tool that turns any git repo into a self-contained project board: every task is a plain `.md` file in the repo, with acceptance criteria, milestones, and dependencies; status is tracked via git history; works with Claude Code, Gemini CLI, Codex, and any MCP-compatible agent; has both an instant terminal kanban view and a web UI. Closest agent-facing analog to Lanework's own repo-embedded, git-diffable philosophy.
|
||||
- **claude-task-master / TaskMaster AI** — ingests a PRD and generates a dependency-aware task hierarchy for AI agents to work through; wired into Cursor/Windsurf/MCP hosts; markdown-adjacent but oriented around task IDs/dependencies more than a visual board.
|
||||
- **TaskForge** — task manager built on markdown files living inside an Obsidian vault, explicitly designed to be "editable by Claude or any agent."
|
||||
- **CodeAgentSwarm** — a literal kanban board (Pending/In Progress/In Testing/Completed) where Claude Code agents themselves read and move their own cards and write completion summaries.
|
||||
- **Nimbalyst** — a Claude Code session kanban board where each running agent session is a card moving through backlog → planning → implementing → validating → complete; positions itself as the broadest "auto-tracks every session" option.
|
||||
- **Cursor's Agent Kanban (SDK)** — a drag-and-drop board shipped as part of Cursor's TypeScript SDK where dropping a card into a column causes an agent to write code in a cloud VM and open a PR.
|
||||
- Windsurf shipped a similar kanban-style view of local/cloud agent sessions in May 2026.
|
||||
|
||||
Pattern: across this whole sub-category, "kanban board" has become the default UI metaphor for supervising AI agents' work-in-progress, and markdown files are the default substrate for describing that work — which is strong external validation that Lanework's core thesis (files + boards + agents as first-class users) is not a niche eccentricity but a live, fast-growing design pattern in exactly this moment. The gap: every one of these tools is scoped to *coding-agent task queues inside a repo*, not general personal/creative/life kanban — Lanework's broader "any kind of board, any kind of file" scope is currently unserved by this cluster.
|
||||
|
||||
## Patterns
|
||||
|
||||
**Pricing norms in this niche.** One-time purchase in the $0–25 range dominates solo/personal-use native Mac kanban apps (Kanbanero $8.99, Truly Simple Kanban $4.99, TaskPaper $24.99, FileBoard $0.99 lifetime, Kanbanier ~$15); free-with-optional-tip/lifetime is common among newer indie entrants (Sprout, Kanri, Zavala); subscriptions appear mainly once an app broadens beyond "just a board" into a full workspace/PKM platform (Craft $8-15/mo, Walling $5-8/mo, Curio $5-7/mo *or* a one-time key). Users in this niche (TidBITS forum thread, App-Store-review sentiment, HN commentary) explicitly and repeatedly express subscription fatigue and a preference for paying once for a tool that "just works" locally — this is a receptive market for Lanework's likely pricing instincts, not a hostile one.
|
||||
|
||||
**What indie/native productivity-app buyers in this niche value, in rough order of how often it recurs across research:** (1) local-first / offline-capable / no-account-required, stated almost universally as a selling point rather than a footnote; (2) data ownership — increasingly phrased explicitly as "my data survives the app" (the "file over app" framing popularized by Obsidian's Steph Ango in 2023 has become a widely-cited north star across this whole space, not just inside Obsidian); (3) speed/native feel — repeated complaints about Electron sluggishness and repeated praise for "feels like a real Mac app"; (4) keyboard-first workflows (Kanbanero, TaskPaper, Zavala, Propel all lead with shortcuts); (5) restraint/simplicity as a stated differentiator against "everything apps" like Notion/ClickUp/Monday — nearly every newer entrant (Sprout, Truly Simple Kanban, Kanri) positions itself explicitly against feature bloat; (6) design polish still matters even in a minimalist tool (Kanbanero's animated shader backgrounds, Planka's Trello-grade visual fidelity) — "simple" doesn't mean "ugly is fine."
|
||||
|
||||
**Convergent evolution toward "folder = column, file = card."** Independently, and apparently without much cross-awareness, at least six different developers/teams arrived at essentially the same data model Lanework uses — Signboard, Tasks.md, Kanban MD, Kanbanero (JSON variant), banban, and FileBoard all map board structure onto filesystem structure, mostly within a roughly 2024-2026 window. Tasks.md's 2.2k GitHub stars is the clearest signal that real demand exists for this pattern; the fact that no single native, polished, well-funded macOS app has yet claimed this territory (Signboard is Electron; Kanbanero uses JSON not markdown and has no card-body/frontmatter richness; FileBoard is brand-new and thin; Tasks.md requires self-hosting a Docker container) is the whitespace Lanework is aimed at.
|
||||
|
||||
**PKM apps are the biggest existing audience for markdown-backed kanban, but treat it as a secondary feature.** Obsidian's Kanban plugin, Logseq's long-requested-but-still-plugin-only kanban, and Curio's "Stacks" all serve real, large user bases who already want exactly this data model, but in every case kanban is bolted onto a broader notes/PKM tool rather than being the product. A dedicated, kanban-first, markdown-native native Mac app is conspicuously not what any of these audiences currently have.
|
||||
|
||||
**AI-agent-friendliness has gone from novelty to expected-by-default in months, not years.** As of this research (Aug 2026), a whole cluster of tools (backlog.md, TaskMaster AI, TaskForge, CodeAgentSwarm, Nimbalyst, Cursor's and Windsurf's built-in agent-kanban views) treat "an AI agent can read/write this board" as a baseline requirement, and markdown-files-in-a-repo is their overwhelming default substrate. This validates Lanework's positioning but also means the window to be "the app that got there first" for a general-purpose (not just coding-agent-queue) board is closing — competitors could plausibly add agent/MCP support to existing kanban apps (Signboard already has one) faster than Lanework can build out breadth.
|
||||
|
||||
**Where the file-based/plain-text movement stands, 2025-2026.** It's no longer a fringe hobbyist position — "file over app" is now a widely-cited framing (helped enormously by Obsidian's scale and Steph Ango's essay), local-first software has its own annual conference (Local-First Conf, Berlin, July 2026, ~350 attendees) and a maturing technical toolkit (Automerge 3.0, CRDT-based sync engines, SQLite-as-universal-app-database patterns), and the practical proof points are stacking up: todo.txt's decade-plus multi-app ecosystem, TaskPaper's 15+-year survival as a paid product, Obsidian's mainstream success, and now Tasks.md's 2.2k-star validation of markdown-as-kanban specifically. At the same time, there are real technical costs to staying pure-file — Taskwarrior's own move from flat files to SQLite in its 3.x line is a pointed reminder that plain-text storage can hit real limits (query performance, conflict resolution, large datasets) that even a beloved plain-text-native tool eventually has to solve by adding structure back in. Lanework's "filesystem is source of truth, with git/editors/agents as first-class users" position sits close to the leading edge of where this movement currently is, particularly in combining it with native macOS polish (most of the current file-based kanban tools are Electron, self-hosted-web, or CLI-first) and with the newest wave of agent-facing demand.
|
||||
@@ -0,0 +1,214 @@
|
||||
# Personal Todo / Task-Management Apps
|
||||
|
||||
This document covers the personal todo/task-management market adjacent to kanban: Todoist, Things 3, TickTick, OmniFocus, Microsoft To Do, Apple Reminders, Any.do, Structured, Sunsama, Akiflow, Motion, Amie, Superlist, Twos, Godspeed, and Lunatask, plus cross-cutting patterns on subscription fatigue, the Apple Reminders squeeze, and todo/kanban convergence.
|
||||
|
||||
Researched: 2026-08-01
|
||||
|
||||
## Todoist
|
||||
|
||||
Positioning: the default, cross-platform "does everything reasonably well" task manager for individuals and small teams; broadest platform reach in the category.
|
||||
|
||||
Pricing: freemium subscription (Beginner free tier; Pro $5/mo annual or $7/mo monthly; Business $8/user/mo annual or $10/mo monthly). Prices rose in December 2025 (Pro $4→$5, Business $6→$8 annual), and regional pricing was pulled for many international users, effectively doubling their cost overnight — a real source of anger in reviews.
|
||||
|
||||
Standout features / direction: added a native kanban view ("Todoist Boards") alongside lists; has layered in AI features; remains the most feature-complete free-to-paid ladder in the category.
|
||||
|
||||
Traction: bootstrapped (Doist Inc.), no outside investment, ~$11.2M revenue in 2025 on a claimed 30–50M user base (figures vary by source, 300K paying customers cited in 2024); ~93–102 employees. This is a durable, profitable indie-scale business, not a rocket-growth one.
|
||||
|
||||
Common complaints: pricing creep and the regional-pricing removal; cost scales steeply for teams; some users feel plan limits (free tier) are too tight to be useful.
|
||||
|
||||
## Things 3 (Cultured Code)
|
||||
|
||||
Positioning: the design-forward, Apple-only GTD app for people who want a beautiful, opinionated, single-owner tool and are willing to pay once instead of forever.
|
||||
|
||||
Pricing: one-time purchase per platform — $49.99 Mac, $19.99 iPad, $9.99 iPhone/Watch (~$80 for the full set); Things Cloud sync included free, no subscription anywhere. This model is a genuine differentiator and a point of loyalty in an increasingly subscription-saturated category.
|
||||
|
||||
Standout features / direction: in 2025 Cultured Code rewrote the Things Cloud backend in Swift (showcased by Apple at WWDC 2025 State of the Union); shipped OS 26 support (Liquid Glass redesign, Control Center integration, Spotlight quick-add on Mac, visionOS support). Development is steady but slow and incremental — no calendar view, no time blocking, no AI.
|
||||
|
||||
Traction / sentiment: reviews remain very favorable; the brand halo (Apple's own praise) is strong. The flip side is a recurring complaint that development pace is glacial next to subscription competitors with continuous funding — "beautifully designed but frozen in scope."
|
||||
|
||||
Common complaints: no AI (smart scheduling, task extraction, pattern analysis) at all in 2026, which is now a competitive gap as "every productivity app has AI assistants"; no kanban/board view natively (a third-party app, KanbanView, fills the gap); Apple-only, no Android/Windows.
|
||||
|
||||
Kanban: no native board view; one-dimensional lists only.
|
||||
|
||||
## TickTick
|
||||
|
||||
Positioning: the value-for-money all-rounder — Todoist-equivalent feature set (calendar sync, habit tracking, Pomodoro, kanban) at a fraction of the price, cross-platform including Android/Windows where Things and OmniFocus aren't.
|
||||
|
||||
Pricing: single Premium tier at $35.99/year (~$3/mo) or $3.99/mo — dramatically cheaper than most of this list; free tier is capped (9 lists, 99 tasks/list) but usable.
|
||||
|
||||
Standout features / direction: native kanban board view (rare in this list — only Todoist and TickTick have it natively); habit tracking, Pomodoro timer, 2-way calendar sync, custom filters all gated to Premium. No team/family plan — deliberately personal-only.
|
||||
|
||||
Traction: unfunded/bootstrapped (Santa Clara, founded 2010 by Zhimin Chen); estimated ~$5M company revenue, Android Play Store revenue estimated ~$1.8M/year; ranks in the 70s-100s on US App Store free/productivity charts — solidly mid-tier, durable, not viral.
|
||||
|
||||
Common complaints: fewer surfaced in research than for pricier competitors, consistent with its low price largely defusing the value objection; free tier is capped enough to push conversions.
|
||||
|
||||
Kanban: yes, native board view.
|
||||
|
||||
## OmniFocus (The Omni Group)
|
||||
|
||||
Positioning: the power-user GTD engine for people who want deep customization (perspectives, AppleScript, complex repeat/defer logic) and don't mind a learning curve; Apple-only.
|
||||
|
||||
Pricing: fragmented and expensive — Mac Standard $49.99 / Pro $99.99 one-time, iOS subscription $9.99/mo or $99.99/yr, web $4.99/mo. Effectively the most expensive app in this list to own across platforms.
|
||||
|
||||
Standout features: custom perspectives, AppleScript/Shortcuts automation, tagging and deep filtering — the most powerful rules engine in the category.
|
||||
|
||||
Common complaints: price is called "high" or "prohibitive" repeatedly, especially for solo/small users; steep learning curve; occasional sync issues; no collaboration features; Apple-only lock-in is explicitly cited as disqualifying for mixed-platform households ("expensive, complex, and Apple-locked — if that doesn't fit your life, you'll hate it").
|
||||
|
||||
Kanban: no native board view found.
|
||||
|
||||
## Microsoft To Do
|
||||
|
||||
Positioning: the free, bundled-with-Microsoft-365 option for people already living in Outlook/Teams; the spiritual (if diminished) successor to Wunderlist.
|
||||
|
||||
Pricing: free.
|
||||
|
||||
Direction / status: update cadence is uneven across platforms (Windows/iOS updated as recently as March 2026, Android's last update was over 11 months stale at time of research), consistent with a broader pattern of Microsoft consumer apps drifting toward "neglected relic" status as the company's real investment goes into Copilot/AI/enterprise/cloud. No sign of active feature investment or a stated roadmap; reads as maintenance-mode, not a growth product.
|
||||
|
||||
Historical note: it is literally the app Microsoft built to replace and then sunset Wunderlist (2015 acquisition → 2020 shutdown), a cautionary tale for what happens when a beloved indie todo app is absorbed and slow-walked to death (see Patterns below).
|
||||
|
||||
## Apple Reminders
|
||||
|
||||
Positioning: the free, built-in default that keeps getting better and is the single biggest headwind every paid competitor on this list has to answer.
|
||||
|
||||
Pricing: free, bundled with every Apple device.
|
||||
|
||||
Recent direction: iOS 26 shipped a real redesign (Liquid Glass), faster task entry, time-zone support (Calendar-style, useful for travelers), and — critically — Apple Intelligence features: automatic categorization of lists into grouped sections, and AI-suggested to-dos pulled from emails/notes. iOS 26.2 (Dec 2025) added alarm-style urgent reminders with snooze/slide-to-stop. This is a steady multi-year climb from "barely a checklist app" to "credible everyday task manager with light AI."
|
||||
|
||||
Assessment: for single-ecosystem Apple households, Reminders now covers the majority of what casual users need — Siri capture, native sync, decent organization — at zero cost. It remains meaningfully behind on cross-platform support (no real Android/Windows story), advanced recurrence, and power features, which is exactly the seam third-party apps still live in.
|
||||
|
||||
## Any.do
|
||||
|
||||
Positioning: sits between a lightweight personal task manager and a broader family/small-team planning platform — tasks, reminders, calendar, shared spaces, and (per its own 2026 marketing) workflow/kanban boards in one app.
|
||||
|
||||
Pricing: freemium; free tier plus Premium and Teams paid tiers (exact current price not confirmed in research, but occasional promo-driven annual discounting is called out).
|
||||
|
||||
Traction: ~25M+ users claimed; funding is old and modest ($9M total, last round 2016 seed) — this is not a growth-funded story, more a long-tail bootstrapped-since-funding operator. Revenue figures found in research were inconsistent/unreliable (one stale data point of ~$40K ARR looks wrong for a 25M-user app and should not be trusted).
|
||||
|
||||
Common complaints: Premium is seen by some as not worth it since competitors give the same features free; calendar view gets crowded/hard to read with many same-day tasks; feature overload for people who want something simple; not team-oriented enough for larger groups despite the "Teams" positioning.
|
||||
|
||||
Kanban: markets "workflow boards" / kanban-style views as of 2026, alongside its own blog content pitching kanban as a category it competes in.
|
||||
|
||||
## Structured
|
||||
|
||||
Positioning: visual, timeline-based daily planner — less "task database," more "see your whole day as blocks." iPhone/iPad-first (also Mac, Android, Watch).
|
||||
|
||||
Pricing: subscription, roughly $19.99–27.99/year (sources vary) or a lifetime option around $64.99; free tier lets you try the timeline UI.
|
||||
|
||||
Standout feature: the visual timeline itself is the product — the differentiator is the daily-planning UX, not task-database depth.
|
||||
|
||||
Traction / complaints: limited hard data found; positioned and reviewed as a well-liked, focused single-purpose planner rather than a broad task-management system.
|
||||
|
||||
## Sunsama
|
||||
|
||||
Positioning: premium daily-planning ritual tool for professionals who believe the *act* of intentional planning has value — pulls tasks in from other tools (Slack, email, Trello, Todoist, etc.) rather than replacing them, then has you build a realistic daily plan.
|
||||
|
||||
Pricing: raised prices in 2026 for the first time in five years — Pro now $20/mo annual or $25/mo monthly (up from $16/$20). Wirecutter named it "best scheduling app" in 2025.
|
||||
|
||||
Standout features: time tracking, focus mode, deep integrations for pulling tasks from other systems into one daily view; explicitly not an automatic scheduler — the user does the planning work each day.
|
||||
|
||||
Common complaints: mobile apps are widely called "read-only" or "companion apps" — real planning only happens on desktop; smart/automation features are thin relative to price; because it requires daily active planning, a lapsed user gets zero value while still paying — a structural churn risk called out directly by reviewers.
|
||||
|
||||
Kanban: not native; it's a daily-planning layer on top of other tools' task lists, not a board.
|
||||
|
||||
## Akiflow
|
||||
|
||||
Positioning: time-blocking command-center that aggregates tasks/calendars from many sources into one keyboard-driven, drag-to-schedule interface.
|
||||
|
||||
Pricing: no free plan, trial only — $34/mo monthly, $17/mo billed yearly, or a "Believer 730" plan at $14.90/mo billed every two years. Among the more aggressively tiered/expensive apps in this list.
|
||||
|
||||
Sentiment: mixed-to-concerning. Praise for consolidating everything into one view and a clean UX; but a "growing number of users" reporting billing problems, buggy mobile apps, and integrations that don't work as advertised. No evidence found of a shutdown or acquisition — it's still shipping updates as of April 2026 — but the billing/reliability complaints are a decline signal worth tracking.
|
||||
|
||||
Kanban: not found as a native feature; it's calendar/time-block-centric, not board-centric.
|
||||
|
||||
## Motion
|
||||
|
||||
Positioning: started as an AI auto-scheduler for individuals, has since pivoted hard toward B2B — marketing itself in 2025–2026 as an "agentic work suite" / "AI Employees" platform for small businesses rather than a personal todo app. Worth noting this pivot explicitly: it is drifting out of the personal-task category into agentic-workflow/AI-labor territory.
|
||||
|
||||
Pricing: complex and has gotten less transparent — AI Workplace plan from $29/user/mo annual; separate "AI Employees" tiers from $49 (Starter) up to $599 (Plus) for multi-seat bundles.
|
||||
|
||||
Traction: well-funded and growing fast — $75M total raised, $550M valuation (2025), revenue estimates range from $10M to $50M ARR depending on source, 10,000+ paying customers, 3x YoY growth in the AI-Employees line. This is the one app in the list with real venture-scale momentum.
|
||||
|
||||
Common complaints: difficult onboarding, cluttered UI, weak/frustrating mobile app (G2 desktop 4.5/5 vs mobile 2.7/5), pricing that has risen more than once, and reports of trial-to-annual billing surprises and refund friction.
|
||||
|
||||
Read for Lanework: Motion is instructive as a "where the AI-scheduling money is going" signal — it's leaving pure personal-task-management for agentic B2B, which somewhat validates that solo/individual task apps are not where the biggest funding rounds chase growth right now.
|
||||
|
||||
## Amie
|
||||
|
||||
Positioning: was an "opinionated," design-forward calendar + todo app; as of July 2024 it announced a pivot away from calendar/todo toward being an AI meeting notetaker, with a full UI rebuild completed by February 2025. Calendar/todo functionality still exists but is explicitly no longer the priority.
|
||||
|
||||
Pricing: moved from free to a subscription-only model (~€6/year cited by early users) with no free plan and no monthly option, which upset its early adopter base.
|
||||
|
||||
Funding: raised ~$7–8M (Spark Capital-led seed, 2022), small team (~14 people); no evidence of a shutdown, but the pivot away from its original todo/calendar identity is itself a decline signal for anyone evaluating it as a task-management tool specifically.
|
||||
|
||||
Read for Lanework: a cautionary example of a well-funded, well-designed calendar/todo app that couldn't find a sustainable business in the category itself and pivoted to a different product entirely (AI notetaking) rather than iterate task management further.
|
||||
|
||||
## Superlist
|
||||
|
||||
Positioning: the spiritual successor to Wunderlist, built by several of the original Wunderlist co-founders (led by Christian Reber) after Microsoft's shutdown of that app — explicit "we're rebuilding what you loved" positioning.
|
||||
|
||||
Pricing: reworked pricing with a genuinely free-forever Basic tier (unlimited private/shared lists, sublists, integrations) and Pro at $8/user/mo annual — deliberately undercutting Notion Team ($16) and beating Todoist Business on value.
|
||||
|
||||
Standout features / direction: added AI Meeting Notes in May 2025 (records Zoom/Meet/Teams/Slack calls, auto-generates actionable tasks) — the clearest "AI eating adjacent categories" move among the pure-personal-todo apps.
|
||||
|
||||
Traction: privately funded, Berlin-based; no acquisition found in research despite searching specifically. Marketed heavily to former-Wunderlist-diaspora as "the best Wunderlist alternative in 2026."
|
||||
|
||||
Kanban: a kanban view is a requested/roadmap feature per its own public feedback board (Frill), not confirmed shipped — i.e., users are actively asking for it, which is itself a signal of demand.
|
||||
|
||||
## Twos
|
||||
|
||||
Positioning: fast, flexible, gamified note-plus-task capture app aimed at brain-dump/quick-capture use cases — popular specifically among ADHD and bullet-journal-style users.
|
||||
|
||||
Pricing: notably not a recurring subscription — free tier is fully-featured with no data/note/task caps, and paid unlocks are one-time $2 purchases (plus an in-app currency/coin system for earning free unlocks). This is a real outlier pricing model in a subscription-saturated category.
|
||||
|
||||
Standout features: fast cross-device sync, tagging, rollover of undone items, light gamification, sharing.
|
||||
|
||||
Common complaints: modest learning curve up front; requests for better UI polish, widgets, shortcuts, habit tracking, and attachments.
|
||||
|
||||
Kanban: not found as a feature; it's a linear/list capture tool, not board-based.
|
||||
|
||||
## Godspeed
|
||||
|
||||
Positioning: a keyboard-first, "fastest to-do app" for power users who prefer typing to clicking — every interaction targets sub-50ms response, includes a "Hardcore Mode" that disables the mouse entirely. Mac + iOS.
|
||||
|
||||
Pricing: $6/mo — called out explicitly as "at the top of the task manager market" and a real barrier next to free alternatives (Todoist free tier, Microsoft To Do).
|
||||
|
||||
Reception: generally positive (8.0/10-class scores), praised for labels/attachments/notes/snoozing; some instability reported on iOS.
|
||||
|
||||
Kanban: not found as a feature; single-list, speed-first tool.
|
||||
|
||||
## Lunatask
|
||||
|
||||
Positioning: privacy-first, end-to-end-encrypted "better to-do list" that bundles notes, journaling, habit/mood tracking, and a relationship manager — pitched heavily at ADHD users and people who distrust cloud task apps with their data.
|
||||
|
||||
Pricing: $6/mo (annual) or $8/mo (monthly) for Premium; a lifetime license is available direct from the website for $220. Free tier exists, no credit card required to start.
|
||||
|
||||
Standout features: end-to-end encryption, no in-app analytics/tracking, no data sale — a genuine privacy differentiator most competitors don't offer. Lets users switch freely between multiple workflow paradigms on the same task list: list, kanban board (vertically-stacked sections rather than horizontal columns, but conceptually the same), and Eisenhower Matrix — without losing data switching between them.
|
||||
|
||||
Kanban: yes, native, and notably flexible (switch between kanban/matrix/list without restructuring data) — one of the few apps in this list that treats board view as a first-class, freely-interchangeable perspective rather than a bolted-on extra.
|
||||
|
||||
## Kanban-view summary
|
||||
|
||||
Native kanban/board view confirmed: Todoist (Boards), TickTick, Any.do (workflow boards), Lunatask (kanban workflow, vertical-stack style).
|
||||
Requested but not confirmed shipped: Superlist (on public roadmap/feedback board).
|
||||
No native board view: Things 3 (third-party workaround exists — KanbanView), OmniFocus, Sunsama, Akiflow, Godspeed, Twos, Structured, Microsoft To Do, Apple Reminders.
|
||||
Motion and Amie are calendar/AI-scheduling-centric and don't fit the board paradigm at all.
|
||||
|
||||
## Patterns
|
||||
|
||||
**Subscription fatigue is real and rising, and this category is not exempt.** Active cancellation rates among US consumers jumped from 31% (2024) to 47% (2026); the fastest-growing fatigue category in 2026 is AI-feature subscriptions specifically, with the average person paying for four AI tools at ~$66/month and 53% saying they now treat subscriptions as churn-and-restart rather than long-term commitments. Weekly-subscription revenue share nearly doubled in two years (43%→56%), meaning even paid apps are being pressured toward more escapable, lower-commitment pricing. Every subscription todo app in this list (Todoist, TickTick, Sunsama, Akiflow, Motion, Godspeed, Lunatask) is competing against this headwind; the two structural outliers — Things 3 (one-time purchase) and Twos ($2 one-time unlocks) — are explicitly positioned against subscription fatigue and get credit for it in reviews. A one-time-purchase or low-commitment model reads as a genuine trust signal right now, not just a pricing choice.
|
||||
|
||||
**Apple Reminders is the market's quiet ceiling, not just a "free alternative."** It went from a bare checklist app to a genuinely competent task manager with Apple Intelligence categorization, AI-suggested to-dos pulled from mail/notes, and a real design pass (Liquid Glass) — all free, all pre-installed, all deeply Siri-integrated. For any single-ecosystem Apple household with light-to-moderate task needs, Reminders now covers "enough." The seam every paid competitor lives in is: cross-platform households (no real Android/Windows story for Reminders), power features (recurrence, filtering, automation), and specialized workflows (GTD rigor, time-blocking, kanban). This means positioning against Reminders on "basic todo list" grounds is now close to a losing argument — differentiation has to be structural, not featural.
|
||||
|
||||
**Todo and kanban are converging, but slowly and mostly at the UI-view layer, not the data-model layer.** Todoist and TickTick both ship kanban as an alternate view over the same flat task list; Any.do markets "workflow boards"; Lunatask goes furthest by making board/list/matrix freely interchangeable views over one underlying task set; Superlist's own users are asking for it on the public roadmap. What's notably absent across all of them: none treat the board as the *native* data model the way a dedicated kanban tool would — it's always "todo app that also has a board view," never "board app that also has a todo view." That's the open lane. Nobody in the personal-task category has built kanban-as-first-class-primitive with file-backed, git-friendly, agent-legible data — which is closer to Lanework's own territory (see doc 03) than to this list.
|
||||
|
||||
**Subscription vs. one-time is a real fork in user trust, and price alone doesn't explain reactions — the *removal of value* does.** Todoist's backlash wasn't really about the absolute price increase, it was regional pricing being pulled and effectively doubling cost overnight for non-US users; Sunsama's backlash risk isn't the $20–25/mo, it's that a lapsed week of not planning means paying for nothing; Akiflow's complaints cluster on billing surprises, not the sticker price. Users tolerate high prices for tools they actively use every day (Motion at $29+/user/mo has a fanbase); they revolt when the pricing model itself feels like it's taking something away or when it charges for idle non-use.
|
||||
|
||||
**Apple-only, cross-platform, and "no platform at all" (encrypted/local) are three distinct trust postures competing for the same user.** Things 3 and OmniFocus bet on deep Apple integration and accept the ceiling that puts on their addressable market; Todoist/TickTick/Any.do bet on maximum reach; Lunatask bets on privacy/encryption as the differentiator entirely separate from platform. None of the three postures is "winning" outright — they're serving genuinely different anxieties (design/quality vs. reach vs. data trust).
|
||||
|
||||
**AI is now table stakes for the subscription tier of this category, but its absence is not fatal if the rest of the product is trusted.** Every subscription-model competitor (Todoist, TickTick's roadmap direction, Any.do, Sunsama's integrations, Akiflow, Motion, Amie, Superlist's meeting notes) is adding AI — categorization, suggested tasks, auto-scheduling, meeting-to-task extraction. Things 3 is the explicit counterexample: reviewers call out "no AI" as a real gap in 2026, yet the app remains well-reviewed and trusted because the core promise (fast, reliable, beautifully simple, no subscription) hasn't been diluted chasing feature parity. The lesson for a well-differentiated tool: AI absence is a tolerated trade-off, not an automatic disqualifier, as long as the core value prop stays sharp.
|
||||
|
||||
**Funding flows toward agentic/B2B, not toward better personal todo lists.** Motion is the one app here with real venture money ($75M raised, $550M valuation) and it's spending that trajectory pivoting toward "AI Employees" for small businesses, not toward a better personal task manager. Amie, also venture-funded, pivoted away from calendar/todo into AI meeting notes. The two most durable pure personal-task apps in this list (Todoist, TickTick) are both bootstrapped, profitable, unfunded-by-choice-or-necessity businesses. This suggests venture capital doesn't see standalone personal task management as a category with room for outsized returns anymore — it sees the money in agentic B2B or adjacent categories (meeting notes, scheduling-as-a-service) that can upsell into task management rather than starting there.
|
||||
|
||||
**The historical cautionary tale every player in this space knows: Wunderlist.** Peaked at ~13M users and ~1B to-dos/day, was acquired by Microsoft in 2015, then was starved of updates and finally shut down in 2020 in favor of Microsoft To Do — described by users at the time as "migration hell that destroyed the fan-base." Superlist exists specifically to re-capture that diaspora, and Microsoft To Do itself now shows the same early-stage neglect signals (stale platform updates, no clear roadmap, strategic focus elsewhere) that preceded Wunderlist's decline. The pattern — beloved indie tool acquired by a platform giant, then slow-walked to death or absorbed into a bigger, blander umbrella product — is the standing risk case for any small todo app that considers an acquisition exit, and a reason users are wary of trusting their task data to venture-funded upstarts long-term.
|
||||
|
||||
**What personal-task users say they want heading into 2026, synthesized across reviews:** speed of capture above almost everything else (Twos, Godspeed, and Apple's own "faster add" work in Reminders all compete on this axis specifically); trustworthy AI that discloses what model powers it and lets them opt out of training use, not just AI-for-AI's-sake; genuine offline-first reliability after several cloud-only years burned people in low-connectivity moments; and — per multiple 2026 app reviews — a swing back toward "focused tools that do fewer things exceptionally well" after a decade of feature-bloat, which favors sharply-scoped products (Things 3, Twos, Godspeed) over kitchen-sink ones, even as those kitchen-sink apps (Any.do, TickTick, Superlist) keep adding surface area to compete on breadth.
|
||||
@@ -0,0 +1,103 @@
|
||||
# Cross-Cutting Trends and Success Factors, 2024-2026
|
||||
|
||||
This document is a broad first pass on market-wide forces shaping task-management, kanban, and productivity software — market size and where the money is, the AI wave and what stuck, the local-first/data-ownership movement, pricing-model shifts, distribution channels, notable shutdowns and consolidation, and how "tools for thought" apps are eating into task management. It is cross-cutting by design; it does not attempt deep competitor profiles (see 02-04) or a deep dive on AI agents consuming task state (see 06-agents-and-tasks.md).
|
||||
|
||||
Researched: 2026-08-01
|
||||
|
||||
## Market size and where the money is
|
||||
|
||||
Market-research firms disagree on absolute numbers but agree on the shape: a multi-billion-dollar market growing at roughly 14-16% CAGR. Grand View Research puts task-management software at $3.94B in 2025 heading to $12.34B by 2033 (15.6% CAGR); another estimate has it at $5.1B in 2025 to $5.87B in 2026 (15.2% CAGR); a third puts 2025 at $5.71B heading to $19.84B by 2034 (14.84% CAGR). ([Grand View Research](https://www.grandviewresearch.com/industry-analysis/task-management-software-market-report), [Business Research Insights](https://www.businessresearchinsights.com/market-reports/task-management-software-market-119895))
|
||||
|
||||
Cloud-based deployment accounts for over 65% of the market, and North America holds over 36% of revenue share. Growth drivers cited across reports are consistent: remote/hybrid work, real-time collaboration demand, and — increasingly — AI/automation integration as a named growth driver in its own right, not just a feature checkbox. ([Grand View Research](https://www.grandviewresearch.com/industry-analysis/task-management-software-market-report))
|
||||
|
||||
Where the money concentrates is visible in the disclosed revenue of the category leaders, and it is overwhelmingly team/enterprise-seat revenue, not individual subscriptions: Notion reports ~$600M ARR in 2025 (up from $300M in 2024) at an $11B valuation with 100M+ users, reportedly grown with $0 in meaningful paid advertising; ClickUp reports ~$300M ARR (2025/2026) at a $4B valuation, publicly targeting $1B ARR, with 400% YoY AI-sales growth and 800% YoY AI-usage growth cited in its own materials. ([Latka — Notion](https://getlatka.com/companies/notion), [SaaStr](https://www.saastr.com/notion-and-growing-into-your-10b-valuation-a-masterclass-in-patience), [Latka — ClickUp](https://getlatka.com/companies/clickup))
|
||||
|
||||
By contrast, individual-focused indie tools top out one to two orders of magnitude smaller: Sunsama, a well-regarded premium daily planner, reports ~$1.5M ARR (2024) on a ~9-person team, having raised only $2.75M total and reaching profitability off that base in 2022. ([Latka — Sunsama](https://getlatka.com/companies/sunsama)) Obsidian is the outlier that proves the local-first/individual model can still produce real money: ~1.5M monthly active users (22% YoY growth as of Feb 2026), ~$25M ARR, $350M valuation, built by an 18-person team with zero VC funding. ([Fueler](https://fueler.io/blog/obsidian-usage-revenue-valuation-growth-statistics), [ARR Club](https://www.arr.club/obsidian/obsidian-arr-hit-25m-and-350m-valuation-with-just-9-persons))
|
||||
|
||||
Pricing-tier data reinforces the same pattern from the buyer side: most per-seat task tools cluster in an "Economy" $10-19/seat/month tier, "Professional" $19-77.50, and "Enterprise" $77.50+ — i.e., the addressable revenue per team scales with headcount, which is exactly why enterprise/team products (Notion, ClickUp, Monday, Asana) dwarf individual tools in ARR even when individual tools have devoted userbases. **Implication for Lanework**: the big money is in team seats, but that market is saturated and AI-feature-arms-raced; the individual/small-team, ownership-oriented segment is smaller in aggregate ARR but has at least one proof point (Obsidian) that a lean, non-VC team can build a durable, sizable business there without competing on the enterprise axis at all.
|
||||
|
||||
## The AI wave: what stuck vs what's gimmick
|
||||
|
||||
Three distinct AI feature categories are landing differently with users:
|
||||
|
||||
**Auto-scheduling AI (Motion, Clockwise, Reclaim)** — genuinely useful for a narrow persona (solo founders/execs with calendar chaos) but has proven commercially fragile at the company level, not just the feature level. Motion ($29-49/mo individual, $99/3 seats) is well-reviewed for "actually doing things, not just suggesting them" and is explicitly positioned for busy founders/freelancers, not general task management. ([Efficient App](https://efficient.app/apps/motion)) Clockwise, despite serving 40,000 organizations including Uber, Netflix, and Atlassian, was shut down entirely on March 27, 2026 when its team was acquihired into Salesforce Agentforce — all user data deleted, ~1 week's notice given, users routed to Reclaim.ai as the closest replacement. This is a cautionary tale about auto-scheduling specifically: it's a feature that large platforms want to absorb into an "agentic calendar" story rather than a standalone business that survives independently. ([Reclaim](https://reclaim.ai/blog/clockwise-shutdown-news), [usecarly.com](https://www.usecarly.com/blog/clockwise-shut-down/))
|
||||
|
||||
**Natural-language capture (Todoist Ramble, Task Assist)** — this is the AI feature category with the clearest "stuck" signal. Todoist's Ramble voice-capture feature (launched Jan 2026 after an Oct-Dec 2025 beta) improved end-to-end task-creation success from 40% to 62% over its beta and handles 40 languages; independent testing of Todoist's NLP found it correctly parsed 185/200 free-text task descriptions without user correction. Users describe it as "more capable than basic dictation... because it understands context." ([Skywork](https://skywork.ai/skypage/en/todoist-ai-assistant-alternatives/2035949431685529600)) This is the AI feature type most directly relevant to a kanban tool like Lanework — low-friction capture that reduces the "opening the app" tax — and the evidence is that users adopt it readily when it works, unlike auto-scheduling which requires trusting AI with judgment calls.
|
||||
|
||||
**Summarization / subtask generation / AI chat (Notion AI, ClickUp AI)** — high usage-metric growth (ClickUp cites 45% AI-adoption growth in 2024 and 800% YoY AI-usage growth) but murkier signal on whether it's driving retention or just inflating engagement dashboards; reviews describe it as useful for teams already embedded in the platform ("a natural extension of workflow") rather than a reason to switch platforms. Sentiment comparisons show Notion and ClickUp at parity on ease-of-use (75% positive) with no clear AI-driven differentiation reported by third-party review aggregators. ([Capterra comparison](https://www.capterra.com/compare/158833-186596/ClickUp-vs-Notion))
|
||||
|
||||
**Agentic AI ("AI agents managing tasks")** is the emerging 2026 frontier, not yet a proven-stuck feature for consumer task apps. Gartner projects 40% of enterprise apps will ship task-specific AI agents by end of 2026, up from under 5% in 2025, and 52% of gen-AI-using enterprises already have agents in production somewhere. ([Gartner](https://www.gartner.com/en/newsroom/press-releases/2025-08-26-gartner-predicts-40-percent-of-enterprise-apps-will-feature-task-specific-ai-agents-by-2026-up-from-less-than-5-percent-in-2025)) This is an enterprise-software statistic, not a personal-productivity-app statistic — it signals where big platforms (Salesforce/Agentforce absorbing Clockwise) are pointed, but there's no comparable adoption evidence yet for individual/small-team kanban tools. The more concrete, bottom-up version of "AI agents + tasks" is happening in developer tooling (see below and 06-agents-and-tasks.md), not in mainstream productivity apps.
|
||||
|
||||
**Net read**: capture/parsing AI has stuck because it removes friction without requiring trust; summarization AI is used but not obviously a retention driver; full delegation/auto-scheduling AI is high-value for a narrow persona but commercially unstable as a standalone product category (both Clockwise and, per the Height case below, ambitious "autonomous project management" pivots have failed to sustain independent businesses).
|
||||
|
||||
## Local-first / privacy / data-ownership
|
||||
|
||||
The Ink & Switch "local-first software" essay (2019) remains the movement's foundational reference; it now has real conference infrastructure behind it — Local-First Conf launched May 2024 in Berlin with speakers from Linear and Anytype, plus a LoFi Berlin 2025 follow-on event, indicating the ideas have moved from essay to community/ecosystem. ([Ink & Switch](https://www.inkandswitch.com/essay/local-first/))
|
||||
|
||||
Obsidian is the strongest evidence the philosophy converts to a real business: 1.5M+ MAU (22% YoY growth), ~$25M ARR, $350M valuation, 18 people, zero VC funding, low opex specifically because local-first architecture means no server/storage cost scaling with users. 110,000+ Discord members and 2,000+ community plugins signal an unusually durable, high-engagement community for a note-taking tool. ([Fueler](https://fueler.io/blog/obsidian-usage-revenue-valuation-growth-statistics))
|
||||
|
||||
Demand-side evidence: an analysis of 9,300+ Reddit "I wish there was an app that..." posts found 640+ posts (7% of all requests) specifically asking for local-first, self-hosted, or fully-offline tools — framed by users as wanting "control, reliability, and avoiding subscription fatigue" more than privacy per se, and wanting to "own outright" rather than rent. Notably, that analysis found no specific mentions of kanban or markdown-format requests within the local-first bucket — the demand signal is broad ("modern versions of classic desktop apps without mandatory cloud") rather than kanban-specific, which is a mild caution against over-reading a ready-made audience for Lanework's exact format. ([digitalbiztalk.com](https://digitalbiztalk.com/article/what-9300-reddit-posts-reveal-about-app-gaps-in-2026))
|
||||
|
||||
Open-source/local-first "tools for thought" competitors for mindshare in this space include Anytype (IPFS-based P2P sync, end-to-end encrypted, $13.5-29M raised, 43 employees) and AFFiNE (open-core, $6.75-7.99/mo cloud tier, $10/seat team tier, free self-host capped at 3 users). Both are VC-funded open-core plays rather than bootstrapped like Obsidian — a different local-first business model worth noting: open-source-with-paid-cloud-sync as the monetization wedge. ([fahimai.com](https://www.fahimai.com/anytype), [AFFiNE blog](https://affine.pro/blog/affine-vs-appflowy-vs-anytype))
|
||||
|
||||
Failure/near-failure case: Muse ("tool for thought" for iPad/Mac, local-first sync) hit unsustainable unit economics in mid-to-late 2023 — most of the team left, one developer continued, and the product was later relaunched/rebranded as Allume in 2024 with collaboration features added. The lesson generally drawn (including in the project's own HN retrospective) is that local-first sync engineering is expensive and hard to monetize thinly — being local-first doesn't exempt a product from needing a viable business model. ([HN: Muse Retrospective](https://news.ycombinator.com/item?id=40359893), [localfirst.fm interview](https://www.localfirst.fm/20/transcript))
|
||||
|
||||
## Pricing-model trends
|
||||
|
||||
Subscription fatigue is a named, widely-discussed 2025 consumer trend, and one-time-purchase is reported as "returning even when [it isn't] the cheapest option," valued by users for control/predictability and by indie developers for reduced platform dependence. ([influencers-time.com](https://www.influencers-time.com/subscription-fatigue-in-2025-why-one-time-buys-dominate/))
|
||||
|
||||
Things 3 remains the reference case for the one-time-purchase model in the exact macOS-native indie category Lanework sits in: $49.99 Mac / $9.99 iPhone / $19.99 iPad / $29.99 Vision Pro, no subscription tier at all, multiple Apple Design Awards, 4.8/5 across 27,750+ App Store ratings as of July 2026. The one recurring criticism is that per-platform pricing feels fragmented versus a single bundle — but reviewers note users still prefer that fragmentation to a subscription. ([ellieplanner.com](https://ellieplanner.com/productivity-copilot/things-3-pricing), [richardriviere.com](https://richardriviere.com/things-3-pricing))
|
||||
|
||||
At the other end, per-seat SaaS pricing is under visible strain in the team-tool segment: standard per-seat rates ($10-15/user/month across Monday/Asana/ClickUp/Teamwork) scale painfully with headcount (a 20-person team pays $220-300/mo), and per-seat costs are cited as a structural adoption blocker in enterprises needing broad cross-team visibility. This is driving a flat-rate counter-trend (e.g., Basecamp's flat $349/mo, which beats per-seat pricing once a team crosses ~75 people) and hybrid models (seat-plus-usage) for tools 3+ years in market. ([thickethq.com](https://www.thickethq.com/blog/flat-rate-project-management), Celoxis pricing guide)
|
||||
|
||||
Premium individual-tier daily planners (Sunsama $17-22/mo, Akiflow $14.90-34/mo) show the subscription model still works at the high end of individual productivity tooling when the product sells a habit/ritual, not just software — Sunsama's pitch is explicitly the "done for the day" daily-review ritual as the retained value, not feature count. ([lifestack.ai](https://lifestack.ai/blog/sunsama-planner-pricing), [thebusinessdive.com](https://thebusinessdive.com/akiflow-vs-sunsama))
|
||||
|
||||
Setapp remains a live secondary distribution/monetization channel for indie Mac developers: Setapp Membership takes ~10% and pools 20% of subscription revenue to partner developers by usage; standalone single-app distribution through Setapp takes ~25% (still lower than typical app-store cuts). Setapp's own 2025 developer survey found only 20% of surveyed Mac developers distribute exclusively via the Mac App Store — most indie Mac devs now run multi-channel distribution. ([Computerworld / Setapp survey](https://www.computerworld.com/article/3621224/setapp-survey-reveals-what-mac-developers-are-thinking-about-right-now.html), [setapp.com/developers](https://setapp.com/developers))
|
||||
|
||||
## Distribution and growth
|
||||
|
||||
Concrete, sourced detail on exactly which channels move the needle for productivity apps specifically was thin in this pass (this is a good candidate for deeper, narrower research later — e.g. pulling specific Product Hunt leaderboard entries and r/macapps threads directly rather than via aggregator commentary). What is corroborated:
|
||||
|
||||
- Product Hunt remains an active launch venue for productivity/AI tools specifically, but generic "best practices" content (Tuesday/Wednesday ~3am PST launches, hunter partnerships) dominates the available sources over concrete named 2025-2026 productivity-app launch case studies. ([Product Hunt 2026 categories](https://www.producthunt.com/categories/productivity))
|
||||
- r/macapps is confirmed as an active, relevant community for Mac utility discovery, with the standard indie-marketing advice being to participate/contribute before pitching.
|
||||
- Notion's growth to $600M ARR / 100M+ users is repeatedly cited as achieved with "$0 in meaningful paid advertising" — i.e., organic/content/community-led growth at the very largest scale in this market, which is directionally consistent with (though not proof of) productivity tools being unusually word-of-mouth/creator-driven relative to other SaaS categories. ([ehroo.com case study](https://ehroo.com/case-studies/notion-organic-growth-case-study))
|
||||
- Sunsama's growth strategy is documented concretely: a 600+-member "owned influencer/ambassador community" built over four years, credited with contributing a significant share of annual revenue, plus organic screenshot-sharing of its "done for the day" completion screen as an unprompted word-of-mouth loop. This is a specific, replicable-sounding playbook for a premium individual productivity tool. ([getsaral.com](https://www.getsaral.com/customer-stories/sunsama))
|
||||
- YouTube productivity creators (Ali Abdaal, 5.5M+ subscribers; Thomas Frank) function as de facto top-of-funnel for Notion and Todoist specifically — both creators build content and paid courses around these tools, and both are cited as recommending Notion for structured work and Todoist for task tracking. This channel appears to matter more for note-taking/PKM tools (Notion, Obsidian) than for kanban specifically. ([Medium roundup](https://medium.com/@kaivalshah/what-ive-learned-from-productivity-youtubers-ali-abdaal-thomas-frank-and-matt-d-avella-8afe3a929bdb))
|
||||
|
||||
**Gap flagged for a follow-up pass**: none of the sources found gave a concrete, named recent (2025-2026) HN/Product Hunt launch case study for a kanban or file-based task app with real numbers (upvotes, signups, revenue) — worth a targeted narrow-pass search later, e.g. searching HN/PH directly rather than through SEO aggregator commentary.
|
||||
|
||||
## Consolidation and failures, 2024-2026
|
||||
|
||||
| Product | What happened | When | Why (as reported) |
|
||||
|---|---|---|---|
|
||||
| Clockwise | Shut down entirely; team acquihired into Salesforce Agentforce; all user data deleted | Announced ~mid-March 2026, dead March 27, 2026 | Platform (Salesforce) wanted the autonomous-scheduling team/IP for its own agentic product, not the standalone business |
|
||||
| Height | Full project-management app shut down | Announced March 28, 2025; final day Sept 24, 2025 | $18.3M raised (incl. $14M Series A, 2021), 7 years old; couldn't out-compete Linear despite "stunning design" and a late pivot toward autonomous PM; generic shutdown messaging drew criticism for lack of transparency |
|
||||
| Rise Calendar | Shut down | Users told to export by March 31, 2025 | Company closure after 4+ years |
|
||||
| Mayday (calendar) | Shut down after acquisition | All services ended May 5, 2024 | Acquired, then terminated rather than integrated |
|
||||
| Amie | Not shut down, but pivoted away from its calendar/task core toward AI meeting notes as the headline feature | Through 2025 | Calendar/task side effectively deprioritized in favor of the AI notetaking bet |
|
||||
| Muse | Near-failure, not full shutdown: team shrank drastically, later relaunched/rebranded as Allume | Mid-late 2023 unsustainability; Allume relaunch late 2024 | Local-first sync product with unit economics that couldn't sustain the original team size |
|
||||
|
||||
Sources: ([Reclaim on Clockwise](https://reclaim.ai/blog/clockwise-shutdown-news), [usecarly.com](https://www.usecarly.com/blog/clockwise-shut-down/), [Creativerly on Height](https://www.creativerly.com/height-app-is-shutting-down/), [AlternativeTo on Rise](https://alternativeto.net/news/2025/1/rise-calendar-is-shutting-down-users-are-urged-to-export-their-data-by-march-31-2025), [AlternativeTo on Mayday](https://alternativeto.net/news/2024/4/mayday-calendar-app-announces-acquisition-and-upcoming-termination-of-all-services), [skywork.ai on Amie](https://skywork.ai/blog/amie-review-2025-calendar-tasks-ai-meeting-notes/), [HN Muse Retrospective](https://news.ycombinator.com/item?id=40359893))
|
||||
|
||||
What did *not* consolidate or fail, contrary to a plausible assumption going in: Superlist (the Wunderlist successor) is still operating and expanding — it merged with Fragment Software in June 2025 rather than shutting down, and Trello (Atlassian, acquired 2017 for $425M) remains an active 50M+-user product with no signs of sunset. ([PitchBook on Superlist](https://pitchbook.com/profiles/company/436263-04), [sqmagazine on Trello](https://sqmagazine.co.uk/trello-statistics/))
|
||||
|
||||
**Pattern across the failures**: none of the notable 2024-2026 shutdowns were bootstrapped/indie products — Height ($18.3M raised), Clockwise (well-funded, acquihired), Rise, and Mayday were all VC-funded companies that either ran out of runway trying to out-feature a category leader (Height vs. Linear) or got absorbed into a bigger platform's agentic-AI roadmap (Clockwise into Salesforce). This is a mild positive signal for a small, low-burn indie approach: the failures cluster in "raised money, needed hypergrowth or an acquirer, didn't get either" — a dynamic a self-funded native Mac app with no VC runway clock doesn't face in the same way.
|
||||
|
||||
## "Tools for thought" eating task management
|
||||
|
||||
Notion, Tana, and Capacities represent a real convergence trend where PKM/notes tools are absorbing task management as one more "block type" or "object" rather than leaving it to dedicated apps. Tana specifically markets itself as ending "context switching between tools" by combining free-flowing notes, structured data, and — per its own positioning — working "especially well for tasks, projects, research, and meeting-heavy workflows," using an AI-native outliner/knowledge-graph model. Capacities takes a similar "everything is a connected object" approach as a Notion alternative. ([Ness Labs on Tana](https://nesslabs.com/tana-review), [xda-developers](https://www.xda-developers.com/i-found-a-notion-obsidian-and-capacities-killer-and-im-absolutely-thrilled/))
|
||||
|
||||
For a dedicated kanban/task tool like Lanework, this is a real competitive pressure at the low end (a Notion or Tana user may simply never feel the need for a separate task app, since the notes tool already "does tasks fine") but it is also a differentiation opportunity: these all-in-one tools are, without exception, cloud-native, app-mediated, and not filesystem-transparent — a Tana or Notion task doesn't exist as a file you can open in a text editor, diff in git, or hand to an arbitrary AI agent via the filesystem. Lanework's plain-folder-and-Markdown model is structurally incompatible with the "everything is a database object in our proprietary graph" approach these tools are converging on, which is a real point of difference rather than a feature gap to close.
|
||||
|
||||
## Adjacent and directly relevant: markdown/git-native kanban for AI coding agents
|
||||
|
||||
This surfaced unprompted while researching the AI-agent angle and is worth flagging prominently because it validates part of Lanework's core thesis from an unexpected direction: there is an active, fast-moving 2025-2026 niche of markdown-file-based, git-native kanban/task tools built specifically for AI coding agents (Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI) to read and write task state directly as plain files, with a human-usable kanban view layered on top. Examples found: **Backlog.md** (tasks as `.md` files with YAML frontmatter in a git repo, zero-config CLI, explicitly designed so "Claude, please take over task 33" works, plus a terminal/web kanban view — "nearly all of Backlog.md's own code is written by AI agents working through Backlog.md itself"), **Kanban-md** (Show HN, Feb 2026, "no server, no DB, no API tokens"), **Kanban CLI** (Rust, Show HN June 2026), **VS Code Agent Kanban** (Show HN, persistent markdown task files with `[user]`/`[agent]` conversation-log markers committed alongside code), **AgentsBoard**, **Agent Kanban**, and **AgentsRoom**. ([GitHub: Backlog.md](https://github.com/MrLesk/Backlog.md), [HN: Kanban-md](https://news.ycombinator.com/item?id=46957653), [HN: Kanban CLI](https://news.ycombinator.com/item?id=48256520), [HN: VS Code Agent Kanban](https://news.ycombinator.com/item?id=47307169))
|
||||
|
||||
This niche is distinct from Lanework's positioning but adjacent enough to matter directly: these tools validate that "plain Markdown files as the task-state source of truth, readable/writable by both humans and AI agents" is a real, actively-growing pattern with multiple independent implementations converging on it in the same 18-month window — not a niche idea unique to Lanework. The difference is audience and surface: these are developer-CLI/git-repo tools aimed at orchestrating coding agents inside a single repo, not native GUI kanban apps aimed at a general "boards are folders on disk" personal/team workflow with a first-class macOS UI. Lanework sits at the intersection of this validated agent-file-format pattern and the native-app-quality-bar end of the market that these CLI-first tools don't attempt to serve — worth a closer, dedicated look in 06-agents-and-tasks.md.
|
||||
|
||||
## Open questions for later, narrower passes
|
||||
|
||||
- Concrete named Product Hunt / HN launch case studies for kanban or file-based task apps specifically, with real traction numbers (this pass only found generic "how to launch" content).
|
||||
- Whether the Backlog.md/Kanban-md/Agent-Kanban cluster has any user overlap or awareness of native GUI tools like Lanework, or whether the two remain in totally separate discovery funnels (git/CLI users vs. Mac App Store/Setapp users).
|
||||
- A harder look at Superlist's post-Fragment-merger direction, since it's the closest thing to a "modern Wunderlist" and is actively expanding rather than consolidating.
|
||||
- Reddit/App Store review mining specifically for kanban-format (not just PKM/notes) local-first demand, since the 9,300-post analysis found no kanban-specific signal within its local-first bucket.
|
||||
@@ -0,0 +1,81 @@
|
||||
# The AI-Agent + Task-Management Intersection
|
||||
|
||||
This document covers the segment Lanework's core bet actually lives in: how AI coding agents (Claude Code, Cursor, Codex, Copilot, Devin, aider) currently consume and update task/project state, the purpose-built tools emerging to serve that need, how mainstream trackers (Linear, GitHub, Jira/Atlassian, Notion) are courting agents, the multi-agent orchestration UIs that visualize agent work as boards, developer sentiment on the files-vs-API debate, and where the gaps sit for a human-grade native UI over agent-readable files.
|
||||
Researched: 2026-08-01
|
||||
|
||||
## How agents are given task lists and project state today
|
||||
|
||||
- **Ad hoc markdown files (the default, no tooling required).** The most common pattern is still a plain `TODO.md`, `PLAN.md`, or `ROADMAP.md` at the repo root that a human or the agent itself writes and updates; Claude Code and similar tools read/edit it like any other file. Workflows described in the wild: "keep your tasks in a simple markdown file (todo.md) and let Claude Code implement them automatically," or a `ROADMAP.md` that gets updated as part of a "study codebase → update roadmap → do priority task" loop. Zero adoption friction (every agent already reads files) is the appeal; the cost is no structure — no dependencies, no status enum, no ownership, easy for the file to drift from reality across a long session.
|
||||
- **AGENTS.md as the emerging cross-tool convention.** A markdown file at repo root giving agents project-specific context (build commands, conventions, architecture notes); as of 2026 it's read natively by 30+ tools including Claude Code, GitHub Copilot, Cursor, Devin, and aider. This is adjacent to task management (it's project *context*, not a task queue) but it's the closest thing to a cross-vendor standard that exists, and it establishes the pattern of "one markdown file every agent already knows to look for."
|
||||
- **Claude Code's built-in TodoWrite/Tasks.** Claude Code ships a first-class in-session task list: the agent calls a `TodoWrite` tool with items carrying `content`/`activeForm`/`status` (pending/in_progress/completed), rendered live in the terminal UI so the human can see "where am I, what's next" turn to turn. As of Claude Code v2.1.16 (Jan 22, 2026) this was replaced/extended by "Tasks," which adds dependency tracking, filesystem persistence, and cross-session collaboration — i.e., Anthropic itself moved from an ephemeral in-memory todo list toward a durable, file-backed task model, which is a notable signal that even the agent vendor sees session-scoped todos as insufficient once work spans sessions.
|
||||
- **Cursor / aider / Devin.** Cursor has no native task-tracker; a live "Simple Task Management" feature request thread on Cursor's community forum shows users want one and don't have it. aider is explicitly single-session/human-in-the-loop and doesn't attempt project-level task state. Devin instead plugs into whatever the team already runs — hand it a Jira ticket, bug report, or feature request and it manages that item's lifecycle, and teams can assign it 10 independent tickets to work in parallel sandboxes; Devin's task management is thus outsourced entirely to the host tracker rather than built in.
|
||||
- **MCP servers as the connective tissue.** Rather than each agent vendor building tracker integrations one-by-one, the Model Context Protocol (MCP) has become the standard plug for wiring an agent to whatever tracker a team already uses — GitHub, Linear, Jira/Confluence, Notion all now ship official remote MCP servers (see below). This is the mechanism, not a tool in itself, but it's the dominant one as of 2026.
|
||||
- **MCP Tasks extension (protocol-level, not tool-level).** The MCP spec itself added a Tasks extension formalizing a small state machine for long-running work — `working` / `input_required` / `completed` / `failed` / `cancelled` — with durable task IDs, polling, and TTL/poll-interval metadata, so a tool call that takes minutes or needs human approval doesn't require holding a connection open. It's infrastructure for async tool calls, not a project-management surface, but it shows the protocol layer itself is growing native task/state vocabulary.
|
||||
|
||||
## Purpose-built agent task tools
|
||||
|
||||
- **[Beads](https://github.com/steveyegge/beads) (steveyegge/beads).** A distributed, git-backed issue tracker built specifically to replace "messy markdown plans" with a dependency-aware graph so agents can handle long-horizon work without losing context. Storage is Dolt (a version-controlled SQL database) in embedded or server mode, with `.beads/issues.jsonl` as an export/interchange format, not the source of truth — data syncs across machines via `bd dolt push/pull` against git remotes. Dependency types include blocks, related-to, duplicates, supersedes, replies-to, and parent-child; IDs are hash-based (e.g. `bd-a1b2`) specifically to avoid merge collisions when multiple agents create issues concurrently; a "semantic compaction" feature summarizes closed tasks to conserve context windows. Created by Steve Yegge, released October 13, 2025; hit ~1,000 stars and ~50 forks in its first six days, and per a later check sits at roughly 25.8k stars / 1.7k forks — one of the fastest-growing tools in this whole space and the clearest signal of pent-up demand for "an issue tracker an agent can drive." Notably it explicitly rejects the "just use markdown" approach at scale, arguing a real dependency graph plus real merge semantics is needed once agents create issues faster than humans can triage them.
|
||||
- **[Trekker](https://github.com/obsfx/trekker)** — a deliberately minimal reaction to Beads: a Claude Code plugin with a lightweight dashboard, built by a developer who used Beads, found "giving an agent a task tracker helps a lot with focus and continuity," but wanted a stripped-down alternative with fewer abstraction layers. Posted to Show HN Jan 22, 2026. Signals the space is already forking into "full dependency-graph database" vs. "minimal enough to not need one" camps.
|
||||
- **[Backlog.md](https://github.com/MrLesk/Backlog.md)** — markdown-native task manager and terminal/web kanban visualizer for any git repo; explicitly "for humans and AI Agents," works with Claude Code, Gemini CLI, Codex, Kiro, and any MCP/CLI-compatible assistant. Tasks are per-file markdown (not one big TODO file) with acceptance criteria, milestones, and dependencies; ships both a CLI and an MCP server exposing task operations as typed tools ("the recommended approach for AI agents that support tool use"). 100% offline/private, git-native, no external services. Its Show HN thread (June 2025) is a good sentiment read: the creator's own success curve was 50% with docs alone → 75% with per-task markdown files → 95%+ once task generation was automated, and commenters converged on "lightweight, git-integrated markdown workflows suit AI-assisted development better than centralized platforms" — with the caveat that large markdown files blow agent context budgets, so atomic per-task files matter.
|
||||
- **[claude-task-master](https://github.com/eyaltoledano/claude-task-master)** — an AI-powered task-management system dropped into Cursor, Lovable, Windsurf, Roo, etc.; parses a PRD into tasks and exposes MCP tools (`get_tasks`, `next_task`, `set_task_status`, `expand_task`, `parse_prd`, ...) in core/standard/full tool-count tiers (7/15/36 tools). One of the earliest and most-forked entries in the space (numerous community forks: vibehat/claude-task-manager, ben-vargas/ai-claude-task-master, developerz-ai's autonomous-orchestration fork, etc.) — the fork count itself is a signal of how much people want to bend this to their own workflow rather than adopt one opinionated shape.
|
||||
- **Other MCP task servers**: `taskqueue-mcp` (structured task queue with optional human-approval checkpoints), Dooist (tasks carry intent/spec/desired-output/status so any session can pick one up), Tasks.md MCP server (plain-markdown Epics/Stories/Tasks/Milestones via MCP tools, no database), `madebyaris/agent-orchestration` (shared memory + task queue + resource locks for multi-agent collaboration). Long tail, mostly single-maintainer, mostly reinventing the same small set of primitives (queue, status enum, dependency edge, context blob).
|
||||
- **GNAP — Git-Native Agent Protocol** ([farol-team/gnap](https://github.com/farol-team/gnap)) — an RFC-stage, zero-server coordination protocol where agents literally share a git repo as the task board: tasks live as JSON files in `board/todo/`, an agent claims one by moving it to `board/doing/`, and commits the result to `board/done/`; git history *is* the audit trail. Reference deployment: 4 agents (2 AI + 2 human) at "Farol Labs" coordinating 50+ tasks through one repo. Proposed as a bolt-on for Letta, OpenHands, Roo Code, Plandex, and others. This is the closest conceptual sibling to Lanework's own bet (state lives as files in a git-friendly tree, no server) but it's aimed at agent-to-agent coordination with no human-facing UI at all — it's infrastructure, not a surface.
|
||||
|
||||
## How mainstream trackers are courting agents
|
||||
|
||||
- **Linear.** Hosted MCP server (`mcp.linear.app`, built with Cloudflare + Anthropic) launched May 2025, covering every issue/project/cycle/comment/attachment the authorizing user can read; a Feb 2026 update added initiatives, milestones, and project updates/labels. As of April 23, 2026, "Linear Agent" can itself connect out to other tools via MCP, i.e. Linear moved from *being* an MCP target to *hosting* agents that call other MCP servers. Linear also became the standout proof point for "tracker as agent control plane": **OpenAI's Symphony** (open-sourced, openai.com/index/open-source-codex-orchestration-symphony) is a spec that turns a Linear board into the control plane for Codex — agents pull issues from "Todo," move them to "In Progress," open a PR and move to "In Review" on completion, and GitHub webhooks close the issue when the PR merges. OpenAI reported internal teams saw a **500% increase in landed pull requests** after adopting this pattern, with the caveat that the constraint became "humans writing executable tickets," not agent capability. This is arguably the single strongest piece of evidence in this whole research pass that structured, stateful trackers (vs. raw chat/markdown) meaningfully unlock agent throughput at scale — and that a *board with real states*, not a to-do list, is what did it.
|
||||
- **GitHub.** Two tracks: (1) **Copilot coding agent** — assign it a GitHub Issue and it works autonomously in an Actions-powered sandbox, iterating through test failures and opening a PR for review with no further prompting; GA by 2026, used by ~90% of Fortune 100, Copilot overall at 20M users / 4.7M paid (+75% YoY as of Jan 2026). (2) **GitHub Agentic Workflows** (`github.github.io/gh-aw`) — repo automation written in plain Markdown that runs Copilot/Claude Code/Codex/Gemini inside Actions with sandboxed, read-only-by-default execution (e.g. an issue-triage workflow that labels and comments on new issues); and GitHub Projects now surfaces agent sessions directly in table/board views so a maintainer can see at a glance which items have an attached agent session and its status. GitHub's official `github-mcp-server` (19.9k+ stars) is the other half — issue/PR CRUD, repo search, and triage exposed as MCP tools for any client.
|
||||
- **Jira / Atlassian (Rovo).** Rovo agents reached GA in Jira in 2026 — can be assigned work, @-mentioned in comments, and embedded in workflows, operating across Jira, Confluence, JSM, and 50+ connected apps (Slack, Drive, GitHub, Salesforce, Notion). Atlassian shipped an official remote MCP server (`atlassian/atlassian-mcp-server`, OAuth 2.1, built on Cloudflare's Agents SDK with Anthropic) connecting Jira/Confluence/JSM/Bitbucket/Compass to Claude, ChatGPT, Cursor, VS Code, etc. Framing at Atlassian Team '26 (May 2026, Anaheim) was explicit: AI moving "from assistance to active participation."
|
||||
- **Notion.** Hosted MCP server (18 tools: search, page CRUD, database creation, comments, users) plus page content exposed as enhanced Markdown (`retrieve-page-markdown` / `update-page-markdown`) — notable because it means Notion, a database-backed product, deliberately presents itself to agents *as if* it were a markdown file store, echoing the "virtual filesystem" pattern seen elsewhere (see Files vs. API below). Notion Custom Agents (2026) can also participate in cross-tool workflows via pre-built partner MCP integrations (Linear, Figma, HubSpot) or custom servers.
|
||||
- Pattern across all four: every major mainstream tracker independently converged on the same shape in the last ~12 months — official hosted MCP server + agents that can be assigned/mentioned/take actions inside the existing board — meaning "give the agent API access to our tracker" is now table stakes, not a differentiator. The differentiator is what happens on top (see Gaps, below).
|
||||
|
||||
## Multi-agent orchestration UIs
|
||||
|
||||
A genuinely dense cluster of tools now visualizes parallel-running coding agents as a board or queue — this is the segment closest to Lanework's own UI concept, though none of them treat the board itself as a portable, human-editable file tree the way Lanework does.
|
||||
|
||||
- **[Conductor](https://conductor.build)** (Melty Labs, YC S24) — free native Mac app; each new "workspace" runs `git worktree add` and starts Claude Code or Codex inside it, fully isolated; features include Checkpoints (rollback snapshots), Spotlight testing (sync a workspace's changes back to main for testing), and multi-model mode (run Claude and Codex on the same prompt side by side). Used by engineers at Linear, Vercel, Notion, Stripe, Life360 per its marketing. No plain-file board — the workspace list is the "board," implicitly, not a kanban.
|
||||
- **Crystal → Nimbalyst** ([stravu/crystal](https://github.com/stravu/crystal), now deprecated/renamed) and **crystl** (a macOS-native Swift rewrite using Keychain, throttled off-screen rendering) — Electron/native apps for running multiple Claude Code/Codex sessions in parallel git worktrees, session-per-tab rather than card-per-task.
|
||||
- **[Vibe Kanban](https://github.com/BloopAI/vibe-kanban)** — an open-source kanban board purpose-built for AI coding agents (Claude Code, Codex); each card is an agent task, parallel execution runs each in an isolated git worktree, one-click dev-server startup per card. Reported figures vary by snapshot but land around 8-9k GitHub stars, making it one of the most-starred tools in this whole document. Notably its creator (Bloop) shut down in April 2026 and the project transitioned to community maintenance — a caution flag that "hot open-source agent tool" and "sustainable business" are not the same thing yet in this space.
|
||||
- **[Kanban Code](https://github.com/langwatch/kanban-code)** (LangWatch) — the closest direct conceptual neighbor to Lanework found in this research. Native macOS (SwiftUI, "liquid glass") + Windows (Tauri) app whose stated goal is "easing the context-switching bottleneck ... by centralizing all context needed for each Claude session into their cards." Each kanban card automatically links a Claude Code session, a git worktree, a tmux terminal, and a GitHub PR, flowing through Backlog → In Progress → Waiting → In Review → Done → All Sessions. Built with a clean unidirectional-data-flow architecture (`AppState`/`Reducer`/`EffectHandler`, a separated `KanbanCodeCore` Swift library) and an embedded terminal (SwiftTerm). Storage, notably, is *not* one-file-per-card the way Lanework or Backlog.md do it — it's `~/.kanban-code/settings.json` and `~/.kanban-code/links.json` (a central "links" record) plus scanning `~/.claude/projects/` for session discovery; the board state is app-owned JSON, not a portable folder of files a human or shell script would casually edit. ~300 stars / 31 forks, AGPLv3, explicitly synthesized from five predecessor projects by the same team. This is a real existence proof that "native Mac app, kanban-as-agent-orchestrator" is a validated shape people want — but it competes on session/terminal/worktree integration, not on being a human-grade editable-files surface.
|
||||
- **A long tail of similar single-purpose boards**, mostly terminal (TUI) or small web apps, all converging on the same primitive (task = card = worktree = agent session): OpenKanban (TUI, TechDufus), agent-kanban ("mission control for your AI workforce," leader agent plans/assigns, workers claim and ship PRs), ai-agent-board (DanWahlin, drag-and-drop, multi-engine: Copilot/Claude/Codex/OpenCode), Cline's built-in `cline --kanban`, opencode-kanban (Rust TUI for OpenCode+tmux). None found with meaningful star counts beyond Vibe Kanban and Kanban Code; this is a "everyone is building the same toy" moment, which usually means the primitive is right but no single implementation has won yet.
|
||||
- **Google Antigravity's Agent Manager ("Mission Control")** — not a kanban board but the same underlying need from a different angle: a dedicated surface (built on VS Code, powered by Gemini 3 Pro) to spawn/monitor/coordinate multiple agents working asynchronously across workspaces, flipping the usual "agent embedded in the IDE" relationship to "IDE surfaces embedded in the agent manager." Signals that even the big-lab-built IDEs are converging on "a board of parallel agents" as the primary developer-facing surface for agentic coding, not chat.
|
||||
- **Enterprise-scale orchestrators worth noting from `awesome-agent-orchestrators`**: Fusion (kanban board + plan-review-execute gates + per-task worktrees + hierarchical missions), gastown (scales to 20-30 agents with a coordinator, git-backed issue tracking, Bors-style merge queue), multi-agent-shogun (tmux orchestrator, up to 10 parallel agents, zero coordination-API cost). These lean further into "swarm ops tooling" than "human-legible board."
|
||||
|
||||
## Developer sentiment: files vs. API/database, and "agents need issue trackers"
|
||||
|
||||
- **The core discourse has a name now**: multiple 2026 pieces frame it explicitly as "issue trackers as AI agent infrastructure" — the argument (from MindStudio, Nate B. Jones, and others covering Symphony) is that issue trackers already encode most of what an autonomous agent needs structurally: state, ownership, permission hierarchies, immutable history — things a raw chat context or a loose markdown file don't durably have. "A conversation has no durable state outside the context window" is the recurring one-liner.
|
||||
- **Filesystem vs. API vs. database is being explicitly litigated**, not just assumed. An Arize engineering piece ("AI Agent Interfaces in 2026: Filesystem vs API vs Database") lands on: filesystems win as an *interface* not because they're theoretically best but because "everything else is worse" — agents have massive pretraining on bash/file operations, so a filesystem needs no schema explanation, while APIs burn context explaining endpoints and databases require query languages agents use less fluently. Its tradeoff table: filesystem = familiar but reinvents search/locking/validation poorly at scale; API = better for humans, context-expensive for agents; database = proper persistence/query but unfamiliar query surface. The resolving pattern it documents is a **"virtual filesystem"**: store data in a real database but expose it to the agent *as if* it were files (LangSmith is cited as doing this) — which is precisely what Notion's MCP server does by exposing pages as "enhanced Markdown" rather than raw JSON, and arguably what Backlog.md's MCP server does the other direction (real files, but with a typed-tool API layered on top for agents that prefer tool calls over `cat`/`grep`).
|
||||
- **The Backlog.md and Beads reception both point the same direction**: plain markdown works great until (a) files get large enough to blow context budgets, or (b) multiple agents/humans are creating and closing issues fast enough that merge conflicts and lost updates start to matter — at which point people reach for atomic per-task files (Backlog.md's fix) or a real dependency graph with conflict-safe IDs (Beads' fix). Nobody in this research surfaced a strong voice arguing markdown-only *doesn't* scale to a single dev/small team; the scaling concern is specifically multi-agent-concurrent-writers and long-horizon-context.
|
||||
- **Show HN threads as a sentiment proxy**: Trekker's post ("giving an agent a task tracker helps a lot with focus and continuity" — then building a *simpler* tool than Beads because Beads had drifted from what the poster actually needed) and Mission Control's post (commenters pushing on task provenance/auditability, and flagging that "agent completed the task correctly but solved the wrong problem" is a live failure mode current tools don't self-detect) both show a builder community actively iterating on primitives, not settled on one winner.
|
||||
- **No one is defending Jira/enterprise-tracker UX on the merits for agent-driven work** in anything surfaced here — Jira/Linear/GitHub win this discourse specifically *because* they already have durable structured state and audit trails, not because their UI is considered good for the job; several pieces (and the Backlog.md thread) explicitly note enterprise users still want a *bridge* to Jira rather than abandoning file-based local tools, suggesting the two aren't seen as mutually exclusive.
|
||||
|
||||
## Gaps: what's missing
|
||||
|
||||
- **No one treats the board as a portable, human-editable file tree.** Every mainstream tracker (Linear/GitHub/Jira/Notion) exposes agent access via API/MCP over a server-owned database; every native-feeling orchestration UI found (Kanban Code, Conductor, Crystal, Vibe Kanban) stores its own state as app-owned JSON/SQLite, not as a folder of files a human could open in Finder, diff in git, or grep from a shell script independent of the app. Lanework's literal "boards are folders and Markdown files on disk" is not the pattern any competitor in this specific intersection actually ships, despite GNAP and Backlog.md gesturing at the same philosophy from the tooling/CLI side.
|
||||
- **The CLI/MCP tools are agent-first with weak or no human GUI**; the GUI tools (Kanban Code, Vibe Kanban, Conductor) are agent-orchestration-first with app-owned state, not a general-purpose human kanban surface that happens to also be agent-legible. Nothing found combines "genuinely good native human kanban app" with "the underlying files are the actual source of truth, and any agent/script/editor can read and write them without going through the app's API or a bundled MCP server." That combination — first-class human UI *and* first-class agent-of-any-kind substrate, at once, with neither role privileged — is the gap Lanework's bet targets, and this research pass didn't surface a direct occupant of it.
|
||||
- **Multi-agent-concurrent-write safety on plain files is still unsolved-ish.** Beads' entire reason to exist is that markdown/plain-file approaches degrade once agents create/close issues fast concurrently (merge collisions, lost updates); GNAP's answer (git as the coordination bus, todo/doing/done directories) is elegant but has no human review surface at all. A native app that could make git-mediated concurrent file edits legible and safely mergeable *for a human watching a board update live* is unaddressed.
|
||||
- **Provenance/audit and "did the agent actually solve the right problem" surfaced as an explicit gap** in the Mission Control HN thread — current tools track task status (done/not done) but not whether the outcome matched intent, and rely on humans to catch scope drift. A board UI that made an agent's diff/PR trivially reviewable against the original card text (which Kanban Code and Symphony both gesture toward via PR-linking, but don't make the primary UI object) is only partially built out anywhere.
|
||||
- **No dominant, sticky product yet.** Every purpose-built agent task tool in this document is either brand-new (Beads: Oct 2025), community-maintained after its creator shut down (Vibe Kanban), a low-star long tail (OpenKanban, agent-kanban, ai-agent-board, Kanban Code at ~300 stars), or a spec/RFC with a single reference deployment (GNAP, Symphony). The mainstream trackers (Linear/GitHub/Jira/Notion) have won the "agents can act on our data" layer but not the "this is where humans go to see agent work as a board" layer — that layer is still up for grabs, actively being prototyped by a dozen small teams, and none has separation yet.
|
||||
- **Cross-repo / cross-project agent task state** was flagged as an open problem in the Backlog.md thread (users asking how to run one backlog across separate frontend/backend repos) and isn't solved by any tool surveyed — every file-based approach here is scoped to a single git repo.
|
||||
|
||||
## Sources
|
||||
|
||||
- [Backlog.md](https://github.com/MrLesk/Backlog.md), [Backlog.md Show HN thread](https://news.ycombinator.com/item?id=44483530)
|
||||
- [Beads (steveyegge/beads)](https://github.com/steveyegge/beads), [Beads Show HN](https://news.ycombinator.com/item?id=46709872), [Beads coverage, Better Stack](https://betterstack.com/community/guides/ai/beads-issue-tracker-ai-agents/)
|
||||
- [Trekker](https://github.com/obsfx/trekker)
|
||||
- [claude-task-master](https://github.com/eyaltoledano/claude-task-master)
|
||||
- [GNAP — Git-Native Agent Protocol](https://github.com/farol-team/gnap)
|
||||
- [Mission Control Show HN](https://news.ycombinator.com/item?id=47165602)
|
||||
- [Linear MCP changelog](https://linear.app/changelog/2026-04-23-linear-agent-mcp-support)
|
||||
- [OpenAI Symphony announcement](https://openai.com/index/open-source-codex-orchestration-symphony/), [Symphony/Linear 500% PR increase writeup](https://www.mindstudio.ai/blog/openai-symphony-spec-linear-agent-control-plane-500-percent-pr-increase)
|
||||
- [GitHub MCP Server](https://github.com/github/github-mcp-server), [GitHub Agentic Workflows](https://github.github.io/gh-aw/), [Assigning issues to Copilot coding agent](https://github.blog/ai-and-ml/github-copilot/assigning-and-completing-issues-with-coding-agent-in-github-copilot/)
|
||||
- [Atlassian remote MCP server](https://github.com/atlassian/atlassian-mcp-server), [Rovo agents in Jira](https://www.atlassian.com/blog/rovo/ai-agents-in-jira)
|
||||
- [Notion official MCP server](https://github.com/makenotion/notion-mcp-server)
|
||||
- [Claude Code Todo/Tasks docs](https://code.claude.com/docs/en/agent-sdk/todo-tracking)
|
||||
- [Conductor (Melty Labs)](https://conductor.build)
|
||||
- [Vibe Kanban](https://github.com/BloopAI/vibe-kanban)
|
||||
- [Kanban Code (LangWatch)](https://github.com/langwatch/kanban-code)
|
||||
- [awesome-agent-orchestrators](https://github.com/andyrewlee/awesome-agent-orchestrators)
|
||||
- [AI Agent Interfaces in 2026: Filesystem vs API vs Database, Arize](https://arize.com/blog/agent-interfaces-in-2026-filesystem-vs-api-vs-database-what-actually-works/)
|
||||
- [Google Antigravity Agent Manager](https://antigravity.google/blog/introducing-google-antigravity)
|
||||
- [AGENTS.md best practices](https://www.betterclaw.io/blog/agents-md-best-practices)
|
||||
@@ -0,0 +1,54 @@
|
||||
# Schema Comparison: Signboard vs Lanework
|
||||
|
||||
Signboard is the closest live competitor (see its profile in [03-native-indie-filebased.md](03-native-indie-filebased.md)), and both apps make the same headline promise: boards are folders and Markdown files on disk. This document compares the two on-disk formats in depth — how each is defined, the structural choices, and what those choices cost — because the format is the product's foundation and the differentiation turns out to live there. This is the first narrow-pass artifact; the pattern (per-competitor deep dive) is the template for the rest of pass two.
|
||||
|
||||
Researched: 2026-08-01
|
||||
|
||||
## How each format is defined
|
||||
|
||||
Signboard's format is open but informal: documented in prose in [docs/using-signboard.md](https://github.com/cdevroe/signboard/blob/main/docs/using-signboard.md), with the MIT-licensed source as the de-facto normative spec. There is no formal schema document, no schema version key on disk, and no stated compatibility or round-trip guarantees — the code is the spec, and the format is free to drift with releases.
|
||||
|
||||
Lanework's format is a normative contract: `DESIGN/01-storage-format.md` (graduating to `SCHEMA.md`), a `schema: 1` version key at board root, an explicit five-verdict defect taxonomy (refuse / refuse writes / tolerate / coerce / heal), and byte-level preservation guarantees. External writers can target the contract, not the implementation.
|
||||
|
||||
## The formats side by side
|
||||
|
||||
| Axis | Signboard | Lanework |
|
||||
|---|---|---|
|
||||
| Card | Single `.md` file | Folder with `index.md` + `attachments/` |
|
||||
| Identity | Filename: `[order]-[title]-[random-id].md`, plus `signboard_id` in frontmatter | Folder name = immutable UUID; title only in frontmatter |
|
||||
| List/lane order | Numeric prefix in the folder name | `order` rank in each item's frontmatter |
|
||||
| Card order | Numeric prefix in the filename | Gapped fractional `order` rank |
|
||||
| Location | Path, plus `signboard_board` / `signboard_list` duplicated in frontmatter | Path only ("level is position") |
|
||||
| Dates | Inline body syntax `(due: YYYY-MM-DD)` on checklist items | Frontmatter (`due` reserved for the tracker era) |
|
||||
| Frontmatter posture | Deliberately flat, Obsidian-property-friendly (`title`, `signboard_id`, `signboard_board`, `signboard_list`, `status`, `signboard_uri`, `related`, `linked_objects`) | Minimal schema-owned keys; unknown keys, comments, and formatting preserved verbatim |
|
||||
| Versioning | None | `schema: 1` at board root |
|
||||
| Round-trip promise | None stated | Byte-perfect: unknown keys, comments, line endings, untouched bodies all survive |
|
||||
| Validation/healing | None documented | Integrity service: coercion rules, defect taxonomy, inline/on-touch/scheduled heals |
|
||||
| Trash/archive | `XXX-Archive` folder (named to sort last) | Reserved `.trash/`, restore = ordinary move, `kind` discriminator |
|
||||
| Settings | `board-settings.md` at root | Board `index.md` frontmatter |
|
||||
|
||||
## What the differences mean in practice
|
||||
|
||||
**Identity is the deep divergence.** Signboard encodes title and order into the filename, so a rename or reorder renames the file. That is friendly in Finder — a raw board reads at a glance — but identity is unstable: git sees renames instead of edits (history detaches unless rename detection catches it), sync engines see delete+create, and an agent mid-edit can have the file move out from under it. Lanework paid the Finder-legibility cost (opaque UUID folders) precisely to buy immutable identity: renames and reorders never move or rename anything, git history stays attached to the card forever, and the card window tracks its card by UUID through any foreign move. A genuine trade, not a strict win — Signboard's boards are more browsable raw — but for the agent/git thesis, stable identity is the right side of it.
|
||||
|
||||
**Ordering by name-prefix causes write cascades.** Inserting a card between positions in Signboard means renaming files to make room; reordering lists renames directories (their docs say so explicitly). Every rename is a sync-conflict surface and a git-history discontinuity. Lanework's gapped fractional ranks rewrite exactly one file per reorder, with a rare, localized renumber when midpoints exhaust.
|
||||
|
||||
**Signboard denormalizes; Lanework doesn't.** `signboard_board` and `signboard_list` inside each card duplicate what the path already says — done for Obsidian-properties interop, so a card is self-describing inside a vault. The cost: a card moved by hand, script, or agent — the exact users both apps court — carries stale location metadata afterward, and nothing in Signboard's docs describes healing it. Lanework's level-is-position rule means there is nothing to go stale, and where defects can arise the integrity service owns the repair story. Signboard has no documented equivalent of validation, coercion, or preservation rules; hand-edited files with unknown keys or odd YAML get whatever the code happens to do.
|
||||
|
||||
**Single-file cards vs folder cards.** Signboard's card is lighter and Obsidian-native (a card is a note), with `linked_objects` pointing at external files by reference. Lanework's folder-per-card is heavier but gives cards real owned contents — attachments that travel with the card through moves, copies, trash, and clipboard, and a future `comments/` thread. Reference-style links break when targets move; owned folders don't.
|
||||
|
||||
## Strategic read
|
||||
|
||||
The two formats optimize for different first-class citizens. Signboard's schema is shaped by Obsidian: flat properties, vault embedding, human-readable filenames, Bases generation. Lanework's is shaped by git and agents: immutable identity, minimal-write ordering, byte-perfect round-trips, a versioned contract, a seeded `CLAUDE.md`. Neither app can cheaply adopt the other's posture — Signboard cannot get stable identity without breaking every existing vault's filenames — so this is durable structural differentiation, not a feature gap either side closes with a release.
|
||||
|
||||
Consequences worth carrying into positioning and planning:
|
||||
|
||||
- The formats will not interoperate directly, but a Signboard importer would be mechanical to write (their docs show the full shape). Signboard already imports Trello, Obsidian boards, and Tasks.md — consolidating the niche via importers is their explicit playbook, and it can be Lanework's too.
|
||||
- "Our format is a versioned, guaranteed contract" is a marketable claim Signboard structurally cannot match today, aimed exactly at the agent/script/git audience both apps court.
|
||||
- The Obsidian-shaped choices that weaken Signboard's format for agents are the same choices that give it distribution into the largest markdown-board audience (vault embedding, companion plugin). Format rigor wins the agent story; vault interop wins the Obsidian story. Watch whether Signboard tries to have both — retrofitting stable identity would be its hardest possible migration.
|
||||
|
||||
## Open questions
|
||||
|
||||
- Does Signboard's MCP server/CLI mediate writes in a way that compensates for the format's fragility (e.g. fixing up `signboard_list` on move), and what happens when an agent bypasses them and edits files directly?
|
||||
- How does Signboard behave on hand-edited files: are unknown frontmatter keys preserved on rewrite? Is there any conflict story when a file changes mid-edit? (Testable empirically — it's free for personal use.)
|
||||
- Whether Obsidian Bases' first-party kanban adopts a format of its own, which would pressure both apps' interop stories.
|
||||
@@ -0,0 +1,24 @@
|
||||
# Market Research
|
||||
|
||||
Long-term competitive-landscape research for Lanework: the kanban app market plus the adjacent personal todo/task-management market, with special attention to the file-based/local-first niche and the emerging AI-agent + task-management intersection — the two axes Lanework's bet actually lives on.
|
||||
|
||||
This directory is a living body of work. The first pass (2026-08) is deliberately broad — mapping segments, trends, and success factors. Later passes will narrow: deep-dives on the direct competitive set, positioning, and pricing.
|
||||
|
||||
## Documents
|
||||
|
||||
- [01-market-overview.md](01-market-overview.md) — synthesis: the map of the market, where Lanework sits, and what the broad pass says matters (written after the segment docs; start here)
|
||||
- [02-mainstream-kanban.md](02-mainstream-kanban.md) — mainstream/team kanban and project boards: Trello, Asana, Monday, Jira, ClickUp, Notion, Linear, and company
|
||||
- [03-native-indie-filebased.md](03-native-indie-filebased.md) — native macOS, indie, and file-based/plain-text tools: Lanework's nearest neighborhood
|
||||
- [04-todo-adjacent.md](04-todo-adjacent.md) — personal todo/task apps: Things, Todoist, TickTick, OmniFocus, Reminders, and the daily-planner wave
|
||||
- [05-trends-success-factors.md](05-trends-success-factors.md) — cross-cutting trends: AI features that stuck, local-first momentum, pricing models, distribution, notable failures
|
||||
- [06-agents-and-tasks.md](06-agents-and-tasks.md) — the AI-agent + task-management intersection: how agents consume task state today and what's missing
|
||||
|
||||
Narrow-pass deep dives (per-competitor, added as they happen):
|
||||
|
||||
- [07-schema-comparison-signboard.md](07-schema-comparison-signboard.md) — Signboard's on-disk format vs Lanework's: definition rigor, identity, ordering, denormalization, and the strategic read
|
||||
|
||||
## Conventions
|
||||
|
||||
- Each document opens with a scope note and a `Researched: YYYY-MM-DD` line; treat facts as snapshots of that date.
|
||||
- Broad passes favor coverage over depth; a claim worth acting on gets re-verified in a narrow pass first.
|
||||
- Prose is unwrapped — one line per paragraph or list item.
|
||||
Reference in New Issue
Block a user