Vibecode NicheMaps
track this build5 steps, step by step0%NOT REALLY · don't bother
price $25.99/moyou'd save $311.88/yrbuild time closest consolation build: one sittingcategory 📊 analyticsreplaced by 0 people
You can build a personal watchlist that checks a handful of store listings and ad-library pages, but NicheMaps' value is a continuously refreshed catalog of millions of iOS/Android apps with ad-status, IAP, velocity, and creative evidence you cannot rebuild in one sitting.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of NicheMaps. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # NicheMaps indie build ## Goal Build the smallest trustworthy replacement for the core NicheMaps workflow for one developer or a tiny team. ## Scope Track a small list of competitor apps, pull public store metadata, open their Google Ads Transparency and Meta Ad Library pages, and note which creatives are still running. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 5M+ app catalog with searchable filters - live ad-running status across the whole store - IAP and install/rating velocity joins - aggregated Google and Meta creative history - working-niche discovery at market scale If those capabilities are essential, use google-play-scraper instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a local competitor-app watchlist, the one slice of NicheMaps worth building solo. Requirements: - Node 22 + TypeScript + SQLite + a tiny localhost UI (Vite + React is fine). - apps.json lists up to 25 apps with platform (ios|android), store id, and optional advertiser name. - `npm run refresh` fetches public store listing fields (title, rating, ratings count, free/paid, last updated) via the facundoolano google-play-scraper / app-store-scraper libraries. Respect rate limits; sleep between requests. - For each app, store deep links to Google Ads Transparency and Meta Ad Library search URLs (domain or advertiser name). Do not pretend you have store-wide ad-running bitmaps. - Optional: with PLAYWRIGHT=1, open those two URLs headlessly and save a dated HTML snapshot plus a count of creatives mentioning the app name. Expect blocks; document proxy/env needs and fail soft. - SQLite tables: apps, snapshots, creative_checks. Keep full history. - Localhost dashboard: table of watched apps, sparkline of ratings-count delta, last creative-check time, and buttons to open the transparency URLs. - Secrets in .env only (.env.example shipped). No accounts, no cloud, no telemetry. - Out of scope: crawling the whole store, IAP detection at scale, "apps advertising now" filters, and niche ranking across categories. That dataset is the subscription. - README: setup, refresh cron example, honest statement that NicheMaps is a proprietary multi-store + ad-library index and this replaces a personal watchlist, not the catalog. ## Required capabilities - App Store / Play public listing access - Google Ads Transparency Center - Meta Ad Library - SQLite or local JSON storage - optional residential proxy if scraping at volume ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of NicheMaps. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # NicheMaps indie build ## Goal Build the smallest trustworthy replacement for the core NicheMaps workflow for one developer or a tiny team. ## Scope Track a small list of competitor apps, pull public store metadata, open their Google Ads Transparency and Meta Ad Library pages, and note which creatives are still running. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 5M+ app catalog with searchable filters - live ad-running status across the whole store - IAP and install/rating velocity joins - aggregated Google and Meta creative history - working-niche discovery at market scale If those capabilities are essential, use google-play-scraper instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a local competitor-app watchlist, the one slice of NicheMaps worth building solo. Requirements: - Node 22 + TypeScript + SQLite + a tiny localhost UI (Vite + React is fine). - apps.json lists up to 25 apps with platform (ios|android), store id, and optional advertiser name. - `npm run refresh` fetches public store listing fields (title, rating, ratings count, free/paid, last updated) via the facundoolano google-play-scraper / app-store-scraper libraries. Respect rate limits; sleep between requests. - For each app, store deep links to Google Ads Transparency and Meta Ad Library search URLs (domain or advertiser name). Do not pretend you have store-wide ad-running bitmaps. - Optional: with PLAYWRIGHT=1, open those two URLs headlessly and save a dated HTML snapshot plus a count of creatives mentioning the app name. Expect blocks; document proxy/env needs and fail soft. - SQLite tables: apps, snapshots, creative_checks. Keep full history. - Localhost dashboard: table of watched apps, sparkline of ratings-count delta, last creative-check time, and buttons to open the transparency URLs. - Secrets in .env only (.env.example shipped). No accounts, no cloud, no telemetry. - Out of scope: crawling the whole store, IAP detection at scale, "apps advertising now" filters, and niche ranking across categories. That dataset is the subscription. - README: setup, refresh cron example, honest statement that NicheMaps is a proprietary multi-store + ad-library index and this replaces a personal watchlist, not the catalog. ## Required capabilities - App Store / Play public listing access - Google Ads Transparency Center - Meta Ad Library - SQLite or local JSON storage - optional residential proxy if scraping at volume ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of NicheMaps. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # NicheMaps product brief ## Problem You can build a personal watchlist that checks a handful of store listings and ad-library pages, but NicheMaps' value is a continuously refreshed catalog of millions of iOS/Android apps with ad-status, IAP, velocity, and creative evidence you cannot rebuild in one sitting. ## Product outcome Track a small list of competitor apps, pull public store metadata, open their Google Ads Transparency and Meta Ad Library pages, and note which creatives are still running. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - App Store / Play public listing access - Google Ads Transparency Center - Meta Ad Library - SQLite or local JSON storage - optional residential proxy if scraping at volume ## Explicit non-goals for v1 - 5M+ app catalog with searchable filters - live ad-running status across the whole store - IAP and install/rating velocity joins - aggregated Google and Meta creative history - working-niche discovery at market scale ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a local competitor-app watchlist, the one slice of NicheMaps worth building solo. Requirements: - Node 22 + TypeScript + SQLite + a tiny localhost UI (Vite + React is fine). - apps.json lists up to 25 apps with platform (ios|android), store id, and optional advertiser name. - `npm run refresh` fetches public store listing fields (title, rating, ratings count, free/paid, last updated) via the facundoolano google-play-scraper / app-store-scraper libraries. Respect rate limits; sleep between requests. - For each app, store deep links to Google Ads Transparency and Meta Ad Library search URLs (domain or advertiser name). Do not pretend you have store-wide ad-running bitmaps. - Optional: with PLAYWRIGHT=1, open those two URLs headlessly and save a dated HTML snapshot plus a count of creatives mentioning the app name. Expect blocks; document proxy/env needs and fail soft. - SQLite tables: apps, snapshots, creative_checks. Keep full history. - Localhost dashboard: table of watched apps, sparkline of ratings-count delta, last creative-check time, and buttons to open the transparency URLs. - Secrets in .env only (.env.example shipped). No accounts, no cloud, no telemetry. - Out of scope: crawling the whole store, IAP detection at scale, "apps advertising now" filters, and niche ranking across categories. That dataset is the subscription. - README: setup, refresh cron example, honest statement that NicheMaps is a proprietary multi-store + ad-library index and this replaces a personal watchlist, not the catalog. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted NicheMaps capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# NicheMaps indie build ## Goal Build the smallest trustworthy replacement for the core NicheMaps workflow for one developer or a tiny team. ## Scope Track a small list of competitor apps, pull public store metadata, open their Google Ads Transparency and Meta Ad Library pages, and note which creatives are still running. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 5M+ app catalog with searchable filters - live ad-running status across the whole store - IAP and install/rating velocity joins - aggregated Google and Meta creative history - working-niche discovery at market scale If those capabilities are essential, use google-play-scraper instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a local competitor-app watchlist, the one slice of NicheMaps worth building solo. Requirements: - Node 22 + TypeScript + SQLite + a tiny localhost UI (Vite + React is fine). - apps.json lists up to 25 apps with platform (ios|android), store id, and optional advertiser name. - `npm run refresh` fetches public store listing fields (title, rating, ratings count, free/paid, last updated) via the facundoolano google-play-scraper / app-store-scraper libraries. Respect rate limits; sleep between requests. - For each app, store deep links to Google Ads Transparency and Meta Ad Library search URLs (domain or advertiser name). Do not pretend you have store-wide ad-running bitmaps. - Optional: with PLAYWRIGHT=1, open those two URLs headlessly and save a dated HTML snapshot plus a count of creatives mentioning the app name. Expect blocks; document proxy/env needs and fail soft. - SQLite tables: apps, snapshots, creative_checks. Keep full history. - Localhost dashboard: table of watched apps, sparkline of ratings-count delta, last creative-check time, and buttons to open the transparency URLs. - Secrets in .env only (.env.example shipped). No accounts, no cloud, no telemetry. - Out of scope: crawling the whole store, IAP detection at scale, "apps advertising now" filters, and niche ranking across categories. That dataset is the subscription. - README: setup, refresh cron example, honest statement that NicheMaps is a proprietary multi-store + ad-library index and this replaces a personal watchlist, not the catalog. ## Required capabilities - App Store / Play public listing access - Google Ads Transparency Center - Meta Ad Library - SQLite or local JSON storage - optional residential proxy if scraping at volume ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# NicheMaps product brief ## Problem You can build a personal watchlist that checks a handful of store listings and ad-library pages, but NicheMaps' value is a continuously refreshed catalog of millions of iOS/Android apps with ad-status, IAP, velocity, and creative evidence you cannot rebuild in one sitting. ## Product outcome Track a small list of competitor apps, pull public store metadata, open their Google Ads Transparency and Meta Ad Library pages, and note which creatives are still running. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - App Store / Play public listing access - Google Ads Transparency Center - Meta Ad Library - SQLite or local JSON storage - optional residential proxy if scraping at volume ## Explicit non-goals for v1 - 5M+ app catalog with searchable filters - live ad-running status across the whole store - IAP and install/rating velocity joins - aggregated Google and Meta creative history - working-niche discovery at market scale ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a local competitor-app watchlist, the one slice of NicheMaps worth building solo. Requirements: - Node 22 + TypeScript + SQLite + a tiny localhost UI (Vite + React is fine). - apps.json lists up to 25 apps with platform (ios|android), store id, and optional advertiser name. - `npm run refresh` fetches public store listing fields (title, rating, ratings count, free/paid, last updated) via the facundoolano google-play-scraper / app-store-scraper libraries. Respect rate limits; sleep between requests. - For each app, store deep links to Google Ads Transparency and Meta Ad Library search URLs (domain or advertiser name). Do not pretend you have store-wide ad-running bitmaps. - Optional: with PLAYWRIGHT=1, open those two URLs headlessly and save a dated HTML snapshot plus a count of creatives mentioning the app name. Expect blocks; document proxy/env needs and fail soft. - SQLite tables: apps, snapshots, creative_checks. Keep full history. - Localhost dashboard: table of watched apps, sparkline of ratings-count delta, last creative-check time, and buttons to open the transparency URLs. - Secrets in .env only (.env.example shipped). No accounts, no cloud, no telemetry. - Out of scope: crawling the whole store, IAP detection at scale, "apps advertising now" filters, and niche ranking across categories. That dataset is the subscription. - README: setup, refresh cron example, honest statement that NicheMaps is a proprietary multi-store + ad-library index and this replaces a personal watchlist, not the catalog. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted NicheMaps capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent
They pay for the dataset and the joins, not the UI. Knowing which niches are buying ads right now across millions of apps is the product; a DIY watchlist only covers apps you already know to check.
x5M+ app catalog with searchable filters
xlive ad-running status across the whole store
xIAP and install/rating velocity joins
xaggregated Google and Meta creative history
xworking-niche discovery at market scale
share on X ↗"I just replaced NicheMaps ($25.99/mo) with one prompt"
NicheMaps pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/workspace | $0/workspace | Full app catalog and metadata, installs, ratings, growth and filters; 1 ad-running app emailed per day; ad-status signals and creatives excluded |
| premium | $25.99/workspace | $19.99/workspace | Full catalog plus ad-status filtering, live Google and Meta creatives, sustained-spend/niche-velocity views, and CSV-ready tables; no numeric query/export cap published |
free tierFull catalog browsing/search and app metadata; 1 ad-running app emailed daily; no access to catalog-wide ad status or ad creatives
billingmonthly + annual; monthly has 20% off first month and an extra 7 days; separate 7-day card-required trial; cancel via Stripe
hidden costsThe 7-day trial keeps a card on file and converts to paid unless canceled; the $20.79 monthly headline is only the first month, with renewals at $25.99.
verified 2026-08-12 · source ↗
Vibecode NicheMaps
Not really. NicheMaps's value is not the code: Consolation prompt covers a personal competitor watchlist only. See the honest breakdown above.
How much does NicheMaps cost?
NicheMaps costs about $25.99/month (Premium, checked 2026-08-12), which is $311.88 per year.
What do I lose by replacing NicheMaps?
Honestly: 5M+ app catalog with searchable filters; live ad-running status across the whole store; IAP and install/rating velocity joins; aggregated Google and Meta creative history; working-niche discovery at market scale. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to NicheMaps?
Yes: google-play-scraper (Node library for public Play Store listing metadata; does not provide ad-status or creatives), app-store-scraper (Node library for public App Store listing metadata; same consolation-layer limits). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.