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.