4 ms·
Thanks for the great feedback. That's something we can definitely give more priority to. I actually had an iOS library version that would poll infrequently in
by jeremyis 6y ago
Thanks for the great feedback.
That's something we can definitely give more priority to.
I actually had an iOS library version that would poll infrequently in a background thread and had a synchronous API. Something like:
Configly.init(API_KEY, { values: [keyOne, keyTwo]})
// (other code runs)
print(configly.shared().get('keyOne')) // would be cached by the background thread
but was slightly concerned about unwanted bandwidth/battery usage for mobile users but perhaps that mode would be useful exactly for the situation you describe.
- kall 6y agoI think if battery/data even becomes a concern, you have already put too much data into config and probably need a database? Does anyone really care about a couple hundred KB (at most) these days? Or am I underestimating the config size/usage?