Skip to content
kumo

Products and Store Pages

Each thing the studio sells or gives away is a product: the game, a DLC, a demo, a soundtrack or a bundle. A product’s store page is kept once in kumo:

  • its name and texts in every language;
  • its pictures and trailers;
  • its prices and age ratings;
  • its system requirements;
  • the stores it is sold at.

Find it in Tasks → Production → Products.

  1. Type its title at the top and pick what it is. A DLC, a demo or a soundtrack also asks for the game it belongs to.
  2. Press Add product. It opens beside the list.
  3. Under Stores, pick each store it is sold at. Add its id there and its page’s address.

Everything is saved as you type.

Write the name, short description, description, features, keywords and what’s new for each language. To add a language, enter its code, such as it or pt-BR.

Each text is counted against the tightest limit of the stores the product is sold at, so one text fits every store. For example, Google Play allows 80 characters in the short description and the App Store 30 in its subtitle.

Pick what a picture is for, such as a header capsule, a feature graphic or a screenshot, then press Add pictures or trailers. kumo keeps the original file, which is the one a store needs. Each store’s checklist shows whether a picture is a size that store takes.

Each store has a checklist under the product, field by field and language by language:

  • Copy puts a field on your clipboard to paste into that store’s page, and marks it Copied.
  • A field that changes after you copied it says Changed since copied.
  • A text over the store’s limit, or a picture in a size the store doesn’t take, is counted under to fix.

Sending the text to the App Store and Google Play

Section titled “Sending the text to the App Store and Google Play”

kumo can write a product’s text to these two stores itself:

  • Google Play: the title, the short and full descriptions, the icon, the feature graphic and the phone screenshots.
  • App Store: the name, subtitle, description, keywords and what’s new, and the screenshots, each placed for the device size it fits.

A picture made for one language goes to that language; the rest go to every language. A picture the store already has is not sent again.

  1. In Integrations, connect the store for the whole studio:
    • App Store Connect API (studio): the key ID, the issuer ID and the contents of the .p8 key.
    • Google Play API (studio): the contents of the service account’s .json key.
  2. On the product, give the store its id there: the Apple ID number, or the Play package name such as com.studio.game.
  3. In that store’s checklist, press Send the text to App Store or Send the text to Google Play.

The checklist then shows when the text was sent, by whom, and what happened to each language there:

  • Google Play changes the whole page at once, or nothing if any part is refused. It never replaces changes already in review.
  • The App Store takes the description, keywords and what’s new only while a version is being prepared. Until then, only the name and subtitle change.

Pictures still go in by hand: press Uploaded there once each one is in.

Everyone who can see the board can see its products. A product is changed and deleted by:

  • whoever made it;
  • the people and groups named under Who can change it;
  • whoever manages the project’s access.

Connect each store’s reports for the whole studio in Integrations. Every few hours, kumo then reads the sales, wishlists and installs of each product sold there into Insights:

  • Steam: sales and wishlists. Connect Steam Financial API (studio) with the key of a Financial API Group; a publisher’s ordinary key can’t read sales.
  • App Store: sales. Give App Store Connect API (studio) your vendor number.
  • Google Play: installs and sales. Give Google Play API (studio) your reports bucket (in Play Console, Download reports, then Copy Cloud Storage URI), and let the service account view app information and financial data.

In Insights, start a dashboard from the Store sales template, or chart the store-sales, store-wishlists and store-installs feeds yourself. Revenue is kept in the currency each store reports it in.

Each product lists what its builds became in its stores: the store, the channel, the version and the build, and whether it is live. A publish step in an automation records each one.

A demo also names the automation that builds and publishes it. Press Build and publish it now to start it. Set The demo ends, and its owners are told a week before and on the day. They can choose how to hear about it under Settings → Notifications → Demos about to end.

Under Press kit, tick Publish a press kit. The studio’s server then shows a public page for journalists at /press/<studio>/<address>, built from the product:

  • its text in the visitor’s language;
  • its release date, platforms and prices;
  • its trailers, screenshots, logos and art, each with its original file to download;
  • its age ratings and system requirements;
  • what you add here: the developer, the publisher, the website, the press contact and a word about the studio.

Untick it and the page answers “no press kit here” again.

Hand out keys to streamers, YouTubers and writers without a spreadsheet:

  1. In the product’s Press kit, tick Let creators ask for a key from the press kit, and say what you ask of them (a tag, a date, a disclosure). The press kit then links to a form where a creator asks for a key for one of the product’s stores.
  2. Under Creator keys, pick a store and paste its keys, one a line. kumo keeps each key sealed on the studio’s server and shows only how many are left.
  3. When a creator asks, the product’s owners find it in their inbox. Each request shows the creator’s channel, their audience and a proof word.
    • Check the channel looks for the word in the channel’s description, so nobody can claim someone else’s channel. It needs the studio’s YouTube Data API or Twitch API connection in Integrations; other channels are checked by hand.
    • Send a key gives the creator the next key of their store, shown on the link they got when they asked. Decline says no.
  4. Links to what a creator made with the key, added by them or by you, stay with the request.

Show players what is coming, without showing them your board:

  1. Give the product an address under Press kit first. Then, under Public roadmap, tick Publish the roadmap at the product’s address.

  2. Add cards. Each card is what players read: a title, a few words and a picture.

  3. Move each card through Planned, In progress and Out, and up or down within its column.

  4. Give a card a progress bar if you like:

    • a percent you set yourself;
    • a milestone’s done tasks;
    • how many tasks match a formula, out of a target.

    The bar moves by itself as the work is done. Players see only the percent, never the tasks behind it.

Players open the roadmap from the press kit, or at /hooks/portal/<studio>/<address> on your studio’s server. To vote, they sign in with Discord, Steam or a kumo account. A vote is one per player and card, and a second click takes it back.

Tick Let players suggest ideas and signed-in players can send you ideas, which other players then vote on. An idea shows only once you decide it, under Ideas from players:

  • Show puts it on the roadmap for everyone to vote on.
  • Hide takes it off.
  • Merge into a card files it under one of your cards, whose votes it then adds to.
  • Ban this player stops their votes and ideas from counting, on every roadmap of the studio.