OpenCreators in one minute
- Service and digital-product pages explain a creator-authored offer and can start an OpenCreators purchase.
- Game pages use game catalog data and available external-store offers.
- Creators should verify full text, type-specific fields, media, price, navigation, and action behavior.
A storefront card supports scanning; a product page supports a decision. OpenCreators product pages load a public product record and present the creator, media, title, description, price, and type-specific information needed for the next action.
The page must follow the product kind. A creator service is not a game offer, and a game page should not reuse service assumptions. This distinction affects description source, detail sections, price data, and the primary button.
Core product information
The public product record includes a product identifier, creator identifier, name, optional description, price and currency, product kind, optional service type and duration, media, engagement data, share information, and optional game payload.
The interface chooses the best available image variant for the layout. Missing optional fields should disappear cleanly. A page should never fill a missing duration, developer, review count, or offer with invented text.
Service and digital-product actions
For creator-authored products, the Buy action requests a purchase record using an idempotency key. The response can include order number, amount, currency, status, redirect URL, paid time, and error information. The interface should represent the actual response rather than assuming immediate completion.
The creator description remains central. It should explain fulfillment and communication. The page cannot compensate for an unclear service definition after the buyer has already committed.
Game-specific detail
A game payload can contain short and full descriptions, release date, review count, covers, developers, publishers, tags, and offers. The page can also include rich descriptive content such as headings, media, or video when present in the catalog source.
Selecting a game offer calls an offer-specific redirect endpoint. The external destination controls the final transaction, so OpenCreators should display the store and offer accurately and avoid styling that makes it look like a platform-owned checkout.
Navigation and responsive behavior
A detail page can be opened from a storefront, Discover, Home, or a shared link. If browser history exists, a back control can return to the previous page. If a shared link has no meaningful history, the control should lead Home instead of pointing to an empty past.
Check desktop and mobile independently. Image ratio, long titles, tag wrapping, rich descriptions, video controls, and sticky actions can behave differently at narrow widths.
Frequently asked questions
Why can two product pages have different actions?
The action follows product type. Creator products can use an OpenCreators purchase flow, while game offers can redirect to an external store.
Where does a game's short description come from?
It comes from the game data in the product payload. Service cards and pages use the creator product description instead.