I'm wondering why Dndbeyond decided to built the player app as a native Android app instead of using a framework like Cordova (https://cordova.apache.org/).
Since the website works perfectly putting it into a mobile chrome browser and maybe adding a service worker to cache some data for offline use would have delivered all features of the website while still using the same code, so any new feature added to the website would've been available in the app as well.
This is not meant to be criticism, I am just curious what the reason behind this decision was. :-)
iOS has a feature that behaves similarly (I think) to what you’re describing. I was curious on this point as well. Basically it would keep all the features of the web version while removing the browser chrome and be able to save/store data between sessions.
Every technology has its pros and cons. We have very ambitious plans for the app and in terms of scalability, native is the best choice. It may come at a slightly bigger effort but at the same time it allows us to utilise what's best on both platforms.
I'm wondering why Dndbeyond decided to built the player app as a native Android app instead of using a framework like Cordova (https://cordova.apache.org/).
Since the website works perfectly putting it into a mobile chrome browser and maybe adding a service worker to cache some data for offline use would have delivered all features of the website while still using the same code, so any new feature added to the website would've been available in the app as well.
This is not meant to be criticism, I am just curious what the reason behind this decision was. :-)
iOS has a feature that behaves similarly (I think) to what you’re describing. I was curious on this point as well. Basically it would keep all the features of the web version while removing the browser chrome and be able to save/store data between sessions.
-
View User Profile
-
View Posts
-
Send Message
D&D Beyond StaffEvery technology has its pros and cons. We have very ambitious plans for the app and in terms of scalability, native is the best choice. It may come at a slightly bigger effort but at the same time it allows us to utilise what's best on both platforms.
Thank you for your reply. :-)