Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how is this different from code push? #9

Open
bansal-rahul opened this issue Jan 2, 2019 · 2 comments
Open

how is this different from code push? #9

bansal-rahul opened this issue Jan 2, 2019 · 2 comments

Comments

@bansal-rahul
Copy link

bansal-rahul commented Jan 2, 2019

@surya-kanoria
Can you please explain how is this different from other OTA-update services like code push?

@PavanGangireddy
Copy link

@surya-kanoria
Is this still under active development?

@gupta-ji6
Copy link

@surya-kanoria
Can you please explain how is this different from other OTA-update services like code push?

@bansal-rahul, I found this which explains how is it different from CodePush

When we looked at the known existing solutions like CodePush etc, we found three major issues that were not solved but were critical for us:

  1. The updates were not really instant as a cached bundle gets loaded while it silently gets updated in the background.
  2. These updates were enormous in size (around 700kB) as the entire bundle gets downloaded at the client-end everytime an update is shipped. For our average 2G users who visit the app once a month, it would take more than 30s for the React Native bundle to get downloaded and the page to be loaded everytime the App is launched.
  3. We have multiple teams maintaining their own React Native bundles. When these teams themselves share a lot of common components besides the React Native Framework Code, lots of redundant download is caused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants