Documentation

Creating your account

You can sign up using Google, GitHub, or a magic link sent to your email. Head to the login page to get started.

• Google or GitHub — click the provider button and authorize access. Your account is created automatically.
• Magic link — enter your email and we'll send you a one-time sign-in link. No password needed.

Choosing your role

When you first sign up, you choose a role that determines what you can do on the platform:

• Builder — submit apps for testing and review bug reports.
• Tester — claim apps to test and earn money for finding bugs.
• Both — access all builder and tester features.

You can change your role at any time from your profile page.

Setting up your profile

Visit your profile page to set your display name, update your role, and connect your Stripe account (required for testers who want to receive payouts).

Submitting an app

Head to the submit page to start the submission wizard. It has four steps:

1. App details — enter your app name, the deployed URL (must be publicly accessible), and a description of what the app does.
2. Testing scope — tell testers what to focus on, which user flows to test, and any known issues to avoid. Be specific to get the most useful feedback.
3. Choose a tier — select Quick Check, Deep Dive, or Stress Test based on how thorough you want testing to be.
4. Review and pay — confirm your submission details and complete payment via Stripe. Your app moves to the test queue once payment is confirmed.

Your app starts in Draft status while payment is pending. Once payment succeeds, it moves to Open and becomes visible to testers in the queue.

Testing tiers explained

Each tier determines how many testers work on your app and for how long. More testers means more coverage and a higher chance of catching edge cases.

Reviewing bug reports

When testers submit issues for your app, you'll see them on your my apps and on the app detail page. For each issue, you can:

• Accept — confirms the issue is valid. The tester gets credited.
• Reject — marks the issue as invalid. You can add a comment explaining why.
• Bulk accept — accept all pending issues at once from the app detail page.

Exporting reports

From the app detail page, you can export all issue reports in two formats:

• Markdown — formatted for pasting into GitHub issues, Notion, or docs.
• CSV — for importing into spreadsheets or project management tools.

Finding apps to test

Visit the test queue to see all apps that are currently open for testing. Each listing shows the app name, description, tier, and how many tester slots remain. Only apps with the "Open" status and available slots appear in the queue.

Claiming a test session

When you claim an app, a test session is created with a 2-hour time window. During this time, you explore the app and report any issues you find.

Important rules:

• You must have the Tester or Both role to claim sessions.
• You cannot test your own apps.
• You must submit at least one issue before completing your session.
• If your session expires, you can no longer submit issues for it.

Reporting issues

The test session page has a split-screen view: the app being tested on one side and the issue reporting form on the other. For each issue, you submit:

• Title — a short, clear summary of the bug.
• Category — what kind of issue it is (see below).
• Severity — low, medium, high, or critical.
• Steps to reproduce — numbered steps to trigger the bug.
• Expected vs actual behavior — what should happen vs what does happen.
• Screenshots — visual evidence of the issue.

Issues start with Pending status until the builder reviews them.

Issue categories

Every issue must be tagged with one of five categories:

Earnings and payouts

Visit the earnings page to see your total earnings, pending payouts, and payout history.

Your payout for each test session is calculated based on the proportion of your issues that are accepted by the builder. The more issues that are accepted, the higher your payout multiplier (ranging from 50% to 100% of the base rate).

Payouts are processed via Stripe Connect. You must have a connected Stripe account to receive payments.

How payments work

DidItWork.app uses Stripe for all payment processing.

• Builders pay upfront when submitting an app. Payment is collected via Stripe. Once payment succeeds, the app moves to the test queue.
• Testers are paid for accepted bug reports. Payouts are sent to their connected Stripe account after the builder reviews reports (or after the 48-hour auto-accept window).

Connecting Stripe

Testers must connect a Stripe account to receive payouts. You can do this from your profile page or earnings page.

Clicking "Connect Stripe" creates a Stripe Express account and redirects you to Stripe's onboarding flow where you provide your bank details and identity verification.

Platform fees

DidItWork.app charges a 20% platform fee on tester payouts. This means testers receive 80% of the applicable payout amount. There are no additional fees for builders beyond the tier price and standard Stripe processing fees.