How malikyakub/mk-passes works
Project type and purpose
• This is a full-stack, cross-platform mobile application built with Expo/React Native (android/ and ios/ folders, metro.config.js, index.js, app/ screens, components/, hooks/).
• It also includes a small Node.js “backend” (backend/server.js) alongside a Supabase-backed database (utils/supabase.js).
• Purpose: a password-generator and message-encrypter app featuring user authentication, CRUD for saved passwords, and message encryption/decryption.
File structure
• Top-level:
• android/, ios/ → native build artifacts and configurations for Android and iOS
• app/ → Expo Router directory: each .tsx/.jsx file is a screen or layout in the navigation tree
• components/ → reusable UI pieces (cards, headers, navigation controls)
• hooks/ → custom React hooks handling auth (useAuth), data (usePasswords, useUsers), font loading (useL-Fam)
• utils/ → supabase.js for initializing the Supabase client
• backend/ → Node.js API (server.js + package.json) that may offer custom endpoints or middleware beyond Supabase
• Build & deployment:
• app.json, eas.json → Expo config & build profiles
• .github/workflows/codeql.yml → CI/CodeQL scanning
• tsconfig.json, package.json → TypeScript & dependency management
README
• Confirms: “Mk-passes – password generator and message encrypter”
• No additional architecture notes; everything is implicit in the folder layout.