About
Independent software, built to keep working.
An independent practice making Android apps, Unity games, desktop and web software. 36 projects so far, 6 of them finished.
What gets built here
The range is wide and the constraint is narrow. A camera app that approximates how other animals see. Offline encyclopedias for people choosing a pet. A festival companion that works when the signal has gone. Arcade games built from procedural art and synthesised sound. A notes application that starts empty and stays on your machine.
What connects them is that each one has to be useful with no connection, no account and nobody watching. That rules out a great deal of ordinary app architecture, and it is the reason these projects look the way they do: local databases instead of back ends, bundled content instead of feeds, atomic saves instead of cloud sync.
It also rules out the usual business model. There is no advertising SDK in any of these projects, no analytics, and nothing that phones home. Several go further and remove the internet permission from the manifest outright, so the claim is verifiable rather than promised.
The work in numbers
- Projects
- 36
- Finished
- 6
- Collections
- Mobile Apps, Games, Web Applications, Desktop Software, Developer Tools, Experiments
- Platforms
- Android, Web, Windows, Desktop
- Recurring technologies
- 25
How the work gets made
Five decisions that apply to every project, and show up in the code.
Offline first, not offline capable
Local storage is the primary store, not a cache. Every project is designed to be fully useful with the aeroplane mode switch on.
Never lose someone’s data
Versioned saves, checksums, atomic writes and retained backups. A corrupt file is reported, never silently treated as valid.
Say what is true
Statuses, permissions and limitations are stated plainly, including the unflattering ones. This site fails its own build if a project claims a store listing it does not have.
Accessibility is part of the build
Contrast, colour-blind palettes, reduced motion, text scaling and screen-reader labelling are designed in from the start rather than retrofitted before release.
Craft and accountability
Work is finished properly or labelled unfinished. Where something could not be verified — signing, device testing, a real-world measurement — that gap is written down rather than papered over.
Own the assets
Procedural art, synthesised audio and correctly licensed photography with the credit travelling alongside the image.
The longer version, with what each principle rules out, is on Aims and principles. Who is behind the work, and on what basis, is on Business information.
AI-assisted, and open about it
These projects are built with AI assistants working alongside conventional engineering practice — for research, implementation planning, code review, refactoring and accelerated iteration. That is worth stating plainly rather than hiding, and worth stating precisely rather than claiming more than it is.
What it does not mean: the architecture, the constraints, the accessibility decisions and the honesty rules are deliberate choices that get reviewed, argued with and frequently rejected. Tests, audits and device checks decide what ships. Where verification was not possible, the projects say so.
Projects are grouped by the workflow they actually came through, because it is genuinely informative — and because the evidence for it is sitting in each repository.