Services

Native iOS and Android applications, built from one codebase and shipped through the App Store and Google Play. We handle the parts that make mobile genuinely hard: working offline, syncing without losing data, and passing store review.

Our own product TerpTrakker is the reference build — a local-first consumption journal and analytics app on iOS, Android, and web. What went into it:

• Offline-first data — a full local database, so the app works with no connection and cloud sync is opt-in rather than required.
• On-device document scanning — reading lab reports, labels, and receipts through the camera and OCR without uploading the image anywhere.
• An analytics engine — correlating structured user input against reference data to produce findings that hold up, computed on the device.
• Conflict-safe sync and user-owned backup — across devices, plus restore to a Google Drive or OneDrive folder the user controls.
• Modern authentication — passwordless sign-in, passkeys, and authenticator-app 2FA.
• Subscription billing — store-native purchases and entitlement handling across both platforms.

That is a sample, not the full inventory — it is there to show the shape of what we can build.

Web applications, browser extensions, and internal tools — the software people keep open all day. We build for the browser when the work belongs where the user already is, rather than in another app they have to remember to open.

Our extension Focally is the reference build — a focus timer that lives in the browser side panel and connects to the systems a team already runs:

• Multi-service OAuth integration — ClickUp, Salesforce, Microsoft Graph, and Fireflies, each authenticated properly and scoped to only what the feature needs.
• Two-way sync — pulling tasks and meeting action items in, then writing time entries and activity back automatically when work completes.
• Calendar-aware behavior — reading the day's meetings to suggest and schedule blocks of work around them.
• Local-only storage — settings, history, and access tokens stay in the browser; no account, no server, no analytics.
• Serverless where it's needed — a stateless function handles the one OAuth exchange that cannot ship inside a public extension, and stores nothing.

The same techniques apply to dashboards, portals, and internal tools — anywhere the job is unifying systems that don't talk to each other.

The work that doesn't fit a category. Desktop software, hardware integration, daemons and background services, automation, and systems built to a specification that exists nowhere else.

Our project Caldera is the reference build — a Stream Deck control surface for Bluetooth vaporizer hardware:

• Bluetooth LE device control — communicating directly with hardware over its own protocol, with live device state read back and displayed.
• Cross-platform desktop — a plugin paired with a background service that runs on macOS and Windows.
• A capability model for multiple devices — one adapter per hardware model, with the interface adjusting to what each device can actually do.
• Automation sequencing — user-defined multi-step routines with timing, state transitions, and safety fallbacks.
• Entirely local — no cloud, no account, no data leaving the machine.

If your problem involves a device, a protocol, or a process that no vendor sells software for, this is the category it falls in.

We keep engagements small enough to stay accountable for outcomes.

• Understand first. We spend real time on how the work is done today, including the workarounds. Those usually describe the requirements better than a spec does.
• Ship in increments. Working software early and often, so direction can change while changing it is still cheap.
• Build it to be owned. Documented, tested, and handed over in a state your team or ours can maintain. No deliberate lock-in.
• Privacy and security as defaults. Least data, least privilege, and no quiet collection — the same commitments we publish in our privacy policy apply to what we build for you.