Build your own Google Drive.

# Build an original app inspired by Google Drive

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 shared file library called Filegrove, inspired by Google Drive. It serves a small team uploading owned files, organizing nested folders, and granting explicit viewer/editor access. The main journey is uploading a file, placing it in a folder, sharing it with a teammate, and revoking access. Document storage quotas and version retention.

## Design
Use an original responsive file explorer with breadcrumbs, list/grid views, a preview panel, and an accessible sharing dialog. Show owner, version, quota, trash, and shared status clearly. Move/copy controls need keyboard alternatives and recoverable outcomes.

## Features
1. File and folder management: upload supported files with size limits, create/rename/nest/move folders, move files, and prevent circular ancestry. Handle same-name conflicts deliberately rather than overwriting silently.

2. Versioned files: upload a replacement as a new immutable version, inspect version history, download a chosen version, and restore an earlier version as the current one. Keep content hashes and retention rules.

3. Sharing: grant an authenticated teammate viewer/editor access, share folders with a documented inheritance rule, revoke grants, and create optional expiring read-only links. Every download/version access must check effective permissions.

4. Preview and search: preview permitted images/PDF/text safely, download unsupported types, search authorized filenames, and filter owned/shared/recent items. Avoid executing uploaded HTML or office macros.

5. Trash and operations: soft-delete/restore items, display real quota usage, handle interrupted uploads, and log permission changes. Permanent deletion must clean all retained versions only after a clear confirmation.

## Tech stack
Use a TypeScript app/API, PostgreSQL metadata, and private object storage. Issue short-lived upload/download URLs after authorization and validate final object metadata. Compute folder inheritance on the server, and keep permission checks consistent for previews, versions, links, and search. Use a transaction or revision check for metadata changes.

## Data & behavior
User; Workspace; Folder {parentId}; File {folderId, ownerId, currentVersionId, deletedAt}; FileVersion {objectKey, bytes, hash}; Grant {resourceId, principalId, role}; ShareLink {tokenHash, expiresAt, revokedAt}; UploadSession; Quota; AuditEvent. Moving a file must recompute inherited access.

Acceptance checks and scope:
Test share/revoke with a second account, moving a shared file into a private folder, circular moves, stale signed links, unauthorized old versions, quota exhaustion, and replacement upload failure. Exclude Google Docs editing, desktop synchronization, Google-account federation, and existing Drive imports.

## 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.