How tuando169/ar-scan-fe works
Project type and purpose
• This is a single-page front-end application built with React, TypeScript, and Vite. There is no embedded backend in the repo; all server-side behavior is delegated to external APIs (endpoints defined in src/apiEndpoints.ts).
• The purpose is an AR-enabled model viewer/manager with user authentication, model scanning, and model-management UIs.
File structure
• public/
• Static assets (e.g., druid.gltf) and index.html
• src/
• App.tsx, main.tsx: the SPA entrypoint
• apiEndpoints.ts: central config for all HTTP endpoints
• components/
– ar/: AR scene and 3D model renderers
– auth/: Login/Register popups
– scan/: scanning UI
– manage/: CRUD popups for models
– layouts/: shared layout elements (e.g., BottomNav)
• types.tsx: shared TS types
• config files: vite.config.ts, tsconfig*.json, eslint.config.js
README for additional insights
• It’s a minimal Vite template with HMR, React + TS setup, ESLint rules.
• No built-in backend; the architecture relies on external services.
Elements
– Labels: “User Browser,” “Vite Dev Server,” “Static Host (CDN),” each React module.
• from Browser → Static Host (initial load)
• from React Components → API Gateway → Services
• between Services → Databases / Asset Storage
• Blue rectangles for front-end modules
• Gray clouds for external services
• Orange diamonds for build tools (Vite)