insurance-claims-myclaim

byJames sam

You are an expert no-code/low-code app builder. We are building an MVP called MyClaim that helps people manage insurance claims. This is a data-driven CRUD app with file uploads, not a marketing site or mockup. Generate a working app with real screens, a real database, authentication, and file storage. 1. Product purpose MyClaim helps users: Organize insurance claims. Store claim-related documents. Track deadlines and important dates. Manage contacts (adjuster, broker, lawyer, repair shop). Keep a timeline of events for each claim. Target users: people managing auto insurance claims first, with the data model designed so it can later support home, travel, disability, and property claims. This is a personal claims organizer. It does not file claims with insurers or replace official insurer portals. 2. Core data model Create these entities with the following fields and relationships: Claims id (auto) claim_number (text, optional) claim_type (text; examples: “Auto”, “Home”, “Travel”, “Disability”, “Property”) insurance_company (text) status (text or enum; examples: “Open”, “In Review”, “Negotiating”, “Closed”) date_opened (date) date_closed (date, optional) policy_number (text, optional) deductible_amount (number, optional) claim_amount (number, optional) notes (long text, optional) primary_contact_id (relationship to Contacts, optional) next_deadline (date, optional) next_action (text, optional) Contacts id (auto) name (text) company (text, optional) role (text; examples: “Adjuster”, “Broker”, “Lawyer”, “Repair Shop”, “Other”) phone (text, optional) email (text, optional) preferred_contact_method (text; examples: “Phone”, “Email”, “Text”, optional) last_contacted_date (date, optional) claim_id (relationship to Claims) Documents id (auto) file (file attachment; support PDFs and images) file_name (text, derived from file) type (text; examples: “Estimate”, “Police Report”, “Settlement Offer”, “Receipt”, “Photo”, “Other”) upload_date (date, auto-set to today) source (text; examples: “User”, “Adjuster”, “Repair Shop”, “Lawyer”, optional) category (text; examples: “Estimate”, “Medical”, “Photos”, “Correspondence”, “Other”, optional) claim_id (relationship to Claims) Timeline id (auto) date (date) event_type (text; examples: “Called Adjuster”, “Vehicle Inspection”, “Submitted Documents”, “Received Offer”, “Email Sent”, “Other”) notes (long text) requires_follow_up (boolean, default false) follow_up_date (date, optional) contact_id (relationship to Contacts, optional) claim_id (relationship to Claims) 3. Relationships Configure relationships so that: One Claim has many Contacts. One Claim has many Documents. One Claim has many Timeline events. Each Contact, Document, and Timeline event is linked to exactly one Claim. Ensure that when viewing a Claim, I can see its related Contacts, Documents, and Timeline events. 4. Authentication and permissions Require user accounts to access the app. Support email/password login at minimum; add Google/Apple OAuth if available. Each user can only see and edit their own Claims, Contacts, Documents, and Timeline events. Provide a simple “Log out” action. Do not make the app public/read-only. This is a private personal organizer. For now, focus on creating the data model and authentication. In the next prompt, I will define the screens and navigation.