Anyone who has tested an app — a real beta, not a finished product — knows the problem. You're using it, something feels off, you want to report it. What do you do? Write an email? Find a bug tracker somewhere? Hope for a feedback button that then catapults you into some web form?

What usually happens: nothing. You close the app, think "I'll report that later", and later never comes. The developer sits on the other side waiting for feedback that never arrives.

TesterPayKit is the attempt to flip that.

Bonblick is using TesterPayKit as a pilot. If you have Bonblick installed via TestFlight or as a beta APK, you'll see a small red bug button in the lower right corner of the app. Tap it — and in two or three steps you've reported whatever you want to say.

What you can do with it

You don't have to guess what the developers want to hear. You just say what's happening on your side:

  • Something doesn't work. "The receipt isn't being recognized." Or: "The app crashes when I tap X." Tap, write a sentence, done.
  • Something is confusing. "What does 'staple share' mean? I don't get it." That's gold for developers too. If you don't understand something, most other people don't either.
  • Something is missing. "I'd like a list of my favorite receipts." Feature requests are welcome — they show what you hope from the product.
  • You have a question. "What actually happens to my receipts when I uninstall the app?" — straight to the developer, no help desk in between.

You can also: - attach a screenshot (TesterPayKit captures the current screen automatically) - record a screen capture if the problem is several taps away - send a voice note when typing is slower than talking

What happens behind the scenes

Once you tap send, your message goes directly to the developer. Not into a queue, not into a ticket system, not to an external service. Direct.

For Bonblick, that means: your feedback lands with me. I usually read it within hours. If I have follow-up questions, I reply — and you see the answer in the same app you reported from.

That's the most important change compared to the usual bug-tracker flow: there's a real dialogue. No silent ticket numbers, no email threads disappearing into spam.

What TesterPayKit is meant to become

Today Bonblick is one of the first projects using TesterPayKit. The app component — the red bug — already works stably. What's still in progress is the platform around it.

The idea: a tester who consistently gives valuable feedback to an app — finds bugs, leaves clear requests, contributes seriously — does real work. Today testers almost never get anything for that work. They do it voluntarily, often with the quiet hope that the product they're using will get better.

TesterPayKit wants to add a different layer: developers should be able to actually pay testers for good feedback. Not for every report, not inflationary. But where a piece of feedback makes the difference — finds a serious bug, sharpens a feature, brings in a real idea — it should be felt.

What that looks like exactly — amounts, payout, anti-spam incentives — is currently being built. The idea isn't "testers are unpaid employees". The idea is "testers are partners with recognition."

Why "Pay" is in the name

The name comes from exactly this thinking. TesterPayKit = a tool kit that brings testers into the process properly, instead of treating them as a free resource. The "pay" is the second stage, not the first. In stage one, it's enough that tester feedback arrives in a structured way and gets fast answers.

Stage one is running. Stage two is coming.

What's in it for you as a Bonblick tester

Concretely today, while Bonblick is still early:

  • Your feedback reaches me directly. No help-desk layer in between.
  • You see that Bonblick listens. If you report something and the next version fixes it, we tell you.
  • You don't have to install anything besides Bonblick. TesterPayKit lives entirely inside the app. No second account, no login.

And later — once TesterPayKit as a platform is finished — anyone who consistently gives good feedback will maybe receive a small thank-you back that's more than a "thanks" in the app.

Status

TesterPayKit is currently an early platform in development. The app component is actively used in Bonblick and stable. The admin interface for developers and the tester-payment layer are not yet public. If you're curious as a tester or a developer:

  • If you're beta-testing Bonblick, you're already using TesterPayKit — no extra setup.
  • If you have your own app and want to try TesterPayKit, see testerpaykit.com for current info.

We'll come back to this in the journal once the platform is open for more apps.

Bottom line

Beta tests were one-way streets for a long time. Testers send feedback into the fog, developers hope someone responds, both sides talk past each other. TesterPayKit reverses that: one button, one dialogue, one direct connection.

That's the app half of the idea. The tester-appreciation half is still coming. Both together are the actual goal.

Bonblick is the first project to take this path seriously. So when you test Bonblick and tap the red bug, you're not just helping Bonblick get better — you're also helping testers be treated differently from the way they have been so far.