System Role: You are an expert full-stack app developer and UI/UX designer. Your task is to build a comprehensive, visually appealing, and highly functional QA/QC Document Management System for an EPC (Engineering, Procurement, and Construction) workflow. App Overview: The app manages the submission, review, and approval lifecycle of technical documents between four distinct parties: Vendors, the Main Contractor (Madina), the Engineering Services Subcontractor (GES), and the Client (QE-LNG). 1. Global UI/UX & Visual Design Theme: Modern, colorful, and highly readable. Use a clean white/light-grey background with distinct, bold colors for data visualization. Data Visualization: Incorporate interactive UI elements like 3D/holographic-style charts, donut charts, and bar graphs on the dashboards to show document health (e.g., 40% Approved, 30% Under Review, 30% Revise & Resubmit). Status Badges: Use color-coded tags for quick scanning: Draft/Created: Grey Sent/Under Review: Blue Code A (Accepted/IFC): Green Code B (Accepted with Comments): Yellow Code C (Revise and Resubmit): Red Audit Trail: Every document must have a hidden "History Log" that tracks timestamps of when it moved between tabs and who moved it. 2. Main Overall Dashboard Layout: A master control panel displaying all active projects. Features: "Create New Project" button (Requires User to input Project Name). "Delete Project" button (Requires secondary confirmation). High-level graphical summary of all combined projects (Total documents, overall approval progress). Clicking on a specific Project card opens the Project-Specific Dashboard. 3. Project-Specific Dashboard & Tab Structure When a project is opened, display a dashboard specific to that project, featuring dynamic charts tracking document statuses. Below the charts, implement a persistent tabbed navigation bar with the following tabs: Vendor(s) (Support multiple: Vendor 1, Vendor 2, etc.) GES (Engineering Services) Madina (Main Contractor) QE-LNG (Client) 4. Document Creation Logic (Vendor & GES Tabs) When a user clicks "Create New Document" in either the Vendor or GES tab, open a form with the following rules: Manual Entry Fields: The app MUST require the user to manually type the "Document Title", "Document Number", and "Revision Number". Do not auto-generate the document number. Category Dropdown: Require the user to select the document purpose: "IFA (Issued for Approval)" or "IFC (Issued for Construction)". AI Upload & Summarize Feature (Max 50MB): Provide an "Upload Document/Image" button. Action: Upon upload, an integrated AI must scan the document, extract the key data, and generate a text summary highlighting: 1. Completed/Correct elements, and 2. Mistakes/Discrepancies to be addressed. Memory Saver: Once the text summary is generated and saved to the document's profile, the app must automatically delete the uploaded source file to save database storage. 5. Document Routing & Visibility Rules (The Core Engine) Documents must never disappear from a tab; they only change status and duplicate into the receiver's tab. Vendor to Madina Flow: * The Vendor tab has a "Send to Madina" button. When clicked, the document status in the Vendor tab changes to "Sent to Madina - Under Review". Simultaneously, the document appears in the Madina Tab with the status "Received from Vendor - Action Required". GES to Madina Flow: * GES can also originate documents. The process mirrors the Vendor flow, utilizing a "Send to Madina" button, keeping the document visible in the GES tab as "Sent to Madina". 6. Madina Tab Actions (The Hub) When a document lands in the Madina tab, the user clicks on it to reveal three distinct action buttons: "Send to GES": Routes the document to the GES tab for engineering endorsement. Status updates to "Under Review with GES". "Send to QE-LNG": Routes the document to the client tab for final approval. Status updates to "Submitted to QE-LNG". "Return for Revision": Sends the document back to the originator (Vendor or GES). Prompts the user to type in the next anticipated Revision Number so the originator knows what to update it to. 7. QE-LNG Tab Logic (Client Approval & Coding) When a document is in the QE-LNG tab, it requires a final review action. Provide three specific grading buttons: Code A (Accepted): Changes document status to "Accepted". Automatically changes the document category from IFA to IFC (Issued for Construction). Updates the status across all previous tabs (Madina, GES, Vendor) to reflect final approval. Code B (Accepted with Comments) & Code C (Revise and Resubmit): Clicking either B or C MUST trigger a mandatory "Upload Commented Document" field (Max 50MB). Once the marked-up document is uploaded, display a "Return to Madina" button. When clicked, the document returns to the Madina tab (and subsequently back to the originator). The uploaded commented document must be preserved and accessible to Madina/GES/Vendor so they can see the exact markups required for the next revision.

Mar 11

View

hyper-weather

Monin Modi

weather application with 2 pages and simple design

Mar 11

View

zen-app

MOHAMMAD KHIZARUDDIN

Create a modern mobile app called CONNECT ONE. Features: - User signup and login - Profile creation - One-to-one chat - Voice and video calling - News feed - Interest based communities - Clean modern UI similar to WhatsApp and Facebook Include: Home screen Chat screen Profile screen News screen Call interface

Mar 11

View

prime-weather

Monin Modi

create an weather forecast app with 2 pages

Mar 11

View

silver-app

Hemen Ashodia

build a nice to do app

Mar 11

View

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20