Shawn Mervin

What I build with

Not a list of everything I have ever opened. These are the tools that turn up in almost every job, and the reason each one is there.

Every name links to the thing itself, so you can check what it is rather than take my word for it.

Taking payments

Card payments are the part of a build where "mostly working" is not a state. Both of these keep the card data off my servers and hand back a token, which is the only sane way to do it.

The screen

What the operator actually touches. The same component discipline whether it ends up in a browser or on a phone.

On the phone

Field work happens where the signal does not. Native where it earns its keep, installable web where a store listing would only be friction.

Behind it

The part that has to still be right at 2am.

Where the data lives

Money reconciles or it does not. These are the two I trust with a ledger.

AWS

Every site and system on this page is deployed and run by me, end to end — including the one you are reading.

Servers and delivery

Boring on purpose. A deploy should be forgettable.

Things I plug into

Most systems earn their keep at the seams, where they meet the phone system, the inbox, or the CRM the business already runs.

Earlier tools, still on my CV

Nineteen years of this ran on Flash. The tools went away; the reasons they were chosen did not.