Cuewise

Inspiration

Streaming gave us more to watch—and somehow made deciding what to watch harder.

Cuewise started with a simple question: what if a recommendation product made fewer decisions instead of giving you more options?

Rather than another endless grid of titles, Cuewise asks about the context that matters tonight: what services you have, what mood you're in, and how much time you have. Then it makes one confident recommendation.

The goal is to turn “What should we watch?” from a 20-minute search into a small ritual.

What it does

Cuewise helps you decide what to watch tonight.

Choose your streaming services, tell Cuewise your mood and available time, and it narrows the catalog to one recommendation—your Cue.

Instead of presenting another list to evaluate, Cuewise explains why this title fits tonight and lets you watch it, save it, say you've already seen it, or ask for another.

For returning users, the experience gets shorter. Cuewise already knows things like your streaming services and can use your interactions to make future decisions more useful.

How we're building it

Cuewise began as a web product built in Replit and is now becoming a native mobile product for Shipaton.

The product combines a recommendation system with an interaction and motion system built around a principle we call Progressive Resolution:

«As certainty increases, the interface becomes less necessary.»

Services recede. Mood becomes atmospheric. Time becomes focused. Signals converge during Finding. Then the interface resolves into one recommendation.

For Shipaton, we're taking that foundation into Expo / React Native, preserving the recommendation engine and product identity while redesigning interactions where native mobile calls for something different.

We're also integrating RevenueCat to explore a sustainable Cuewise+ model without putting monetization in front of the product's first moment of value.

Challenges

One of the hardest problems hasn't been generating recommendations. It's been deciding what not to show.

Streaming products are optimized for browsing. Cuewise is intentionally optimized for deciding.

That has forced us to think carefully about recommendation quality, streaming availability, repeat recommendations, already-seen titles, provider accuracy, motion, cognitive load, and how much explanation a recommendation actually needs.

The Shipaton challenge adds another layer: taking an existing web experience into native mobile without simply wrapping the website or rebuilding working systems unnecessarily.

What's next

The next phase is about proving Cuewise can become a habit, not just a compelling demo.

We're focused on shipping the native app early enough to spend the rest of Shipaton learning from real usage: activation, repeat recommendations, retention, saves, watch intent, and eventually conversion to Cuewise+.

The question we're trying to answer by September 30 isn't just “Can we ship it?”

It's “Will people come back tomorrow night?”