Inspiration
The problem we saw in existing analytics tools What inspired us (Spotify Wrapped, Chess.com, Duolingo) The vision behind the name "LegendScope"
What It Does
Detailed explanation of all 4 core features Real examples of insights users get The "magic" of offline-first functionality
How We Built It
Architecture philosophy (Clean Architecture) Tech stack with reasoning for each choice (in a table!) Week-by-week development timeline AI integration details
Challenges We Ran Into
7 major challenges with solutions: Riot API rate limits IndexedDB debugging Playstyle analysis algorithm Making AI natural Offline-first complexity TypeScript strict mode Mobile split-screen layout
Accomplishments We're Proud Of
7 key achievements: SignaturePlaystyleAnalyzer (900+ lines) Offline-first working perfectly Context-aware AI Design system Clean Architecture FormattedMessage component Split-screen experience
What We Learned
11 lessons across technical, design, and product: Technical: Clean Architecture, TypeScript, AI prompts Design: Design tokens, micro-interactions, context-aware UI Product: Narrative beats statistics, offline builds trust
What's Next for LegendScope
Short-term (3 months): The Arc, Social features, Year-End Wrapped, Live companion, Champion mastery Mid-term (6-12 months): Team analytics, Coach dashboard, Video analysis, Mobile app, ML predictions Long-term (1-2 years): Multi-game support, Creator tools, Educational platform, Public API, Enterprise features
Log in or sign up for Devpost to join the conversation.