# Project foundations Explore repositories by project goal or target platform. Compare business applications, app foundations, game engines and supporting libraries before choosing your starting point. Page 1 of 1 ## Ignite Project generator React Native and Expo project generator with reusable components, navigation, theming and test conventions. ### Why we recommend it Ignite is useful when a team wants a consistent mobile application structure rather than assembling every convention independently. Its generator and bundled boilerplate give a starting point for screens, components, localization and development tooling that can be adapted to the product. ### When to choose it - Cross-platform customer apps and internal mobile tools. - Teams building several React Native products with shared architecture and testing conventions. ### What to consider - This clone contains the Ignite CLI and boilerplate source; creating your app with the published CLI is a separate step. - Native builds still need platform tooling, signing and store preparation. The MIT code license does not grant permission to reuse Ignite or Infinite Red trademarks. ### Start with this project Prepare Node.js and the React Native or Expo development environment for your target platforms. Use the documented Ignite CLI to generate the actual app in a separate directory, review the generated code and dependencies, then set up a simulator or device build. iOS builds require Apple's tooling. Technology: TypeScript, React Native, Expo License: MIT Default branch: master Sources checked: 2026-10-25 [Explore project](https://orqestria.com/en/catalog/repositories/ignite) [Start a project in Orqestria](orqestria://catalog/project?repository=ignite) Choose a name and location in Orqestria to clone the generator source and assign the recommended team. Generating your actual application is a separate step. No dependencies are installed and no application is started. ### Official sources - [https://github.com/infinitered/ignite](https://github.com/infinitered/ignite) - [https://github.com/infinitered/ignite/blob/master/README.md](https://github.com/infinitered/ignite/blob/master/README.md) - [https://github.com/infinitered/ignite/blob/master/LICENSE](https://github.com/infinitered/ignite/blob/master/LICENSE) ## Obytes React Native Starter Application starter Expo and React Native starter with file-based navigation, data fetching, localization and environment-specific configuration. ### Why we recommend it We recommend it when a TypeScript team wants a mobile app with clear conventions for routing, API calls and reusable UI. The starter brings these foundations together, making it easier to spend the next iteration on customer journeys and backend integration. ### When to choose it - Mobile customer portals and employee apps backed by an existing API. - A shared iOS and Android codebase with development, staging and production environments. ### What to consider - The sample authentication flow still needs a real backend and a deliberate credential-storage design; it is not a completed identity system. - Native modules, permissions and custom development builds require platform setup. Expo services and app-store distribution have their own terms and possible fees. ### Start with this project Use the pnpm version declared by the repository and an Expo-compatible Node.js environment. Follow the starter's documentation, configure app identifiers and environments, review dependencies, then prepare the development client and target-platform tooling before testing on devices. Technology: TypeScript, React Native, Expo, Expo Router License: MIT Default branch: master Sources checked: 2026-10-25 [Explore project](https://orqestria.com/en/catalog/repositories/obytes-react-native) [Start a project in Orqestria](orqestria://catalog/project?repository=obytes-react-native) Choose a name and location in the app. Orqestria clones the repository into a new project and assigns the recommended agent team. It does not install dependencies or start the application. ### Official sources - [https://github.com/obytes/react-native-template-obytes](https://github.com/obytes/react-native-template-obytes) - [https://github.com/obytes/react-native-template-obytes/blob/master/README.md](https://github.com/obytes/react-native-template-obytes/blob/master/README.md) - [https://github.com/obytes/react-native-template-obytes/blob/master/LICENSE](https://github.com/obytes/react-native-template-obytes/blob/master/LICENSE) - [https://github.com/obytes/react-native-template-obytes/blob/master/package.json](https://github.com/obytes/react-native-template-obytes/blob/master/package.json) ## Very Good CLI Project generator Dart command-line generator for Flutter applications, packages, plugins and other Dart projects. ### Why we recommend it Very Good CLI is useful when your team wants repeatable project generation with established analysis and testing conventions. Select a Flutter application template for a new mobile product, or a narrower package template when building reusable functionality. ### When to choose it - Flutter mobile products that need a consistent project structure. - Teams maintaining multiple Flutter applications and shared Dart packages. ### What to consider - The repository is the CLI source, not a generated mobile app. Choose a template and generate the application separately. - Template choices and Flutter or Dart SDK requirements evolve. Native plugins, signing, store releases and any hosted services remain separate project work. ### Start with this project Install compatible Dart and Flutter SDKs, then follow the published Very Good CLI documentation. Generate a flutter\_app in a separate directory, review its configuration, fetch dependencies and run its checks. Configure the Android and iOS toolchains for the platforms you will ship. Technology: Dart, Flutter License: MIT Default branch: main Sources checked: 2026-10-25 [Explore project](https://orqestria.com/en/catalog/repositories/very-good-cli) [Start a project in Orqestria](orqestria://catalog/project?repository=very-good-cli) Choose a name and location in Orqestria to clone the generator source and assign the recommended team. Generating your actual application is a separate step. No dependencies are installed and no application is started. ### Official sources - [https://github.com/VeryGoodOpenSource/very\_good\_cli](https://github.com/VeryGoodOpenSource/very_good_cli) - [https://github.com/VeryGoodOpenSource/very\_good\_cli/blob/main/README.md](https://github.com/VeryGoodOpenSource/very_good_cli/blob/main/README.md) - [https://github.com/VeryGoodOpenSource/very\_good\_cli/blob/main/LICENSE](https://github.com/VeryGoodOpenSource/very_good_cli/blob/main/LICENSE) - [https://github.com/VeryGoodOpenSource/very\_good\_cli/blob/main/pubspec.yaml](https://github.com/VeryGoodOpenSource/very_good_cli/blob/main/pubspec.yaml) ## Now in Android Reference project Google's Kotlin and Jetpack Compose reference application demonstrating modular Android architecture. ### Why we recommend it Use it to study and selectively adopt Android UI, data and testing patterns. It shows how multiple modules fit together in a working content application, which is valuable when planning a larger native Android product. ### When to choose it - Native Android apps with a modular architecture and a substantial test strategy. - Teams evaluating Compose, dependency injection and data-layer organization before starting their own app. ### What to consider - This is a reference app about Android news, not a generic business starter. Replace its content, branding and domain model rather than treating it as a finished product. - The production backend is not public. Use the demo build variants with local data; the prod variants are not a ready-to-run service. ### Start with this project Import the clone into a compatible stable Android Studio with the required Android SDK and Gradle toolchain. Select the app module and demoDebug variant for local exploration. Study the architecture and modularization guides, then choose the patterns your business app actually needs. Technology: Kotlin, Jetpack Compose, Gradle License: Apache-2.0 Default branch: main Sources checked: 2026-10-25 [Explore project](https://orqestria.com/en/catalog/repositories/now-in-android) [Start a project in Orqestria](orqestria://catalog/project?repository=now-in-android) Choose a name and location in Orqestria to clone these sources and assign the recommended team. Check the setup guide: an engine or library repository needs a separate game or application project. No dependencies are installed and no application is started. ### Official sources - [https://github.com/android/nowinandroid](https://github.com/android/nowinandroid) - [https://github.com/android/nowinandroid/blob/main/README.md](https://github.com/android/nowinandroid/blob/main/README.md) - [https://github.com/android/nowinandroid/blob/main/LICENSE](https://github.com/android/nowinandroid/blob/main/LICENSE) ## Clean Architecture SwiftUI Reference project SwiftUI reference app showing separated presentation, business logic and data access with SwiftData persistence. ### Why we recommend it It is useful when planning a native Apple-platform app whose interface and data layer should remain independently testable. The countries demo makes navigation, dependency injection and state management concrete enough to adapt thoughtfully to your own product. ### When to choose it - Native SwiftUI apps with persistent data and a clearly separated domain layer. - Teams comparing architecture and test patterns before implementing customer or employee workflows. ### What to consider - This is a countries demo backed by an external API, not a complete business application or authentication starter. - Adapting it requires replacing the domain and checking Apple deployment targets, SwiftData requirements and dependency compatibility. ### Start with this project Open the project with a compatible Xcode and Apple SDK on macOS. Review the demo's data API and package dependencies, run its tests and explore navigation and persistence. Build your own domain and authentication flow separately instead of retaining the demo's assumptions. Technology: Swift, SwiftUI, Combine, SwiftData License: MIT Default branch: master Sources checked: 2026-10-25 [Explore project](https://orqestria.com/en/catalog/repositories/clean-architecture-swiftui) [Start a project in Orqestria](orqestria://catalog/project?repository=clean-architecture-swiftui) Choose a name and location in Orqestria to clone these sources and assign the recommended team. Check the setup guide: an engine or library repository needs a separate game or application project. No dependencies are installed and no application is started. ### Official sources - [https://github.com/nalexn/clean-architecture-swiftui](https://github.com/nalexn/clean-architecture-swiftui) - [https://github.com/nalexn/clean-architecture-swiftui/blob/master/README.md](https://github.com/nalexn/clean-architecture-swiftui/blob/master/README.md) - [https://github.com/nalexn/clean-architecture-swiftui/blob/master/LICENSE](https://github.com/nalexn/clean-architecture-swiftui/blob/master/LICENSE)