project-793ea2e0

:rocket: HACKATHON PROJECT BRIEF: PROJECT LOCALSYNC The Real-Time Field Operations & Command Center Ecosystem (8-Hour Sprint) :clipboard: 1. PROJECT OVERVIEW Your team is tasked with building LocalSync, a cross-platform logistics and coordination ecosystem designed for fast-paced field operations. Due to the aggressive 8-hour timeline, the team must focus strictly on the Core Real-Time Loop: building an API that instantly links a lightweight Mobile tracking interface with a Desktop monitoring dashboard. :hammer_and_wrench: 2. MINIMAL VIABLE PRODUCT (MVP) REQUIREMENTS A. The Backend API (The Brain) • Live Stream: Implement a simple WebSockets or Server-Sent Events (SSE) server to receive and broadcast coordinates.. • Volatile In-Memory Storage: Skip complex database migrations. Store active user locations in global memory arrays or a simple JSON file for instant speed.. • Single Dispatch Endpoint: A basic HTTP POST endpoint to assign a task ID to an agent ID.. B. The Mobile App (The Field Agent) • Coordinate Ping: A single screen with a "Go Online" toggle button that sends simulated or real location updates every 3 seconds via WebSockets.. • Task Alert: A simple pop-up or layout change that flashes when a task is pushed to them from the desktop command center, with a single button to click "Complete".. C. The Desktop App (The Command Center) • The Live Map: A layout rendering a map web-view showing the live, moving point of the mobile user.. • Instant Dispatch Button: Next to the map, a list of available agents with a manual button next to their name that instantly pushes a task to their phone.. :warning: 3. STRICT 8-HOUR CONSTRAINTS & RULES 1. Code Sharing is Mandatory: The team must use a single language or framework ecosystem across all environments (e.g., Flutter for both apps, or a TypeScript Monorepo for Node/React/Electron) to eliminate context switching.. 2. No Advanced Polish: Do not waste time on secure user registration, forgot password loops, cloud media storage, or complex CSS styling. Use raw UI components or a basic component library.. 3. The "One-Device" Demo Rule: Because time is short, the mobile app can be run inside an emulator on the exact same computer running the desktop app to simplify deployment and testing.. :stopwatch: 4. CRITICAL 8-HOUR SPRINT MILESTONES • Hour 0–1 (The Blueprint): Initialize your monorepo. Define your shared JSON payload interface (what does a location update look like?). Boot up a skeleton backend server.. • Hour 1–3 (The Data Bridge): Establish the raw WebSocket connection. Verify that typing mock coordinates into a mobile text-box prints them live in the desktop terminal console.. • Hour 3–5 (The Visual Loop): Hook up the map library on the Desktop app to show the pin moving visually. Hook up the simple task push button.. • Hour 5–7 (The Workflow & Integration): Verify the entire end-to-end loop: Dispatch from Desktop :arrow_right: Alert pops up on Mobile :arrow_right: Click complete on Mobile :arrow_right: Desktop updates.. • Hour 7–8 (The Freeze & Demo prep): Hard code-freeze. Do not touch any core files. Practice the 3-minute live presentation run-through to make sure it functions perfectly for the judges.. :bar_chart: 5. JUDGING & EVALUATION CRITERIA CriteriaWeightWhat Judges Look ForReal-Time Data Flow40%Does moving the mobile client immediately update the desktop dashboard without refreshing?End-to-End Workflow30%Can you successfully push a task to the mobile app and see it get completed?Speed & Resourcefulness20%How smartly did the team cut scope and reuse code to match the 8-hour limit?Pitch & Demo Stability10%A working, live, crash-free presentation. :outbox_tray: 6. SUBMISSION TEMPLATE • Repository Link:[Insert Code URL here]. • Tech Stack Used:[Frontend, Backend, Desktop, Mobile]. • How to run it in under 60 seconds:[Provide exactly 2 or 3 terminal terminal commands to boot the whole stack up for the judges]. Good luck, team! Under an 8-hour constraint, a dirty, working prototype is 100 times better than beautiful, broken code.