Is it necessary to set the `elementKey` property of views beforehand?
Show HN: Taplytics – Mobile A/B testing you'll actually use
21–25 of 25 posts
Re: Show HN: Taplytics – Mobile A/B testing you'll actually use
#22Is it necessary to set the `elementKey` property of views beforehand?
No, currently you don't need to set the 'elementKey'. It provided transitional functionality for some of our early beta testers and is no longer necessary.
Re: Show HN: Taplytics – Mobile A/B testing you'll actually use
#23From the demo's it looks like you are doing overlays and test if these before better than the original.
I hardly need this. Usually it's more about flows, full screens etc.
Can you do eg alternate user flows?
best wishes Andreas
Re: Show HN: Taplytics – Mobile A/B testing you'll actually use
#24Just played with it a little bit. It's really cool. Do you have the same for android as well ? Or are you planning to launch anytime soon ?
Re: Show HN: Taplytics – Mobile A/B testing you'll actually use
#25Is it necessary to set the `elementKey` property of views beforehand?
No, currently you don't need to set the 'elementKey'. It provided transitional functionality for some of our early beta testers and is no longer necessary.
Oh that's great! You may want to remove that from your sample app—it gave me the impression that I'd need to set that everywhere.