WebPPTMarch 12, 20265 min read

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.

David Zhu

Section 01#

The workflow is different enough to stand alone

InkFlow Pro is built around deep writing and long-form structure. WebPPT is built around narrative sequence, interaction, playback, and presentation control. They are connected, but they are not the same product surface.

If WebPPT is buried under another product's navigation, users will misread what it is for.

A sketch of WebPPT as a web-native narrative surface rather than a slideshow export.

Section 02#

Separate surface, shared infrastructure

Giving WebPPT its own site does not mean duplicating identity or account logic. The better pattern is separate product surfaces on top of a shared account pool and shared service layer.

That keeps the story clean for users while letting the system stay coherent underneath.

Separate hostname and product positioning.
Shared account pool and shared membership truth.
Product-specific data tables and product-specific UI layers.

Further note

Users can share one account pool without forcing one product story.

Further note

Clearer product surfaces reduce long-term product and UX debt.

Section 03#

Why this matters now

It is easier to create the separation early than to untangle a mixed surface later. WebPPT will gain features that deserve their own narrative, from slide generation to collaborative playback and HTML-native presentation editing.

Why WebPPT needs its own product surface

The workflow is different enough to stand alone

Separate surface, shared infrastructure

Why this matters now

Related reading

Redesigning OinkSky for a multi-product company

One account, many products

Structure before generation