Strib Bot

AI-Powered Search for Minnesota State Fair

Device Screen

Project Scope

Platform: Responsive Web
Timeline: 2024
Current Stage: Live

Role & Team

Product Designer (Contract)
Star Tribune Team
ScreenGenius Partnership

Technical Details

React/Next.js
OpenAI GPT-4
Vercel

Key Metrics

6,900 User Sessions
12,000 AI Searches
1.9M Fair Visitors
PROBLEM SPACE

Two clients. Competing goals. One product. The challenge wasn't solving discovery—it was deciding whose version ships.

THE CHALLENGES

AI vs. Editorial

ScreenGeni.us wanted to showcase semantic search. Star Tribune wanted to showcase journalism. Same product, competing goals.

Trust vs. Utility

AI could surface great matches. Users with dietary restrictions couldn't verify the system wasn't hallucinating ingredients.

Depth vs. Speed

Star Tribune had rich content worth exploring. Users had 12 seconds of attention in a hot, crowded environment.

THE OPPORTUNITY

How do we balance editorial showcase, AI demonstration, and user needs—when each pushes against the others?

Progressive Disclosure

Lead with editorial (Star Tribune wins), surface AI for power users (ScreenGeni.us wins).

Transparent Attribution

Sparkle emoji distinguished AI from journalism. Users trusted both more when they knew which was which.

Designed for the Environment

12 seconds of attention in crowds and heat. Scannable cards first, deep content for users who want it.

Home Page: From AI-First to Editorial Navigation

Star Tribune wanted badges. ScreenGeni.us wanted search. Users just wanted to find food fast.

V2 - How might we showcase editorial while maintaining AI search? screenshot

Search Results: Building Trust Through Transparency

AI mistakes become publisher mistakes. Star Tribune cut any data they couldn't validate—price, distance, ingredients.

V2 - How might we clarify sources while simplifying? screenshot

Vendor Detail: From Prototype to Ship

V1 explored what's possible. V2 shipped what timeline, data, and scope allowed.

V2 - Shipped: What could we build and verify? screenshot
INSIGHTS

What I Learned

1

Publisher Stakes Are Different

News organizations can't treat AI like a startup. One wrong ingredient claim is a credibility crisis. Star Tribune cut anything editorial couldn't verify—that's not scope creep, that's brand protection.

2

Prototypes Explore, Products Ship

V1 asked "what's possible?" V2 asked "what can we build, verify, and support?" The gap between those questions is the actual job.

3

Engineering Tradeoffs Are Design Decisions

What engineers can scrape, verify, and ship shapes the product as much as wireframes do. Design with build constraints, not against them.

Got more churn than a butter factory?

Let's whip your product into shape!

Get in Touch

Designed & Built by Drew Miller

© 2026. Version 3.1.4