Build your own Airtable.

# Build an original app inspired by Airtable

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original spreadsheet-style database app called Fieldwork, inspired by Airtable. It is for individuals organizing structured projects such as an inventory or content calendar. The main flow is defining a table, entering typed records, and switching between useful views of the same data.

## Design
Use a light, practical interface with base navigation, table tabs, a view sidebar, and a data grid. Keep headers fixed, selections obvious, and cell editors appropriate to each field type. Use soft colors for select values and one warm accent. Make record details usable on phones.

## Features
1. Bases and tables: create and rename bases and tables; configure text, long text, number, checkbox, date, single select, and linked-record fields. Prevent accidental deletion of populated fields.

2. Grid editing: add and delete records, edit typed cells, resize columns, and open a record detail panel. Validate values and show useful errors without silently changing data.

3. Saved views: save filter and sort settings, hide columns, and create a board grouped by a single select. A gallery displays selected text and image URL fields with safe rendering.

4. Linked records: link rows across tables in the same base; show readable primary-field labels; handle deleted linked rows without broken references.

5. Data exchange: import CSV with a column-mapping preview and validation; export the current view as CSV with proper escaping. Provide an original inventory and content calendar sample.

## Tech stack
Use the existing repository and conventions if there is one. If starting from scratch, use React with TypeScript and a practical, lightweight styling approach. Pick well-maintained libraries only when they materially help. Keep components, domain logic, and data access separate. Explain your chosen stack briefly, then begin implementation.

Follow the persistence requirements in Data & behavior. Personal tools may use IndexedDB. Products with public submission, bookings, permissions, or shared messaging require an authenticated backend with server-side authorization and durable storage. Use infrastructure already available in the environment. Do not put secrets in frontend code. If external infrastructure is unavailable, build a clearly labeled local demo, provide the schema and setup instructions, and state which shared features need configuration. Do not present simulated sharing or authentication as production functionality.

## Data & behavior
Base {id, name}; Table {id, baseId, name, primaryFieldId}; Field {id, tableId, name, type, options}; Record {id, tableId, values}; Link {sourceRecordId, fieldId, targetRecordId}; View {id, tableId, name, type, filters, sorts, visibleFields, groupFieldId}. Store data in IndexedDB for the personal MVP. Use transactions for schema changes and imports. Version schemas and never evaluate formulas as JavaScript.

Acceptance checks and scope:
Test typed validation, combined filters, persistent view settings, CSV with commas and line breaks, and deletion of linked records. Warn before destructive schema changes. Adjust data and views coherently when the requested feature set changes. Exclude arbitrary formulas, automation builders, and shared-team access from the MVP.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.