The most useful thing a software partner can show you is not a capability list — it is what they have actually built. Below is a selection of our own application and library work: mobile platforms, developer tooling, identity components, and licensing infrastructure. Status is stated for each, because “we built this” and “this is a finished product” are different claims and we keep them apart.
PDF Essentials Professional
Our most substantial application: an Android enterprise document platform, built in Kotlin with Jetpack Compose, Material 3, Room, and WorkManager, on top of a Pdfium rendering core.
On the document side it handles direct PDF editing, annotations, page organisation, OCR and searchable scans, form filling, handwritten and certificate-based signatures, irreversible redaction, password protection, watermarking, document comparison, review threads, voice comments, and secure export. The redaction is worth calling out specifically — irreversible means the content is removed, not covered with a black rectangle that survives a copy-paste.
Its AI assistant provides document summaries, question answering, action-item extraction, semantic search, multi-document workspaces, and voice interaction — with citations tied back to specific pages and regions. That last detail is the difference between an assistant you can trust with a contract and one you cannot: every answer points at where in the document it came from. It is the same retrieval-grounded approach our AI practice applies at enterprise scale.
The enterprise layer covers tenant configuration, policy-controlled AI and sharing, WebDAV and S3-compatible connectors, offline synchronisation, migration and recovery, and accessibility support. The engineering around it — automated tests, CI release gates, SBOM generation, and production build validation — is the part that decides whether a mobile platform can actually be maintained.
Status: working prototype, actively refined.
Mobile Engineering Foundations
- Android PDF Viewer — the Pdfium-based rendering library and viewer foundation used to work through page rendering, gestures, and document display. It is the base layer beneath PDF Essentials Professional, not the same thing as it. In progress.
- File Preloader Library — a reusable Android library that preloads and caches files before they are needed, cutting perceived load time. Library project.
- Privacy Dashboard — an Android utility that surfaces which applications are accessing the camera, microphone, and location, presented in a standard Android or OneUI-style interface. Android development project.
This is what Android and cross-platform work looks like underneath the surface: rendering internals, caching strategy, and platform permission behaviour.
Identity and Biometric Login
A facial-recognition login system, with a liveness-detection variant that adds presentation-attack protection — distinguishing a live person from a photograph or a replayed video. This work is built on and evaluated against established open-source components including face-api.js and CompreFace; the recognition engines are theirs, our work is the login flow, the liveness handling, and the integration.
Biometric authentication is one of those areas where the security design matters more than the demo. If you are considering it, the questions worth asking are about fallback, spoofing, and what happens to the biometric template — which is properly secure-development territory. Status: in progress.
Voice Interaction API
A reusable service for adding spoken interaction to an application: speech recognition, AI response generation, voice synthesis, interruption handling, conversation state, and command execution. The intent is one voice layer usable across mobile, desktop, web, and agent applications rather than rebuilding it per project. Interruption and conversation state are the hard parts — they are what separate a voice interface from a dictation box. Status: in progress.
Software Licensing and Entitlement
A consolidated body of work around protecting and licensing software: licence and serial-key generation, activation validation, machine and host binding, expiration, feature-level entitlements, API-based key validation, licence management, and Java application integration. Parts of it build on existing open-source licensing libraries rather than reinventing the cryptography.
We describe this as one licensing and entitlement capability rather than as several separate products, because that is what it actually is — components of a single problem solved across a few repositories. Status: developed project.
Developer Utilities
HTML Live Editor and Live Code Editor — browser-based editors that render or execute as you type, without a build-and-refresh cycle. Useful for prototyping, testing snippets, teaching, and quickly building interface components. Status: developed utilities.
What This Is Meant to Show
Not that we sell these as products — most are internal builds, prototypes, and libraries. What they demonstrate is the range the team works across: a full enterprise mobile platform with its own release engineering, rendering and caching internals, biometric and identity flows, voice interfaces, and licensing infrastructure. That is the spread you want in a partner for custom software, because most real projects touch several of those at once.
Where a project needs specialist depth — AI agents, building automation, security engineering, business systems, or games — it routes to the relevant specialist practice rather than being forced through a generalist lens.
Tell us what you are building and we will tell you honestly which of this is relevant, what we would reuse, and what we would build from scratch.