FAQ

I don't know some technology! Should I buy TurboStarter?

You should be prepared for a learning curve or consider learning it first. But, TurboStarter will still work for you if you're willing to learn.

Anyway, without knowing some technologies, you can still use rest of the features.

I don't need mobile app or browser extension, what should I do?

You can simply ignore the mobile app and browser extension parts of the project. You can remove the apps/mobile and apps/extension directories from the project.

The modular nature of TurboStarter allows you to remove parts of the project that you don't need without affecting the rest of the stack.

Will you add more packages in the future?

Yes, we will keep updating the TurboStarter with new packages and features. This kit is designed to be modular, allowing for new features and packages to be added without interfering with your existing code. You can always update your project to the latest version.

Does it set up the production instance for me?

No, TurboStarter does not set up the production instance for you. This includes setting up Supabase, Stripe, and any other services you need. TurboStarter does not have access to your Stripe or Supabase accounts, so setup on your end is required. TurboStarter provides the codebase and documentation to help you set up your SaaS project.

Does the starter include Solito?

No. Solito will not be included in this repo. It is a great tool if you want to share code between your Next.js and Expo app. However, the main purpose of this repo is not the integration between Next.js and Expo — it's the code splitting of your SaaS platforms into a monorepo. You can utilize the monorepo with multiple apps and it can be any app such as Vite, Electron, etc.

Integrating Solito into this repo isn't hard, and there are a few official templates by the creators of Solito that you can use as a reference.

Does this pattern leak backend code to my client applications?

No, it does not. The api package should only be a production dependency in the Next.js application where it's served. The Expo app, browser extension and all other apps you may add in the future, should only add the api package as a dev dependency. This lets you have full typesafety in your client applications, while keeping your backend code safe.

If you need to share runtime code between the client and server, you can create a separate shared package for this and import it on both sides.

How do I get support if I encounter issues?

For support, you can:

1. Visit our Discord
2. Contact us via support email (hello@turbostarter.dev)

How do I deploy my application?

Please check the production checklist for more information.

How do I update my project when a new version of the boilerplate is released?

Please read the documentation for updating your TurboStarter code.

Can I use the React package X with this kit?

Yes, you can use any React package with this kit. The kit is based on React, so you are generally only constrained by the underlying technologies and not by the kit itself. Since you own and can edit all the code, you can adapt the kit to your needs. However, if there are limitations with the underlying technology, you might need to work around them.