Expo Go comes with a pre-configured set of libraries, known as the Expo SDK. This makes development much faster, and essentially makes the mobile development experience much closer to the web development experience. However, additional native code cannot be added to Expo Go on the fly, so this means you are limited in terms of what dependencies you can add.
In the bare workflow, we have full access to the underlying native projects and any native code. It's a "bare" native project with React Native and one or more packages from the Expo SDK installed. Anything that you can do in a native project is possible here.
true, it does come with its advantages, but a lot of issues in development, and i try as much as possible to avoid issues on production, as to what customers may run into.
now the issue is, isn't there a way one could build react native using CLI and still harness the power of Expo while utilizing other libraries.
i loved expo while using it, but the issues i ran into, made my experience terrible, i've been trying to delve into flutter development, and i still would, but at the moment, it wouldnt be bad to see how best to master react native CLI.
its just not good for a while in development process... this gives me concern... as to what happens if an issue is unresolved, and more keeps piling up each day.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why not expo?
true, it does come with its advantages, but a lot of issues in development, and i try as much as possible to avoid issues on production, as to what customers may run into.
now the issue is, isn't there a way one could build react native using CLI and still harness the power of Expo while utilizing other libraries.
i loved expo while using it, but the issues i ran into, made my experience terrible, i've been trying to delve into flutter development, and i still would, but at the moment, it wouldnt be bad to see how best to master react native CLI.
a lot of those issues still unresolved. here's a list and it just keeps increasing..
github.com/expo/expo-cli/issues
its just not good for a while in development process... this gives me concern... as to what happens if an issue is unresolved, and more keeps piling up each day.