Should you build your own Fomr?

Build a deliberately narrow personal form builder inspired by Fomr, starting from an empty repository.
Use exactly this stack: Next.js 16, TypeScript, Tailwind CSS, SQLite, and Drizzle ORM.
The core loop is create a form, preview it, publish it, collect responses, and export them.
Make it single-owner and protect the admin area with an ADMIN_PASSWORD from .env.
Create an admin form editor with a reorderable field list and a live respondent preview.
Support short text, long text, email, number, select, radio, checkbox, rating, date, and content blocks.
Allow required fields, labels, help text, placeholders, choices, and basic min/max validation.
Support one simple conditional rule per field: show it when another answer equals a configured value.
Add form-level colors, font choices, logo upload, cover image, spacing, and light or dark appearance.
Publish each form at /s/<slug> with accessible labels, keyboard navigation, and mobile layouts.
Validate every submission on the server against the saved form schema.
Store forms, immutable schema versions, responses, and timestamps in SQLite.
Provide a private response table with search, detail view, deletion, and CSV export.
Send optional owner notifications through SMTP, but keep collection working when SMTP is absent.
Add a honeypot, per-IP rate limiting, request-size limits, and safe upload handling for branding assets.
Include a configurable thank-you message and optional redirect URL.
Handle empty, loading, validation, success, not-found, and recoverable failure states.
Keep user data local and add JSON export and import for forms.
Do not add analytics, telemetry, ads, billing, or third-party accounts.
Put every secret in .env and include a complete .env.example.
Write unit tests for schema validation and branching plus one end-to-end publish-and-submit test.
Create a README covering setup, deployment, data location, backups, SMTP, security limits, and recovery.
Deliberately exclude custom domains, team collaboration, OAuth integrations, payments, and enterprise compliance.
Deliberately exclude a marketplace-sized template library and promise only personal-scale reliability.
Run tests and a production build before finishing, fixing failures instead of merely describing them.