Encoders and decoders
Base64, URL, HTML entities, JWT inspection. Everything decoded in the page, never posted to a server.
BrowserConverters, calculators, counters, formatters, document scanners, timers. A tool in this group should be usable within two seconds of the icon being tapped, with the thing you came for already on screen.
We spend most of the effort on the part nobody notices: the keyboard that opens with the right layout, the result you can copy with one tap, the last value still there when you come back tomorrow.
What this looks like in practice
Your records stay yours
Habits, expenses, meter readings, workouts, inventory, maintenance. These apps live on trust, because you only find out whether the data was safe on the day you need it.
So we start from local storage and working export, then add syncing only when a person asks for it and understands what it means.
The toolkit on our home page is one of these. Short, local, and good enough that you stop keeping a tab open for it.
Base64, URL, HTML entities, JWT inspection. Everything decoded in the page, never posted to a server.
BrowserJSON, XML, SQL. Pretty-print, minify, and point at the character where the parse broke.
BrowserPattern, sample text, live matches with group names, and an explanation of what each piece does.
BrowserSide-by-side or inline, with whitespace handling you can switch off when it lies to you.
BrowserUnix timestamps, time zones, cron expressions in plain language, UUID and hash generation.
Browser · CLIScripts that strip unused permissions, check an AAB against its manifest, and report what shipped.
CLIA connection is a convenience that disappears exactly when you need it. We design the offline path first and treat the network as an improvement on top.
In practice that means the database is local, the interface never blocks on a request, and anything that failed to send is queued and retried without a dialog interrupting you.
Room with Kotlin, Hive or Drift with Flutter. Reads are instant because nothing is remote.
Changes made without a connection are kept and sent when one returns.
The interface says what is saved locally and what has reached the server.
You have a defined piece of software you want built on Android or the web. We agree the scope, the stack and the date, then build it. We prefer projects small enough to finish than ones large enough to drift.
Fixed scope · Fixed dateAn app got slow, grew to forty megabytes, or was rejected by a store and nobody is sure why. We audit it, write down what we find, and rebuild the parts that need it. Sometimes the answer is to delete features, and we will say so.
Audit · Report · RebuildA paragraph is enough to start. What it should do, who uses it, and when you need it.
Get in touch