8 comments

[ 3.6 ms ] story [ 20.2 ms ] thread
This approach makes a lot of sense. I tried something similar with an iOS app and was surprised to find that Apple frowns upon this practice. They'd prefer that developers do usability testing beforehand instead of native A/B testing in the wild. Does anyone know if Apple has clarified this position?

It would be much more developer friendly to encourage this and would ultimately lead to better experiences for users.

Can you elaborate? Your app got rejected?
We were just encouraged to take a different approach. Not rejected. That's why I'm curious to see if others have had a different experience if they've been up front about what they're doing.
(comment deleted)
Apple does not want beta products in the app store, which makes sense. But I've not seen an outright ban on testing. Testing allows us to make the app better! In any case, we've not been rejected.
Brilliant! Can I ask how long this methodology took to implement?
Glad you like it. We got the testing/config system working in a day. Of course, we've spent time tweaking and adding features since