Redesigning OinkSky for a multi-product company
Why the company layer needed to stop looking like a placeholder and start explaining the system behind InkFlow Pro, WebPPT, and what comes next.
Blog
Blog
Ideas, product notes, and working principles from OinkSky. The newest writing is always at the top.
Latest article
Editor's notes
We write here to make product judgment visible: what is shipping, why the architecture is arranged this way, and how writing, decks, and release craft connect under one company layer.
Why WebPPT needs its own product surface
WebPPT should not feel like a tab inside another product. It needs its own story, its own entry point, and its own product logic.
WebPPT should be understood as its own product, not a sub-feature.Users can share one account pool without forcing one product story.
One account, many products
The right split for OinkSky is shared identity with product-specific data. That keeps the account layer unified without mixing every table together.
Structure before generation
The quality of AI output depends heavily on whether the work was shaped before generation started. OinkSky is built around that assumption.
This is where OinkSky explains the system behind the product family.
We write here to make product judgment visible: what is shipping, why the architecture is arranged this way, and how writing, decks, and release craft connect under one company layer.
Read the methodsArchive
A running stream of product notes, architecture decisions, and working principles from across OinkSky.
February 27, 2026Product
Release-grade output is a product feature
The last mile of expression should not be left outside the product boundary. Finish is part of the job, so it has to be part of the software.
5 min read
February 20, 2026Academy
Building Academy as a method layer
Academy is not content for content's sake. It is the place where OinkSky turns product judgment into reusable workflows and shared standards.
5 min read