|
| 1 | +# 🔮 Updates & Roadmap |
| 2 | + |
| 3 | +This document outlines the future vision for `react-native-lab`. We prioritize features that reduce "setup fatigue" and enforce professional best practices. |
| 4 | + |
| 5 | +## 📦 Package Manager Recommendation |
| 6 | + |
| 7 | +For developing `react-native-lab` itself, we recommend using **npm**. |
| 8 | + |
| 9 | +- **Why?** It is the default for Node.js, ensuring maximum compatibility for contributors without requiring additional tools. |
| 10 | +- **Future Consideration:** If the repository grows into a monorepo (e.g., separating templates into packages), we will migrate to **pnpm** for its workspace efficiency and disk space savings. |
| 11 | + |
| 12 | +--- |
| 13 | + |
| 14 | +## 📅 Roadmap |
| 15 | + |
| 16 | +### v1.4.0: Asset Optimization & Splash Screens 🎨 |
| 17 | + |
| 18 | +**Goal:** Automate the tedious process of generating app icons and splash screens. |
| 19 | + |
| 20 | +- **Feature:** `npx react-native-lab generate-assets` |
| 21 | +- **Why:** Developers hate manually resizing images for Android/iOS. |
| 22 | +- **Tech:** Integrate `react-native-bootsplash` or similar tools automatically. |
| 23 | + |
| 24 | +### v1.5.0: State Management Selection 🧠 |
| 25 | + |
| 26 | +**Goal:** Give developers options for rigorous state management beyond React Context. |
| 27 | + |
| 28 | +- **Feature:** Option to add **Zustand** or **Redux Toolkit** during setup. |
| 29 | +- **Why:** As apps scale, Context API often falls short. Zustand is growing in popularity for its simplicity, while Redux remains the enterprise standard. |
| 30 | + |
| 31 | +### v1.6.0: API & Networking Layer 🌐 |
| 32 | + |
| 33 | +**Goal:** Provide a production-ready networking setup. |
| 34 | + |
| 35 | +- **Feature:** Pre-configured `TanStack Query` (React Query) + `Axios` instance. |
| 36 | +- **Why:** Dealing with caching, loading states, and error handling is mandatory in every app. We should automate the best-practice setup. |
| 37 | + |
| 38 | +### v2.0.0: The Plugin System 🧩 |
| 39 | + |
| 40 | +**Goal:** Move from a "CLI tool" to a "Platform". |
| 41 | + |
| 42 | +- **Feature:** Allow the community to create and publish their own templates (e.g., `react-native-lab init --template @user/my-template`). |
| 43 | +- **Why:** We can't maintain every possible stack. Empowering the community scales the ecosystem indefinitely. |
| 44 | + |
| 45 | +### v2.1.0: Expo Support? 🤔 |
| 46 | + |
| 47 | +**Goal:** Support the Expo ecosystem. |
| 48 | + |
| 49 | +- **Feature:** `react-native-lab init --type expo` |
| 50 | +- **Why:** Expo is becoming the default for many. Creating a unified CLI for both bare and Expo workflows would be powerful. |
| 51 | + |
| 52 | +--- |
| 53 | + |
| 54 | +## 🛠️ Internal Improvements (Continuous) |
| 55 | + |
| 56 | +- **Test Coverage:** Increase unit and E2E test coverage for the CLI. |
| 57 | +- **Telemetry:** Optional, anonymous usage tracking to see which templates are most popular (strictly no PII). |
0 commit comments