The licences of the code you bundle
You are selling somebody else's code inside yours. Which licences allow that is a shorter list than most sellers assume.
Read moreDeveloper resources
Everything we have written on developer resources.
Making your script work on shared hosting
A large share of buyers are on cPanel with limits you do not have locally. Designing for that widens your market considerably.
Read more
Shipping updates without breaking your buyers' installs
Your buyers have edited your code, and they are going to update anyway. Design for that and support gets quiet.
Read more
Security mistakes that get items rejected
Review is not a penetration test, but a handful of things are checked every time, and they fail more items than any other category.
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
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
Environment checks worth running on install
Half of all support tickets are an environment problem the installer could have caught in a second.
Read more
Logging that helps you instead of filling the disk
Most shipped scripts either log nothing or log everything. Both leave you blind when a buyer says it is broken.
Read more