Tasks
Quiet task management.
A calm, keyboard-first task manager built on Next.js and Convex — natural-language input, a daily Plan ritual, and a quiet Feed instead of notifications. Free for teams in beta.
// the_objective
Build a calm, free task manager that sits in the middle between throwaway to-do apps and exhausting project tools — simple enough for anyone you invite, capable enough that a real team never outgrows it. The promise is literal: simple to start, hard to outgrow.
// our_approach
Our approach
Natural-language capture
One sticky input parses the date ("tomorrow", "Friday", "Jun 15"), #tags, @assignees resolved against project members, recurrence and priority — entirely client-side, before the write ever reaches the database. A quiet toast confirms what it caught.
The Plan engine
A pure scoring function ranks the day's candidates and a daily ritual proposes a shortlist, grouped by reason — overdue, due today, assigned to you, recurring. A carry-over banner sweeps yesterday's unfinished work forward, so nothing quietly slips.
An event-sourced core
Every meaningful change records an immutable event rather than mutating state in place. That single decision powers the day-grouped Feed, a 7-day Pulse rollup and a trustworthy history — the app can always tell you exactly what happened and when.
Reactive backend, cost-bounded
A self-hosted Convex backend makes every view live without polling. Hot reads stay cheap through denormalised counters and cursor pagination, and every write runs a fixed perimeter — auth, then rate-limit, then access check — before any side effect.
Optimistic, never snap-back
Drag-to-reorder and inline rename apply instantly while the server round-trips, and a draft-persistence layer keeps unsaved edits alive across tab switches, page hide and reload. The interface never fights you and never loses a keystroke.
// the_product
The product
Today
Tuesday, May 18 · 2/5 done
// key_highlights
Key highlights
A native twin, one backend
A full iOS and Android app, built with Expo, runs on the very same backend and shared types as the web app — so a backend change reaches the phone with no app rebuild.
Eight smart views
Feed, Inbox, Today, Upcoming, Assigned to me, All Tasks, Completed and Bin — plus a #tag index and per-project lists — every slice of the work, one keystroke away.
Six themes, three densities, zero flash
From OLED true-black to a soft pastel skin, each re-themes the whole app through CSS variables and applies before first paint — no flash of the wrong theme, on web or mobile.
Free at viral scale
Free for teams in beta with no card — and engineered to stay that way: denormalised counters and event rollups keep hot reads cheap no matter how large a workspace grows.
// the_stack
Tech stack
Next.js 16
Single-route web app, App Router + Turbopack
React 19
UI, with the React Compiler in the build
Convex
Self-hosted reactive queries, mutations, crons + auth
TypeScript
End-to-end types; shared Zod schemas across apps
Tailwind CSS v4
CSS-variable tokens; six themes, three densities
dnd-kit
Optimistic drag-to-reorder for tasks, lists, projects
Expo / React Native
Native iOS + Android twin on the same backend
Dokploy + Traefik
Standalone Docker, path-routed under one domain
// faq
Frequently asked questions
- Does Foways build its own products, or only client software?
- Both, and products come first. Foways is a product studio: we design, engineer and run our own software end to end, and we take a small number of custom briefs each year alongside it. Every line is written by our own senior team, never subcontracted.
- Can a product be deployed for a single department or organisation?
- Yes. Setu and Foways Office are both delivered as single-tenant deployments — one instance per customer, self-hosted on infrastructure you choose, updated over the air by us. Nothing is shared with another tenant.
- Can Foways adapt a product to our own requirements?
- Yes. Both government products are built to be extended rather than configured around: capability is added in TypeScript through a stable module interface, so a department gets what it actually needs without forking the product or losing its update path.
// next_step
Talk to us about Tasks.
Tell us what you're trying to run. We'll show you the product working, scope the deployment, and give you a straight answer on timeline.