Show HN: Micasa – track your house from the terminal

Original Article ↗ Hacker News Discussion ↗

Overall reception & TUI design

  • Many commenters praise the TUI as beautiful, slick, and more pleasant than most project-management tools, with particular appreciation for the playful “destructible house” and humorous testimonials.
  • Several note the broader trend of new, polished TUIs and express nostalgia for classic DOS/terminal apps.
  • Some say this is exactly the kind of tool they need once they’ve owned a house a few years and forgotten when anything was last serviced.

Terminal vs web/mobile & household adoption

  • A recurring concern: a terminal-only tool is unusable for non-technical spouses or household members, and many people do home tasks on phones while walking around.
  • Several suggest a web UI or PWA as the “real” primary interface, keeping the TUI as a power-user client.
  • There’s discussion of WAF (“wife acceptance factor”); households currently rely on Trello, Apple Reminders, Paprika, or shared notes instead.
  • Some propose running it as a home server with multiple clients, or exposing functionality via agents/voice (e.g., through Home Assistant).

Spreadsheets, org‑mode & existing “home manager” tools

  • Many argue a spreadsheet (Google Sheets, Grist, Obsidian tables, org-mode) is “good enough” and easier to share, sync, and script.
  • Others counter that spreadsheets miss relational structure, links, and domain-specific workflows; this tool is seen as a curated domain model for home data.
  • There’s mention of existing home-management apps (Home Assistant, HomeChart, Manor, Honeydew, Wellrun) and tension between “do everything” platforms and overwhelming UX.

AI, agents & PDF ingestion

  • Commenters are excited about planned LLM features: auto-populating projects from contractor quote PDFs and natural-language/agent-based data entry.
  • Some see the PDF-to-structured-data pipeline as the true killer feature given messy, inconsistent quotes.
  • Others warn about LLM hallucinations; suggested pattern is: use LLMs for extraction/classification, but rely on deterministic logic for calculations and comparisons.

Technical details, features & UX feedback

  • SQLite-with-BLOBs in a single file is widely liked, but one commenter notes cp is unsafe for live backups; safer methods are recommended.
  • Requests include: cron/email/SMS reminders, column summing and ad-hoc queries inside the TUI, better ID-column editing UX, keybinding tweaks, locale/metric support, and stable IDs/history for auditability.
  • Some propose SSH-only deployments, Home Assistant/TUI integrations, and support for other asset types (cars, boats, health, etc.).

Meta: TUIs, domain models & SaaS

  • Several reflect that many SaaS apps are essentially curated domain models plus CRUD UIs; this project is seen as an Excel/SQLite “template with opinions.”
  • Discussion branches into whether we’ve “cracked” the ideal UI over relational data, comparing TUIs, spreadsheets, and full web UIs for power vs accessibility.