FlyTrap Competitor Teardown New Any of 1,600+ apps, or pick a new one

Their app,
taken apart in Figma.

Pick a competitor from the Play Store. FlyTrap installs it, explores it like a first-time user, and hands back the navigation map, the user flows and the feature list. Then you paste the whole thing into Figma.

The Saturday nobody bills for

Competitor research is a weekend of screenshots

Everyone has done the teardown by hand once. Almost nobody has done it twice, which is why the board in your Figma file is from two releases ago.

  1. 01

    Install theirs

    Four competitor apps, four sign-ups, four onboarding tours before you see a single real screen.

  2. 02

    Screenshot everything

    Two hundred screenshots on a Saturday. Half of them are the same screen with a different toast.

  3. 03

    Rebuild it in Figma

    Drag, align, draw arrows. By the end you remember the flows, nobody else on the team does.

  4. 04

    It expires

    Their next release moves the paywall and the whole board is wrong. Nobody redoes it.

What comes out

Four artifacts from one run

A teardown is only useful if it lands somewhere you already work. Every artifact traces back to a screen the run opened.

  • Navigation map

    Every screen the run reached and every transition between them. Dead ends and loops included, because those are the interesting parts.

    23 screens · 31 transitions
  • User flows

    Start-to-finish paths named from what they do. Scan a meal. Start a trial. Edit a goal. Each one with its screens in order.

    6 flows · 5 to 14 steps
  • Feature list

    Screens grouped into the features they make up, in the same vocabulary your own build is described in. Diffable against yours.

    11 features · each with evidence
  • Figma export

    The map copied to your clipboard as frames, images and vectors. One paste and it is editable in Figma.

    Screenshots as images · arrows as vectors
How it works

The crawler that tests your build, pointed at theirs

Nothing here is new machinery. Exploration already opens every screen of an app you upload. Picking from the store just means the app does not have to be yours.

  1. 01

    Pick from the store

    Search the Play Store by name inside FlyTrap. No APK to find, no device to borrow. The same picker you use for your own app.

  2. 02

    We install and explore

    A fresh install on a real device, opened like a curious first-time user. Same crawler that tests your build, pointed elsewhere.

  3. 03

    Screens become flows

    Every screen is fingerprinted, grouped into features and chained into the paths the run actually walked.

  4. 04

    Paste into Figma

    Export copies the whole map. Paste it into any Figma file and it arrives as frames you can move, annotate and present.

One flow, opened

Six taps from Home to a logged meal

A flow is the screens in order plus what it took to get between them. Open one and the timing, prompts and detours come with it.

dashboard.flytrap.dev/teardown/com.viraldevelopment.calai/flows/scan-a-meal
Flow 04
Scan a meal

Camera to logged entry

6 steps 5 screens 2.1s to result
Home Camera Result Edit portion Logged
  1. 01 tap Scan on the Home tab bar 1 tap from launch
  2. 02 prompt Camera permission asked at first use, not at launch
  3. 03 tap Shutter no crop step
  4. 04 wait Result: calories and macros 2.1s, one primary action
  5. 05 tap Edit portion size optional, one sheet
  6. 06 tap Save back on Home, meal logged
Every step is a real tap on a real device Screens link back to the navigation map
The feature list

Every feature they ship, as a list you can diff

Screens group into features by what is on them. Because your own build is described the same way, the two lists line up without anyone translating.

dashboard.flytrap.dev/teardown/com.viraldevelopment.calai/features
11 features

Cal AI

com.viraldevelopment.calai

4 of 8 not in your build
Feature Their screens In your build
Meal photo scan 6 screens Missing
Barcode scanner 3 screens Have
Macro targets 4 screens Have
Streaks and badges 5 screens Missing
Water tracking 2 screens Have
Weekly report 3 screens Have
Referral code 2 screens Missing
Rating prompt inside onboarding 1 screen Missing
Eight of eleven shown The right column fills in once your own build has been crawled
Into Figma

The whole map, one paste

Export copies the navigation map to your clipboard. Paste it into any Figma file and the screenshots arrive as images, the arrows as vectors and the labels as text. Everything is editable.

Read it correctly

What a teardown contains, and what it doesn't

It is a record of what a fresh install showed a first-time user. That is a lot, and it is also exactly where it stops.

What it contains

  • Every screen a first-time user can reach from a fresh install, in the order the run reached it.
  • Each transition as a real tap, swipe or prompt, with timing.
  • Features named from the screens, in the same vocabulary as your own build.
  • A Figma-ready map that stays attached to the run it came from.

What it does not

  • Not their code, backend or analytics. Only what the screen showed.
  • Not a verdict. Fourteen onboarding screens is a fact, not a mistake.
  • Not a market map. You choose the apps, the store does not.
  • Not a one-off. Run it again after their next release and diff.

The apps you pick are public and the device is ours. What comes back is what anyone with the app installed could have seen, written down properly for once.

Pick a competitor and watch it come apart

Search the store, pin the apps you care about, and get the map, flows and feature list back. The Figma file is one paste away.