How thomino/expo-playground works
Project type and purpose
• This is a single-page mobile application built with React Native + Expo.
• It’s a “playground” app demonstrating UI features: onboarding slider, masonry grid, light/dark theming, etc.
File structure
• Top-level code lives under:
• app/ – core React components, screens, hooks, contexts, and the entry point (index.tsx)
• components/ – reusable UI components (Header, SlideUp, ThemeToggle, etc.)
• utils/ & lib/ – pure utilities and helpers (date, BackHandlerManager, useShadow, etc.)
• assets/ – images and Lottie animation JSONs
• Config & build scripts: metro.config.js, babel.config.js, postcss.config.js, tailwind.config.js, tsconfig.json, plus standard package.json & app.json for Expo.
README for additional insights
• Light/dark theme toggle
• Masonry layout screen
• Onboarding slider
• Built with Expo + React Native, tailwind/nativewind for styling.
Diagramming recommendations
• Use clear labels for each layer/component (e.g., “ThemeContext Provider,” “Onboarding Screen”).
• From user → UI components → navigation → screens → contexts/utilities.
• From bundler → JS bundle → Expo runtime → native platform.
• Another for state management (contexts/hooks)
• A third for build/config (Metro/Babel/Expo)
• A fourth for assets & utils