Words Are Flowing

Docs

Words Are Flowing counts what people do in your app, on the device, and at the moment your rules name it either shows a private feedback ask or asks the platform for its native store-review prompt.

Quickstarts

Then: the rules reference and the store policy.

Concepts

Product
One app or game in the portal. Notes, counters and rules all belong to a product.
API key
A product's key (it starts with waf_live_). The SDK sends it with every request; the portal shows it once when it is created, and you can rotate it.
Trigger
A behavioural moment your code names, such as level_completed or trip_finished. Lowercase letters, digits and underscores, up to 40 characters. You report it with TrackAsync; the SDK counts occurrences on the device.
Rules
A JSON document you edit in the portal: for each trigger, when to show the private ask and when to ask for the store prompt. The SDK downloads it in InitializeAsync, so a change needs no app update.
Private ask
A small card, "Anything we should fix?", with an optional 1-to-5 rating and a text box. What the user writes goes to your portal, never to a store.
Store prompt
The platform's own review sheet: Google Play In-App Review on Android, StoreKit on iOS. The platform decides whether it actually appears, and does not say. There is none on the web.
Decision
What one TrackAsync call decided: nothing (with a reason you can log), an ask, or a store prompt. It is returned, and also raised as the DecisionMade event.

Two actions, never a gate

The private ask and the store prompt are two independent actions. The SDK never asks a question in front of the store prompt, and it exposes no call that opens the store prompt directly: it fires only from TrackAsync, which you call from behaviour, never from a button. Your rules may order the two — the ask first, the store prompt later, skipped for anyone who wrote to you recently. That ordering is defensible, not blessed by the stores; the store policy page explains why.