Playground

Try the core workflow before you create a workspace.

The playground shows what AppTide actually does: resolve a real app, inspect live keywords, discover competitors, and expose the same result as JSON and MCP-ready prompts.

Try app import Read docs

✦ Import real App Store and Google Play listings
✦ Inspect live keyword rankings before saving anything
✦ Discover visible competitors from repeated search results
✦ Copy the same workflow into REST or MCP

AppTide playground showing app import, keyword inspection, and competitor discovery.

Step 01

Start with one app

Paste a bundle ID, package name, or search term. The playground resolves a normalized app record without creating a workspace first.

Step 02

Inspect a keyword live

Run a real keyword check to see rank, traffic, difficulty, visibility, and the top apps appearing for that term.

Step 03

Turn it into automation

Copy the request shape, JSON response, or MCP prompt straight into your own tooling once the result looks right.

Step 1

Resolve a real listing before you save anything

Search by app name, bundle ID, or package name. The playground returns the same normalized app payload the product uses internally.

No app selected

Start from a preset or resolve your own app first.

Search termApp identifierPlatform

CountryLanguage

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/import
{
  "search": "Notion",
  "appIdentifier": "optional",
  "platform": "ios",
  "store": "app_store",
  "primaryLanguage": "en",
  "country": "US"
}

Response preview

{
  "message": "Resolve an app to see the normalized payload."
}

MCP prompt

Import a real app listing, normalize the metadata, and explain which fields should be saved to my workspace.

What the playground proves

This is not a mock demo. It is the product boundary made visible.

The public playground uses the same import, keyword, and competitor logic that powers the logged-in workspace. It exists so a developer can tell, in a few minutes, whether AppTide is worth trusting with a real app workflow.

Use it when you want to validate the data shape. Move into a workspace when you want saved context, crawl jobs, API keys, billing, and repeatable automation.

Next move

Save the workflow once the live result looks right.

The playground now keeps a local browser workbench for recent app, keyword, and competitor inputs. Create a workspace when you want server-side history, shared context, usage windows, API keys, MCP access, and recurring refresh jobs.

Create workspace Compare plans