How codeback-up/sticker-smash-expo works
Project type and purpose
• This is a front-end–only mobile application built with Expo (React Native).
• It employs Expo’s managed workflow and “file-based routing” via the Expo Router, providing a tabbed navigation UI and several reusable components (buttons, emoji pickers, image viewers, etc.).
File structure
• Top-level directories:
• app/ – your source code using Expo Router for navigation (tab layout under app/(tabs)).
• components/ – reusable UI widgets (Button, EmojiPicker, ImageViewer, etc.).
• assets/ – static fonts and images.
• Config files:
• app.json & app.config.js – Expo configuration (app metadata, asset bundling).
• eas.json – EAS Build and Submit configurations.
• tsconfig.json & package.json – TypeScript and dependency setup.
• No backend or server code—pure client.
README for additional insights
• Confirms it’s a “create-expo-app” starter, customized via file routing.
• Emphasizes developing inside app/ and running via “npx expo start.”
Detail
• Config files and scripts that drive the build & deploy process.
• Don’t omit the routing conventions (file names map to routes).
• Optional extension points (e.g., where you’d plug in push notifications or analytics).