[verdict][curated prompt][source: nichemaps.io]
Can I vibecode NicheMaps?
// the value is the network, the data or the infrastructure
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.
confidence: high
what it is: Find mobile niches already making money via live ad spend, IAP, and growth signals
Buildability index · an editorial game
- Price 79 $/month weight: plus 3
- Time closest consolation build: one sitting weight: minus 1
- Category analytics no weight
- Moat proprietary data · infrastructure scale weight: minus 4
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site nichemaps.io (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
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.
what you need
- 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
Honest no: the catalog and ad joins are the moat. Consolation prompt covers a personal competitor watchlist only.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
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. Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- 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
Why people still pay
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.
moat: Proprietary data Infrastructure scale what a moat is
store-wide crawl + ad-library joins at freshness
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- google-play-scraper (opens in a new tab) — Node library for public Play Store listing metadata; does not provide ad-status or creatives
- app-store-scraper (opens in a new tab) — Node library for public App Store listing metadata; same consolation-layer limits
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.