Technologies
The tools we build with, and why each one.
Technology is a means: what matters is that the product works, is fast, is secure and can be maintained. Here is what we build with, organised by what it does, with the reason we use each and where you can see it running.
How we choose
- 01
The product decides
We choose by what the product needs, not by fashion. The same problem may need a website or an app, a native app or one shared by both platforms.
- 02
Tools others know
Every tool here is widely used and documented, so any capable team can maintain your system after us — yours included.
- 03
Shown, not listed
Where a tool runs in work of ours you can open today, we say so and link to it.
Interfaces
What people see and touch, on the web.
TypeScript
One typed language from the screen to the server, so a mistake is caught while writing, not by your customers.
React
Interfaces with many moving parts — forms, lists, dashboards — that stay fast and predictable as they grow.
Astro
Websites that send pages, not programs: fast on the weakest phone and easy for search engines to read. This site is built with it.
three.js / WebGL
3D in the browser with nothing to install, for a product to show itself or a game to be played.
Servers and data
What runs behind the screen, and where the data lives.
Node.js
The server side of a system and the tools that build it, in the same language as the interface.
Cloudflare Workers
Code that runs close to your users, in data centres around the world, with no server for you to look after.
SQLite / D1
Data that sits beside the code that uses it. In MedOne, each clinic’s records live in a database of their own.
PostgreSQL
The established choice for large shared data and heavy reporting, when a system needs it.
REST APIs
Clear, documented interfaces, so your system can talk to the ones you already use.
IndexedDB
Storage inside the browser that lets work carry on without a connection and sync when it returns. It is how a doctor writes in MedOne offline.
Phone apps
Android and iOS.
React Native
One app for Android and iOS when the product allows it, sharing its code with the web.
Kotlin
Native Android, when an app needs everything the device can do.
Swift
Native iOS, for the same reason.
Games and 3D
Engines, languages and models.
Unity
Mobile games, PC games and augmented reality. One of the two engines our founder specialises in.
Unreal Engine
For games and scenes whose picture must be of the highest quality. The other engine he specialises in.
C#
Unity’s language, for a game’s logic and its tools.
C++
Unreal’s language, where every millisecond counts.
Blender
3D models and their animation. LANDER’s models are made in it.
Artificial intelligence
Where it saves real time.
Workers AI
Language and vision models running on Cloudflare’s network, close to the rest of the system. This site’s assistant runs on it.
Large language models
For answering from your own information and drafting what repeats, with a person where it matters.
Vision models
For reading invoices and forms into data. In our platform, supplier invoices are read this way, and a doubtful line is confirmed before saving.
Security
Built in from the design, not added at the end.
OWASP
The recognised list of how software is attacked, which we check against from the design onward.
Content Security Policy
A browser rule that refuses any script from an unexpected source. This site runs under a strict one.
OAuth / OpenID Connect
Sign-in through accounts people already trust, such as Google, without the system keeping their passwords. It is how MedOne is signed into.
Encryption
Data protected on its way and where it is kept, and keys kept out of the code.
Code obfuscation
Making a game or an app hard to take apart, copy or cheat.
Design
Before the code, and alongside it.
Figma
Screens designed and agreed before a line of code, so a change costs minutes, not weeks.
Design systems
One set of components and rules, so every screen agrees with the others.
WCAG
The accessibility standard: contrast, sizes and controls everyone can use, on any device.
Interactive prototyping
A clickable version you try before it is built.
A tool in mind, or none at all?
Tell us what the product must do; we suggest the tools and say why.