34 lines
1.2 KiB
Markdown
34 lines
1.2 KiB
Markdown
_model: devlog-entry
|
|
---
|
|
schema_version: 1
|
|
---
|
|
title: Choosing a native-only product boundary
|
|
---
|
|
date: 2026-07-17
|
|
---
|
|
author: Christopher Chambers
|
|
---
|
|
summary: Thinkloom removed its hosted and browser-companion paths so the implementation matched its local-first product promise.
|
|
---
|
|
tags: architecture, local-first, privacy
|
|
---
|
|
source_commit: 7866081c7882f8c59d137b126a6fe0278eda87df
|
|
---
|
|
body:
|
|
|
|
During implementation, Thinkloom briefly contained hosted and browser-facing
|
|
scaffolding alongside the desktop application. That created a mismatch with the
|
|
product being described: a native, local-first writing studio with no required
|
|
account or hosted companion.
|
|
|
|
The project removed the Sites, Next, worker, and browser-companion paths and
|
|
made Tauri the sole application target. This reduced the deployment surface and
|
|
made the privacy boundary easier to understand: manuscripts, project state, and
|
|
credentials belong on the writer's machine.
|
|
|
|
The change was as much a product decision as a technical cleanup. A smaller,
|
|
clearer architecture made it possible to state honestly what Thinkloom was—and
|
|
what it deliberately was not.
|
|
|
|
[View the native-only commit](https://git.labyricorn.com/Labyricorn/thinkloom-openai-hackathon/commit/7866081c7882f8c59d137b126a6fe0278eda87df)
|