How rayaan-khan428/beacon works
Project type and purpose
• This is a multi-component full-stack application.
• “ios_app” is an iOS SwiftUI mobile client (“BeaconAI”).
• “website” is a Next.js/React marketing/web client.
• “backend” is a Python service (likely REST/GraphQL API).
• “lambda” contains a zipped Python AWS Lambda deployment (with Twilio and other dependencies) for serverless workflows and webhooks.
• Purpose (inferred): BeaconAI mobile and web clients interact with a core Python backend, which delegates certain async or telephony tasks to AWS Lambda functions (e.g., via Twilio), plus a public website.
File structure
• Top-level directories:
• backend/venv – Python virtual environment for the main API.
• ios_app/BeaconAI – Xcode project implementing the mobile UI and data models (Item.swift, OnboardingView.swift, etc.).
• lambda/ – all Python dependencies and the “lambda_function.py” entry point packaged for AWS Lambda. Many Twilio SDK modules are present.
• website/ – Next.js (app/, components/, lib/) with TailwindCSS, TypeScript, and configuration files.
• Patterns and config:
• backend/ likely hosts your core API (no code shown, but venv suggests Flask, FastAPI, or Django).
• lambda/ contains a self-contained deployment package (third-party libs + your function).
• website/ is a standard React/Next.js monorepo layout.
• No explicit infrastructure-as-code files in root (e.g., Terraform), but assume AWS SAM/CloudFormation elsewhere.
README
• README is empty, so we rely on conventions and directory names. The “BeaconAI” branding signals a location/beacon-related AI offering with telephony or messaging integrations.