How apknation/skincare-app works
Sura Yangu is an Android skincare marketplace: shoppers assess their skin, discover and compare approved products, check out, and track orders; sellers manage products and fulfilment, while admins moderate the platform. The Flutter client talks to a Dart HTTP API backed by PostgreSQL, with product images stored separately. The README documents the major capabilities and API flow, but no runtime source was sampled, so implementation-level client dispatch and backend route wiring are not asserted.
Main entry points: api_client.dart API client · server.dart HTTP server · app.dart Role-based app shell · checkout_page.dart Cart and checkout
Components 21
Flutter client
- Role-based app shell
lib/app.dart - Client state
lib/data/store.dart - API client
lib/data/api_client.dart
Shopper experience
- Skin assessment
lib/features/skin/assessment_page.dart - Product matching
lib/data/recommendation_engine.dart - Catalog and comparison
lib/features/catalog/catalog_page.dart - Product detail
lib/features/product/product_details_page.dart - Cart and checkout
lib/features/cart/checkout_page.dart - Payment selection
lib/features/cart/payment_sheet.dart - Order tracking
lib/features/orders/orders_page.dart
Seller and admin tools
- Seller operations
lib/features/seller/seller_dashboard_page.dart - Administration
lib/features/admin/admin_page.dart
API and persistence
- HTTP server
backend/bin/server.dart - Auth and core API
backend/lib/api_core.dart - Order API
backend/lib/api_orders.dart - Image upload API
backend/lib/api_uploads.dart - PostgreSQL
backend/migrations/001_init.sql - Uploaded images
backend/uploads
Other components
- Shopper
- Seller
- Admin
Connections 25
- Shopper → Role-based app shell: uses
README.md - Seller → Role-based app shell: uses
README.md - Admin → Role-based app shell: uses
README.md - Role-based app shell → Skin assessment: offers
README.md - Skin assessment → API client: saves profile
README.md - Product matching → Catalog and comparison: ranks matches
README.md - Shopper → Product matching: receives matches
README.md - Shopper → Catalog and comparison: browses
README.md - Catalog and comparison → Product detail: opens product
README.md - Shopper → Cart and checkout: checks out
README.md - Cart and checkout → Payment selection: selects payment
README.md - Cart and checkout → API client: submits order
README.md - Payment selection → API client: starts and confirms
README.md - Order tracking → API client: loads orders
README.md - Seller → Seller operations: manages shop
README.md - Seller operations → API client: uses seller endpoints
README.md - Admin → Administration: moderates
README.md - Administration → API client: uses admin endpoints
README.md - API client → HTTP server: sends JSON requests
README.md - HTTP server → Auth and core API: routes API requests
README.md - HTTP server → Order API: routes order requests
README.md - HTTP server → Image upload API: routes uploads
README.md - Auth and core API → PostgreSQL: persists marketplace data
README.md - Order API → PostgreSQL: persists orders
README.md - Image upload API → Uploaded images: stores image bytes
README.md