October 2025: one set of maps, built on Google Maps
By October 2025 TradeYoke needed maps in many places. We built one shared set on Google Maps, so a customer, a job and the whole team all use the same map.
Auteur
AssemblySoft DevOps
The engineering team behind TradeYoke: how it is built, deployed and kept running.
August 2025: getting the address right, with postcodes and map pins
Everything on a round depends on the address. August 2025 added type-ahead address search, UK postcode lookup and a pin on a map for every customer.
June 2025: inspections, checklists with pass or fail, evidence and sign-off
June 2025 brought inspections: a checklist you build once, work through on site marking each item pass or fail, with evidence for every fail, signed off and sent as a report.
April 2025: searching inside your documents, not just their names
A library is only as good as your ability to find things in it. In April 2025 we made the library search inside the files, not just at their names.
March 2025: the page a customer accepts a quote on
March 2025 gave the customer somewhere to say yes: a secure link to the quote, no login, with lines they can untick and a way to tell you when suits.
November 2024: a ledger that cannot be quietly edited
November 2024 was about trust. The invoicing ledger only ever adds entries: a correction is a new line, not an edit. Here is why that makes the books easier to trust.
September 2024: getting an existing round in without retyping it
Nobody wants to retype four hundred customers. September 2024 was about import: check the file first, show what will happen, never silently merge, and flag the duplicates.
July 2024: a library for the paperwork, filed where you will look
Once customers and jobs worked, the paperwork started to pile up: photos, certificates, notes and PDFs. In July 2024 we built a document library that files things where you will look.
One codebase and offline-first: the early engineering decisions
Two decisions made in the first half of 2024 shaped everything since: one shared codebase for the web and the apps, and a phone that keeps working when the signal drops.
Designing a job that repeats: every four weeks, for years
A window clean happens again and again. May 2024 was about designing a job that repeats: its frequency, its next-due date, and what happens when it is paused or skipped.