Playground

Import a real app before you read another ASO page.

The playground is AppTide's no-account proof path: resolve a listing, inspect keyword evidence, discover rival pressure, and see the payloads behind the workflow.

Start import See example output

What happens here

1Resolve a real store listing
2Check rank, traffic, and difficulty
3Surface repeated rival pressure

Import

Start with one app

Paste a store URL, bundle ID, or app name. AppTide resolves the real listing before showing anything else.

Keywords

Refresh proof

Inspect keyword rank, traffic, difficulty, language, country, and current store results.

Competitors

Find rival pressure

Discover competitors that repeatedly appear against the terms that matter to this release.

Step 2

Run one live keyword check against that app

Use the imported app as context, then inspect a keyword to see rank, traffic, difficulty, visibility, and the top visible results.

No app selected

Start from a preset or resolve your own app first.

KeywordCountryLanguage

Why this page exists

A live product trial, not a brochure.

Resolve a real listing and inspect the output shape before you sign up.

See the request and response format that a script or agent would use.

Move into a workspace only when you want persistence, API keys, jobs, and billing.

Local workbench

Recent work stays on this device.

Loading local session...

Apps

No local app inputs yet.

Keywords

No local keyword inputs yet.

Competitors

No local competitor inputs yet.

REST request

POST /api/playground/inspect
{
  "application": {
  "appIdentifier": "import app first"
},
  "keyword": "chatgpt",
  "country": "US",
  "language": "en"
}

Response preview

{
  "message": "Import an app, then inspect a keyword to see live ranking data."
}

MCP prompt

Inspect the keyword "chatgpt" for my imported app in US en, then summarize rank, traffic, visibility, and next actions.

AI ASO Analyst

Ask about release keywords, competitors, listing copy, and ranking strategy in natural language.

Ask AI analyst

Proof path

Same product logic as the workspace. No mock data.

The public route should prove the loop before signup. When it repeats, the workspace adds saved history, API keys, MCP access, quotas, and jobs.

What the playground proves

Real store ingestion, not synthetic payloads
Same import, keyword, and competitor logic as dashboard
Validate data shape before committing to a workspace
Copy request or MCP prompt when automation makes sense

Next move after proof

Server historyAPI keysMCP accessUsage windowsRecurring jobs

Create workspace API path

Repeatable ASO

When the public loop works, save it.

Use the playground for first proof. Create a workspace only when app history, AI plans, developer tooling, and recurring refreshes become useful.

Import your app See example output