RiftSnap - Riftbound Card Collection App

Application Overview

RiftSnap is a mobile application designed to help Riftbound players manage their physical and digital card collections. The app enables users to:

Scan Cards: Use device camera with YOLO computer vision to instantly recognize Riftbound cards
Organize Collections: Categorize cards into collections, wishlists, and folders for easy management
Build Decks: Create and organize Riftbound deck lists for theoretical play planning
Track Cards: Monitor card availability, pricing, and personal preferences
Share & Collaborate: Share collections and deck ideas with friends in the Riftbound community

Key Purpose

RiftSnap is a card collection management and deck building tool. It does NOT simulate or automate Riftbound gameplay. Players still play the game manually and socially, the app exists only to help organize cards and plan decks for physical play.

How It Works

Flow & architecture

User Flow

1. User Authentication: Players sign in using Clerk authentication with options for email, Google, Apple, or Discord.

2. Card Scanning: Users point their device camera at a Riftbound card. The on-device YOLO model detects and identifies the card in real-time.

3. Collection Management: Recognized cards are added to the user's collection with quantity tracking.

4. Deck Building: Users organize cards into named decks for planning purposes before physical play.

5. Cloud Sync: Collections and decks sync to the cloud backend for cross-device access and backup.

6. Social Features: Users can share collections and deck lists with other players.

Technical Architecture

Mobile Frontend

Framework: Flutter (iOS, Android)
ML: YOLO v8 ONNX (on-device card detection)
Storage: Hive (local cache)

Backend API

Runtime: Cloudflare Workers
Database: Cloudflare D1 (SQLite)

Card Data Source

Official: Riot Games Riftbound API
Images: Direct from Riot API URLs
Updates: Synced on app launch

Authentication

Provider: Clerk
SSO: Google, Apple
Security: JWT tokens, HTTPS only

Compliance with Riot Games Policies

Compliance details (approved use, monetization, and restrictions)

✓ Approved Use Case

RiftSnap is a Card Collection & Deck Management Tool this is an explicitly approved use case per Riot's Riftbound Digital Tools Policy.

What We Do (Approved)

Card Gallery: Display Riftbound cards from official Riot API
Deck Building: Allow players to organize cards into theoretical deck lists
Collection Management: Track cards owned by players for personal use
Card Information: Display official card text, images, and metadata
Sharing: Let users share deck lists with friends for discussion

Monetization Model

✓ Free Tier Available

Free Plan Includes:

Up to 200 cards in collection
Up to 4 deck lists
Up to 2 collection folders
Unlimited card scanning sessions
Scan history tracking
Basic collection management

Premium Plan Includes:

Unlimited cards in collection
Unlimited deck lists
Unlimited collection folders
Friend system and social sharing
Advanced collection organization
Priority support

All paid features provide transformative value through enhanced organization, collaboration tools, and expanded capacity, not just raw card data access. The free tier provides full core functionality for casual collectors.

What We Don't Do (Prohibited)

❌ No Automated Gameplay: We do not simulate or enforce Riftbound rules

❌ No Skill Ranking: No leaderboards, MMR calculators, or player ranking systems

❌ No Metagame Analytics: We do not publish or track deck win rates, card play rates, or meta statistics

❌ No Betting/Gambling: No wagering or gambling mechanics

❌ No Unofficial Content: All cards sourced exclusively from official Riot API

❌ No Standalone Game Client: This is a collection tool, not a game platform

Asset Usage

All Riftbound card data and images are sourced from the official Riot Games Riftbound API. The app uses:

Official card art via API-provided image URLs
Official English card text from API
Official card metadata and rules text
No external, fan-made, or unofficial card data

Legal Disclaimers

The app displays the required Riot Games disclaimer in a prominent location:

"RiftSnap isn't endorsed by Riot Games and doesn't reflect the views or opinions of Riot Games or anyone officially involved in producing or managing Riot Games properties. Riot Games, and all associated properties are trademarks or registered trademarks of Riot Games, Inc."

Platforms & Distribution

iOS & Android distribution

Supported Platforms

📱 iOS

via Apple App Store

🤖 Android

via Google Play Store

Availability

The app will be distributed through official app stores and will be available for download in all regions where Riftbound is officially supported.

User Privacy & Data

Data collection & security

Data Collection

RiftSnap collects the minimum necessary data to function:

User Identity: Email and username (via Clerk authentication)
Collections: Cards the user has added to their collection
Decks: Deck lists created by the user
Preferences: App settings and user preferences

Data Security

All data transmitted over HTTPS with encryption
Authentication via secure Clerk service
Rate limiting and security headers on all API endpoints
User data isolated per account with access controls
GDPR compliance with data deletion request support

Screenshots & Visual Overview

Below are actual screenshots from the RiftSnap mobile application. Navigate through each screen to see key features:

Live card scanning with real-time detection

Live Card Scanner

Real-Time Card Detection: Users point their camera at a physical card. The YOLO computer vision model instantly recognizes the card and displays information including card name, set code, and current market value. The session total tracks cumulative value of all cards scanned in the current session.

Review scanned cards with quantity controls

Scan Review & Quantity

Scan Review Screen: After scanning, users review detected cards with thumbnail preview, card name, set information, and unit price. Quantity can be adjusted with +/- controls. Cards can be saved to collections or discarded if incorrectly detected.

Scan History

Scan History: Comprehensive log of all scanning sessions with total scans count and cumulative value. Each session entry shows timestamp, number of cards found, and session value. Sessions marked with "New High" indicate peak value scans.

Card collection gallery with portfolio tracking

Collection Management

My Collection: Main collection view displays portfolio value, total card count, and card gallery. Users can search, filter, and organize cards into named binders. Wishlist functionality allows tracking desired cards. No gameplay mechanics, purely organizational.

Deck Library

Deck Library: Users create and manage theoretical deck lists for planning physical gameplay. Shows active deck count and deck details including card count and last modified time. This is a deck planning tool, it does NOT simulate gameplay.

Social Features & Profile

Profile & Sharing: User profile displays nickname, friend management system, and collection sharing controls. Users can share specific collections with friends for collaborative planning. No competitive features, purely social.

Key UI Observations

Dark Mode Interface: Modern, card-focused design optimized for readability
Bottom Navigation: Five main sections: Collection, Scanner, History, Decks, Profile
No Gameplay Elements: No turn timers, health counters, game boards, or match interfaces
Organization Focus: All features centered on cataloging, tracking, and planning
Price Integration: Market value tracking

Riot API Integration

API endpoints & rate limiting

API Endpoints to use

RiftSnap will integrate with Riot's official Riftbound API to fetch:

Card Catalog: Complete list of Riftbound cards with metadata
Card Images: Official card art URLs (thumbnails and full resolution)
Card Text: Official English text and rules information
Set Information: Riftbound set releases and updates

Rate Limiting Compliance

The app implements proper rate limiting:

Development environment respects 10 calls per 10 seconds limit
Production will use appropriate rate limiting for expected volume
Aggressive caching of card data to minimize API calls
Batch requests where possible to optimize API usage