How tkhwang/tkcapture works
Project Type and Purpose
• The project is designed as a multi-app monorepo featuring a backend (using Nest.js) and two client applications—a mobile app (tkCaptureBook) built with React Native Expo and a web app.
• It’s positioned as a development tool suite with AI components (as noted in the “Common” section) and covers authentication, book searching, camera features, and other UI‐features using libraries like jotai and tailwind.
• The README emphasizes a tech stack for the mobile app that includes supabase for backend services, which—per your special instructions—should be directly connected to the mobile app rather than integrated with the Nest.js backend.
Breaking Down the File Structure
• There is a clear separation at the top level:
• apps/backend → Contains Nest.js-based backend logic, controllers, modules, and test suites.
• apps/tk-capture-book → Houses the mobile application’s business logic, user interface (React Native with Expo), supabase calls, assets, and various features (auth, camera, book search, etc.).
• apps/web → Contains a web interface built with a modern React-based framework (layout, CSS, components).
• packages/mobile-components → A shared library that might offer UI components for mobile.
• Build and configuration files (e.g., package.json files, tsconfigs, Android & iOS subdirectories) show that each application is configured separately for its respective platform.
Major Components and Relationships
a. Core Components to Represent:
• Mobile App (tkCaptureBook): Built with React Native Expo. This is the primary consumer of Supabase given the new instructions.
• Web App: Provides a browser-based user experience.
• Supabase: As the data and authentication backend. With the custom instruction, this is disconnected from the backend service and shown as a direct dependency of the mobile app.
• Shared/Utility Components: Such as libraries (mobile-components) and possibly other utilities (e.g., jotai-storage, react-query-client) seen in the tkCaptureBook’s lib directory.
b. Connections and Data Flow:
• The Web App might or might not directly interact with Supabase based on how its own lib/integration is defined; assess if there’s a direct connection or if it relies on the Nest.js API (if it does use Supabase directly, mark that accordingly).
Architectural Patterns and Technologies
• That the mobile app uses a modern frontend stack (React Native Expo with jotai state management and tailwind css styling).
• That the backend is implemented with a Nest.js framework suggesting a modular architecture.
• That Supabase is used as a Backend-as-a-Service for mobile app data management and authentication (and now, per instructions, it is decoupled from the backend).
• Use of build/deployment tools (EAS Build scripts for iOS and Android) as part of the mobile development cycle.