1. Hosted HTML5 game platforms
Status: active_mainline
Platforms host the game and own the ad surface, so we do not need a purchased domain or AdSense site approval first.
Zero-domain: yes | Sales: not needed | Rewarded ads: possible
First signal: Dashboard submitted/in-review status, platform reply, accepted game, then plays and ad revenue after eligibility.
Next action: Submit Neon Lane Dash to CrazyGames and Yandex first, then Playgama/GamePix, using the review-readiness report as moderation evidence.
Current assets and blockers
Assets: Neon Lane Dash ZIP, Upload Limit Panic ZIP, SDK adapters, mobile/desktop screenshots, review-readiness reports
Blockers: Developer account login, CAPTCHA/legal forms, payout setup after approval, moderation wait
2. Douyin mini-game port
Status: prepare_after_mainline_submission
Douyin has huge domestic casual-game traffic and official mini-game ad monetization, including rewarded video. It can monetize through platform ads without direct sales.
Zero-domain: yes | Sales: not needed | Rewarded ads: possible
First signal: Mini-game app created, package uploaded, ad unit IDs available, review submitted.
Next action: After overseas submissions are in review, create a Douyin mini-game developer app and port Neon Lane Dash controls/rewarded assist into the Douyin runtime.
Current assets and blockers
Assets: Existing HTML5 game logic can be ported, Rewarded assist design already exists, Ad safety rules are documented in the current build
Blockers: Douyin Open Platform developer account, real-name/entity and settlement setup, mini-game appId, ad unit IDs, ByteDance mini-game packaging/testing
3. Bilibili mini-game port
Status: backup_domestic_route
Bilibili mini-games can run through the platform with incentive video ads, but traffic and account gates are less direct than Douyin for this project.
Zero-domain: yes | Sales: not needed | Rewarded ads: possible
First signal: Bilibili mini-game account/app draft and package review status.
Next action: Keep pure front-end gameplay, avoid server requests, then port only if Douyin or overseas platforms show demand.
Current assets and blockers
Assets: Existing HTML5 game logic can be ported, No-server gameplay avoids ICP/domain complications
Blockers: Bilibili mini-game account, appId, ad unit IDs, review metadata, server domain/ICP only if remote services are added
4. Free subdomain utility site with ads
Status: secondary_validation
Cloudflare Pages, GitHub Pages, Netlify, Vercel, and similar hosts provide free subdomains. They are good for content and utility validation, but display ads need review and cannot be used as an ad-view gate.
Zero-domain: yes | Sales: not needed | Rewarded ads: not suitable
First signal: Search impressions, downloads, and eventual ad-network approval, not instant revenue.
Next action: Keep the tool site as a discovery/SEO asset while games pursue platform-managed ads.
Current assets and blockers
Assets: PrintableTools Lab, Search Console verification, content pages, tool pages
Blockers: AdSense/ad-network review, traffic ramp, free subdomain review uncertainty, no incentivized ad-click behavior
5. Low-quality short-video or repost channel
Status: rejected_for_risk
Automated low-quality or repost-style content can violate platform policies, burns account trust, and is not a clean path to stable verified revenue.
Zero-domain: yes | Sales: not needed | Rewarded ads: not suitable
First signal: Account views may appear, but monetization is fragile and enforcement risk is high.
Next action: Do not use this as the core route; use short videos only as compliant promotion for accepted games or useful free tools.
Current assets and blockers
Assets: None
Blockers: platform enforcement, creator monetization thresholds, manual content operations, low trust