TechTree
The ultimate mobile-games market-intelligence platform — understanding every game in depth, triangulating data that today lives in silos across GameRefinery, SensorTower, and App Annie.
Mobile-game product teams rely on fragmented tools today — GameRefinery for feature taxonomies (curated by human analysts), SensorTower for revenue, App Annie for rankings — and none of them actually watch the games. TechTree’s vision was the ultimate platform that understands every mobile game deeply, triangulating the signals those tools fragment.
The product was built as three coordinated systems. A live gameplay capture agent instruments a running mobile game on an Android device or emulator, records every screen and touch interaction as it happens, and auto-annotates each screen against a hand-built 7-domain / 35-category mechanic taxonomy (core loop, monetization, live ops, progression, competitive, UX, analytics). A video analysis pipeline does the same job at scale from public YouTube gameplay, ingesting whole videos, deduplicating frames, and populating a PostgreSQL + pgvector feature database. An AI chatbot analyst sits on top, answering natural-language questions like “show me all the gacha systems in match-3 games” by combining semantic search with SQL joins across the feature, screenshot, and taxonomy tables — and returning explanations with the annotated screenshots inline.
uiautomator2 + adb for device control, YOLO for UI recognition, GPT-4 vision for screen canonicalization. GameMarketer_HybridProcessingFlow/yt-dlp downloads, FFmpeg + perceptual hashing deduplicates frames (91% volume reduction), Gemini 2.5 Pro with context caching annotates the whole video against the taxonomy in a single pass, and results land in PostgreSQL with pgvector embeddings. The v1→v2 rewrite inverted the architecture — from per-frame annotation to whole-video reasoning — and saved two API calls per feature. UnifiedFlow/holistic_annotation_flow_v2.pyfeatures_game, screenshot_feature_xref, and taxonomy. A Pydantic AgentResponse(user_response, developer_note) structure gives every turn a hidden meta-channel that surfaces the agent’s own prompt-quality concerns back to the PM. GameMarketer_Frontend/utils/agent_config.py