Rebuilding TriviaPot in place, all the way to the App Store
An existing codebase, weeks of sustained engineering, and the thousands of issues behind a finished product.
The work behind the product
TriviaPot · April–September 2026
2,665
created
2,497
closed
May
The work expands
Descant decomposes the rebuild and discovers follow-ups. Issue creation initially outpaces completion.
Early June
Completion catches up
The backlog reaches its widest gap. Completion then outpaces new issue creation as implementation converges.
Late June / early July
A working product
The initial implementation converges. TriviaPot is working well, with the core feature set in place.
Early July
A deliberate design overhaul
We choose a full visual redesign and remove real-money features for the free-to-play release. This new scope creates the next wave of issues.
View chart data
| Date | Created | Closed |
|---|---|---|
| 2026-04-01 | 189 | 169 |
| 2026-04-08 | 189 | 169 |
| 2026-04-15 | 191 | 191 |
| 2026-04-22 | 191 | 191 |
| 2026-04-29 | 192 | 191 |
| 2026-05-06 | 193 | 191 |
| 2026-05-13 | 629 | 308 |
| 2026-05-20 | 1235 | 862 |
| 2026-05-27 | 1587 | 1010 |
| 2026-06-03 | 2109 | 1379 |
| 2026-06-10 | 2133 | 1535 |
| 2026-06-17 | 2208 | 1855 |
| 2026-06-24 | 2225 | 1976 |
| 2026-07-01 | 2241 | 2068 |
| 2026-07-08 | 2524 | 2404 |
| 2026-07-15 | 2561 | 2457 |
| 2026-07-22 | 2561 | 2457 |
| 2026-07-29 | 2561 | 2457 |
| 2026-08-05 | 2561 | 2457 |
| 2026-08-12 | 2589 | 2473 |
| 2026-08-19 | 2627 | 2487 |
| 2026-08-26 | 2659 | 2494 |
| 2026-09-02 | 2665 | 2497 |
| 2026-09-03 | 2665 | 2497 |
Keep the history. Rebuild the product
TriviaPot was already an existing system when we put the next generation of Descant to work on it. We chose to rebuild in place. Keeping the repository made the old implementation easy to consult: it preserved product history, earlier decisions, and useful references while substantial parts of the system changed around it.
That is a demanding setting for autonomous engineering. Every change has neighbors. A new implementation must fit the surrounding application, and the code that remains can reveal follow-up work as the product evolves. Over weeks, the effort extended through the game, the mobile experience, support, release work, and the operations around the product. On September 3, the public website was updated to point to TriviaPot's live App Store listing.
Convergence, then a deliberate new direction
The first wave of work grew quickly as Descant decomposed the rebuild and captured discoveries as follow-up issues. Creation initially outpaced completion. Then the balance shifted: the backlog narrowed as the implementation converged. By the beginning of July, TriviaPot was working well, with the core feature set in place.
We then chose a new direction: a full visual overhaul and the removal of real-money features for the free-to-play release. That deliberate expansion of scope drove the next rise in issues in early July. Descant carried the redesign across the application, then worked through the visual refinements and follow-ups. The numbered chart annotations show that progression from an expanding plan to a working product and onward into the next development phase.
A codebase that improves with each change
Focused pull requests helped keep a large transformation tractable. Each change could be reviewed in context. Related discoveries could be captured without turning the current patch into an open-ended rewrite. Over time, that discipline changed the whole codebase: new capabilities arrived, existing foundations improved, and the work around launch was completed alongside the application.
This is the kind of sustained development we are building Descant for. We remain responsible for product direction, architecture, and engineering standards. The R&D version supplies an increasingly capable way to execute that direction across many changes, then brings the lessons back into Descant. TriviaPot is available on the App Store if you want to see the resulting product.