KAppMaker KAppMaker — Monetization
Before running any command
- Prerequisites —
kappmaker --version(install:npm i -g kappmaker). If a credential is missing the CLI says so; re-runkappmaker config init. - Read
AiGuidelines/first — the PRD, positioning and UI spec already answer most questions.
Re-syncing prices on existing products
"Refresh my prices", "re-apply PPP", "add the new price point everywhere" — after upgrading the CLI or editing prices in the configs, push without re-running the full store setups:
- iOS:
kappmaker appstore-monetization-push [--subscriptions-only | --iap-only]— details in kappmaker-asc. - Android:
kappmaker gpc monetization push [--subscriptions-only | --iap-only]— details in kappmaker-gpc.
Both are idempotent: existing products get their PPP fan-out refreshed, listings and data safety stay untouched.
The provider is a separate skill
This skill covers the products. Wiring them to a provider's dashboard and SDK is that provider's
skill — kappmaker-adapty or kappmaker-revenuecat. A project normally uses ONE of them; the
quick-add commands detect which by its config file (Assets/adapty-config.json /
Assets/revenuecat-config.json). When neither exists and the user is setting up monetization,
ask which provider they want — don't pick silently — then run that provider's setup skill.
Quick-add Subscription / IAP — One new product, no config edit
For iterating on a live app after the initial setup is done. Instead of editing Assets/{googleplay,appstore,adapty}-config.json and re-running the full flow, these add ONE product end-to-end and push to all relevant stores in one command.
Trigger phrases:
- "add a new weekly subscription at $9.99"
- "create a $19.99 monthly subscription for iOS only"
- "add a 50-credit pack for $14.99"
- "create a v2 yearly subscription"
Two commands:
kappmaker subscription add --period <slug> --price <usd> — Play + ASC, then mirrors into the
project's subscription provider so the paywall can serve it (RevenueCat: product + premium
entitlement + package in the default offering; Adapty: product on the Premium access level).
kappmaker iap add --credits <n> --price <usd> — Play + ASC, then the provider (RevenueCat:
credit_pack_access entitlement + credit_pack_<credits> package in the credits_pack offering;
Adapty: product on the credit_pack_access access level).
Which provider gets the push — the --provider flag on both commands:
auto (default: whichever of Assets/adapty-config.json / Assets/revenuecat-config.json exists;
both files → both providers), adapty, revenuecat, both, none. With auto and no config
file, the provider push is skipped with a pointer to the setup commands — relay that choice to
the user ("push this to Adapty or RevenueCat as well?") rather than letting it silently skip.
Common flags (both commands):
| Flag | Default | Notes |
|---|---|---|
--platform |
all |
all / ios / android. iap add includes Adapty only in all. |
--product-version <n> |
1 |
Bumps every v marker in the IDs. For subs: --product-version 2 → myapp.premium.weekly.v2.999.v2 + myapp.premium.weekly.v2 + autorenew-weekly-999-v2. For IAPs: v1 stays unsuffixed; v2+ appends _v2 to the credit-pack ID. (Named --product-version rather than --version to avoid clashing with Commander's root kappmaker --version.) |
--bundle-id <id> |
from configs | iOS bundle ID override — use when Assets/appstore-config.json doesn't exist yet. |
--package-name <pkg> |
from configs | Android package name override — use when Assets/googleplay-config.json doesn't exist yet. |
--name <text> |
derived | Localized display name. Subs default the ASC name to "<Period> Premium" (e.g. Weekly Premium) and the Play listing title to "<AppName> <Period> Premium"; IAPs default to "<credits> Credit Pack". |
--description <text> |
derived | Subs: period-derived (e.g. weekly → "Full access for one week."). IAPs: "<credits> credits to use in the app.". |
--review-screenshot <path> |
top-level review_screenshot |
Apple required — without one, products stay in MISSING_METADATA. |
--app-name <name> |
from configs | Override if no config exists yet. |
Subscription-only flags:
| Flag | Default | Notes |
|---|---|---|
--period <slug> |
required | weekly / monthly / twomonths / quarterly / semiannual / yearly |
--price <number> |
required | USD anchor; PPP fans the rest |
--group <ref> |
first group in appstore-config.json |
If the ref doesn't exist on ASC, it's auto-created |
--group-name <text> |
inherits from config group's localizations[0].name, else "Premium Access" |
Used only when auto-creating a new group |
IAP-only flags:
| Flag | Default | Notes |
|---|---|---|
--credits <number> |
required | Positive integer |
--price <number> |
required | USD anchor; PPP fans the rest |
What it creates:
- Auto-aligned product IDs across stores:
{appname}.premium.<period>.v<N>.<priceDigits>.v<N>for ASC,{appname}.premium.<period>.v<N>for the Play product +autorenew-<period>-<priceDigits>-v<N>for its base plan,credit_pack_{credits}_{priceDigits}_{appname}for credit packs everywhere. The full alignment table lives in kappmaker-gpc. - Full PPP fan-out on both stores — territory mechanics and counts are the platform skills' business: kappmaker-asc (CSV import) and kappmaker-gpc (
convertRegionPrices+ native currencies). - en-US listing/localization on both stores.
- Review screenshot upload on ASC (resized to 1290 × 2796 if needed).
- For new ASC subscription groups: auto-created with proper en-US localization so the App Store UI shows the right group name.
Idempotency: safe to re-run. Existing products are PATCHed (Play) or report "already exists — refreshing pricing" (ASC) and re-apply the full PPP fan-out. To stand up a separate v2 line, use --product-version 2.
When to use vs. the full flow:
- Use
subscription add/iap addwhen iterating on an existing app — adding one more price point, launching a v2, or replacing stuck legacy products. - Use
create-appstore-app/gpc setupfor initial setup with the full canonical product set, or when you need multi-locale, intro offers, or custom regional pricing overrides that aren't covered by the quick-add flags.
Not yet supported via flags (require editing the JSON config):
- Free trials / intro offers
- Multi-locale listings
- Custom per-territory price overrides (PPP covers the common case)
Where this sits in the flow
- Before this: kappmaker-asc and/or kappmaker-gpc — products need the store app record to exist first.
- After this: kappmaker-adapty to wire the products to the provider.