Someone asked me recently whether I was building Seekquel too fast. New things keep turning up, and that usually means something is about to break. It is a fair thing to wonder, so I wrote out the actual answer.

Short version: the first year produced almost nothing anyone could look at. It was planning, and then building one piece at a time under a rule that if two parts of the app need the same thing, they use the same thing rather than a copy of it. That is why a new feature now is mostly made of parts that have been in use for months.

The other half is that a lot of what shows up in an update is old work. Some of it predates the first public release. A handful of testers had been living with it, rough edges and all, long before you saw it.

And it is not just me. My wife tests everything and breaks it in ways I would never think of. Friends run releases on real devices first, which matters most on the e-reader side. Readers repair the catalogue themselves, and the feedback board decides most of what I build next.

Full post: [https://seekquel.app/blog/why-seekquel-ships-so-often](https://seekquel.app/blog/why-seekquel-ships-so-often)

Happy to answer anything in the comments, including the parts that are slow and will stay slow.

How Seekquel gets built, and why updates land so often