📱 Apps

category-applications

Featured post

Readium Devlog #6 — From “No Backend” to a Boundary Layer

Avoiding a backend felt like the right decision at first. But external APIs, security, and system boundaries eventually broke that assumption. This post explores how a “no-backend” design evolved into a minimal boundary layer between the client and the outside world.

Latest posts

2026.04.13 14 min read 📱 Apps 📚 Readium Development Log — Why Design Keeps Failing Architecture Domain Modeling Event Driven Design

Readium Devlog #4 — Why Timeline Had to Become a Record

Designing Timeline as UI data is convenient. But that’s where records begin to break. This post explores why Timeline had to be redefined as facts, and how that led to thin, event-based design.

2026.04.11 15 min read 📱 Apps 📚 Readium Development Log — Why Design Keeps Failing Domain Modeling Software Design Local First

Readium Devlog #3 — Why Session Toggle Was Never Simple

The toggle looked trivial. But behind a single button, sessions, state transitions, and domain policies were all entangled. This is the story of how the simplest feature exposed a broken design.

2026.04.10 16 min read 📱 Apps 📚 Readium Development Log — Why Design Keeps Failing Domain Modeling Software Architecture Event Driven Design

Readium Devlog #2 — Why Domain Models Inevitably Collapse

Domain models don’t fail by accident—they fail by design. This post traces how a seemingly correct state-based model collapses, and why separating state, time, and events becomes inevitable.

2026.04.08 15 min read 📱 Apps 📚 Readium Development Log — Why Design Keeps Failing Software Architecture System Design Local First

Readium Devlog #1 — Starting from a Misdefined Problem

I thought the problem was the lack of records. In reality, I didn’t know how to define what a record is. This post traces the first crack in a system built on that misunderstanding.

2026.04.05 13 min read 📱 Apps 📚 Readium Development Log — Why Design Keeps Failing Software Architecture DevLog System Design

Readium Devlog #0 — Why We Always Start with the Wrong Architecture

Architectures are rarely correct from the beginning. Most projects start without a clear problem definition, inevitably building on flawed assumptions. This post is not about solutions, but about why this series chooses to document how designs collapse and evolve over time.