How ah-oztrk/socialsense works
Project type and purpose
• This is a full-stack “SocialSense” application:
• Back-end API built with Python/FastAPI (folder app/)
• Mobile/React-based front-end built with Expo/TypeScript (folder social-sense/)
• A relational database (e.g. PostgreSQL) accessed via SQLAlchemy or similar
File structure
• Top-level separation:
• app/ – FastAPI server code (API routers, core logic, DB, models/schemas)
• social-sense/ – Expo/React Native front-end (App.tsx, app routes, components, assets, hooks)
• tests/ – Python unit tests for back-end routes
• Within app/:
• api/routes/ – endpoint definitions (auth, forum, history, query, user)
• core/ – application-wide logic (authentication, security utilities)
• db/ – database connection and session management
• models/ & schemas/ – ORM models vs. Pydantic schemas for request/response
• main.py – FastAPI application entrypoint
• Within social-sense/:
• app/(tabs) – Expo Router tab-based screens
• components/ – reusable UI pieces and tests
• assets/, constants/, Tailwind/metro configs
README
• It simply names the project “SocialSense,” so we infer the domain is a social or community-driven mobile application with forum and query/history features.