How Jag Journey, LLC designs, builds, tests and ships its own software, and the principles behind each decision.
100 posts
Live chat, notifications and live video pages need instant updates. Here is why we run our own realtime service, how pages stay working when it hiccup...
People delete the wrong thing. Instead of pretending they will not, we design deletion so most mistakes can be undone. Here is how our trash works.
When we publish pages, settings or articles for a website through code, the change runs once, checks its assumptions and never overwrites what the own...
Code is read far more often than it is written. Here are the habits we use to keep it clear for the next developer or AI assistant who has to change i...
A page made of pasted code looks fine until someone needs to edit it. Here is why our page builder uses native elements, reusable blocks and live cont...
Sending messages people did not ask for damages trust and breaks rules. Here is how our platform treats consent, unsubscribes and suppression as featu...
Before anyone on our team builds something new, they look for what already exists. Here is why that habit saves time, money and customer trust.
In a platform serving many organizations, turning a feature on is not one decision. Here is how platform switches, plan permissions and customer opt-i...
Testing payments is essential, and mixing test transactions with real ones is dangerous. Here is how we keep test and live money clearly separated.
A heading that is white in the editor and dark on the live page is a cascade problem. Here is how CSS cascade layers keep our page builder's styles in...
Passkeys replace passwords with a sign-in tied to your own device. Here is why we support them, how they resist phishing and what people should know b...
Sometimes our team needs to see what a customer sees. Here is how support access is limited, recorded and bound by the same rules that protect custome...