4 ms·

Why would you want to have a version of your app? I think one of the coolest part is it works like a website but natively. If you wanted to version apps, I thi

Why would you want to have a version of your app? I think one of the coolest part is it works like a website but natively. If you wanted to version apps, I think you could version it at git level, or just think of it as an API deployment. No?

CJKinni 10y ago
I didn't ask the question, but had the same thought. Basically, what if the first time someone loads your app, they don't have a network connection? After the first load, it sounds like I can handle the issue with the cache, but I care a lot about a good experience the first time someone opens the app. Still, very cool!
- joelhaasnoot 10y ago
  This indeed: there are more cases than you think where someone downloads your app but has no internet connection when using it. And that could be the first time. Shipping a JSON file ensures the end user will always have something. That something could be as simple as a message "I'm loading data, internet connection is required".
- gliechtenstein 10y ago
  Currently, it is possible to set a data-uri as the root url (in a correct format https://en.wikipedia.org/wiki/Data_URI_scheme https://en.wikipedia.org/wiki/Data_URI_scheme) I think that's one way you could handle this situation. Or one could fork the code and change a couple of lines to make this work, technically it would be just a couple of lines of code, but I think policy-wise it needs to be thought out. Please follow the project and feel free to start an issue thread, we can discuss further! :)
shakna 10y ago
Versioning means you can use Continuous Deployment easier. Once all the tests pass for your new feature, it gets shipped, but not before.
- gliechtenstein 10y ago
  Yup that's what I meant by API versioning. Instead of having to deploy the physical app to the appstore, you are deploying your API, since basically you're building your native app on the server.

CJKinni 10y ago

I didn't ask the question, but had the same thought. Basically, what if the first time someone loads your app, they don't have a network connection? After the first load, it sounds like I can handle the issue with the cache, but I care a lot about a good experience the first time someone opens the app. Still, very cool!

joelhaasnoot 10y ago
This indeed: there are more cases than you think where someone downloads your app but has no internet connection when using it. And that could be the first time. Shipping a JSON file ensures the end user will always have something. That something could be as simple as a message "I'm loading data, internet connection is required".
gliechtenstein 10y ago
Currently, it is possible to set a data-uri as the root url (in a correct format https://en.wikipedia.org/wiki/Data_URI_scheme https://en.wikipedia.org/wiki/Data_URI_scheme) I think that's one way you could handle this situation. Or one could fork the code and change a couple of lines to make this work, technically it would be just a couple of lines of code, but I think policy-wise it needs to be thought out. Please follow the project and feel free to start an issue thread, we can discuss further! :)

shakna 10y ago

Versioning means you can use Continuous Deployment easier. Once all the tests pass for your new feature, it gets shipped, but not before.

gliechtenstein 10y ago
Yup that's what I meant by API versioning. Instead of having to deploy the physical app to the appstore, you are deploying your API, since basically you're building your native app on the server.