Common in the set, missing here
- Skip on onboarding 3 of 5
- Suggestions on an empty search 4 of 5
- Browse before sign-in 4 of 5
- Recently viewed rail 3 of 5
None of these came from a backlog. They came from screens other apps already ship.
Not the five in your pitch deck. The dozens already on their phone. FlyTrap lines your features up against the same feature in all of them, screen for screen.
com.ubercab.eats
Your main features next to the same features in other apps.
A food delivery app's board came back with a travel app, a music player and a document scanner. That is the set its users actually learned from.
A delivery app inherits expectations from the last checkout its user finished. That app was rarely a delivery app.
Onboarding, browse, search, empty states, permission prompts. The same handful repeats in every app on the phone.
Someone wrote it in a deck two years ago. These columns come from screens we crawled, not from a market map.
A board like this needs two things at once: a crawl of your build, and crawls of everyone else's. We already run both.
The exploration run already opened every screen in your build. Nothing extra to record.
Screens group into features from what is on them, not from what your spec called them.
The same feature already sits in thousands of apps we have crawled. Those become your columns.
Your feature is the row. Every match is a column. What nobody matched stays visible as a gap.
Matched screens are countable. Open a row and the numbers under it come with it.
Half your features exist in the set. The interesting reading is the other half, in both directions.
None of these came from a backlog. They came from screens other apps already ship.
Rare is not the same as good. The board tells you which one you are looking at, and leaves the call to you.
One run fills the board with apps you would never have thought to open. No screenshots to gather, no Figma wall to keep alive.