Cooldowns with a reason
One-task rules and warm-up timing reduce ambiguity and make the next action clear.
Projects02 / 02 · Case study
Productivity · Task workflowTaskHub
TaskHub
with fewer loose ends.
A focused workflow for discovering tasks, submitting proof, handling reviews and making reward states understandable.
INTERFACE PREVIEWComplete. Submit. Earn.
Task proof submitted
Cooldown and warm-up state
Approval workflowPending wallet → reviewed reward
01 / The problem
A task marketplace is really a state-management problem.
Members need to know what they can claim, when they can claim it, what proof is required and what happens after submission. Administrators need the same clarity from the other side.
Without explicit states, a task can feel claimed twice, a duplicate proof can slip through, or a reward can appear before it has actually been reviewed.
02 / The workflow
Every important action has a visible next state.
TaskHub is organised around a sequence: account approval, warm-up, claim, submission, review and wallet settlement. The UI makes those transitions legible instead of hiding them behind generic success messages.
The admin side is treated as part of the product, not an afterthought. Reviews, settings and member actions follow the same language as the member experience.
01Approval02Claim03Proof04Review05Wallet
03 / Product decisions
Approval before access
New accounts and submitted proof have explicit review gates instead of silent assumptions.
Pending is not paid
Wallet states distinguish an earned reward waiting for review from a settled balance.
04 / What I learned
Trust comes from small, predictable transitions.
Building TaskHub taught me that the most important interface is often the moment between two states: waiting for approval, waiting for cooldown, or waiting for a wallet review.
When those moments are named and designed, a complicated workflow feels calmer for both the member and the person operating it.
02 / Live projectSee the TaskHub workflow in action.
Open taskshub.in