The latest useful change across the apps is a shared home for their knowledge.
Daniel & Loenne now brings together material for AbiFlow, Boop, Carfolio, Clubfold, OneBite, and QuitNow. The 12 October organization work put app briefs, brand assets, screenshots, motion references, and shared marketing methods into a structure we can return to.
That sounds administrative. It changes the quality of the next product decision.
A file needs a role as well as a name
A beautiful screenshot, an old campaign caption, and an approved brand asset can sit beside each other without meaning the same thing.
The shared library distinguishes historical source material, current product knowledge, proposed strategy, and actual creative approval. A document can then answer a useful question: what can we rely on when making the next piece of work?
Dates matter here. A September screenshot inventory describes a particular build's UI states. An October redesign brief may change the visual direction. An older release caption can remain valuable as history without becoming the copy for today's public page.
Shared craft does not require identical brands
AbiFlow and Clubfold make this especially clear.
The current AbiFlow store-material direction uses cream, forest green, and Avenir Next. Clubfold's store direction is monochrome with Apple system typography. Both can use careful spacing, legible hierarchy, and proportional native screenshots while retaining different identities.
Boop has its own white editorial layouts and a newly documented mascot reference. Older character treatments remain historical material. Keeping the chosen reference and its approval together saves the next designer from guessing which attractive file is current.
Consistency means being faithful to each product's decisions. It does not mean making six apps look like the same template.
The repository and the material library have different jobs
App code, build packages, credentials, and operational verification stay with their technical projects. The shared library holds the concise product knowledge and the source pointers that design and marketing need.
That arrangement lets us collaborate without turning an iCloud material folder into a second development checkout. It also makes it easier to update one product fact without copying a large technical report into every brief.
The important connection is the pointer: where did this statement come from, when was it checked, and which surface does it describe?
This portfolio needs the same discipline
The blog had stopped at its 23 August issue. Today's batch fills the seven missing Sunday issues through 11 October and adds this current update.
The subjects follow the dated work: complete native app loops, screenshot inventories, OneBite's estimate review, Carfolio's domain model, AbiFlow's redesign, Clubfold's door workflow, and Boop's motion story.
Those retrospective posts show their actual publication date as 13 October. Their issue dates preserve the existing weekly archive without pretending the articles were published earlier.
That is also how I want the rest of the portfolio to evolve. Show the work, keep the evidence close to the claim, and make the current direction easy to find. A well-organized library helps the next article start from what happened, rather than from what I happen to remember.