Systems

How the products are built and run.

The technical layer behind AnicorLabs projects: mobile apps, Vue/Vuetify web surfaces, Pinia session patterns, edge APIs, managed data, email delivery, release paths, and deploy checks.

Working stack

Small products need real systems.

The stack stays boring where reliability matters: React Native, Expo, Vue, Vuetify, Pinia, edge APIs, D1, email, migrations, post-deploy checks, and serverless pieces that scale with usage instead of headcount.

Client apps

React Native and Expo for mobile, plus Vue, Vuetify, and Pinia for web/admin clients, session state, and operator surfaces.

Edge backends

Cloudflare Workers and Pages Functions for APIs, validation, webhooks, and product glue code without a standing server fleet.

Community platforms

Discord slash-command systems, install flows, account linking, private responses, and polished community-native product surfaces.

Data and delivery

Managed D1 tables for contact submissions and product data, Turnstile on public forms, and SendGrid for outbound mail.

Release discipline

Migrations, environment secrets, DNS, redirects, and smoke checks before a deploy is called done.

Current pattern

What keeps repeating across projects.

Running

Client apps

React Native and Expo mobile apps plus Vue, Vuetify, and Pinia web/admin surfaces with release, subscription, session, and support paths.

Running

Edge web systems

Astro sites on Cloudflare Pages with Functions, Workers, D1, Turnstile, SendGrid, DNS, and redirects: no server fleet, capacity follows usage.

Running

Community integrations

Discord slash-command systems, account linking, generated cards, minimal-permission installs, and serverless interaction handling for product communities.

Evolving

Reusable project patterns

Project scaffolds, env conventions, Pinia session patterns, migrations, contact forms, and deploy verification that can move from one product to the next.