Briefing a developer to customise what you bought
Most customisation goes wrong in the brief, not in the code. Twenty minutes of writing saves weeks.
Read moreBlog
Guides on buying well, selling more, and licensing your work properly.
Translating what you sell
Most buyers here do not have English as a first language. Making translation possible is worth more than doing the translating.
Read more
Storing a licence key safely in a distributed script
The purchase code lives on somebody else's server, in code they can read. Here is what that means for how you handle it.
Read more
Handling the offline grace period properly
Networks fail, servers block outbound calls, and firewalls exist. What your script does then decides whether buyers trust it.
Read more
When to say no to a customisation request
Saying yes to every request is how a product turns into an unpaid contracting job with a one-star review at the end.
Read more
Why we do not do bundles yet
It is the most requested feature we have not built. Here is the specific problem that has to be solved first.
Read more
Writing an install guide somebody can follow
You cannot see the step you left out, because you already know it. Here is how to find the gaps before your buyers do.
Read more
Database migrations that survive real data
Your migration ran perfectly on an empty table. Your buyer has 400,000 rows and a column full of nulls you never allowed for.
Read more
Accessibility in what you sell
Your buyer may be legally required to meet a standard. If your item cannot, they cannot buy it, and they will not tell you why.
Read more