Show HN: I made an app that consolidated 18 apps (doc, sheet, form, site, chat…)

Original Article ↗ Hacker News Discussion ↗

An ambitious new “superapp” aims to replace dozens of office tools by bundling docs, sheets, forms, chat, sites and more into a single, interoperable, offline‑first workspace. Commenters praise the technical achievement and like ideas such as modular blocks, strong privacy, and end‑to‑end encryption, but question whether a small team can match the depth of Microsoft 365 or Google Workspace while also solving real user pain. Key concerns include unclear positioning and onboarding, data ownership and export/self‑hosting, integration with existing ecosystems, and whether enough people truly feel an “app chaos” problem to justify switching.

Overall Reception

  • Many commenters are impressed by the technical scope (18+ integrated modules, multi‑platform, offline‑first), especially if largely built by one person.
  • Others are skeptical that a single product can match the depth of mature tools like Office, Google Workspace, or Airtable across so many domains.
  • Several say they’d like to try it for small teams, side projects, or as a Notion‑style all‑in‑one workspace.

Positioning, Marketing & Onboarding

  • A recurring critique is unclear messaging: the landing page is described as “word salad,” too focused on blocks/modules and not on concrete use cases or user outcomes.
  • Multiple people suggest:
    • Leading with “who it’s for” and “what problems it solves,” not implementation details.
    • Use‑case oriented pages (e.g., project management, CRM, documentation) and comparison to tools like Notion, Asana, Monday.
    • Demo workspaces, templates, and short videos to show workflows.
  • Onboarding is seen as weak: new users often land on a blank screen with no guidance; concepts like “Sheet,” “Board,” “Calendar” and “blocks” confuse people.

Product & UX Feedback

  • Interoperability of data across modules (blocks/pages usable in docs, boards, calendars, chat, etc.) is viewed as the most novel idea.
  • Some testers find the UI surprisingly intuitive; others struggle with basic actions (creating sheets, forms, fields, or embedding records).
  • Requests include better sheet formulas, more “real” spreadsheet features, code cells, markdown support, plugins/scripting, block‑level mentions, and richer export (especially PDF, DOCX).
  • Bugs and friction noted: verification emails, mobile login loops, missing keyboard shortcuts, odd behaviors on iOS (e.g., letter “m” issue), Snap‑only Linux packaging.

Architecture, Security & Data Ownership

  • Tech stack: GCP, largely serverless backend, React web, Flutter mobile, Electron desktop, local‑first storage with last‑write‑wins sync (not full CRDT yet).
  • Offline‑first design is widely praised; some ask for clearer sync guarantees and options to pre‑sync content.
  • Many emphasize data sovereignty, self‑hosting or single‑tenant deployments, and end‑to‑end/zero‑knowledge encryption; current US‑hosted GCP setup raises concerns for some.
  • Export capabilities (JSON/HTML/CSV now, PDF and open formats later) are seen as necessary but currently limited.

Business Viability & Competition

  • Commenters question:
    • How it meaningfully beats Microsoft 365/Google Workspace/Zoho/Notion/Lark, which already bundle many apps.
    • Whether “app chaos” is a real widespread pain or mostly solved by current suites.
  • Common advice: narrow focus, pick a clear target niche/use case, and make one or a few workflows world‑class before trying to replace whole ecosystems.