For ExpoKit apps and React Native apps I don’t think it’ll change.
But I’m not sure for Expo Apps. Depends on if their implementation allows for 60 second intervals between tasks, or if they use a similar approach as react-native-background-fetch which activates every 15 minutes. Based on the PR itself I wasn’t able to tell which one’s the case.
Love the vision and direction that Expo is taking with ExpoKit! I also love the humbleness and how much this post acknowledges developer pain points in the past with ExpoKit, shows that the Expo team has been working closely with devs to get feedback.
Wow, this is so dope! I haven’t actually put this into test, but does this flow also allow for automating development work on AppSync in multiple environments?
For example, if I make changes to my schema and resolvers, would I be able to push those changes to my other environments?
Hey Charles, thanks for taking the time and responding to my comment!
I think “Maintain consistent native folder structure” is maybe an unrealistic demand because as the ecosystem grows they may have to make drastic changes to the structure. A lot of times the big changes they made in the past has reduced complexity, so I’m…
I really love Expo and I think it has saved countless hours of development for me on various projects.
However, the initial ejection and getting the app to build again is actually one of the simpler parts of living with an ejected Expo app.
This can potentially be a big step towards making Expo available for more users in places like China and Iran. Some of our users from places like that (with either slow internet or behind a VPN) have had trouble with Expo apps due to being unable to download the js bundle from expo servers for whatever reason.