Counting Guidelines
To ensure fair, consistent rankings, all submissions must follow these rules. Submissions that deviate will be rejected during review.
✅ What Counts as a Click
- •Tap / Click — Pressing a button, link, icon, or interactive element. Count: 1
- •Swipe to confirm— A swipe gesture that triggers an action (e.g., "Swipe to submit"). Count: 1
- •Selection from dropdown/menu — Opening a dropdown AND selecting an option. Count: 2 (one to open, one to select)
- •Toggle / Checkbox — Tapping a toggle or checkbox. Count: 1
- •Tab selection — Clicking a tab to switch views. Count: 1
❌ What Does NOT Count
- •Typing text — Entering text into an input field (e.g., typing a stock symbol or amount). Count: 0
- •Scrolling — Scrolling up or down on a page. Count: 0
- •Waiting / Loading — Waiting for a page or spinner to load. Count: 0
- •Reading / Reviewing — Simply looking at a confirmation screen before acting. Count: 0
- •Navigating to the app — Opening the app itself or navigating to the website. Count: 0 (start from within the app)
- •Biometric/Face ID prompts — System-level auth prompts triggered by the OS, not the app. Count: 0
📍 Standardized Starting Point
Every action begins from the main screen after login— the app's home or dashboard screen immediately after signing in.
Since every app requires login, the login process is never counted as part of any other action. Login and signup each have their own dedicated category if you want to measure how many clicks those flows take.
This removes ambiguity about where to start counting. For example, to count “Place Stock Buy Trade” clicks on Robinhood, you start from the home screen after login — not from a previous stock detail page, and not including the login steps.
Only exception — pre-login actions:
- •Categories explicitly marked as pre-login (e.g., Create Account, Login) start from the app's entry or landing screen — before authentication. These are the only categories where the auth flow itself is what's being measured.
📋 Scenario Standardization
To ensure apples-to-apples comparisons, all submissions must follow the standardized scenario defined for each action category. If a scenario is specified, you must:
- 1.Use the account type specified (e.g., free tier, default settings)
- 2.Start from the standardized starting point — the main screen after login (or the app entry screen for pre-login actions)
- 3.Use default settings — no custom shortcuts, widgets, or personalized layouts
- 4.Document the app version and device used
📸Screenshot & Evidence Requirements
- •Every step must have a screenshot. No exceptions.
- •Screenshots must clearly show the UI element being clicked.
- •Video recordings are optional but strongly encouraged.
- •The step description must match what's visible in the screenshot.
🔒 PII Redaction (MANDATORY)
You MUST redact all personally identifiable information before uploading. Submissions with visible PII will be immediately rejected.
What must be redacted:
- • Full name (on account screens)
- • Email address
- • Phone number
- • Account number or ID
- • Account balance or holdings
- • Social Security Number or Tax ID
- • Address
- • Any other personal data
Tip:Use your device's built-in markup tools or any image editor to draw solid rectangles over sensitive information before uploading.
⚠️ Common Rejection Reasons
- PII visible — Screenshots contain unredacted personal information
- Click count mismatch — Sum of step clicks ≠ total click count
- Missing screenshots — One or more steps lack screenshot evidence
- Wrong scenario— Submission doesn't follow the standardized scenario
- Unclear steps— Step descriptions don't match what's shown in screenshots
- Duplicate — Same click count already exists for this app + action with identical steps