Complete mobile workflows
Accounts, navigation, forms, uploads and connected APIs—not just a collection of screens.
Mobile apps. Complex platforms. AI systems. The engineering that brings them to life and keeps them running.
We build the experiences people use and the foundations they depend on.
Shared React Native applications, with the device features and release work that make them usable in practice.
Accounts, navigation, forms, uploads and connected APIs—not just a collection of screens.
Camera capture, QR scanning, deep links and secure local identity storage.
Native builds, testing tracks and compatible over-the-air updates, with new binaries when native code changes.
Built examples: Quotient’s companion app, Rhystic Play and Collect, and Grain Smith’s tradesperson app. Grain Smith remains in testing.
We extend React Native with native Kotlin and Swift where hardware access and performance demand it.
CameraX and OpenCV detect cards, correct perspective and identify artwork on the phone.
AVFoundation, OpenCV and Apple Vision provide camera processing and text recognition behind the same app interface.
Local matching and a packaged search index let the scanner identify cards without sending every frame to a server.
Built example: Rhystic Collect’s scanner. Native modules share a common interface and correctness test vectors.
Responsive interfaces for customers, operators and administrators, connected to real business workflows.
Dashboards, searchable tables, forms, permissions and administration across React applications.
Branded provider locators and integrations that fit into existing sites, including HubSpot embeds.
Keyboard navigation, focus management, labelled controls, reduced motion and automated accessibility checks.
Built examples: OmniActions dashboards and locators, Quotient’s browser interface, Rhystic’s web apps and Grain Smith’s web back office.
Complex APIs that coordinate users, business rules, data and external systems.
Typed requests, validated inputs, permissions and error handling for mobile apps, websites and administrative tools.
Integrations for payment links, email, storage and AI tools, connected to application workflows.
Organization-scoped records and access checks keep each account’s workflows and data in the right context.
Built examples: OmniActions’ marketing and analytics APIs; Quotient’s file and identity services; Grain Smith’s quotes, invoices and Stripe pay links.
We build schemas and migrations, then tune the paths people and applications actually use.
Relational schemas, constraints, tenant boundaries and migrations that evolve with the product.
Indexed analytics tables, database-side aggregation, pagination and batch reads instead of repeated queries.
Query-count tests and budgets for storage, encryption and model calls catch expensive patterns as software changes.
Built examples: OmniActions’ search fact tables and indexed value catalogs; Startly’s batched encryption and database-query budgets. Startly’s current rebuild is in development.
Managed sign-in where it fits. Custom cryptographic identity when the product needs something different.
Quotient uses signed challenges and browser-bound QR approval to connect a user’s phone identity to their server.
Account backups and QR-plus-PIN identity transfer support moving an identity between the browser and phone.
Managed authentication, role checks and organization-scoped access control govern what a signed-in user can do.
Built examples: Quotient’s custom identity flows and OmniActions’ Clerk-based authentication and agency permissions.
Application security, cloud hardening and the engineering work behind SOC 2 readiness.
Scoped service accounts, environment separation, audit logging and controlled access to production systems.
Backup configuration, monitoring, secrets management and reviewed changes support compliance requirements.
Heka Vault provides project-scoped credentials and an audit trail; integrations retrieve secrets without placing them in an agent’s prompt.
Built examples: OmniActions’ SOC 2-oriented GCP controls and Heka Vault. These describe implemented controls and compliance support, not an independent audit certification.
We build the APIs, tool definitions, question screening and answer checks around the model.
Jev decision gates assess intent, scope and sensitive-data requests when enabled.
Gemini on Google Vertex AI receives defined capabilities and structured tool contracts.
Application APIs enforce tenant boundaries and allowed operations. The model does not write SQL.
Evidence checks and numeric verification run before an answer reaches the user.
Built example: OmniActions’ Ask analyst. Layered controls constrain what a prompt can cause the system to do; Jev gates are configurable per agency.
We build mechanisms to inspect, evaluate and improve AI behavior after the first demo.
Citations link claims to query results; code checks numeric statements against the returned data.
Saved evidence snapshots, evaluation cases and regression checks help compare prompts and models.
Sanitized traces, user feedback, quotas and retention policies make the system observable and manageable.
Built example: OmniActions’ analyst includes model traces, evidence inspection and evaluation replay. Screening and verification reduce risk; they do not guarantee every answer is correct.
Our AI work spans information extraction, on-device recognition and assistants that use connected applications.
Startly’s implemented extraction pipeline reads tax slips, employment records and bank statements, with page references for review. Current rebuild in development.
Rhystic Collect combines camera processing, image matching and text recognition in its mobile scanner.
Ghost combines local wake-word and speech components with model-backed reasoning and MCP integrations. Early Linux product.
Capability: choosing where computation runs, connecting models to tools, and making results usable inside a larger application.
Automated build, test and release systems for cloud services, phone apps and software installed on a customer’s machine.
CI checks, database migrations, environment-specific deployment and post-deploy verification.
Build fingerprints determine when an over-the-air update is compatible and when a new native build is needed.
Signed server packages, release channels, fresh-install validation and staged promotion to installed devices.
Built examples: OmniActions’ cloud pipelines, Quotient’s mobile releases and self-updating servers, and Rhystic’s build and deployment automation.
Monitoring and recovery are capabilities we build into the system.
Health endpoints, revision identifiers, logs and alerts show the state of running services.
Deployment checks and rollback tooling provide a defined response when a new version fails.
Read-only operational access and job-run records support troubleshooting while limiting production permissions.
Built examples: OmniActions’ deployment validation and production monitoring; Quotient’s release channels and mainframe diagnostics.
Each product combines several of these capabilities into a working whole.
Web applications, embeds, multi-tenant APIs, analytics, controlled AI and cloud operations.
Mobile and browser apps, custom identity, file services, installation and self-updating servers.
Mobile and web apps, native scanning, on-device recognition and community workflows.
Document intake, extraction, cited figures, encryption and review workflows.
Mobile and web apps, jobs, quotes, invoices and payment integrations.
Voice interaction, connected tools, scoped credentials and audit trails.
A new application. A stronger platform. AI inside an existing workflow. We can build the experience and the engineering underneath it.
Demonstrated engineering skills, with examples from the software we’ve built.
| Capability | Demonstrated skills | Selected examples |
|---|---|---|
| Mobile apps | React Native, Expo, iOS / Android builds, app updates | Quotient, Rhystic, Grain Smith |
| Native & device integration | Kotlin, Swift, camera modules, QR scanning, offline vision | Rhystic Collect, Quotient |
| Web & accessibility | React, responsive applications, embeds, keyboard and focus support | OmniActions360, Rhystic, Grain Smith |
| APIs & integrations | Typed APIs, tenant-scoped workflows, payments, connected services | OmniActions360, Quotient, Grain Smith |
| Databases & performance | PostgreSQL, schemas, migrations, indexes, aggregation, batch queries | OmniActions360, Startly |
| Authentication & access | Signed challenges, QR sign-in, managed identity, roles and permissions | Quotient, OmniActions360 |
| Security & compliance support | Cloud hardening, scoped credentials, audit logs, SOC 2 supporting controls | OmniActions360, Heka Vault |
| AI orchestration & evaluation | Vertex AI, Jev gates, tool calling, grounding, evaluation replay | OmniActions360 |
| Applied AI | Document extraction, page citations, computer vision, voice and MCP tools | Startly, Rhystic Collect, Ghost |
| CI/CD & release engineering | Automated checks, cloud deployment, mobile builds, signed server packages | OmniActions360, Quotient, Rhystic |
| Production operations | Health checks, monitoring, diagnostics, read-only access, rollback tooling | OmniActions360, Quotient |
Examples show implementation experience, not release status. Startly’s current rebuild is in development; Grain Smith is in testing; Ghost is an early Linux product. SOC 2 refers to supporting controls and compliance work.