You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This one is a tad associated to #19
It might not be technically doable though, it's just an idea at this point and some technical research should be done.
But basically, what if LiveBundle could also serve full application binaries (apk/app).
Indeed, given that some application changes will contain native changes, that cannot be distributed in a JS bundle only, LiveBundle could in this case package the whole application binary, and still provide a QR Code / Deep Link. But in that case, instead of downloading/installing the bundle and hot reloading the application, it would instead reinstall the full binary (and application would have to be relaunched). Otherwise, such app binaries would have to be distributed by different means, making it less coherent for a unified approach of any application update deliveries during development. It would also extend use cases for LiveBundle.
The technical question here, is that while it should be possible to achieve this via a separate application running on the phone (which would not be ideal though for UX), can we indeed keep it in LiveBundle inside the application itself.
The text was updated successfully, but these errors were encountered:
This one is a tad associated to #19
It might not be technically doable though, it's just an idea at this point and some technical research should be done.
But basically, what if LiveBundle could also serve full application binaries (apk/app).
Indeed, given that some application changes will contain native changes, that cannot be distributed in a JS bundle only, LiveBundle could in this case package the whole application binary, and still provide a QR Code / Deep Link. But in that case, instead of downloading/installing the bundle and hot reloading the application, it would instead reinstall the full binary (and application would have to be relaunched). Otherwise, such app binaries would have to be distributed by different means, making it less coherent for a unified approach of any application update deliveries during development. It would also extend use cases for LiveBundle.
The technical question here, is that while it should be possible to achieve this via a separate application running on the phone (which would not be ideal though for UX), can we indeed keep it in LiveBundle inside the application itself.
The text was updated successfully, but these errors were encountered: