I Kept Rebuilding Form APIs. So I Finally Built Kin Form.

Description and use

Kin Form unifies form state management across admin portals, eliminating code duplication and ensuring type safety.

Problem

Developers building admin portals repeatedly had to reinvent form APIs across different stacks, leading to inconsistent, UI‑coupled form state management.

Outcome

Kin Form unified form state management across multiple admin portals, reducing duplication, improving type safety, and enabling flexible form tree structures independent of UI frameworks.

Workflow

• 1. Identify the need for a unified form API across multiple projects.
• 2. Extract the form logic from the UI library into a standalone package.
• 3. Design a tree‑based form model inspired by @angular/forms and TanStack Form.
• 4. Implement BaseApi for pub/sub, FieldApi for node state and relationships, and FormApi for form‑level operations.
• 5. Publish the package to JSR and npm, adding bindings for React and Lit.
• 6. Refactor existing portals to use Kin Form, replacing UI‑coupled form logic with the new API.

Evidence

I kept rebuilding form APIs. So I finally built Kin Form.

Source

Kin Form is a framework‑agnostic, type‑safe form state library for TypeScript, with bindings for React and Lit.

Source