zntt-control / Taskie

Desktop app for productivity and task management

Native Windows desktop application built with Tauri and Vue 3. Integrated with a Django API to keep the desktop and mobile apps in sync.

Platforms
Windows Desktop · Mobile
Year
2026
Status
API live · desktop evolving
Role
Desktop and API integration

zntt-control is a Windows desktop task app built around a kanban board: projects by category, columns, tasks with priority, tags and subtasks, a per-task time tracker and progress metrics. It opens instantly, works offline and stores everything in SQLite on the computer.

The same code produces two versions: a local one, with no login, and znttaskie, which talks to the Taskie Django API and shares data with the mobile app. The choice is made at build time, by a data mode that swaps the repository layer without touching the screens.

What the system does

  1. Kanban board per project

    Configurable columns, drag and drop, priority, colored tags, subtasks with progress and a done column.

  2. Time per task

    A timer on every task, session history and total hours per project and per period.

  3. Metrics

    Open and done tasks, progress per project, distribution per column, stalled tasks and hours logged in 7, 14, 30 or 90 days.

  4. Deadlines, trash and history

    Upcoming deadlines across all projects, a trash with restore and an activity history for every task.

  5. Templates and import

    Project templates with ready-made columns and tags, and Trello board import.

  6. Themes, fonts and backup

    Five palettes, typography options, accent color, Portuguese and English interface, and local database backup.

How it was built

Desktop
Tauri 2RustSQLite (tauri-plugin-sql)
Frontend
Vue 3Quasar 2PiniaSortableJS
Backend
Django 4.2Django REST FrameworkSimpleJWT
Data
SQLitePostgreSQL

Technical challenges

  1. One codebase, two builds

    The infrastructure layer has repositories for local SQLite and for the API. A build variable picks which one goes in; screens and stores don't know where data comes from, and features without an endpoint yet stay isolated in stubs until the backend catches up.

  2. Migrations on the device

    The local database evolves with versioned migrations applied when the app opens, so existing users get tags, history, time tracking and templates without losing anything.

  3. A shared backend without breaking mobile

    The Django API is the same one used by the Taskie mobile app, maintained by someone else. Every change is backward compatible, and sign-up now requires manual approval before login is allowed.

Need something
like this?

Tell me the idea or the problem. I help shape the solution and build it from the API to the app.

Let's talk